Adapting openIMIS for Advanced Healthcare Protocols: Complex Products
Content
Page Metadata
Field | Details |
|---|---|
Title | Adapting openIMIS for advanced healthcare protocols: Complex Products |
Keywords | Complex Products, Health Insurance, Clinical Protocols, Product Configuration, UHC, openIMIS, Cameroon Case Study |
Related Pages | Country implementation: https://openimis.atlassian.net/wiki/spaces/OP/pages/3650060289 https://openimis.atlassian.net/wiki/spaces/OP/pages/3230924846 User Manual: https://openimis.atlassian.net/wiki/spaces/KB/pages/3623747892 https://openimis.atlassian.net/wiki/spaces/KB/pages/3623846010 https://openimis.atlassian.net/wiki/spaces/KB/pages/3623747942 https://openimis.atlassian.net/wiki/spaces/KB/pages/3623878810 https://openimis.atlassian.net/wiki/spaces/KB/pages/3623747754 https://openimis.atlassian.net/wiki/spaces/KB/pages/3623878742 |
Related document |  |
Other languages available | Français : https://openimis.atlassian.net/wiki/spaces/OP/pages/4761387009 |
1. Executive Summary and Strategic Vision
The introduction of Complex Products in openIMIS represents a shift from simple administrative fee-for-service management to a system centered on clinical protocol quality . openIMIS is an open-source solution designed to facilitate Universal Health Coverage (UHC) by providing a platform that is adaptable and aligned with international health standards.
Why Move Beyond "Standard" Configuration?
In a standard configuration, the system functions as a digital photocopy of defined procedures where prescribers select individual items and services. However, practical implementation has revealed specific challenges:
Total physician flexibility: Prescribers can add any number of services and items, leading to risks of over-prescription and validation errors.
Frozen maximum quantities: Standard limits are often static and do not adapt to the specific type of service or patient profile (e.g., adult vs. child).
Protocol non-compliance: Standard setups struggle to account for specific treatment packages like pregnancy interventions or complex surgeries.
2. The Conceptual Framework of Complex Products
A Complex Product is defined as a health insurance product that bundles healthcare services (procedures) and medical items (drugs/consumables) into a single package. It integrates specific rules such as age and sex limitations, and quantity ceilings based on mandatory care protocols.
The Three Pillars of Configuration
Successful configuration of a Complex Product relies on the interaction of three dimensions:
Definition of Care: A structured service package including consultation, analysis, examinations, and medical inputs.
Normative Protocol: National clinical guides specifying mandatory medical procedures and administration sequences.
Program Coverage Rules: Eligibility and limitation criteria based on age, pathology, or program-specific budget ceilings.
3. Setting up a Complex Product
3.1. Fundamental configuration elements
To successfully set up a complex product, three core elements must be defined:
Product Name and Identification: Clear naming based on the medical intervention (e.g., "Standardized Caesarean Section").
Treatment Protocol: A predefined and specific list of medical services (e.g., surgery, anesthesia) and medical items (e.g., medicines, devices) that constitute the care package.
Rules and Restrictions: Integration of specific constraints such as maximum quantities per input, age/gender discrimination, and coverage ceilings.
3.2. Technical Implementation Workflow
Setting up a complex product follows a rigorous data flow to ensure system consistency.
Workflow
Workflow description
openIMIS Component | Description | |
|---|---|---|
| 1 | Medical Inputs | Define all drugs, medications, and consumables (names, codes, and base prices). |
| 2 | Medical Services | Define all healthcare services and interventions (e.g., consultations, surgical procedures) |
| 3 | Complex Product Assembly | Bundle specific inputs and services into a named protocol (e.g., "Standardized Caesarean") |
| 4 | Pricelists | Define applicable medical services and items for different categories of Health Facilities |
| 5 | Care Packages / Policies | Define duration, validity, and conditions for beneficiaries to access the product |
| 6 | HF Assignment | Assign adapted price lists to corresponding Health Facilities (e.g., Dispensary vs. Hospital) |
3.3. Clinical Workflow in Health Facilities (HF)
Once configured, the behavior of the system at the point of care changes significantly compared to classic products:
Constrained Selection: When a patient arrives, the provider selects from a predefined list of services and items within the complex product protocol.
Automated Validation: Choices are restricted by the system’s rules (maximum quantities, mandatory procedures), which limits prescription errors and facilitates immediate claim control.
Protocol Compliance: The provider enters the quantities used, and the system validates the claim against the predefined "Standardized Care" package.
4. Practical case study: Cameroon implementation
The Cameroon pilot demonstrates how complex products optimize resources through two distinct logic types :
Variable Complex Product | Fixed Complex Product |
|---|---|
This model allows for clinical flexibility while controlling abuse through Maximum Quantities. | This model ensures a standardized minimum care package via Default Quantities. |
|
|
5. Key Benefits and Lessons Learned
5.1. Advantages for UHC schemes
Strengthened Control: Reduces inappropriate prescriptions and abuse through automatic validation of predefined rules.
Quality Improvement: Aligns health facilities with national standards, ensuring every patient receives essential inputs.
Resource Efficiency: Defines maximum quantities to reduce waste and optimize costs.
Better Traceability: Facilitates clinical studies and monitoring by evaluating the gaps between field practice and theoretical protocols.
5.2. Lessons from the Implementation Phase
Testing is Essential: Regardless of the configuration type, thorough testing is required to ensure accuracy and compliance before deployment.
Role Management: While central administrators should prioritize configuration, delegating certain updates to other levels can be done without compromising security.
Continuous Coaching: Successful implementation requires monitoring, evaluation, and continuous coaching of actors.
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/