HL7 FHIR Consent Directive Project

Back to CBCC Wiki: Meetings

This work is authorized under project 1130 HL7 Patient Friendly Consent Directive Project

HL7 FHIR Consent Directive Project

Weekly Meeting Logistics

Weekly meeting; Fridays 2:00 - 3:00 PM Eastern Time

Dial-in Number: (515) 604-9861

International Dial-in Numbers are provided

Access Code: 429554

Online Meeting Link: http://join.freeconferencecall.com/cbhs

Call Agenda, Attendance, and Call Notes

• FHIR Consent Mar 30, 2017
• FHIR Consent Mar 24, 2017
• FHIR Consent Mar 17, 2017
• FHIR Consent Mar 10, 2017
• FHIR Consent Mar 3, 2017

Pre-STU3 Meetings

Pre-STU2 Meetings

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.

working space

FHIR Consent Directive Implementation Guide

Current Open/Deferred FHIR CPs

• Security Label based (Group A in GForge)
  • 10706 Consent - Obligations (John Moehrke) Considered for Future Use
  • 10707 Consent securityLabel (John Moehrke) Considered for Future Use
  • 10711 Consent.except.purpose - unclear if this is user context, obligation, or data tag (John Moehrke) Considered for Future Use
  • 11055 Remove Consent.except.purpose - 2016-09 core #74 (Kathleen Connor) Considered for Future Use
  • 11056 Change definition of securityLabel - 2016-09 core #75 (Kathleen Connor) Considered for Future Use

• Other Deferred (Group B in GForge)
  • 10692 Grouped Consents (John Moehrke) Considered for Future Use
  • 11068 Issues w/ Consent status - 2016-09 core #87 (Kathleen Connor) Considered for Future Use
  • 11069 Consent resource lacks the ability to clearly differentiate different uses of consent content - 2016-09 core #88 (Kathleen Connor) Considered for Future Use

FHIR Consent Directive Artefacts

• Current Information for Discussion

THese have been provided by Mike Davis, Kathleen Connor and John Moehrke as illustrations for possible reasons for and against having multiple Purpose of Use elements on the FHIR Consent Resource.

• • File:Purpose of Use CBCC 1220 2016 JMD.pptx
  • File:POU De-Mystified.pdf
  • File:Consent-DAM-HCS-vectors-20170131.pptx
  • File:UK Handling Instructions Government Security Classification guidance.doc

• Historical Documents
  • FHIR Consent - Grahame's model
  • FHIR Consent Directive Use Cases
  • FHIR Consent Directive Library
  • Consent Directive Examples
  • FHIR Consent Directive Value Sets
• FHIR Consent Directive DSTU 1 Artifacts

Work breakdown

Now that STU3 has been released, the Consent Resource is posed to completely replace the Contract resource profile. The Consent to share is stable Three additional use cases are being studied: Research consent, Advance Directives and Treatment consent. Each of these are being pursued with the assistance of the relevant Domain Experts workgroups.

Work on the existing path, then expand to review consent for more than disclosure. 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)
• 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.