Skip to main content

HL7v2toFHIR

FHIR Plugin – HL7 v2 to FHIR​

Summary (SEO Meta Description):
The FHIR plugin in WeHub converts HL7 v2.x messages into FHIR resources.
Supports a wide range of HL7 triggers and maps them into standards-compliant FHIR output.

Overview​

The HL7 v2 to FHIR action transforms traditional HL7 v2.x messages into FHIR resources.
It is a critical interoperability function for healthcare workflows, enabling legacy HL7 systems to communicate with modern FHIR-based applications.

This ensures data consistency across EHRs, labs, billing, and clinical systems.

⚙️ Action: HL7 v2 to FHIR​

  • Description: Parses an HL7 v2.x message and converts it into FHIR resources using a selected root template.
  • Use Case: Normalize HL7 admission, lab, order, or billing messages into FHIR for downstream workflows.

Configuration Options:

FieldTypeDescription
LabelStringCustom name for the node (e.g., "Convert ADT_A01 to FHIR").
Root TemplateEnumSelect the HL7 trigger event that defines the mapping. Options include:
ADT_A01, ADT_A02, ADT_A03, ADT_A04, ADT_A05, ADT_A06, ADT_A07, ADT_A08, ADT_A09, ADT_A10, ADT_A11, ADT_A13, ADT_A14, ADT_A15, ADT_A16, ADT_A25, ADT_A26, ADT_A27, ADT_A28, ADT_A29, ADT_A31, ADT_A40, ADT_A41, ADT_A45, ADT_A47, ADT_A60, BAR_P01, BAR_P02, BAR_B12, DFT_P03, DFT_P11, MDM_T01, MDM_T02, MDM_T05, MDM_T06, MDM_T09, MDM_T10, OMG_O19, OML_O21, ORM_O01, ORU_R01, OUL_R22, OUL_R23, OUL_R24, RDE_O11, RDE_O25, RDS_O13, REF_I12, REF_I14, SIU_S12, SIU_S13, SIU_S14, SIU_S15, SIU_S16, SIU_S17, SIU_S26, VXU_V04.

💡 Example Use Cases​

  • Hospital Admissions (ADT_A01): Convert HL7 admission messages into FHIR Encounter and Patient resources.
  • Lab Results (ORU_R01): Transform lab results into FHIR Observation resources.
  • Orders (ORM_O01): Map HL7 order messages into FHIR ServiceRequest resources.
  • Billing (DFT_P03): Convert billing transactions into FHIR Claim resources.
  • Scheduling (SIU_S12): Normalize scheduling messages into FHIR Appointment resources.

FAQ​

Q: What HL7 versions are supported?
A: All major HL7 v2.x versions are supported via templates (e.g., v2.3, v2.5, v2.7).

Q: What output format do I get?
A: Standards-compliant FHIR JSON resources, based on the root template selected.

Q: Can multiple root templates be used in one workflow?
A: Yes. Add multiple FHIR converter nodes for different HL7 triggers.

Keywords: WeHub FHIR Plugin, HL7 v2 to FHIR, FHIR Converter, healthcare interoperability, ADT_A01, ORU_R01, HL7 mapping