Knowledge center

Redox
Build the future: Redox fall update ’22

Redox update Fall 2022 Build (n): to form by ordering and uniting…

Redox
Hello, World!

Over recent weeks, it’s become increasingly clear that Redox needs a better place for our technical team to…

Request for stories: How has healthcare technology impacted you?

A lot of what we do here at Redox is driven by a simple sentence:…

How Redox supports medical device integration

Innovative medical devices are redefining what patient care can achieve. Beyond heart rate and blood pressure, you can…

Integration love triangle: Redox, applications, and health systems

With the often complex landscape of legacy EHRs and IT systems used at hospitals and clinics across the country,…

Working with EHRs and health systems

This webinar is designed to provide a high level overview of Electronic Health Records (EHRs,) including a rundown…

HTTP status codes: What they mean and how we use…

When using our API, you may sometimes run into HTTPS status codes.  Since status codes are an important…

Sending files through Redox

The Redox API is capable of exchanging patient data with EHRs in a variety of message formats. In…

How Redox works with DateTime values and time zones

Our engine connects and enables communication between organizations across the world. With part of that communication containing information…

A healthcare interoperability primer Part 1: HL7 and Jargon

Interoperability—it’s a buzzword, a marketing tool, and something that impacts the quality of healthcare. In this post I…

An interoperability primer part 2: Stylin’ and profilin’

In part 1 of this series, I gave a high-level overview of what HL7 is…

An interoperability primer Part 3: Nomenclature, vocabulary and terminology

In part 1 of this series I gave a high-level overview of what HL7 is and does. In part…

HL7v2: Hurdles to overcome (and how Redox helps)

HL7v2 has been in use for quite a long time in the healthcare industry. It powers much of…

Stay in the know! Subscribe to our newsletter.