Difference between revisions of "Basic Patient Privacy Consents"
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| Line 1: | Line 1: | ||
The ''Basic Patient Privacy Consents'' (BPPC) profile provides a mechanism to record the patient privacy consent(s), a method to mark documents published to XDS with the patient privacy consent that was used to authorize the publication, and a method for XDS Consumers to use to enforce the privacy consent appropriate to the use. | The ''Basic Patient Privacy Consents'' (BPPC) profile provides a mechanism to record the patient privacy consent(s), a method to mark documents published to XDS with the patient privacy consent that was used to authorize the publication, and a method for XDS Consumers to use to enforce the privacy consent appropriate to the use. | ||
| − | + | ||
==Summary== | ==Summary== | ||
Revision as of 10:06, 10 April 2007
The Basic Patient Privacy Consents (BPPC) profile provides a mechanism to record the patient privacy consent(s), a method to mark documents published to XDS with the patient privacy consent that was used to authorize the publication, and a method for XDS Consumers to use to enforce the privacy consent appropriate to the use.
Summary
The Basic Patient Privacy Consents (BPPC) profile provide mechanisms to:
- Record the patient privacy consent(s),
- Mark documents published to XDS with the patient privacy consent that was used to authorize the publication,
- Enforce the privacy consent appropriate to the use.
<Include a simple graphic that, at a glance, gives an impression of what the profile does. See Help - Tips and Tricks for details on including an image/graphic.>
Benefits
An Affinity Domain can
- develop privacy policies,
- and implement them with role-based or other access control mechanisms supported by EHR systems.
A patient can
- Be made aware of an institutions privacy policies.
- Have an opportunity to selectively control access to their healthcare information.
Details
Systems Affected
All systems publishing or using XDS. Also may apply to XDR and XDP.
- EHR System
- PACS System
- EMR System
- Cardiology
- etc...
References
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >
Middle East Technical University, Turkey
See Implementation Experiences On IHE XUA and BPPC December 5, 2006; Tuncay Namlı and Asuman Dogac, Software Research and Development Center, Middle East Technical University, Ankara, Turkey
Also at http://www.srdc.metu.edu.tr/publications
See Also
Profile Status: Trial Implementation
The Patient Care Coordination Technical Framework is the official master document for this Profile.
The BPPC FAQ answers typical questions about what the Profile does.
The BPPC Purchasing describes considerations when purchasing equipment to deploy this Profile.
The BPPC Implementation provides additional information about implementing this Profile in software.
This page is based on the Profile Template