Difference between revisions of "Basic Patient Privacy Consents"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
Line 1: | Line 1: | ||
'''Basic Patient Privacy Consents (BPPC)''' provides a mechanism to record the patient privacy consent(s) and a method for Content Consumers to use to enforce the privacy consent appropriate to the use. This profile complements XDS by describing a mechanism whereby an XDS Affinity Domain can develop and implement multiple privacy policies, and describes how that mechanism can be integrated with the access control mechanisms supported by the XDS Actors (e.g. EHR systems). | '''Basic Patient Privacy Consents (BPPC)''' provides a mechanism to record the patient privacy consent(s) and a method for Content Consumers to use to enforce the privacy consent appropriate to the use. This profile complements XDS by describing a mechanism whereby an XDS Affinity Domain can develop and implement multiple privacy policies, and describes how that mechanism can be integrated with the access control mechanisms supported by the XDS Actors (e.g. EHR systems). | ||
− | ==[https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Formal Specification]== | + | __TOC__ |
+ | |||
+ | ==Formal Specification== | ||
+ | |||
+ | ===[https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Formal Specification]=== | ||
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Final Text] | * [https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Final Text] | ||
Revision as of 11:46, 19 November 2021
Basic Patient Privacy Consents (BPPC) provides a mechanism to record the patient privacy consent(s) and a method for Content Consumers to use to enforce the privacy consent appropriate to the use. This profile complements XDS by describing a mechanism whereby an XDS Affinity Domain can develop and implement multiple privacy policies, and describes how that mechanism can be integrated with the access control mechanisms supported by the XDS Actors (e.g. EHR systems).
Formal Specification
Formal Specification
See Also
This page is based on the Profile Template
Current: IT Infrastructure Technical Framework.