Translating HL7v2 to FHIR

While healthcare isn’t generally known for its technical innovation, the progress we have made wouldn’t be possible without HL7v2. It was born in the 1980s (like many of our Redoxers).

HL7 estimates that 95% of U.S. healthcare organizations use HL7v2. If you’re in healthcare, you’re likely touching HL7v2, or you should be.

Redox translates standard HL7v2 feeds from a healthcare system to modern FHIR® notifications for any of your connections.

HL7v2 to FHIR® translation is helpful for these use cases:

• Providers establishing a new patient’s history.
• Providers looking to power CRM, analytics, or operational dashboards.
• Vendors consuming patient data for service within their app.

For providers: You send patient, order, or scheduling data to Redox via HL7v2 feeds. Redox translates the data into a FHIR® notification, which we push to your connection.

For vendors: You establish what kind of patient, order, or scheduling data you want to receive from your connection. They set up HL7v2 feeds with Redox. We translate the data into a FHIR® notification, which we push to your system.

We translate HL7v2 data to FHIR® notifications to power Redox API actions like these:

• Listen for hospital admissions updates
• Listen for patient record updates
• Listen for scheduling updates
• Receive a request for patient monitoring
• Listen for vital sign updates
• Receive a request for patient enrollment
• Listen for outpatient prescription orders
• Listen for signed provider notes

We translate standard HL7v2 feeds into a detailed or lightweight FHIR® notification. Check out which HL7v2 event types we support below.