This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ConsentDirective FHIR Resource Proposal"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
JohnMoehrke (talk | contribs) |
||
(8 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
− | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
− | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
Line 13: | Line 12: | ||
− | = | + | =ConsentDirective= |
+ | |||
+ | |||
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
Line 30: | Line 31: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
− | [[ | + | [[Community-Based Collaborative Care]] |
+ | |||
+ | Within scope of: [http://gforge.hl7.org/gf/download/docmanfileversion/8234/12028/Project_Scope_Statement_Patient-friendly%20Security%20and%20Privacy%20language%20v%203.4.docx - Patient Friendly/Natural Language for Security and Privacy for Consent Directive Project] | ||
+ | |||
+ | Approved during the [http://gforge.hl7.org/gf/download/docmanfileversion/8234/12028/Project_Scope_Statement_Patient-friendly%20Security%20and%20Privacy%20language%20v%203.4.docx May 27, 2014 CBCC Conference Call] | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
− | + | [[Security]] | |
− | |||
− | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
+ | pending | ||
==Scope of coverage== | ==Scope of coverage== | ||
Line 55: | Line 59: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
+ | Captures a DocumentRoot specific Consent Directory. | ||
==RIM scope== | ==RIM scope== | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
+ | ConsentDirective | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
Line 74: | Line 80: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
+ | Recording and providing access to documentation of a Privacy Consent Directive. | ||
+ | |||
+ | Related to the document form of Privacy Consent Directive | ||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
+ | Health Information Exchanges that manage Privacy Consent Directives | ||
==Content sources== | ==Content sources== | ||
Line 84: | Line 94: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
+ | HL7 Consent Directive | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
+ | |||
+ | Recording that a patient privacy consent directive has been obtained. | ||
+ | |||
+ | Looking up for use or display the current consent directives on file. | ||
==Resource Relationships== | ==Resource Relationships== | ||
Line 99: | Line 114: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
+ | Historic work done as a Profile on the [[Contract FHIR Resource Proposal]] | ||
==Timelines== | ==Timelines== |
Latest revision as of 15:11, 27 February 2017
Contents
- 1 ConsentDirective
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
ConsentDirective
Owning committee name
Community-Based Collaborative Care
Within scope of: - Patient Friendly/Natural Language for Security and Privacy for Consent Directive Project
Approved during the May 27, 2014 CBCC Conference Call
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
pending
Scope of coverage
Captures a DocumentRoot specific Consent Directory.
RIM scope
ConsentDirective
Resource appropriateness
Recording and providing access to documentation of a Privacy Consent Directive.
Related to the document form of Privacy Consent Directive
Expected implementations
Health Information Exchanges that manage Privacy Consent Directives
Content sources
HL7 Consent Directive
Example Scenarios
Recording that a patient privacy consent directive has been obtained.
Looking up for use or display the current consent directives on file.
Resource Relationships
Historic work done as a Profile on the Contract FHIR Resource Proposal