Chair: @Kathleen Connor
Scribe: @Joel Bales
John Moehrke , Co-Chair
Alexander Mense, Co-Chair
Kathleen Connor , Co-Chair
|VA (Book Zurman)||@Trish Williams, Co-Chair||Flinders University|
|@Christopher Shawn, Co-Chair||VA||@Mike Davis||VA|
|@David Staggs||VA (Electrosoft)|
|SRS||@Francisco Jauregui||VA (Electrosoft)|
|@Matt Blackmon||Sequoia||HL7 FHIR|
|@Dave Silver||VA (Electrosoft)||Kaiser|
|VA (Book Zurman)||@Ken Salyards||SAMHSA|
|@Peter VanLiesdonk||Phillips||@Adam Wong firstname.lastname@example.org||HHS|
|@Mohammad Jafari email@example.com||VA (Book Zurman)|
@Ricky Sahu, @1up.health
|x||Joel Bales||DoD/VA Interagency Program Office|
|x||Carlos Polk||DoD/VA IPO||x||Gary Dickinson||CentriHealth/UnitedHealth Group|
|Michael Donnelly||Epic||x||Didi Davis||Sequoia|
Decision Link(if not child)
Recoding URL: https://fccdl.in/ChzNoDBehN
|Basic Provenance Draft|
Walk through guide and conformance statements:
Section 3.1 – basic provenance practices. Review of conformance statements. Key items of interest:
Gary Dickinson, Brett Marquard and the group discussed the level of detail to include in basic provenance and future roadmaps for advanced provenance:
Carequality exchanges 36 million CDAs monthly without including the view seen by clinicians prior to the information being transformed into a CDA document. To maintain quality assurance, Carequality is updating implementation guides to perform monthly ad hoc testing. Must identify minimum requirements for vendors to implement within the next 18 months, and then identify future improvements.
Clinicians require sufficient provenance for clinical decisions (one layer back). Data must carry provenance information useful for the downstream system.
This Basic Provenance project, focused on clinician needs, is scoped similarly to existing systems (DoD-VA Joint Legacy Viewer, Epic Care Everywhere platform, Cerner) which contain time stamp, and author organization. Author may or may not be displayed.
The group discussed the importance of scoping Basic Provenance to move industry forward while setting a roadmap for future enhancements. The guide references previous provenance work in the appendix, which can feed into the roadmap for future industry directions. For example, consider capturing additional data if available in a source system, and clarify that the three basic provenance items are a start, and more may be required in the future. Basic provenance is built on previous work, which helps guide implementation. It defines a minimum testable set of data, but does not limit systems from including more information in their provenance (building on previous work listed in appendices).
Brett and Russ Ott would appreciate assistance for advanced provenance language, because they did not lead previous provenance efforts. Gary Dickinson can assist. Provenance is expected to have additional future requirements. Brett will add a section to the appendix listing use cases (e.g., legal discover) and references to address those use cases (he requested Gary’s assistance).
Brett will add language in the introduction to clarify that Basic Provenance is a first step to solving provenance, but it not solved. He will add disclaimers that this is basic provenance is a minimum, and that more robust data will make provenance stronger. Requested that Gary provide information on which artifacts to include. Need help to add the language for the appendix. These changes can be addressed through ballot comments.
Will present to Security tomorrow to request approval to go to ballot.
|Argonaut Provenance Profile|
Enhance existing invariant to apply to device also
Updates to Argonaut guide:
Next meeting at the WGM in Atlanta
|Call ended||3:45 PM eastern time|