Convert HL7 v2 to FHIR R4: Paste a Sample Message and See FHIR JSON

Turn HL7 v2 messages into FHIR R4 resources, ideal for integration teams modernizing interfaces.

Sample data only, do not paste PHI.
Try HL7 → FHIR Demo (sample data) Schedule a 30-min Technical Consult

What This Tool Does

Redix converts HL7 v2.x messages into FHIR R4 JSON bundles that can be validated as part of an implementation workflow. The converter supports common HL7 v2 workflows, with strongest coverage for ADT and ORU sample scenarios and expanding support for additional message types.

  • Common HL7 workflows: ADT, ORU, and selected order, document, scheduling, immunization, billing, and master-file scenarios
  • HL7 v2.3 to v2.7.1: Reads the HL7 version from the MSH segment and applies configured mapping rules for supported workflows
  • Substantial field coverage out of box, with custom mapping for site-specific and Z-segment fields
  • Available as on-premises engine or REST API with Python and Node.js SDKs

Supported HL7 v2 Message Types

ADT (A01-A08)

Admit, Discharge, Transfer

→ Patient, Encounter, Location, Practitioner

ORU R01

Observation Results (Lab)

→ DiagnosticReport, Observation, Patient

ORM O01

Order Message

→ ServiceRequest, Patient, Practitioner

MDM T01/T02

Medical Document Management

→ DocumentReference, Patient

VXU V04

Vaccination Update

→ Immunization, Patient

SIU S12

Scheduling Information

→ Appointment, Schedule, Patient

RDE O11

Pharmacy/Treatment Encoded Order

→ MedicationRequest, Patient

BAR / DFT / MFN / PPR

Billing, Financial, Master File, Pathway

→ Account, ChargeItem, and more

Example: ADT^A01 → Patient/Encounter Bundle

Here's what the converter produces from a standard admission message:

Sample Input (HL7 v2 ADT^A01)

MSH|^~\&|ADT1|MCM|FINGER|MCM|198808181126|SECURITY|ADT^A01|MSG00001|P|2.3.1
EVN|A01|198808181123
PID|1||PATID1234^5^M11^ADT1^MR^MCM~123456789^^^USSSA^SS||SMITH^WILLIAM^A^III||19610615|M||C|1200 N ELM STREET^^JERUSALEM^TN^99999-1020|GL|(999)999-1212
NK1|1|SMITH^OREGANO^K|WI^WIFE||||20011105
PV1|1|I|2000^2012^01||||004777^CASTRO^FRANK^J.|||SUR||||ADM|A0
AL1|1|DA|PENICILLIN||PRODUCES HIVES
DG1|1||1550|MAL NEO LIVER, PRIMARY|19880501103005|F
IN1|1|A357|BCMD|BC MEDI
Standard ADT^A01 admission message. Full sample data included in the demo.

Sample Output (FHIR R4 JSON Bundle)

{
  "resourceType": "Bundle",
  "type": "collection",
  "entry": [
    {
      "resource": {
        "resourceType": "Patient",
        "name": [{"use": "official", "family": "SMITH", "given": ["WILLIAM", "A"], "suffix": ["III"]}],
        "birthDate": "1961-06-15",
        "gender": "male",
        "identifier": [
          {"system": "http://example.org/mrn", "value": "PATID1234"},
          {"system": "http://hl7.org/fhir/sid/us-ssn", "value": "123456789"}
        ],
        "address": [{"line": ["1200 N ELM STREET"], "city": "JERUSALEM", "state": "TN", "postalCode": "99999-1020"}]
      }
    },
    {
      "resource": {
        "resourceType": "Encounter",
        "status": "in-progress",
        "class": {"code": "IMP", "display": "inpatient encounter"},
        "participant": [{"individual": {"reference": "Practitioner/..."}}],
        "diagnosis": [{"condition": {"reference": "Condition/..."}}]
      }
    },
    {"resource": {"resourceType": "Practitioner", "name": [{"family": "CASTRO", "given": ["FRANK", "J."]}]}},
    {"resource": {"resourceType": "AllergyIntolerance", "code": {"text": "PENICILLIN"}, "reaction": [{"description": "PRODUCES HIVES"}]}},
    {"resource": {"resourceType": "Condition", "code": {"text": "MAL NEO LIVER, PRIMARY"}}}
  ]
}
Simplified for readability. Actual output includes full references, identifiers, and mapping details.

Deployment Options

  • Online demo: Try immediately with Redix sample data. Testing your own de-identified files requires an evaluation key.
  • REST API: Integrate via HTTP endpoints with Python, Node.js, C#, or Java SDKs (Developer Portal)
  • On-premises engine: Native C engine, no JVM overhead. PHI stays in your infrastructure.

Frequently Asked Questions

Which HL7 v2 message types does Redix convert to FHIR?
Redix supports common HL7 v2 conversion workflows, including ADT admission/discharge/transfer messages and ORU lab-result messages. Additional message types such as ORM, MDM, VXU, SIU, billing, and master-file scenarios can be evaluated based on your implementation requirements.
Which HL7 v2 versions are supported?
Redix converts HL7 v2.3, v2.3.1, v2.4, v2.5, v2.5.1, v2.6, v2.7, and v2.7.1. The converter reads the HL7 version from the MSH segment and applies the configured mapping rules for the supported workflow.
What does the FHIR output look like?
Each HL7 message produces a FHIR R4 JSON Bundle containing the appropriate resources. For example, an ADT^A01 admission generates Patient, Encounter, Location, Practitioner, and Organization resources. An ORU^R01 lab result generates DiagnosticReport, Observation, Patient, and Practitioner resources.
How does Redix handle custom Z-segments and site-specific fields?
Out-of-box mapping covers a substantial share of standard fields. Custom Z-segments and site-specific fields require a mapping engagement where Redix configures additional field mappings to reach your target coverage. The converter architecture supports custom extensions without modifying core mappings.
Does the online demo accept real patient data (PHI)?
No. The online demo is for sample and synthetic data only, do not paste PHI. For production use with real patient data, Redix deploys on-premises within your environment, ensuring PHI never leaves your infrastructure.
Can Redix run on-premises?
Yes. The Redix HL7 to FHIR converter runs as an on-premises native C engine. No JVM, no cloud dependencies. Also available as a REST API with Python and Node.js SDKs for integration into existing workflows.

Need this running in your environment?

Run the same Redix engine in your own environment (Docker or on-prem). No PHI leaves your system.

Request Technical Evaluation

We will help you choose the right evaluation path for sample testing, API testing, or deployment in your own environment.

Used in production by large healthcare organizations, including Fortune 500 companies. Trusted for over a decade in healthcare data integration.

Related Tools & Resources