FHIR for Redox

A scalable telemedicine solution made to decrease the complexity of EHR integration.


FHIR for Redox

FHIR, Redox, Kotlin, HAPI library

Health Tech Skills - Case Study Icon

Interoperability and Data Quality Management

Technology and Tech Stack - Case Study Icon

2 Months

Project Duration - Case Study Icon


Our client was a healthcare provider with more than 4.5 million clients. They provided their patients with personalized healthcare and doctor matching services. They did this over the phone, with call centers and dozens of people answering phone inquiries. Our client needed a more effective IT solution that would allow seamless connectivity and uninterrupted healthcare delivery.

Based on the FHIR standard, our solution sought to connect seemingly disparate EHR systems. Our client needed a quick way to communicate information to and from their partner networks, which often used incompatible EHRs. Seamless connectivity between these systems was necessary for the fast and precise delivery of healthcare services.

Therefore, our client asked us to set up an IT infrastructure to make their communication more efficient and interoperable.

Case Study, FHIR for Redox, Diagram


Vicert worked with our client to implement the FHIR standard on top of the Redox data exchange system.

Our client’s exchange system allowed them to collect data from multiple sources and store it in a unified format for further exchange. Our job was to develop a telehealth solution that would allow said data to be exchanged further. We’ve accomplished that by implementing FHIR API, allowing communication with out-of-network partners.

Our job was to make the selected data models, which our client labeled as the most important ones, interoperable as resources.

Vicert started by identifying 20 of such resources and fully defining 14 custom extensions that correspond to Redox Clinical Summary and Notes data models. Once we’ve completed the mapping, we’ve also implemented a Service Adapter that made the conversation on the fly.

The adapter was set up in a scalable manner so that it supported other data models in either JSON or FHIR. We’ve created it as a stand-alone Spring Boot application, leveraging the HAPI library and the Retrofit REST client.


Through our solution, our client was able to eliminate call centers, effectively spawning a number of benefits:

  • Cost reduction: eliminating call centers resulted in a drastic decrease in our client’s expenses.
  • Because of the scalable nature of our solution, its application went beyond this project and was helpful to our client in years to come.
  • Based on our FHIR solution, our client achieved seamless connectivity and increased the speed and efficiency of their healthcare delivery.