This is currently a WIP.

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

Why this companion guide

Purpose: To provide a guide for translating from different sources including providing a provenance resource to describe the actions taken to translate to the observation resource.

Most likely sources:

Three target audiences:

We are working with US Core resources. Each profile has a minimum set of required fields. Beyond those fields additional data SHALL be provided if it is available. When dealing with different data sources there will likely be different levels of data granularity.

In the context of this guide this document provides a mapping of different data sources to the observation profile. The objective of this guide is to enable Payers to map their data from different sources consistently.

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.


We want to complement rather than duplicate work.

Resource Mappings

Mapping Assumptions


The HL7v2-to-FHIR sub-team is currently working through these mapping alignment issues and noting them within the documentation of each HL7v2 segment mapping

Mapping Artifacts

The attached Spreadsheet provides a mapping from Health Plan data sources to the FHIR US Core (R4) Profile:

Latest: Observation-FHIR_R4 v1.4.xlsx

Earlier versions


Example1: HbA1c

The following FHIR instances are in context with the HL7v2 ORU^R01 example for an HbA1c.  They contain references to each other adn should be considered as a group.

Provenance Resource


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):

Other HRex Provenance Notes:

Source = originator

On agent.role 

What is the scope/grounding on identifying intermediaries?

Health Plan Data Exchange (Template)

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

Health Plan Data Sources

Identify the potential data sources the Health Plan would use to support the data exchange...

PDex/HRex FHIR Resources 

FHIR Resources from the PDex and HRex IGs that are used to support the data exchange:

Other Dependent FHIR Resources

Value Sets and Terminologies

Identify the value sets, codings and terminologies that will support the data exchange.


Data Crosswalks

Identify the source to target field mapping by FHIR Resource


FHIR FieldValue/Coding Set usedExample values Health Plan Source Data FieldIndustry Standard document/field source

Data Preparations

Identify the dependencies for creating FHIR resources.....

For example, Patient and Practitioner Resources need to be created before Encounter, Procedure etc. 


Author/contact person with contact information for this page

Tony Benson , BCBS Alabama

Mark Scrimshire, NewWave,