HL7 v2.x to FHIR FAQ

An add-on module for the Redix AnyToAny Engine that converts HL7 v2.x messages to FHIR R4 JSON bundles, using mapping definitions you can read and edit. ADT and ORU passed Redix's internal Tier-1 FHIR audit on reference samples (FHIR validator acceptance pending); ORM, MDM, SIU, and VXU have demo samples, with audits pending. See HL7 to FHIR.

Input scope is HL7 v2.3 through v2.7.1; coverage for your versions and trigger events is checked against your interface samples. Output is FHIR R4 (4.0.1) JSON. Conformance to profiles such as US Core is not assumed: it is assessed and validated per project against the profiles you select and your own data.

• ADT (admit, discharge, transfer) to Patient, Encounter, Location: Tier-1 checks passed on reference samples; live demo
• ORU (observation results) to Observation, DiagnosticReport, Patient: Tier-1 checks passed on reference samples; live demo
• ORM (orders) to ServiceRequest, Patient, Practitioner: demo sample available; audit pending
• MDM (medical documents) to DocumentReference, Patient: demo sample available; audit pending
• SIU (scheduling) to Appointment, Patient, Location: demo sample available; audit pending
• VXU (vaccination updates) to 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.

It depends on the message type: Patient, Encounter, and Location for ADT; Observation and DiagnosticReport for ORU; ServiceRequest for orders; DocumentReference for documents; Appointment for scheduling; Immunization for vaccinations; with Practitioner and Organization where the message carries them.

We do not publish a single coverage percentage. Field coverage depends on your feeds, so it is confirmed against your de-identified interface samples. Configurable field mappings can be edited in the Redix GUI Mapper. Complex transformation rules, custom logic, or integration work may require additional implementation.

The engine is native C, with no JVM warm-up or garbage-collection pauses. Actual timing depends on the message, mapping, and hardware, so measure it on your own messages during evaluation.

CMS-0057-F centers on payer APIs (Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization). Clinical data converted from HL7 v2.x can feed a payer's FHIR data store, but conversion is one component of that work, not compliance by itself. For prior authorization, see the CMS PAS Compliance FAQ.

The licensed engine runs on your own Windows or Linux infrastructure, as a command-line tool, a native DLL/shared library, a folder watcher, or a Docker REST container. The deployment and interface options included for your use are confirmed during evaluation.

Yes. The HL7 and CDA demo converts Redix sample messages, with no local installation. Testing your own de-identified messages requires an evaluation key. Do not upload PHI.

The HL7 to FHIR Module requires the AnyToAny Format Converter Engine (core product) and is licensed separately as an add-on. HIPAA X12 to FHIR is an optional additional module for X12 transactions (837, 835, 834, 270/271, 276/277).