Convert HL7 v2.x messages to FHIR R4
Turn the ADT, ORU, and order traffic your interfaces already carry into FHIR R4 JSON bundles, with deterministic mappings you can read and edit. HL7 v2.3 through v2.7.1, on the same native engine that runs Redix X12 processing.
- HL7 v2.3 to v2.7.1
- FHIR R4 JSON
- On-premises, REST API, or Docker
What converts today, and how far each one is tested
We publish the testing status of each message type rather than a single coverage number. "Tier-1 checks passed" means the conversion passed Redix's internal automated FHIR audit on our reference sample messages; FHIR validator (Tier-2) acceptance has not yet been run for any type, and this is not a third-party certification.
| Message | Description | Main FHIR R4 resources | Status |
|---|---|---|---|
| ADT | Admit, discharge, transfer | Patient, Encounter, Location | Tier-1 checks passed on reference samples; validator acceptance pending; live demo |
| ORU | Observation results (lab) | Observation, DiagnosticReport, Patient | Tier-1 checks passed on reference samples; validator acceptance pending; live demo |
| ORM | Orders | ServiceRequest, Patient, Practitioner | Demo sample available; audit pending |
| MDM | Medical documents | DocumentReference, Patient | Demo sample available; audit pending |
| SIU | Scheduling | Appointment, Patient, Location | Demo sample available; audit pending |
| VXU | Vaccination updates | Immunization, Patient | Demo sample available; audit pending |
Other message types, such as DFT, RDE, or BAR, can be mapped on the same engine as a project. Organization-specific fields and business rules are added in the Redix GUI Mapper without writing code.
Deterministic, inspectable, on your servers
Repeatable mapping rules
Mappings are definitions, not models. For a fixed engine version and configuration the mapping rules apply the same way every time, which makes reviews and audits practical; generated identifiers and timestamps can differ.
Editable mappings
Every field mapping lives in a definition file your team can read and change, through the GUI Mapper or directly.
Your environment
Run on-premises, in Docker, or behind your own REST API. Production messages do not need to be sent to Redix.
| Specification | Value |
|---|---|
| HL7 versions | Input scope v2.3 to v2.7.1; coverage for your versions and trigger events confirmed against your interface samples |
| Output | FHIR R4 (4.0.1) JSON bundles |
| Message types | ADT, ORU (Tier-1 checks passed); ORM, MDM, SIU, VXU (demo samples, audit pending); others by project |
| Interfaces | REST API, Web GUI, command line, batch processing |
| Deployment | Linux, Windows, Docker |
How the module is licensed
AnyToAny Engine
Required. The core engine: single-pass processing, IFD/OFD definitions, and the runtime.
HL7 to FHIR
This module. The HL7 v2.x to FHIR R4 mappings, REST API, Web GUI, and batch processing.
HIPAA X12 to FHIR
Often alongside. X12 claims, remittance, enrollment, eligibility, status, and prior authorization to FHIR R4.
The AnyToAny Engine is required for every conversion; each module is licensed separately. For prior authorization under CMS-0057-F, see the CMS-0057-F Compliance Suite.
See your own messages in FHIR
Start with the live demo's synthetic samples, then send de-identified messages from your feeds. We show the bundles and scope any custom mappings.