Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Held from the 17th-20th February 2026, openIMIS developers and community members from both public and private sectors met in the SAP Data Space in Berlin to network and develop new openIMIS functionalities.
This section is primarily intended for developers.
Before joining the hackathon, we recommend downloading the openIMIS modules on your computer. This will facilitate the developers training and the hackathon, and will reduce the likelihood of connection issues at the venue causing any delays or blockers.
Ideas were submitted over Mural and the most popular ideas will be prioritized during the event.
The 14 Ideas to Vote On:
Social Protection service builder with dynamic workflow
The Social Protection Service Builder provides governments with a flexible digital foundation to configure and manage social protection services, enabling policy-driven workflows, institutional accountability, and scalable program delivery.
Social Protection Service Builder: The Social Protection Service Builder is a configurable digital platform designed to support governments in the efficient design, implementation, and management of social protection programs. The platform enables authorized administrators to define and operationalize social services through configuration rather than custom software development, ensuring flexibility, scalability, and sustainability.
Configurable Service Design: The platform allows program administrators to design service-specific application forms by defining data fields, data types, validation rules, and conditional logic. This enables standardized yet adaptable data collection aligned with program policy and operational requirements.
Document and Evidence Management: Administrators can configure document requirements for each service, including the type, number, and format of supporting documents. Document requirements may be linked to specific stages of the application process or conditional eligibility criteria, supporting transparent and verifiable decision-making.
Workflow and Process Configuration: The Service Builder supports the configuration of end-to-end service workflows, including multiple processing steps, decision points, and approval mechanisms. Workflows may be sequential or parallel and can adapt dynamically based on application data, eligibility outcomes, or administrative decisions.
Task and Institutional Desk Management: The platform enables the definition of task management desks corresponding to institutional roles (e.g. intake, verification, approval, grievance handling). Tasks can be assigned to desks or user roles, supporting clear accountability, workload management, and service-level performance monitoring.
Lifecycle and Case Management: The Service Builder supports full service lifecycle management, from application submission to final determination and closure. It provides real-time status tracking, audit trails, and process transparency, strengthening governance and oversight.
Adaptability and Sustainability: By separating service configuration from core system functionality, the platform enables rapid adaptation to policy changes, program expansion, and new social protection initiatives. Reusable components and standardized processes reduce implementation time and operational costs.
Live Verification for Eligibility Assurance
The Social Protection Service applies live facial verification as part of the eligibility assessment process to support accurate determination of beneficiary entitlement and to reduce the risk of ineligible or erroneous benefit payments. Rather than serving solely as an authentication mechanism, live verification is used to validate program-specific eligibility conditions that require confirmation of an individual’s presence or status at defined points in the service lifecycle (e.g. application review, revalidation, or payment authorization). This supports enforcement of eligibility rules and strengthens assurance that benefits are provided in accordance with program policy.
The use of live verification contributes to:
Verification of beneficiary eligibility at critical decision points
Reduction of duplicate, proxy, or ineligible claims
Improved targeting accuracy and payment integrity
Enhanced fiduciary control over public expenditure
OCR based automated supporting document verification for social protection services
The Social Protection Service integrates an automated document verification tool utilizing Optical Character Recognition (OCR) to support eligibility assessment and program integrity. The tool extracts relevant information from uploaded supporting documents and cross-checks it against data provided in application forms.
This capability enables systematic validation of documentary evidence, reducing manual verification effort and improving the accuracy and consistency of eligibility determinations. The use of OCR-based document verification contributes to:
Reduction in processing time and administrative burden
Enhanced detection of inconsistencies between declared information and supporting documents
The system enhances the existing location management structure by transitioning from a fixed four-level geographic hierarchy to a configurable, multi-level (N-layer) location model. This approach allows governments to define and manage geographic structures that reflect national administrative arrangements and program-specific needs.
Under the enhanced model, administrators can configure any number of geographic levels (e.g. national, regional, district, sub-district, community, facility catchment, or other custom units) and establish parent–child relationships between them. This ensures flexibility in representing administrative boundaries across different sectors and programs.
The multi-level location framework supports alignment with country-specific administrative and governance structures
Central system-generated document printing component
The system introduces a standardized print rendering component to support consistent, reliable, and reusable printing of system-generated documents within openIMIS. The component provides a centrally managed print template that defines page layout, formatting, fonts, margins, and print behavior. Application developers are only required to pass the relevant content (e.g. a defined section of a screen or view) to the component, which then renders the content in a dedicated print window using the predefined template.
This approach ensures uniformity across printed outputs while reducing development effort and minimizing duplication of print logic across modules.
The standardized print component supports:
Consistent document layout and formatting across services and modules
Reduced development and maintenance complexity
Faster implementation of printable outputs
Welfare ranking formula builder
The welfare ranking formula is a formula that is used by many countries for the purpose of sorting households based on certain metrics and methodologies (e.g. PMT). The parameters involved in the formula should be dynamic and would different from one country to another. The purpose of the module is to allow the admins to create and manage the welfare ranking formula based on data and parameters available within the household scheme
Integration of customizable questionnaires for implementation specific datasets
Using bundle instead of contained resource in FHIR (more FHIR like)
Using min.io for attachment / document management
Documents might need to be share between several applica
External workflow manager for the task
every company have different workflow, supporting external workflow engine could help countries using a workflow engine they use in other context making openIMIS flexible to their needs
Using ICHI for service list (part on ICD-11 API)
coding service has many added value, WHO has created a API for the ICHI-11 coding that enable more than just simple coding for service ; ICHI-11 coding tool support text search, uid coding, …
such integration would enable openIMIS to use WHO codding tool
Using ICD-11 API for the diagnosis
coding diagnosis has many added value, WHO has created a API for the ICD-11 coding that enable more than just simple coding for diagnosis; ICD-11 coding tool support text search, uid coding, …
such integration would enable openIMIS to use WHO codding tool
FHIR/DCI Remote Connector for External Registries
Create core classes to GET/POST FHIR / DCI resources from remote systems and map them into OpenIMIS. This fills the gap where OpenIMIS must actively fetch data (e.g. MPI patients, farmer registries), not just expose its own FHIR endpoints.
FHIR API Gateway for openIMIS
Introduce an API Gateway to expose and manage existing OpenIMIS FHIR endpoints. This would centralize access, improve security and interoperability, and make it easier for external systems to consume OpenIMIS FHIR APIs consistently.
Centralized security Enforce authentication, authorization, and token-based access (OAuth2 / JWT) independently from OpenIMIS user accounts.
Access control & role separation Avoid exposing full OpenIMIS credentials to external systems; grant scoped access only to specific FHIR resources and operations.
Rate limiting & abuse protection Prevent unlimited calls to FHIR endpoints, protecting OpenIMIS from overload or misuse.
IP filtering & network policies Restrict access to trusted IP ranges or networks (e.g. national platforms, MPI servers).
Audit & monitoring Track who accessed which FHIR resource, when, and how often — critical for compliance and debugging.
Did you encounter a problem or do you have a suggestion?