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 66: | Line 66: | ||
* Start effort on developing this effort as an Implementation Guide (IG) | * Start effort on developing this effort as an Implementation Guide (IG) | ||
* Have many profiles within the IG | * Have many profiles within the IG | ||
− | ** Simple acknowledgement without deviations... | + | ** Simple acknowledgement without deviations... Equivalent to BPPC |
+ | *** Opt-In, Opt-Out, Opt-Out-fully, etc | ||
** Consent with explicitly authorized individuals | ** Consent with explicitly authorized individuals | ||
+ | *** organization or individual or service delivery location | ||
** Consent with explicitly identified types of objects to exclude | ** 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 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) | ||
* Explain how Consent is related to a Questionnaire presented to a patient | * Explain how Consent is related to a Questionnaire presented to a patient | ||
* Produce a set of Consent logical Principles | * Produce a set of Consent logical Principles |
Revision as of 23:57, 4 November 2015
[Back to HL7 Patient Friendly Language Consent Directive Project]
Contents
Weekly meeting
Wednesdays 6:00 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
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.
Current Open FHIR CPs
November 4, 2015
- 5524 Consent shouldn't be a sub-type of Contract (Lloyd McKenzie) Considered for Future Use
- 5525 Consent Directive does not appear to be aligned with the 80% (Lloyd McKenzie) Considered for Future Use
- 6285 Proposal for ConsentDirective stepping stones (John Moehrke) Considered for Future Use
- 6861 2015May sdc #78 - What is subject? (James Kretz) Considered for Future Use
- 6864 2015May sdc #81 - Only one mandatory element in consent directive (James Kretz) Considered for Future Use
- 6865 2015May sdc #82 - Bundle with consent + request? (James Kretz) Considered for Future Use
- 7252 2015May core #361 - ConsentDirective appears US-specific (Lloyd McKenzie) None
- 7253 2015May core #362 - ConsentDirective violates DSTU 2 rules (Lloyd McKenzie) None
- 7531 2015May core #822 - ConsentDirective ballot status (Grahame Grieve) None
- 7532 2015May core #823 - ConsentDirective documentation (Grahame Grieve) None
- 7533 2015May core #824 - ConsentDirective as a profile (Grahame Grieve) None
- 7871 2015May core #1191 - Where is consent status, advance directive details? Contract resource is inappropriate (Michelle Miller) None
- 5905 Contract.binding is the same as the intent of Consent.legal (John Moehrke) Not Related
- 5906 Contract.signer needs to be clarified (John Moehrke) Not Related
- 5907 Contract.action is not defined (John Moehrke) Not Related
- 6137 Consent has no examples (Lloyd McKenzie) Not Related
- 6284 ConsentDirective vs Contract (John Moehrke) Not Related
- 7691 2015May core #982 - Is "subject" supposed to identify the data covered by the consent? (Ioana Singureanu) Not Related
- 7752 2015May core #1073 - Replace value set with FHIR Signer Type value set (Kathleen Connor) Not Related
- 7770 2015May core #1091 - Rename Contract - Consent is not a Contract (Keith Boone) Not Related
- 7771 2015May core #1092 - Does electronic exchange of contracts fit in the 80%? (Keith Boone) Not Related
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
- VA Online Consent Directive prototype
- Gforge Folder - Consent Directive Examples and state and HIE consent directive policy analysis and governance schemes
- Florida Share All Consent Directive
- Florida Share Partial Consent Directive
- XACML and GUI for 42 CFR samples
- OCR Notice of Privacy Practices - with Patient Friendly templates and good example for FHIR Consent Directive Questionnaire instance
- ONC Personal Health Record (PHR) Model Privacy Notice - with Patient Friendly templates and good example for FHIR Consent Directive Questionnaire instance
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.
- ???