FHIR Consent August 4, 2017

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

Back to FHIR Consent Directive Project Main Page

Attendees

	Member Name		x	Member Name		x	Member Name		x	Member Name
X	David Pyke CBCC co-Chair		.	Johnathan Coleman CBCC Co-Chair		.	Suzanne Gonzales-Webb CBCC Co-Chair		.	Grahame Grieve FHIR Director
.	Alexander Mense Security Co-Chair		X	Kathleen Connor Security Co-Chair		X	John MoehrkeSecurity Co-Chair		.	Jim Kretz CBCC Co-Chair
.	Paul Knapp		X	David Staggs		.	Ken Salyards		.	Diana Proud-Madruga
.	Mike Davis		.	Neelima Chennamaraja		.	Ken Sinn		X	Beth Pumo
X	Joe Lamy, Aegis		X	Joseph Quinn		X	Iona Thraen		.	Serafina Versaggi
.	Igor Sirkovich		.	Ali Khan ONC Patient Choice Project rep		.	Amber Patel ONC Patient Choice Project rep		.	Josh Bagley
.	Lisa Nelson		.	Hank MayersPCWG Representative		.	Laura Heermann Langford PCWG Co-chair		.	Steve Eichner

Back to FHIR Consent Directive Project Main Page

Agenda

• Copied forward from Jul 14*
• Roll-call
• (10 Minutes) Status Update for Business & Reference identifiers for Consent, Audit Event, and Provenance
• Review open CRs as time allows

Minutes

• Status update on Reference Indentifiers (CR 13694)
  • Reference datatype is now (as of STU3) a structure that contains a URL or an Identifier
  • Question is open as to what identifiers are possible (such as a CDA unique identifier or a policy identifier/business UID, etc.)
  • Currently being debated by FHIR-I
  • FHIR is ambiguous -- this is important because a patient wants to identify X datas to be allowed/forbidden and may require business identifiers
  • This may be redundant or perfectly logical, but needs clarification. FHIR-I may make Identifier more or less restrictive which will change how the IDs are used
• Add PractitionerRole to consentingParty (CR
  • FHIR-I agrees that this is the only way, even if it may duplicate
  • Will stand-in for Practitioner for some use cases
• Add Consent.Decision (CR 13598)
  • Discussion as to if the new element is needed or if Consent.category or Consent.policy should be used instead
    • would need to change consent.policy to a codable concept
  • Putting the ActConsentDirective as a codable concept would least overload with Policy being a link to the policy
  • Discussion to limit Consent.category to be the list of the scopes (and for Advance Directives, the types)
    • Consent.policy is a list of laws/regulations/etc.
• Adjourned 3:00