Case Study
Custom Fhir Integration Engine
The Situation
A mid-sized EMR vendor was running on a 15-year-old monolithic Java architecture built around proprietary APIs and limited HL7v2 integrations. The ONC Cures Act Final Rule required FHIR-based patient data access — and the legacy system had no realistic path to compliance without a fundamental rethink.
The challenge was scope. This wasn’t a configuration project. It required rebuilding the integration layer of a production system used by real providers, without disrupting their operations, while delivering standards compliance against a regulatory deadline.
Deployed a production-grade HAPI FHIR Server on AWS with Auto Scaling — purpose-built for enterprise transaction volumes with the elastic capacity to handle growth without re-architecture.
Built full transformation pipelines converting legacy HL7v2 and C-CDA data to FHIR using XSLT — preserving existing data while making it available through standards-compliant APIs.
Defined FHIR profiles aligned to US Core IG with GraphQL for flexible querying and Apache Camel routes for live EMR database synchronization — delivering full US Core conformance validation at 12,000+ daily transactions.
Talk to an Onyx expert about a realistic path from where your systems are today to where regulations require them to be.
