Scribe: @Suzanne Gonzales-Webb
Weekly calls Tuesdays 3PM ET
FreeConferenceCall Online Meeting Link https://www.freeconferencecall.com/join/security36
Dial-in Number (United States): (515) 604-9567 Access Code: 880898#
Motion to Approve 6/11 Minutes : Suzanne / Mike Moved/ Second
Objections: none ; Abstentions: none ; Approve: 9
|Montreal WGM Minutes|
Meeting Minutes reviewed with attendees.
Motion to Approve May Montreal Security WGM
Minutes : Kathleen/JohnM Moved/ Second
Objections:none ; Abstentions: none; Approved: 9
Final TEFCA 2 - HL7 Comments<<link to final approved comments submitted>>
|Sharing with Protections - Mike|
Mike to present on Sharing with Protections paper update
Review came out from the TEFCA;
The paper has more detail; please send comments when convenient and we can drill down more
I see this is as a change in healthcare, what HL7 has put in place. The chaos... and we can advance this.
comment: (Kathleen) This is concnsue on how you share new policies cross dimensional; Vendors could have a nightmare on their hands with different policies, declassification happening. They may have to put in different security requirements for different customers -that to me is chaos. This way customers and vendors can come up with a joint policy/vocabulary to relieve that.
--this is the same as DoD policy, wherein we give different access secret, etc.; we . Sharing w protections provides a way to persist these protections where everyone can understand and deal with the information.
Comment: maybe you can add a snippet of this information to your paper, using the update of TEFCA.
Initial Harmonization Proposal Submissions - Kathleen
Update from Mike Davis - (no updates this week)
FHIR Security Call updates.
Note that John Moehrke will be OOF next week.
Need PSS approval for FHIR DS4P and DS4P CDA IG update
FHIR DS4P IG PSS (Kathleen) - Review of updated draft per 2019-05-28 FHIR-Security Meeting Minutes comments below.
Outreach to current and prospective implementers and potential Connectathon testing concluded. VA, Perspecta, MiHIN, PatientLink added for both categories.
Report out of discussion with CBCP WG at 6/4 meeting.
Check that the DRAFT PSS comments have been adequately addressed:
Mike is proposing a sub-working group, to deliver information to send out for support
LINK to Security/CBCP FHIR DS4P IG PSS
Motion: Kathleen/ Suzanne
Abstention: 1 (Mike, Julie Maas, JohnM); Objections: None; Approved: 6;
Action Item: Develop DS4P CDA IG revision PSS - Kathleen to do
Next call is June 17th - Good progress made. Refined Brett's Provenance Author Participation template for C-CDA. Decision made to include it in the Summer out of cycle C-CDA Companion Guide to get community feedback.
Plan from Monday's call is that Brett is to meet with FHIR Security to check whether the data elements in the proposed C-CDA Provenance Author Participation template is fully supported by FHIR Provenance. Brett is working on Argonaut/US Core Basic Provenance profile. The Basic Provenance IG will point to the C-CDA Provenance Author Participation template and to the FHIR Basic Provenance profile with discussion on the use cases and how these decisions were arrived at.
WG needs to review and approve Basic Provenance NIB for September.
NIB screen shown; Review of NIB
Kathleen moves to have approvated / Brett second
VOTE: Abstentions: none; OBjectsions: none; Approved: 9
Kathleen will submit; Brett sending information to Kathleen.
Different bet Provenance and Lineage
Provenance is 'like what we're doing w basic provenance' pure creation...
anything after that is lineage—whatever happens to that initial thing after provenance.
what healthcare people think of provenance is 'both' the difference would be whether you chain them
MIke would like to view basic provenance is our 'painting' and once sold, the tracking, etc is 'lineage'
JohnM in healthcare - doesn't believe there is any distinction of purely provenance or lineage. It's just a form distinction. basic provenace is spoke of very early on. 'where did I get this information from...?' which ay not be the original painter but the museum... JohM believes in trying to fit them in the hybrids definitions --doenst really fit; I don't disagree with it–just in medical records it seems that way... they just want to know 'why I should trust this information... fromt he author or whomever...why should I trust that informatin/data...'
MikeD - thank you - just want to establish some foundational defitnions.
|Adjournment||Meeting adjourned Arizona time 1259 (Kathleen moved, John seconded)|
Temporary Meeting link: https://fccdl.in/qCAq79d5VY
John Moehrke Co-Chair
Kathleen Connor Co-Chair
|VA (Book Zurman)||@Trish Williams Co-Chair||Flinders University|
|x||@Christopher Shawn, Co-Chair||VA||x|
John Davis (Mike)
|x||@David Staggs||SRS||VA (Electrosoft)|
|SRS||@Francisco Jauregui firstname.lastname@example.org||VA (Electrosoft)|
|@Matt Blackmon||Sequoia||Julie Chan email@example.com||HL7 FHIR|
|@Dave Silver||VA (Electrosoft)||x||Kaiser|
|VA (Book Zurman)||x||ONC|
|@Peter VanLiesdonk||Phillips||@Adam Wong firstname.lastname@example.org||HHS|
|@Mohammad Jafari Mohammad.email@example.com||VA (Book Zurman)|
@Ricky Sahu, @1up.health
|Versaggi Consulting||Wave One|
|Laura Bright firstname.lastname@example.org||Jim Kamper||Altarum|