Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

finish operation #53

Closed
bdc-ehealth opened this issue Feb 23, 2022 · 8 comments
Closed

finish operation #53

bdc-ehealth opened this issue Feb 23, 2022 · 8 comments

Comments

@bdc-ehealth
Copy link
Collaborator

@SmalsJulien

can you add a functional description of this operation?

@SmalsJulien
Copy link
Collaborator

This operation allows a caregiver to notify UHMEP that he has finished the treatment of a prescription.

@bdc-ehealth
Copy link
Collaborator Author

Is this a part of the eHealth standard?

@costateixeira
Copy link
Contributor

If i understand correctly, I think this should not be part of the ReferralPrescription standard. It may be a standard operation, but it would be more generic, also applicable to other requests.

@Mcobbaert
Copy link

Mcobbaert commented Mar 29, 2022

finish operation is an action that should not be part of referral prescription.
Based on information of clinical status of the referral prescription the "finish operation" action can take place

@bdc-ehealth
Copy link
Collaborator Author

@costateixeira from your comment, I understand that "finish" is a more generic action that is executed via a FHIR operation, and this operation should be described in an IG guide. Correct? My question: if it is a generic operation (not on instance level, not on resource level, but on system level) how would you describe the semantics of this operation? What would be the types of its parameters? (https://hl7.org/fhir/R4/operations.html)

@bdc-ehealth bdc-ehealth added this to Inbox in Development issues via automation Jun 9, 2022
@SmalsJulien
Copy link
Collaborator

@bdc-ehealth Do you have some information about the description in the fhir specification of this operation please ?

@bdc-ehealth
Copy link
Collaborator Author

bdc-ehealth commented Jan 19, 2023

WG: the back-end would like to describe this in the form of FHIR resources. We should confirm if the GP/Nurse implementors also see this benefit (@hansdekeersmaecker)

@SmalsJulien
Copy link
Collaborator

To be more FHIR compliant, we try to minimize the use of operations. For the finish operation, we use now the FHIR PATCH method.

Development issues automation moved this from Inbox to Done Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants