HL7 to FHIR Conversion Module.
Production-grade HL7 v2.x to FHIR R4 conversion software for on-premises and API deployments. 14 message types with 85-90% field coverage and sub-150ms processing.
Runs on the AnyToAny Engine. HL7 v2.3 through v2.7.1 input. FHIR R4 JSON output with Provenance.
Want to see input/output? Convert HL7 to FHIR with sample data (no PHI).
Target FHIR R4 Resources
Every conversion produces a validated FHIR R4 JSON Bundle with a Provenance resource for audit trail.
CMS-0057-F programs often run alongside HL7 modernization. If your organization also needs Da Vinci PAS or prior authorization, see the CMS-0057-F Compliance Suite.
Supported Message Types
14 HL7 v2.x message types with 85-90% field coverage out of the box.
| Message | Description | Primary FHIR 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.
Key Features
Standards Compliant
- FHIR R4 JSON output (4.0.1)
- HL7 v2.3 through v2.7.1 input
- Automatic Provenance generation
- US Core compatible (configurable)
Multiple Interfaces
- Web GUI with drag-and-drop
- Command-line tools
- REST API integration
- Batch processing mode
Quality Assurance
- Built-in FHIR R4 validation
- Automatic data normalization
- Detailed error reporting
- Conversion audit logs
Production Ready
- Sub-150ms processing time
- Linux and Windows deployment
- Docker container support
- Sample files included
Want to see real input and output? Convert HL7 to FHIR with sample data (no PHI). Or explore the full Live Sandbox.
Technical Specifications
| 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) |
| 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 |
| Processing Time | 50-150ms per message |
| Audit Support | FHIR Provenance resource included |
| Customization | GUI Mapper for additional field mappings |
| Deployment | Linux, Windows, Docker |
Licensing
AnyToAny Engine
Required. Core conversion engine providing the single-pass architecture, IFD/OFD processing, and runtime environment.
HL7 to FHIR Module
This module. 14 HL7 v2.x message types to FHIR R4 JSON conversion with Provenance and 85-90% field coverage.
HIPAA X12 to FHIR
Optional add-on. HIPAA X12 transactions (837, 835, 270/271, 276/277, 834, 820) to FHIR R4 conversion.
Modular pricing. The AnyToAny Engine is the core product required for all conversions. Each module is licensed separately based on your requirements. For CMS-0057-F compliance, see the CMS-0057-F Suite.