Difference between revisions of "Basic Patient Privacy Consents"

From IHE Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
''This is a template page.  Click edit, Do Not Save This Page, Copy the current text then go edit your page and paste it in.''
+
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.
 
+
__NOTOC__
''<Your page name should simply be Full Profile Name Profile with spaces, with capitals, without the acronym. e.g. Scheduled Workflow Profile>''
 
 
 
''<Tell a user in one sentence what the profile is about so they can decide if they're on the right page (and copy this text into the [[Profiles]] page as well), e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams. >''
 
 
 
''<If you are adding a Profile, you may also want to add a section to the [[:Category:Actors| pages for existing Actors]] or copy the [[Actor Template]] if creating a new Actor.>''
 
 
 
 
 
__TOC__
 
 
 
  
 
==Summary==
 
==Summary==
  
''<Describe the profile in about a paragraph>''
+
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:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on including an image/graphic.>''
 
''<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==
 
==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==
 
==Details==
  
Line 25: Line 23:
  
 
==Systems Affected==
 
==Systems Affected==
''<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''
+
* EHR System
  
 
==References==
 
==References==
Line 32: Line 30:
  
 
==See Also==
 
==See Also==
Profile Status: [[Comments| Final Text]] ''<Replace Final Text with Trial Implementation or Public Comment as appropriate.>''
+
Profile Status: [[Comments| Trial Implementation]]
 
 
The [[Frameworks#IHE Radiology Technical Framework| Radiology Technical Framework]] is the official master document for this Profile. ''<Replace Radiology Technical Framework with the Trial Implementation Supplement or Public Comment Supplement as appropriate.>''
 
 
 
''<Replace the Template links below with links to the actual pages for the Profile>''
 
  
The [[Profile FAQ Template]] answers typical questions about what the Profile does.
+
The [[Frameworks#IHE Patient Care Coordination Technical Framework| Patient Care Coordination Technical Framework]] is the official master document for this Profile.  
  
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.
+
The [[BPPC FAQ]] answers typical questions about what the Profile does.
  
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.
+
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]]
 
This page is based on the [[Profile Template]]
 
 
''<Delete this Category Templates line since your Profile page is no longer a template.>'' [[Category:Templates]]
 
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]

Revision as of 17:39, 27 November 2006

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:

  1. Record the patient privacy consent(s),
  2. Mark documents published to XDS with the patient privacy consent that was used to authorize the publication,
  3. 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

<Detailed discussion of what the profile does and how it works>

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

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