Difference between revisions of "Basic Patient Privacy Consents"

From IHE Wiki
Jump to navigation Jump to search
 
(66 intermediate revisions by 5 users not shown)
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.
+
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).
−
__NOTOC__
 
  
−
==Summary==
+
__TOC__
  
−
The Basic Patient Privacy Consents (BPPC) profile provide mechanisms to:
+
==[https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Formal Specification]==
−
# Record the patient privacy consent(s),
+
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Final Text]
−
# 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:Contents#Tips_.26_Tricks| 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==
 
−
* EHR System
 
−
 
 
−
==References==
 
−
 
 
−
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >''
 
  
 
==See Also==
 
==See Also==
−
Profile Status: [[Comments| Trial Implementation]]
 
  
−
The [[Frameworks#IHE Patient Care Coordination Technical Framework| Patient Care Coordination Technical Framework]] is the official master document for this Profile.
+
This page is based on the [[Profile Template]]
  
−
The [[BPPC FAQ]] answers typical questions about what the Profile does.
+
[[Category:Profiles]]
−
 
+
[[Category:ITI Profile]]
−
The [[BPPC Purchasing]] describes considerations when purchasing equipment to deploy this Profile.
+
[[Category:DocShare]]
−
 
+
[[Category:Security]]
−
The [[BPPC Implementation]] provides additional information about implementing this Profile in software.
+
[[Category:CDA]]
−
 
 
−
This page is based on the [[Profile Template]]
 
  
−
[[Category:Profiles]][[Category:Patient Care Coordination]]
+
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].

Latest revision as of 11:48, 19 November 2021

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

See Also

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.

Retrieved from "http://wiki.ihe.net/index.php?title=Basic_Patient_Privacy_Consents&oldid=126808"