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

MP: references to HealthcareProvider-Organization justified? #267

Open
jd-nictiz opened this issue Apr 13, 2022 · 1 comment
Open

MP: references to HealthcareProvider-Organization justified? #267

jd-nictiz opened this issue Apr 13, 2022 · 1 comment
Assignees

Comments

@jd-nictiz
Copy link
Contributor

jd-nictiz commented Apr 13, 2022

Within the MP profiles, several references to HealthcareProvider-Organization exist, where we decided HealthcareProvider (the Location resource variant) is 'focal'. It should be checked 1. whether the references to the Organization variant are justified and 2. if so, a comment should be added.

zib-DispenseRequest -> IntendedSupplier - Is at Organization-level
zib-AdministrationAgreement and zib-MedicationDispense -> The Supplier is not captured at HealthProfessional level (because Pharmacies do not record individuals), but at HealthcareProvider level as an alternative. Therefore Organization is sufficient. However, if available it seems a good idea to capture the Location in .location, leading to a double mapping.

@jd-nictiz
Copy link
Contributor Author

nl-core: MedicationUse2.Author.

This mapping to HealthcareProvider is used for 'automatically generated' messages, so for 'provenance' reasons. It seems a good idea to capture the information at the highest level, leading to a reference to the Location resource.

jd-nictiz added a commit that referenced this issue Apr 13, 2022
…n MedicationDispense.location with extra guidance
jd-nictiz added a commit that referenced this issue Apr 13, 2022
jd-nictiz added a commit that referenced this issue Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant