The Challenge
The payment platform needed to exchange data with a growing number of EHR systems, each with its own formats, authentication and API behaviour. Vendor-specific logic accumulated across the codebase, making maintenance costly and expansion slow, and because balance retrieval depended on live calls, response times followed third-party availability.
Each EHR integrated as its own build.
Vendor-specific code spread through the codebase.
Response times tied to external system availability.
Transient failures leaving payments partly posted.
Approach & Solution
smartData built a Java middleware platform sitting between the payment application and the EHR estate, exposing one unified API regardless of the system behind it. Vendor-specific behaviour is abstracted into an integration layer, so adding an EHR means implementing an adapter rather than modifying any downstream code.
Data exchange is standardised on FHIR resources, giving a consistent clinical and demographic schema across every connected system. A caching layer with fallback holds recently retrieved balances so routine lookups return in seconds and stay available during upstream outages, with retry logic maintaining consistency.
Key Features
One interface regardless of the system behind.
A consistent schema across every connected system.
Lookups served during upstream provider outages.
Transient failures recovered rather than silently dropped.
Product Showcase
Final Outcome
Adding an EHR is an adapter rather than a rebuild, payment lookups return in seconds and survive upstream outages, and every synchronisation leaves an audit trail that makes discrepancies reconcilable.
