Engineering


Redox Behind the Curtain: Weekly Product Demo and Q+A

March 29, 2021

Redox recently introduced weekly Friday demos of our platform. It’s a space where we offer a look into…

What is HL7 FHIR?

January 20, 2021

There’s a lot of great information on FHIR for developers; however, there isn’t enough help for the…

Ingesting, Processing and Storing Healthcare Data

September 2, 2020

As your healthcare application grows data management becomes a challenge. The firehose from healthcare data APIs introduce complexity…

Want to join the Redox Engineering team? Read this first.

March 13, 2019

Joining a new company is almost always a leap of faith. You never really know what life will…

5 reasons why you shouldn’t do direct-to-database EHR integrations

March 7, 2019

Inside the children’s hospital, the halls were bustling with activity. Providers were rounding, kids were trying…

Enjoying our blog?  Check out our whitepapers!

Learn how we provide the fastest, most cost effective healthcare data sharing between vendors and provider organizations.

A day in the life of a healthcare developer attempting to use Redox

December 17, 2018

Today, I’m building a simple patient demographics web application using C# .NET, MVC5, and Web API 2.0. All…

The Elusive Healthcare Software Developer

August 1, 2018

In mid-July Luke, Terell and I attended the AWS Summit in New York. I gave a…

Pager anti-patterns and heuristics for successfully automating pages

June 5, 2018

At Redox we have been using PagerDuty for almost the entire history of the company. The ability to…

A Method to the Data: Plurality of Concerns part II

March 28, 2018

At Redox, we have embarked on tackling a huge problem: interoperability. I’m stealing the title of one…

5 reasons you should send developers to HIMSS

February 26, 2018

Niko recently wrote a great article about Redox’s vision Supporting the Human Connection in Healthcare. One image…

How to Do Microservice Chassis and Microservice Scaffolding on a Budget

December 14, 2017

At Redox, we're taking a pragmatic approach to building microservices, especially in how we handle cross-cutting concerns. Most refer to this part of a microservice ecosystem as the chassis—things that every microservice needs to have in order for us to be confident that it's a quality product. The chassis includes: