March 27, 2018 CBCP Conference Call

Community-Based Care and Privacy (CBCP) Working Group Meeting

Back to CBCP Main Page

Meeting Information

Dial-in Number:  (515) 604-9861;  Access Code: 429554
* International Dial-in Numbers: https://fccdl.in/i/cbhs

* Online Meeting Link: https://join.freeconferencecall.com/cbhs  
* Click on Join an Online Meeting Enter Online Meeting ID:  cbhs 
* Follow prompts if not automatically connected

Please be aware that teleconference meetings are recorded to assist with creating meeting minutes

Back to CBCP Main Page

Attendees

Call Recording: https://fccdl.in/0gfP7LTghl (temporary)

	Member Name		x	Member Name		x	Member Name		x	Member Name
.	Johnathan ColemanCBCP Co-Chair		x	Suzanne Gonzales-Webb CBCP Co-Chair		.	Jim Kretz CBCP Co-Chair		x	David Pyke CBCP Co-Chair
x	Kathleen Connor Security Co-Chair		x	Mike Davis		x	John Moehrke Security Co-Chair		x	Diana Proud-Madruga
.	Chris Shawn		x	Neelima Chennamaraja		.	Joe Lamy		x	Greg Linden
x	Irina Connelly		.	Saurav Chowdhury		x	Dave Silver		x	Francisco Jauregui
.	Patricia Peretz		.	Amber Patel		x	Becky Angeles		.	Jennifer Brush
.	Mohammed Jafari		.	Ali Khan		.	Ken Salyards		.	Ken Sinn
.	David Staggs		.	Steve Eichner		.	Ioana Singureanu		.	Beth Pumo

Back to CBCP Main Page

Agenda

1. Roll Call, Agenda Review
2. Meeting Minutes approval:
3. (5 min) CBCP FHIR THURSDAY call at 1:00 ET // FHIR Consent Directive Project Wiki, Main page
   • FHIR Consent discussion
   • FHIR CPs for review
4. FHIR Security Project Update - Johnathan
   • FHIR Consent CPs are located: link to ALL Consent Change requests
5. (10 min) Security and Privacy DAM - update, discussion Meeting weekly on Thursdays 11:00 AM ET Meeting Link: http://www.hl7.org/concalls/CallDetails.aspx?concall=38423

Role/ Meeting Minutes approval

Thursday meeting FHIR

• meetings on hold until ballot, no new items noted so far

• Code list issue discussion received from the list
  • need to look at possible solutions
  • Issue: Basic actions for the FHIR consent are not considered mutally exclusive
    • Use not clearly defined as part of 'access' (use should be a sub-code of access)
  • conversations behind the scenes with JohnM and Kathleen ongoing
• very simple QA requests - few tickets on STU3 (ignored - as STU effectively closed)

• • consent action code list

(JohnM) suggests - this consent is higher than consent to treat/consent ...

• there is a different element wthiIN privacy - where there is a set of sub codes that a privacy consent might utilize (which is what I
  • basic concent int he gForge - the action codes themselves are not exclusive (act, collect, use, discloses) and that 'use' requires access - use can be a subcode of 'access' or somehow it mandates access. Unfortunately the code descriptions does not have use includes acess
  • the vocab / why do they need to be neutrally exclusive
  • if you think that your use action, needs access also needs use action - then put them in both.
  • this comes from QA (Michelle Miller) - defined in a proper hierarchy; John would ask if there is a ... he does not recall there being a qA rule to throw an error if codes are xx (check recording)
  • reach out to Lloyd, or David Hay (or wait until JohnM uncovers the qA rule...faster to go to Lloyd/David/Michelle) - what QA rule is this violating? (it may just be Michelle's opinion--if that's so it shouldbe a QA opinion)
    • it wasn't presented as an opinion
  • John believes that several codes are overalapping (only place known where you cannot have an overlap is where you have a status)
• Dave will push back/follow up, send e-mail with CP issue to Lloyd/Dave for comment/response
• (from notes: So, the purpose of the QA review is focused on spelling and grammar – not the actual content of the resources. Feel free to raise a tracker in the usual way if you come across something you’d like to comment on, but for the purpose of this review just focus on the spelling and grammer)

FHIR (of vocabulary) Harmonization - definitions that kathleen put forward to get rid of the purpose piee (ISTPA - turned into the OASIS PMRM) had done an analysis on all privacy frameworks (little aged now), fiar-informaiton practices, underlying privacy practices

• had gone through and looked at key terms, they call it use limitations intended purpose of doing something with the data--needs to be followed and NOT changed
• collection, use discose - access to correct
  • added access (to access only) access by definition prohibited; you can't screen scrape, etc (you can photo) but is inteneded not for use or disclosure.
  • collect - there is obvious some access involved
    • above all - be very clear on definitions
• codes to be presented next week at this meeting ; intent to place through harmonization (currently as an example vocabulary)
  • http://build.fhir.org/valueset-consent-action.html

FHIR Security Project Update John Moehrke

• New Time - Tuesdays - 2:00 PM ET (before Security Call)

FHIR Connectathon Track

• JohnM and Alex running a FHIR Connectathon Track on the GDPR - all of the space that is appropriate where FHIR is to interact (very wide open at this time); we will have a discussion
• in Cologne; Rene SpronK is aware/doing work with SLS and has agreed to pile on what he knows

Security and Privacy DAM update

• BAsed on the WG vote - which Trish shepherded - we are supposed to be publishing the composite S&P DAM Informative from May 2014 - believe Trish started the process... ??
  • Suzanne will follow up with Trish on publication / publicqtion request
• update next week

HIMSS PPT on GDPR

• link to PPT
• also sending to list

Motion to Adjorn: JohnM / Suzanne

• Meeting adjorned at 0935 Arizona Time