Workflows Implementation

Workflows Implementation


Medic / CHT Feedback → openIMIS

https://openimis.atlassian.net/wiki/x/JIDDCAE

EMR / EHR – openIMIS interoperability

BAHMNI → openIMIS - eClaiming Workflow

openSPP Eligibility → openIMIS Enrollment

openSPP Eligibility → openIMIS Enrollment Implementation

MOSIP → openIMIS Insuree Information Collection Workflows

https://openimis.atlassian.net/wiki/x/cgDECAE

 


Master Facility List Sync → openIMIS Update

This workflow outlines how openIMIS can periodically synchronize with a national Master Facility List (MFL) to ensure that facility data used for insurance enrollment, claims processing, and benefit tracking remains up-to-date.

This MFL registry may expose a FHIR-based API (e.g., using Location, Organization, and Endpoint resources), and the workflow uses a scheduled background job within openIMIS .

Trigger

A scheduled task (e.g., every 24 hours) is initiated from openIMIS, requesting the latest MFL data.

Workflow

1. Trigger: Scheduled Task in openIMIS

  • A cron job is configured in the openIMIS environment to query the openHIM FHIR server.

  • Trigger interval: e.g., daily or weekly.

2. FHIR Request to openHIM

  • openIMIS sends a query like to openHIM:

    GET /fhir/Location?lastUpdated=ge{lastSync}

3. FHIR Request to MFL Registry

  • openHIM sends a query like to MFL :

    GET /fhir/Location?lastUpdated=ge{lastSync}

  • Response: A Bundle of Location resources, optionally accompanied by Organization (managing body) and Endpoint (service access info).

FHIR Resources Used:

Resource

Purpose

Resource

Purpose

Location

Physical facility (core data)

Organization

Managing entity

Endpoint

Digital service metadata

4. openHIM Mediator: Validation & Mapping

  • The openHIM facility mediator performs:

    • FHIR resource validation

    • Mapping of codes (e.g., national ID → internal UUID)

    • Deduplication check using cached openIMIS data

5. Push to openIMIS

  • Validated facility records are sent to openIMIS through:

    • FHIR API:

      POST /fhir/Location

6. Acknowledgment & Logging

  • openIMIS responds with status (201 Created, 200 Updated, or error codes).

  • openHIM logs:

    • Request-response details (traceable via the openHIM Console)

    • Failed entries for admin action

Diagram

LocationSyncWorkflow.drawio.png

 

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/