You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much like BPPC does for XDS community. This Implementation Guide (IG) would do for FHIR community. This IG could be used with MHDS, which already has some of the framework for more specific Consents, but BPPCm would be more complete than what is indicated in MHDS. This IG could also be used for organization use or community use beyond MHD/XDS, which would include use-cases like QEDm, and IPA. This would leverage BasicAudit to record access control decisions and recording of consents.
This IG would
Define a set of privacy policies with canonical URI and/or code.
Define a set of Consent patterns that are foundational.
Define actors for creation/update of Consent, Registry of Consents, Decision actor, and Enforcement actor.
should this be focused only on Privacy Consents? And not include Advanced Directives, Consent to a Treatment, and Consent to Participate in Research.
--> Privacy Consents only
Much like BPPC does for XDS community. This Implementation Guide (IG) would do for FHIR community. This IG could be used with MHDS, which already has some of the framework for more specific Consents, but BPPCm would be more complete than what is indicated in MHDS. This IG could also be used for organization use or community use beyond MHD/XDS, which would include use-cases like QEDm, and IPA. This would leverage BasicAudit to record access control decisions and recording of consents.
This IG would
See article - https://healthcaresecprivacy.blogspot.com/2022/05/explaining-fhir-consent-examples.html
The text was updated successfully, but these errors were encountered: