Background: Obstacles

Health.Asia needed to decrease their level of unproductive manual work in appointments and claims processing.


Automate the appointment process for doctors connected to the Health.Asia platform clinics.

Automate the processing of insurance claims.

Our solution

Step 1: Administrative data, appointments, and CD


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).


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


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.


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.


  • • 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.

More cases

Turbota app allows patients to store and use their or their loved ones’ medical data in one Health Wallet

Turbota. Personal Healthcare App

This app allows patients to store and use their or their loved ones’ medical data in one Health Wallet.


National eHealth 

Completed digitization of the Ukrainian healthcare system with over 36,5 million accounts and personal records numbering in the tens of millions.

Elation Case

Deploying a FHIR-Compliant Solution with a Custom Clinical Data Mapper

Edenlab created for Elation Health a solution that bridges the gap between their existing data standards and the FHIR requirements. Through Edenlab’s expertise and support, Elation Health successfully achieved ONC certification, implemented USCORE 5.0.1 support.


Building a FHIR Semantic Layer Analysis Platform

Industry: Healthcare

Country: US

Project type: Analytics Platform

Duration: Ongoing

Let`s chat

We would be glad to share more details about our enterprise-level FHIR software solutions and other cases based on the HL7 FHIR standard.

    Your form has been submitted successfully

    We will contact your shortly

    Kodjin White Paper

    Please leave your email to get Kodjin White Paper

      By downloading files from this site you agree to the Policy

      The Kodjin White Paper has been successfully sent to your email

      We have sent a copy to your email

      Back to website content