FHIR for Redox

A robust and scalable solution resolves the complexity of integrating different EHR systems


Our client is a healthcare provider serving more than 4.5 million members.

They provide personalized healthcare recommendations to their members, as well as doctor matching services for finding the best in-network care providers. They do this by combining a variety of health IT technologies and specialized care teams in call centers, ready to answer phone inquiries.

Seamless integration with a wide variety of different EHRs used by their partner network is important for providing quick, precise and personalized care to their members.

Our client was looking for an efficient way to implement medical information exchange routes between multiple, often incompatible EHR systems.




Vicert worked with the client on implementing a FHIR interface on top of the Redox data exchange system. 

Redox enables our client to collect medical records from different sources and compile them into a unified format. A FHIR layer on top of it enables further data exchange with out-of-network partners downstream. 

The goal of the project was to analyze and transform selected Redox data models, identified as the most important to the client, into FHIR resources.

Vicert identified 20 FHIR resources and fully defined 14 custom extensions that correspond to Redox Clinical Summary and Notes data models. 

Once the mappings were documented, Vicert implemented a Service Adapter component that does the conversion on the fly.

The Service Adapter is a stand-alone Spring Boot application, which leverages the HAPI library and the Retrofit REST client.

The adapter was built in a scalable manner so it can be extended to support other Redox data models in either JSON or FHIR formats, and also to enable our client to push the data to the provider groups in addition to “just” reading it.



By combining the robustness and connectivity of Redox with the standardization of FHIR, our client gained an efficient solution that resolves the complexity of integrating disparate EHR systems.

This solution provided additional data exchange with out-of-network partners downstream.

Most important Redox data models are transformed into FHIR resources.

The scalability of the adapter provides support for other Redox data models in multiple formats.