September 22, 2015 CBCC Conference Call

Community-Based Collaborative Care Working Group Meeting

Back to CBCC Main Page

Attendees

	Member Name		x	Member Name		x	Member Name
.	Johnathan ColemanCBCC Co-Chair		x	Suzanne Gonzales-Webb CBCC Co-Chair		x	Jim Kretz CBCC Co-Chair
.	Max Walker CBCC Co-Chair		x	Mike Davis Security Co-Chair			John Moehrke Security Co-Chair
x	Kathleen Connor		.	Ken Salyards CBCC Interim Co-Chair			Lori Simon CBCC Interim Co-Chair
x	Diana Proud-Madruga		x	Rick Grow			Harry Rhodes
.	Serafina Versaggi			Ioana Singureanu			David Bergman
x	Steve Eichner		.	Steve Daviss		.	Wende Baker
.	Reed Gelzer		.	Marlowe Greenberg			Chris Clark, WV
.	Paul Knapp		.	Matt Peeling			Brian Newton
	Lisa Nelson		.	Mike Lardiere		.	Amanda Nash
.	Mohammed Jafari			Oliver Lawless			Keith Boone
x	Neelima Chennamaraja			Susan Litton			Sandra Huyck
.	William Kinsley		.	Debbie Bucci			Chirag Bhatt
.	Linda Bailey-Woods		x	Lee Wise			Lori McNeil Tolley
.	Peter Fiaspa, Colombia University		x	[mailto: Gary Dickenson ]		x	Russell McDonell

Back to CBCC Main Page

Agenda

1. (05 min) Roll Call, Approve Meeting Minutes from September 15, 2015 CBCC Conference Call
2. (05 min) Patient Friendly Language for Consumer User Interfaces - (Standing Agenda Item) - Update
3. (05 min) Data Provenance IG Update (Standing Agenda item)
4. Behavioral Health Domain Analysis Model (HL7 BH DAM) Update update
   • Unique Ballot ID: V3_DAM_BH_R2_I1_2015SEP, HL7 Version 3 Domain Analysis Model: Behavioral Health Record, Release 2 (Project Insight ID: 1174)
5. (10 min) PASS Access Control Services Conceptual Model - (Standing agenda item) update (Diana)
6. (10 min) Joint EHR, Security, Privacy Vocabulary Alignment - (Standing agenda item) update (Diana/Mike)
   • continued work at WGM WED Q3, THU Q3
7. (10 min) Action Item Review (if any)
   • October 2015 CBCC Working Group Meeting - Atlanta, GA 29th Annual Plenary & Working Group Meeting October 4-9, 2015
     • Please send desired items to Suzanne for inclusion to the upcoming Agenda
     • *NEW* Joint EHR, Security, Privacy Vocabulary Alignment -continued work at WGM WED Q3, THU Q3

Meeting Minutes (DRAFT)

Approve Meeting Minutes from September 15, 2015 CBCC Conference Call

The minutes from the September 15 were approved.

1 Abstain (McDonell); Objections: None; Affirmatives: 8

Data Provenance - update

The IG will be distributed to the CBCC listserv for the WG's review. The plan is to vote on publication of the document as a DSTU at the HL7 WGM two weeks from now.

Please contact Suzanne if you would like to receive the information and are not yet part of the list serve.

Data Provenance Metadata Relations

• contains Provenance Metadata; have the option to link the metadata to any data (clinical statement, document, etc.); the parent document information in the header of the CDA can also link to the Reference Choice and relay that one or more document is related to one or more documents
• author of provenance data can also be identified in this section
• creates a more robust accounting of documents
  • what causes the provenance...(what entity) causes the provenance to happen

Provenance Label

• part of the HCS, labels related to provenance
• i.e. data alteration, level of confidence, supported by/asserted by...set of labels specific to provenance as found in the HCS
• gives you the ability to say that the preceding artifact was fine, but because this is a CDA, a signature was broken--this gives you the opportunity to say that you received the artifact and that it's fine

Provenance Policy Information File

• specifies your provenance policy that you (the receiver of the provenance data) have agreed to abide by

Questions:

(JimK) What is the minimum amount of data required to complete the provenance data? 300 bytes of data? 500 bytes?

(Kathleen) It's not so much the size of the data, rather the ability to retrieve, populate and read it...the more data, the more complex it will be, and most likely domain specific. Even though an item may say SHALL, they may not have that information (i.e. we only require that the author be identified)

(JimK) This may become an issue when a CDA has been accumulated over a number of times.

(Kathleen) If this CDA were to go to someone else, they would not be keeping the provenance data; they would be starting their own provenance.

Behavioral Health Domain Analysis Model - Neelima

Ballot is in; will be working on the ballot reconciliation once ballot is complete

• Note: Neelima will not be at the upcoming WGM

PASS Access Control Services Conceptual Model - Diana

Ballot comments are due September 28. Please review and comment!

Joint EHR, Security Privacy Vocabulary Alignment

• coming to consensus on the process
  • agreed to avoid arguing over nuances in the Lifecycle Event definitions
  • the project team will address the nuances in the identification of properties. The properties can be used as test criteria to see whether the term is being used in the context of a Lifecycle Event versus another context.
• group has agreed to meet at the WGM on Wed Q3, Thurs Q3 in Atlanta to do some face-to-face work

Motion to adjourn: (Gary/Kathleen) --Suzannegw (talk) 14:57, 22 September 2015 (EDT)