February 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
* Online Meeting Link: http://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

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

Back to CBCP Main Page

Agenda

1. (05 min) Roll Call, Approve Agenda
   • Approve Meeting Minutes for February 20 NOT COMPLETE, (move to next week)
   • Approve Meeting Minutes for February 13 NOT COMPLETE, (move to next week)
2. (20 min) CBCP FHIR THURSDAY call at 1:00 ET // FHIR Consent Directive Project Wiki, Main page
3. eLTSS PSS Review - Irina
   • FHIR Consent discussion
   • FHIR Consent CPs are located: link to ALL Consent Change requests
4. (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
5. January 2018 CBCP Working Group Meeting - New Orleans, Louisiana, USA

FHIR CBCP Thursday

• Lightly attended meeting last week on Thursday
• topic: research consent - more to come in the following weeks
• topic: Consent template for approval (clinician working on this has been MIA)
• CPs
  • two issues to close in gForge `15012, 15112'
  • 15102 - cardinality
  • 15112 - request to make subject patient optional; interesting conversation w/John Moehrke
    • there is no down side to it--potential for use in other manners not originally set; sets patient to optional from 0 to 1; updateing the code list (four scopes to four plus, )
    • changes privacy to privacy-patient (is that correct..?)
    • voted to do this and moving forward for simplicity--expecting comments back
• Feedback received from workflow update report - need to review on Thursday, (Thursday not a huge agenda)
  • CRs are largely caught up
  • still need to do treatment use case (need additional information)
  • Advance directive models to start again
    • and use in consent - WE NEED ASSISTANCE (David will start but requires SME feedback)

Security and Privacy DAM update

• from the PASS and Security working group
• Security proposed to publish the 2014 balloted DAM
• DAM is broken; there should be a process to revise and update it, but has not been brought up as an action item.
• for the upcoming ballot (Security) we will include the Trust Framework 22600 conformant 'mini-DAM; which will be Normative'... no direct relation to HL7 DAM. (The mini-DAM is associated with PSAF)
• when PSAF started 1. authentication 2. authorization 3. audit, provenance

as things have developed security has come to realize that the trust exchange and trust framework is established before exchange for information --the Trust is related to but not connected with the AC system for a particular instance for exchange. The Trust has to be set up before request happens directly.

• the model that we have is off-base (slightly) with 22600 at the highest level:policy/basic policy/meta, in recent modeling discussion we are only focusing on basic policy... the others are related to run-time and require additional data.
• gist - we've moved away from the model... we need trust (not necessary Access Control (AC)), but we don't need the instances of metadata of an AC decision. we've always done this but it was unconscious.
• as we have been developing - we've come up wit policy bridging model an diagrams for that. we're moving now to say that is 'trust' its a conceptual model, it includes identify assurance.
• we see that the trust volume is not about AC
• subordinate model is the Behavioral model volume 2 (balloting in May 2018)
  • then produce an identity trust model
  • then identity and access model
• it has an abbreviated 22600 model (only about policy) and security parlance, requestor and target object being accessed.

NIB is out for both the trust model volume, behavior conceptual model for normative ballot in May 2018

• modelers are developing... may be basis for Information model should CBCP and Privacy desire to update--no specific PSS for this project. do we need new PSS for update?

eLTSS - Becky status update:

• Patient Care would like to be an interested party;
• still chasing down Orders and Observation folks
• Kathleen okay with being vocab facility in relation to privacy/security/FM...
  • caveat: for clinical comments or BH--Kathleen will reach out to PC, CBCP for assistance.

Motion to adjourn: (Johnathan) 1030AM Arizona Time