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

Add explanation as to if and when it is acceptable to bundle Patient Resources in ITI-65 #89

Closed
simoneOnFhir opened this issue Sep 15, 2021 · 2 comments
Assignees

Comments

@simoneOnFhir
Copy link

The MHD Spec is unclear as to whether Submitting DocumentReferences with bundles Patients is allowed.

There is an example showing this, but the verbage is a bit unclear:
"Patient would typically only be allowed by the Document Recipient in PUSH interaction situations, but may be accepted for other reasons at the discretion of the Document Recipient actor policy."
https://profiles.ihe.net/ITI/MHD/ITI-65.html#23654121-bundle-resources

Apparently this refers to "Bundled Patients" but the sentence above is very ambiguous.
Also it is not clear, what constitutes a "PUSH interaction situation" and whether this is within the scope of ITI-65 or not.

see Zulip discussion: https://chat.fhir.org/#narrow/stream/179223-ihe/topic/MHD.20bundled.20vs.2E.20contained.20Patient

@JohnMoehrke
Copy link
Contributor

Agree wit the need. I welcome recommended text changes to make these points more clear.

@JohnMoehrke JohnMoehrke added Discussion Committee Discussion needed documentation Improvements or additions to documentation labels Sep 15, 2021
@JohnMoehrke JohnMoehrke added MHD-Improvements and removed documentation Improvements or additions to documentation Discussion Committee Discussion needed labels Feb 17, 2022
@JohnMoehrke
Copy link
Contributor

do we need to allow for subject.identifier and not subject.reference? such as for regions with a national identifier?

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

No branches or pull requests

2 participants