Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is currently a WIP.

Name of GuideVersionStatusDate
PDex IG Companion Guide Template0.1DRAFT2019-06-26


A provenance resource SHALL be constructed for each record to identify the originator of the data (the provider/organization etc.), the transmission format (C-CDA, ADT, 837 etc.) which indicates the type of translation performed.

Mapping from Sources:




  • To leverage the work already being done in the community. This may include the existing work from:
    • O&O - HL7v2-to-FHIR project
    • C-CDA on FHIR project 
  • To address Provenance from the payer perspective
  • Develop mappings for payer-specific sources (e.g.: 837 claims)

We want to complement rather than duplicate work.

Resource Mappings

Mapping Assumptions



sourceintermediary (who)targetcomments
ref lab
payersimplest use case
ref labproviderpayeras claim w/ results
payerin-house lab 
providerpayer (former)payer (new)PCDE use case

Data received from (transport and payload):

  • Provider via HL7 V2
  • Provider via C-CDA
  • Provider via 837 Claim
  • Provider via "Paper Chart"

  • Provider Attestation (Pass through billing)
  • Payer Intermediate Translation
  • Provider by copy of formal lab report

Other HRex Provenance Notes:

Source = originator

On agent.role 

  • provider could be a validator or transcriber.
  • payer could be a transcriber.

What is the scope/grounding on identifying intermediaries?

  • keep in mind...we're doing this through the lens of the payer and what visibility do they have in the data received?
    • e.g.: if there's a claim that only states that a lab test was done then what can be deduced fro that content?
    • e.g.: if there is a translation from HL7v2 to C-CDA, does there need to be an intermediary here?  (is it secondary data at this point?)

Health Plan Data Exchange



Document how the health plan will support the use case scenario outlined above....