This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 FHIR Consent Directive Project"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| Line 2: | Line 2: | ||
[[CBCC|Back to CBCC Wiki: Meetings]] | [[CBCC|Back to CBCC Wiki: Meetings]] | ||
| − | This work is authorized under project 1130 [[HL7 Patient Friendly | + | This work is authorized under project 1130 [[HL7 Patient Friendly Consent Directive Project]] |
[[HL7 FHIR Consent Directive Project]] | [[HL7 FHIR Consent Directive Project]] | ||
Revision as of 16:09, 12 February 2016
This work is authorized under project 1130 HL7 Patient Friendly Consent Directive Project
HL7 FHIR Consent Directive Project
Contents
New Weekly Meeting Logistics
Fridays 12:00 - 1:30 PM Eastern Time
- Phone: +1 770-657-9270, Participant Code: 994563
- Web meeting Info: https://global.gotomeeting.com/join/520841173
Call Agenda, Attendance, and Call Notes
- FHIR Consent February 12, 2016
- FHIR Consent February 5, 2016
- FHIR Consent January 29, 2016
- FHIR Consent December 30, 2015
- FHIR Consent December 23, 2015 is Cancelled
- FHIR Consent December 16, 2015
- FHIR Consent December 9, 2015
- FHIR Consent IG - December 4, 2015
- December 2, 2015
- November 18, 2015
- November 11, 2015
- November 4, 2015
- October 28, 2015
Purpose
To track the progress of the HL7 FHIR Consent Directive Project. Prior to 10/27/2015, some of this content was kept on the [HL7 Patient Friendly Language Consent Directive Project] page.
FHIR Consent Directive Implemenation Guide
Current Open FHIR CPs
FHIR Consent Directive Artifacts
- FHIR Consent Directive Use Cases
- FHIR Consent Directive Library
- Consent Directive Examples
- FHIR Consent Directive Value Sets
- FHIR Consent Directive DSTU 1 Artifacts
Consent Directive Examples
Work breakdown
Work on the existing path, thus deferring resolution of "Consent as a Resource" vs "Consent as a Profile on Contract". It is best to get progress, and this difference is holding progress. Once we make more progress we can resolve and adjust.
- Start effort on developing this effort as an Implementation Guide (IG)
- Have many profiles within the IG
- Simple acknowledgement without deviations... Equivalent to BPPC
- Opt-In, Opt-Out, Opt-Out-fully, etc
- Consent with explicitly authorized individuals
- organization or individual or service delivery location
- Consent with explicitly identified types of objects to exclude
- By clinical type of data
- By repository holding that data
- Consent with explicitly identified objects to exclude
- Consent with explicitly identified object and any other object related to that object (order number --> all results)(e.g. accession number)
- Consents with explicitly identified author to include/exclude
- Defining combination of terms within a single policy
- Defining combination of terms when they are individual policies (opt-out + opt-in-for-Bob != opt-in-for-Bob + opt-out)
- Simple acknowledgement without deviations... Equivalent to BPPC
- Explain how Consent is related to a Questionnaire presented to a patient
- Produce a set of Consent logical Principles
- e.g. when writing rules, you are only adding things into scope
- Explain how CDA-ConsentDirective can inform FHIR Consent.
- ???
