FHIR R4 handler for claims and insurance

Hi @dkayiwa @ibacher I’m trying to consume and make the fhir r4 bundles of claims and insurance available at NDHM.IN\NHCX Profiles - FHIR v4.0.1 . Is the fhir2 module capable of doing that?

The FHIR2 module translates OpenMRS concepts into FHIR and vice-versa. There are no standardised model for storing the data in those insurance resource in the OpenMRS data model, so there is no pre-built functionality that will do that. However, the FHIR2 module is extensible, so if you define how to store those FHIR resources in an OpenMRS-like data model, you should be able to add those capabilities to the FHIR2 module via a separate module.

1 Like

Hi @ibacher Thank you for the information.

However, the module GitHub - openmrs/openmrs-module-insuranceclaims: For checking patient insurance enrolment on registration (in external Insurance Management Information System) status and submitting claims (managing patient billing), I’m trying to use this for the claims but it supports only dstu3. Is there any other module available for the fhir R4 versions or can it be changed to support R4?

It could be update to support both DSTU3 and R4; there’s no reason that it can only support one module. However, that module is designed to work the the old FHIR module and is likely not compatible with FHIR2 at least without further modifications.

Hi @ibacher ,

I’ve been trying to modify the insurance claims module for my requirements. There is a function - BaseOpenMRSDataUtil.readBaseExtensionFields(BaseOpenmrsData openmrsData, DomainResource fhirResource);

It is available in fhir module and used to initialise base openmrs data in the object. Is there a similar function available in fhir2 module which I can use?

No. In general, in FHIR2, we haven’t yet found a need to communicate the properties that that writes in general and where we have (e.g., for observations), we map them to appropriate fields in the standard FHIR data model, that is, we don’t use those extensions in FHIR2 at all, so there’s no method to create them.

There is a utility method to help populate the meta.lastUpdated property for each resource which we use like this: https://github.com/openmrs/openmrs-module-fhir2/blob/f3f33567f9da236d6738b347c7176516bb8631c5/api/src/main/java/org/openmrs/module/fhir2/api/translators/impl/MedicationRequestTranslatorImpl.java#L124C1-L125C69