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

start operation #52

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

start operation #52

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

Comments

@bdc-ehealth
Copy link
Collaborator

@SmalsJulien

can you add a description of the functionality of this operation?

@SmalsJulien
Copy link
Collaborator

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

@bdc-ehealth
Copy link
Collaborator Author

Is this a part of the eHealth standard?

@Mcobbaert
Copy link

"start operation" activity is not part of referral prescription standard
Based on "status" of referral prescription the "start operation" activity can take place

@bdc-ehealth
Copy link
Collaborator Author

@Mcobbaert @annenerenhausen , if this involves interaction with a server that follows the FHIR specifications, this should be part of a FHIR implementation guide, because a FHIR implementation guide describes how to interact with a FHIR server.

@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 ?

Additional information :
This operation can have a parameter. If it is the case, it means that the caregiver notifies UHMEP that he started the prescription in the past. The parameter will be the executionStartDate.

image

@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 start 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

3 participants