ParseanHL7Message
HL7 Plugin – Parse an HL7 Message
Summary (SEO Meta Description):
The HL7 Parser in WeHub converts HL7 v2.x messages into structured data based on a schema.
Supports multiple HL7 versions and triggers for seamless healthcare data integration.
Overview
The Parse an HL7 Message action allows workflows to ingest HL7 v2.x messages and transform them into structured JSON or schema-based outputs.
It is commonly used in healthcare integrations, such as normalizing admission, discharge, and lab messages into workflow-friendly formats.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Parse ADT Message"). |
| Version | Enum | Select the HL7 version to parse. Options: V210, V220, V230, V231, V240, V250, V251, V260, V270, V271, V280. |
| Triggers | Enum | Choose the HL7 event type. Examples: ADT_A01, ORM_O01, ORU_R01, etc. |
💡 Example Use Cases
-
Hospital Admissions (ADT_A01 – Admit/Visit Notification)
Parse admission messages to register patients into local systems. -
Laboratory Results (ORU_R01 – Unsolicited Observation Message)
Extract lab results and feed them into analytics or FHIR-based workflows. -
Orders (ORM_O01 – Order Message)
Convert HL7 orders into structured data for order tracking systems. -
Billing (BAR_P01 – Add/Update Billing Account)
Normalize billing messages into ETL workflows.
FAQ
Q: Can I parse multiple HL7 versions in one workflow?
A: Yes, you can add multiple parser nodes with different version/trigger combinations.
Q: What format is the parsed data returned in?
A: Parsed HL7 is returned as JSON structured data, optionally validated against a schema.
Q: What if my HL7 message doesn’t match the trigger event?
A: The parser may fail or return incomplete results. Ensure the correct trigger is selected.
Keywords: WeHub HL7 Parser, HL7 v2.x, ADT_A01, ORU_R01, healthcare data integration, parse HL7 message