Convert HL7 v2.x ADT, ORU, ORM, MDM, and SIU to FHIR R4
14 HL7 v2.x message types to FHIR R4 JSON bundles with Provenance. 85–90% field coverage. US Core compatible.
Runs on the AnyToAny Engine. On-premise, REST API, or Docker. Sub-150ms processing.
14 Message Types FHIR R4 JSON US Core Compatible Sub-150ms On-prem / Docker
Built on the same Redix engine used in production by a national US pharmacy organization to migrate 100+ healthcare conversion scripts.
ADT, ORU, ORM, MDM, SIU — Supported HL7 v2.x Message Types
14 HL7 v2.x message types with 85–90% field coverage out of the box. Each row shows the source HL7 message, its primary FHIR R4 target resources, and field coverage. Every conversion produces a validated FHIR R4 JSON Bundle with a Provenance resource for audit trail.
| Message | Description | Primary FHIR R4 Resources | Coverage |
|---|---|---|---|
| ADT | Admit / Discharge / Transfer | Patient, Encounter, Location | 90% |
| ORU | Lab Results | Observation, DiagnosticReport, Patient | 90% |
| ORM | Clinical Orders | ServiceRequest, Patient, Practitioner | 90% |
| MDM | Medical Documents | DocumentReference, Patient | 85–88% |
| DFT | Financial Transactions | Claim, Patient, Encounter | 90% |
| RDE | Pharmacy Orders | MedicationRequest, Patient | 90% |
| VXU | Vaccinations | Immunization, Patient | 85–88% |
| SIU | Scheduling | Appointment, Patient, Location | 85–88% |
| BAR | Billing Account Records | Account, Patient, Coverage | 85–87% |
| REF | Patient Referrals | ServiceRequest, Patient, Practitioner | 87–90% |
| OUL | Lab Orders | ServiceRequest, Specimen | 85–90% |
| ACK | General Acknowledgment | OperationOutcome | 90% |
| QRY | Query Messages | Parameters | 85–88% |
| RSP | Query Response | Bundle (searchset) | 85–88% |
Close the gap. The remaining 10–15% is covered using the Redix GUI Mapper, allowing your team to implement custom field mappings and organization-specific business rules without writing code.
Technical Specifications
Engine-level facts. Same answers a developer or solution architect needs to scope an integration.
| Specification | Value |
|---|---|
| HL7 Versions | v2.3, v2.4, v2.5, v2.5.1, v2.6, v2.7, v2.7.1 |
| Output Format | FHIR R4 JSON (4.0.1), US Core compatible (configurable) |
| Message Types | 14 (ADT, ORU, ORM, MDM, DFT, RDE, VXU, SIU, BAR, REF, OUL, ACK, QRY, RSP) |
| Field Coverage | 85–90% out of the box; remaining 10–15% via GUI Mapper |
| Processing Time | 50–150ms per message |
| Validation | Built-in FHIR R4 validation, automatic data normalization, detailed error reporting |
| Audit Support | FHIR Provenance resource on every conversion; conversion audit logs |
| Interfaces | REST API, Web GUI (drag-and-drop), CLI tools, batch processing |
| Deployment | Linux, Windows, Docker |
Licensing
The HL7 to FHIR module is sold as an add-on to the AnyToAny Engine. Each module is licensed separately.
AnyToAny EngineRequired
Core conversion engine providing the single-pass architecture, IFD/OFD processing, and runtime environment.
HL7 to FHIR ModuleThis Product
14 HL7 v2.x message types to FHIR R4 JSON conversion. Provenance, US Core compatibility, REST API, Web GUI, and batch processing.
HIPAA X12 to FHIROptional Add-on
HIPAA X12 transactions (837, 835, 270/271, 276/277, 834, 820) to FHIR R4. Often deployed alongside HL7 modernization.
Modular pricing. The AnyToAny Engine is the core product required for all conversions. Each module is licensed separately. For CMS-0057-F prior authorization, see the CMS-0057-F Compliance Suite.