As your healthcare application grows data management becomes a challenge. The firehose from healthcare data APIs introduce complexity that isn’t seen in other systems. Message volumes and payload sizes vary wildly, FIFO processing is often critical but very challenging, and patient record duplication and identifier inconsistency is all too common. In addition, both the quantity of data and the need to scale across a number of health systems introduces major challenges.
In this talk Redox Engineering Team Lead Tristan Wilkinson will review these complexities and demonstrate solutions that any developer can use in their own application. By watching you will learn:
how workflows send different patient data depending on their system of origin,
the complexities of ingesting, processing and storing health care data,
an architectural approach for scaling a system in data intensive health care applications.
X12 standards are complex and inflexible for developers who are used to working with modern API resources. It is nearly impossible for every organization to have sufficient internal X12 expertise to deal with these transactions at scale.
Redox’s X12 to FHIR capability is a solution for developers looking to optimize their payer/provider administrative workflows without becoming experts in X12.
Engineering
Distributed Cache for Highly Available Local Representations of Remote Bounded Context Data
October 13, 2021
The need for a Distributed Cache As our products have evolved from monolithic services to microservices, sharing data…
Engineering
Infrastructure
Event Driven Architecture with Kafka and RabbitMQ
September 20, 2021
With the continuing journey towards microservice architectures, Event-Driven Architectures have become highly popular. Its flexibility is rooted in…