Page tree

Versions Compared

Key

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


This page is a template for creating companion guide pages to support the PDex IG.
Name of GuideVersionStatusDate
PDex IG Companion Guide Template0.1DRAFT2019-06-26

Mapping from Sources:

https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-observation-lab.html
Source InformationTargetMinimum FHIR FieldsLink
Hl7 V2ObservationLOINCCCDAObservationClaimObservationDiagnosticReportSpecimen

Why this companion guide

Add some context here.

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

...

  • HL7 V2 2.3, 2.5.1
  • C-CDA R1.1, R2.1
  • X12 837


Three target audiences:

...

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:

Source InformationTargetMinimum FHIR FieldsLink
HL7 V2Observation
https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-observation-lab.html
C-CDAObservation

Claim (X12)Observation


DiagnosticReport




Specimen



Resource Mappings

Mapping Assumptions

HL7v2-to-FHIR

  • We will leverage as much of the ongoing work from the O&O HL7v2-to-FHIR mapping project as possible. 
  • HL7v2.5.1 will be the source data standard which will be mapped to FHIR.  While there are other more recent versions of HL7v2, version 2.5.1 is cited for CLIA conformance.
  • Semantic mappings might be approximate in cases where the term descriptions are ambiguous. 
  • Structural mappings might not align in several ways noted below:
    • cardinality
    • data type
    • non-existent elements

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:

...

Examples


Provenance Resource 

https://www.hl7.org/fhir/provenance.html

...

  • 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



Health Plan Data Exchange Overview

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 FHIR Resources 

Identify the FHIR Resources from the PDex IG that are used to support the data exchange...


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


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

Author/contact person with contact information for this page

...