Bild
News header
News

Connecting hospital records to health insurance records in Nepal using FHIR R4

 

Many low- and middle-income countries have introduced electronic medical or health record systems (often referred to as EMRs or EHRs), making it easier for health facilities to record, store and access patient information. 

In countries where health services are financed through health insurance, information recorded in these systems is also needed by insurers to process claims and reimburse health facilities. Yet electronic hospital information and health insurance systems are often unconnected, requiring staff to enter the same information several times. This creates additional work and increases the risk of transcription errors, incomplete information and rejected claims. It also contributes to delays in reimbursement by insurers, which can lead to liquidity problems for health facilities. 

In Nepal, a new integration between NidanEHR and openIMIS is helping to bridge this divide. NidanEHR brings together the electronic systems used to record and manage different aspects of patient care, while openIMIS is used by Nepal’s Health Insurance Board and Social Security Fund to manage health insurance and other social protection programs, including disability and accident insurance. By connecting the two, information can pass directly between the hospital and the insurance system, bringing insurance processes into the hospital’s existing digital workflow.  

This was the focus of the September openIMIS Bhela community meeting, where Dipak Thapa of Trigonal Technology and Sunil Parajuli of Tinker Technologies demonstrated how the integration works in practice – following an insured patient from registration and eligibility checking through treatment to claims submission and review.  

Following an explanatory presentation by Sunil, Dipak used the openIMIS sandbox – a testing environment where developers and implementers can explore how an EHR or other external system can exchange information with openIMIS, without connecting to a live health insurance system – to take participants through the patient journey, illustrating how the two systems work together. 

Underpinning the connections is FHIR R4, an international standard that enables different digital systems to exchange information in a consistent and structured way. Through this standardized exchange, the hospital system can identify an insured patient, check their eligibility and benefits, retrieve the insurer's list of covered services and medicines, submit a claim and receive information on the outcome of that claim. 

Nepal provides a particularly useful setting for demonstrating this kind of interoperability. FHIR is already used by NidanEHR to connect the different digital systems involved in managing patient care in Nepal – clinical records, laboratory, pharmacy, imaging and billing – while openIMIS provides the platform for the national health insurance scheme managed by the Health Insurance Board.

The integration is also particularly relevant in settings where hospitals work with more than one health insurance scheme, each with its own coverage and rules. In Nepal, for example, formal sector health insurance (including for migrant workers) is provided through the Social Security Fund of Nepal, with different rules and levels of coverage from those of the Health Insurance Board, which provides the national social health insurance scheme.

NidanEHR draws on the same coded diagnoses (using ICD-11) and catalogue of eligible medicines and services used by each insurance program, allowing clinicians to see what is covered and helping to ensure that claims include only eligible items and remain within each scheme’s specific limits (such as price and quantity caps). As the presenters stated during the Bhela meeting, “the claim never asks for more than the system allows”.

The openIMIS sandbox provides an opportunity for other EHR developers and implementers to test their own connections to openIMIS, explore different insurance and claims scenarios and identify where adaptations may be needed for different country contexts. The Nepali team is inviting the openIMIS community to test the integration, share their own claims workflows and use cases, and help strengthen the approach for wider adoption.