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

BeReferralPrescription - Put "replaces" field in "Must support" #51

Closed
SmalsJulien opened this issue Feb 23, 2022 · 3 comments
Closed

Comments

@SmalsJulien
Copy link
Collaborator

SmalsJulien commented Feb 23, 2022

When a prescription is created based on an expired prescription, UHMEP will use this field in the new prescription to give the reference of the expired prescription.

@SmalsJulien SmalsJulien changed the title ServiceRequest - Put "replaces" field in "Must support" BeReferralPrescription - Put "replaces" field in "Must support" Feb 23, 2022
@Mcobbaert
Copy link

This functionality needs to be described in the business rules document - cookbook. Is not part of Fhir.
We use "based on" instead of "replaces" already included in the "must support".

@bdc-ehealth
Copy link
Collaborator

@Mcobbaert @annenerenhausen , I think @SmalsJulien is right. From a semantic interoperability view, the reference to the expired request should be in the ServiceRequest.replaces (https://hl7.org/fhir/R4/servicerequest-definitions.html#ServiceRequest.replaces).

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

WG: solved in #47

Development issues automation moved this from Inbox to Done Jan 19, 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