Difference between revisions of "Basic Patient Privacy Consents"

From IHE Wiki
Jump to navigation Jump to search
 
 
(69 intermediate revisions by 6 users not shown)
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.''
+
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).
 
 
''<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__
 
__TOC__
  
 
+
==[https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Formal Specification]==
==Summary==
+
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html Final Text]
 
 
''<Describe the profile in about a paragraph>''
 
 
 
''<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==
 
 
 
 
 
==Details==
 
 
 
''<Detailed discussion of what the profile does and how it works>''
 
 
 
==Systems Affected==
 
''<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''
 
 
 
==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| Final Text]] ''<Replace Final Text with Trial Implementation or Public Comment as appropriate.>''
 
 
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 [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.
 
 
The [[Profile Implementation Template]] 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]]
  
 +
[[Category:Profiles]]
 +
[[Category:ITI Profile]]
 +
[[Category:DocShare]]
 +
[[Category:Security]]
 +
[[Category:CDA]]
  
''<Delete this Category Templates line since your Profile page is no longer a template.>'' [[Category:Templates]]
+
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
 
 
[[Category:Profiles]]
 

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.