HEALS.ASIA

About the project
One of the largest TPAs in Hong Kong challenged the Edenlab team to switch to a modern FHIR architecture. The project was built on top of the Edenlab Kodjin FHIR server and terminology service
TASK
Background: Obstacles
Health.Asia needed to decrease their level of unproductive manual work in appointments and claims processing
Challenges
automate the appointment process for doctors connected to the Health.Asia platform clinics
automate the processing of insurance claims
PROCESS DESCRIPTION
Step 1: Administrative data, appointments, and CD
Challenges
to expose the provider directory FHIR API (search facilities, search in practitioners by name or specialty), as well as the appointments FHIR API (book an appointment, check in, etc.), for a third-party mobile application
to collect the clinical data from two separate EHR systems, connected to the TPA, in the centralized clinical data repository (CDA)
Solutions
For the first set of functionalities, an FHIR facade implementing extract-transform-load from the client’s proprietary data in real-time was developed based on the Edenlab Kodjin FHIR server. Our team created custom profiles corresponding to the proprietary data with all the relevant terminologies
The appointments module was developed from scratch with the FHIR-first approach with custom FHIR profiles and a custom business logic layer
Custom profiles were created, and the terminology service was configured with the custom terminologies. A pseudonymization technique was used to protect the patients’ clinical data
Step 2: Financial data and auto-adjudication engine
Challenges
to standardize the financial API consumed by various providers connected to the TPA: all the main workflows from the FHIR financial module should be exposed as FHIR operations
to automate these workflows from the TPA side, i.e., to introduce the auto-adjudication engine that was able to generate the eligibility responses and claim predetermination responses based on the insurance plan data and the history of claims
Solutions
The solution was a hybrid FHIR/non-FHIR application. While all the data that was exchanged was stored in the FHIR server, for the insurance plan the complex structure enabling the auto-adjudication logic was implemented. The engine itself was designed as a framework, so new limits and constraints could be added in the future.
Results
- The provider directory FHIR API was implemented on top of the existing data and processes. The appointments FHIR API for a third-party mobile application was implemented. The mobile application was successfully connected to the FHIR API
- FHIR-based claim exchange module, powered by the auto-adjudication engine, was implemented
Read our last articles
Let’s chat
We would be glad to share more details about our enterprise-level solutions and other cases based on the FHIR standard
Schedule demo
We will share all details about our enterprise-level solutions and other cases based on the FHIR standard
Thank you!
KODJIN WHITEPAPER
Please leave your email to get Kodjin White Paper.
By downloading files from this site you agree to the Policy