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

Extension for Reference to Practitioner as Validator of Immunization entry (Roeland Luykx, RALY GmbH) #87

Closed
ralych opened this issue Sep 23, 2021 · 4 comments
Labels

Comments

@ralych
Copy link
Collaborator

ralych commented Sep 23, 2021

No description provided.

@ralych ralych changed the title Extension for Validator of Immunization entry Extension for Reference to Practitioner as Validator of Immunization entry (Roeland Luykx, RALY GmbH) Sep 30, 2021
@ralych ralych added the enhancement New feature or request label Sep 30, 2021
@ralych
Copy link
Collaborator Author

ralych commented Nov 16, 2021

Will be resolved not via extension but by change of author.
Author == Patient means not validated
Author == Practitioner means validated

This will be done by a ImmunizationAdministration Document with "replaces" relation to the source document where a patient added the Immunization entry (Patient as Author)

--> Comment this in the profile and description page in IG

@ralych ralych added review-fix Review the fix of the issue and removed work-in-progress labels Dec 22, 2021
@eHealth-Suisse
Copy link
Collaborator

I agree with the text written, but why then is there still an extension on the IG? http://build.fhir.org/ig/ehealthsuisse/ch-vacd/StructureDefinition-ch-vacd-ext-immunization-recorder-reference.html should be done via XDS metadata

@eHealth-Suisse eHealth-Suisse removed the review-fix Review the fix of the issue label Jan 13, 2022
@ralych
Copy link
Collaborator Author

ralych commented Jan 14, 2022

There is no author nor recorder reference property in the immunization resource. this is the reason for the extension.
and no via XDS metadata should this not be done. it belongs to the FHIR resource independent of the storage procedures and ERP context.

@eHealth-Suisse
Copy link
Collaborator

discussion 14.1.: ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants