This is currently a WIP.
|Name of Guide||Version||Status||Date|
|PDex IG Companion Guide Template||0.1||DRAFT||2019-06-26|
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.
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
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
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.
|ref lab||payer||simplest use case|
|ref lab||provider||payer||as claim w/ results|
|provider||payer (former)||payer (new)||PCDE use case|
Data received from (transport and payload):
Other HRex Provenance Notes:
Source = originator
What is the scope/grounding on identifying intermediaries?
Document how the health plan will support the use case scenario outlined above....
Identify the potential data sources the Health Plan would use to support the data exchange...
FHIR Resources from the PDex and HRex IGs that are used to support the data exchange:
Other Dependent FHIR Resources
Identify the value sets, codings and terminologies that will support the data exchange.
Identify the source to target field mapping by FHIR Resource
|FHIR Field||Value/Coding Set used||Example values||Health Plan Source Data Field||Industry Standard document/field source|
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, email@example.com