|
|
| (6 intermediate revisions by the same user not shown) |
| Line 8: |
Line 8: |
| | ==USE CASE INDEX== | | ==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 | | 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 |
| | + | |
| | + | *[TBD - John's exemplar instance for others to use to create FHIR CD instances goes here] |
| | + | |
| | + | [[SSA to VA Patient Authorization]] |
| | | | |
| | [[FHIR Consent Directive Use Case Examples by Tarik Idris]] | | [[FHIR Consent Directive Use Case Examples by Tarik Idris]] |
| Line 15: |
Line 19: |
| | [[Canadian Real World Consent Directive Scenarios by Pat Pyette]] | | [[Canadian Real World Consent Directive Scenarios by Pat Pyette]] |
| | | | |
| − | [[Austrian Medicare FHIR Consent Directive Use Case and xml examples by Russell McDonald]] | + | [[Australian Medicare FHIR Consent Directive Use Case and xml examples by Russell McDonald]] |
| − | | |
| − | ==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]
| |
| − | | |
| − | 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>
| |
| − | | |
| − | *[http://gforge.hl7.org/gf/download/docmanfileversion/8881/13439/Simple%20FHIR%20BPPC%20Consent%20Directive.xlsx Simple FHIR Privacy Consent Directive examples using [http://gforge.hl7.org/gf/download/docmanfileversion/8881/13439/Simple%20FHIR%20BPPC%20Consent%20Directive.xlsx DSTU 1 FHIR Consent Directive]
| |
| − | | |
| − | ==Real World Consent Directive Scenarios==
| |
| − | The following scenarios are based on existing jurisdictional policy and are realized in existing systems in Canada. The default policy is one of implied consent for the provision of care, so these scenarios all deal with withdrawal or withholding consent for that purpose. In other jurisdictions, where an express consent model is used (Opt-In), these would be express consent rather than withdrawal.
| |
| − | | |
| − | 1) Withhold or withdraw consent for disclosure of records related to specific domain (e.g. DI, LAB, etc.)
| |
| | | | |
| − | 2) Withhold or withdraw consent for disclosure of a specific record (e.g. Lab Order/Result)
| + | [[Data Segmentation for Privacy Pilot Use Cases]] |
| | | | |
| − | 3) Withhold or withdraw consent for disclosure to a specific provider organization
| + | [[HIMSS Privacy Demonstrations with ONC and VA]] |
| | | | |
| − | 4) Withhold or withdraw consent for disclosure to a specific provider agent (an individual within an organization)
| + | [[HITSP Transaction Package 30 Use Cases]] |
| | | | |
| − | 5) Withhold or withdraw consent for disclosure of records that were authored by a specific organization (or service delivery location).
| + | [[HL7 v.3 Consent Directive Use Cases]] |
| | | | |
| − | 6) Combinations of the above, such as withhold or withdraw consent to disclose all of my Labs to every organization except for Good Health Clinic and Sunny Ways Hospital, and then only allow disclosure of records 1234 and 4567.
| + | [[HL7 v.2 Consent Directive Use Cases]] |
