HL7
HL7 Plugin
Summary (SEO Meta Description):
The HL7 Plugin in WeHub enables workflows to parse and produce HL7 v2.x messages.
It supports multiple versions and triggers, allowing healthcare data to move seamlessly between systems.
Overview
The HL7 Plugin is a core healthcare integration tool in WeHub.
It allows workflows to both ingest HL7 v2.x messages and generate HL7 messages for interoperability with EMRs, LIS, RIS, billing, and other healthcare systems.
HL7 is the standard format for healthcare data exchange, making this plugin essential for hospitals, labs, and healthcare providers.
⚙️ Actions
1. Parse an HL7 Message
- Description: Takes an incoming HL7 v2.x message and transforms it into structured JSON data based on the selected schema.
- Direction:
HL7 → Workflow Data - Use Case: Normalize ADT, ORU, or ORM messages for internal processing or conversion to FHIR.
Configuration Options:
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Parse ORU_R01 Message"). |
| Version | Enum | HL7 version (V210, V220, V230, V231, V240, V250, V251, V260, V270, V271, V280). |
| Triggers | Enum | HL7 event type (e.g., ADT_A01, ORM_O01, ORU_R01, DFT_P03, etc.). |
2. Produce an HL7 Message
- Description: Generates a valid HL7 v2.x message from structured workflow data.
- Direction:
Workflow Data → HL7 - Use Case: Send admissions, lab results, or billing data back to healthcare systems.
Configuration Options:
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Produce ADT_A01 Message"). |
| Version | Enum | HL7 version (V210, V220, V230, V231, V240, V250, V251, V260, V270, V271, V280). |
| Triggers | Enum | HL7 event type (e.g., ADT_A01, ORM_O01, ORU_R01, DFT_P03, etc.). |
💡 Example Use Cases
-
Hospital Admissions (ADT_A01):
Parse admission messages from external systems and normalize them for internal apps.
Produce new admission messages to send updates back to the EMR. -
Lab Results (ORU_R01):
Parse incoming lab results for workflow automation.
Produce lab result messages for downstream clinical systems. -
Orders (ORM_O01):
Convert HL7 order messages into structured JSON for processing.
Generate new HL7 orders to communicate with pharmacy or radiology. -
Billing (DFT_P03):
Normalize billing transactions into internal formats.
Produce billing HL7 messages to integrate with financial systems.
FAQ
Q: What HL7 versions are supported?
A: HL7 v2.1 through v2.8 are supported (V210, V220, …, V280).
Q: What happens if I select the wrong trigger?
A: Parsing may fail or return incomplete results; ensure the correct HL7 event type matches your message.
Q: What output format does Parse return?
A: Structured JSON data, optionally validated against a schema.
Q: What output format does Produce return?
A: A raw HL7 string message, ready for transmission to external systems.
Keywords: WeHub HL7 Plugin, HL7 Parser, HL7 Producer, Parse HL7 v2.x, Generate HL7 message, ADT_A01, ORU_R01, healthcare data integration