This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR Consent Directive Use Cases"

From HL7Wiki
Jump to navigation Jump to search
Line 5: Line 5:
 
==Purpose==
 
==Purpose==
 
Record FHIR Consent Directive Use Cases
 
Record FHIR Consent Directive Use Cases
 +
 +
==USE CASE INDEX==
 +
Please add links to additional use case pages here, e.g., State HIE Consent Directive use cases where current local electronic or paper forms are candidates for FHIR Consent Directive instances
 +
 +
==Basic "Simple" Consent Directive Use Cases from Current FHIR Change Proposal==
  
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6285 [#6285] Summary: Proposal for ConsentDirective stepping stones]
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6285 [#6285] Summary: Proposal for ConsentDirective stepping stones]

Revision as of 22:40, 28 October 2015

Back to CBCC Wiki: Meetings

Back to HL7 FHIR Consent Directive Project

Purpose

Record FHIR Consent Directive Use Cases

USE CASE INDEX

Please add links to additional use case pages here, e.g., State HIE Consent Directive use cases where current local electronic or paper forms are candidates for FHIR Consent Directive instances

Basic "Simple" Consent Directive Use Cases from Current FHIR Change Proposal

  • [#6285 Summary: Proposal for ConsentDirective stepping stones]

Might I suggest that the ConsentDirective project include a "Basic-ConsentDirective" that supports blanket consents without exceptions. Essentially the common HIE policies from BPPC. These would be scoped to sharing beyond the original organization and purpose for which the health information was created. This form of a Consent Directive would need only (identifier, issued, applies, subject, authority, domain, type=consent, subtype=<some vocabulary>, and possibly friendly and legal). This Basic Consent Directive would support the following HIE subtypes:

1) Opt-In -- Agree to publish "All" healthcare information. Agree to Use and Disclosure to "any" authorized individual of a "Treatment" or "Payment" organization "For the Purpose" of "Treatment" or "Payment". No Redisclosure allowed without further authorization. This agreement does not authorize other accesses.

2) Opt-Out allowing break-glass -- Agree to publish "All" healthcare information. Agree to Use and Disclosure to "any" authorized individual of a Treatment organization for specifically "Emergency Treatment" PurpoeOfUse, and Payment of those treatment. This agreement does not authorize other accesses.

3) Opt-In summary access only -- Agree to publish "All" healthcare information. Agree to Use and Disclosure to "any" authorized individual of a "Treatment" or "Payment" organization "For the Purpose" of "Treatment" or "Payment"; to only the medications and allergies summary. No Redisclosure allowed without further authorization. This agreement does not authorize other accesses.

4) Opt-In break-glass summary access only -- Agree to publish "All" healthcare information. Agree to Use and Disclosure to "any" authorized individual of a "Treatment" organization "For the Purpose" of "Emergency Treatment" and Payment of those treatment; to only the medications and allergies summary. No Redisclosure allowed without further authorization. This agreement does not authorize other accesses.

5) Opt-Out no break-glass -- Agree to publish "All" healthcare information. This agreement does not authorize any accesses.

6) Opt-Out completely -- Agree to publish "No" healthcare information beyond originating organization intended use.

From <http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6285>