Translating HL7v2 to FHIR

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

It came out of a “meeting of the minds,” but maybe most prominently from the mind of Donald Simborg, who was CIO of University of California, San Francisco Health System (UCSF Health) at the time. In 1981, he connected four microcomputers to a network to exchange transitions between the UCSF registration system, clinical laboratory, outpatient pharmacy, and radiology systems.

Living in Silicon Valley, Donald thought he could make a business out of it and founded STATLan. He struggled to get traction and had the idea to boost his business by developing a non-proprietary healthcare standard. He gathered several influencers, and with that, HL7 was born. HL7v2.1 was first implemented in production in 1990 and there's been little stopping it since.

HL7 estimates that 95% of U.S. healthcare organizations use HL7v2. Whether you're a health tech vendor or healthcare organization today, it's likely that you're touching HL7v2, or that you should be.

Redox can benefit customers on any side of the HL7v2 data exchange, including:

• healthcare organizations establishing a new patient's history;
• healthcare organizations looking to power CRM, analytics, or operational dashboards; or
• health tech vendors consuming patient data for service within their app.

For healthcare organizations: You send patient, order, or scheduling data to Redox Nexus™ via HL7v2 feeds. We translate the data into a FHIR® notification, which we push to your connection.

For health tech 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 Nexus. We translate the data into a FHIR® notification, which we push to your system.

Either way, you can send and receive HL7v2 data as FHIR® notifications with Redox API actions like these:

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