Skip to end of metadata
Go to start of metadata

Chair:  @Kathleen Connor

Scribe: @Belle Rogers







John Moehrke , Co-Chair


Alexander Mense, Co-Chair

HL7 Austria

Kathleen Connor , Co-Chair

VA (Book Zurman)

@Trish Williams, Co-ChairFlinders University

@Christopher Shawn, Co-ChairVA

@Mike DavisVA

@David Staggs

VA (Electrosoft)


@Francisco JaureguiVA (Electrosoft)

@Joe LamyAegis

@Matt BlackmonSequoia


@Dave SilverVA (Electrosoft)


VA (Book Zurman)

@Ken SalyardsSAMHSA

@Peter VanLiesdonkPhillips

@Adam Wong adam.wong@hhs.govHHS

@Mohammad Jafari mohammad.jafari@bookzurman.comVA (Book Zurman)

@Ricky Sahu,

1up Health


xCraig NewmanAltarum

Belle Rogers

xEric Kettler
xCarlos PolkIPO

Gary DickinsonCentriHealth/UnitedHealth Group
xSerafina Versaggi

Michael DonnellyEpic

Agenda Topics

Agenda Item


Decision Link(if not child)

Review Provenance Outline

Brett Marquard reviewed the Provenance IG outline to gather feedback from WG on the format: introduction, implementation guides, and appendix (including other provenance efforts, mapping to other work, additional use cases and examples).

Discuss the Fivew's

  • N/NC meaning
  • 'Provenance in the Resource' vs the 'Provenance Resource'
  • Asserter and Author
  • Review Allergy Intolerance

John Moehrke provided historical background on how the Fivew's (previously known as 'W5'; not intended to be visible) may guide Data Provenance discussion but the primary purpose of the Fivew's is a modeling tool to ensure consistent use within the FHIR resources of who, what, when, where and why.

John Moehrke, Kathleen Connor, and Mike Davis also clarified that the discrepancy perceived in the "asserter" and "author" roles are corrected when considering the life cycle events.

CDA Data Provenance

  • Assigned Author

Brett Marquard shared that the initial intent was to leverage the CDA Data Provenance to build the Data Provenance IG. However, there were distinct elements from this document that posed challenges to the idea. Kathleen Connor was one of the people responsible for the artifact and explained that the request at the time was to have a rigid set of rules to allow adopters to determine whether the elements applied to them in a more clear way – Kathleen agreed the 2016 publication could be improved and future update is under consideration. 

CDA: the conceptual description of elements and discreet rules can be leveraged, but not directly reused. Work Group agrees the Basic Provenance guide will have to develop updated constraints. Brett Marquard intends to focus on this work during the next call.

FHIR: this group could either leverage a profile built by another community (e.g. Argonauts) or create a new one. Prefer leverage existing. 

L7 CDA R2 Data Provenance (written by CBCP)

Next Agenda

Call ended4:00 pm Eastern Time
  • No labels