1 of 12

EMERGING USE CASES

2 of 12

Reaching HIV Epidemic Control

Problem Statement

As many countries supported by the PEPFAR approach epidemic control, it is becoming clear that some of the remaining “last-mile” obstacles can only be addressed through the use of longitudinal patient-level data.

Emerging Use Case: Retention on care

By solving Lost to Follow-up (LTFU) issue i.e. the ability to intervene with patients who appear to be on a path toward LTFU for ongoing treatment needs.

    • Why: Increasing patient retention is critical because it reduces the risk of spreading HIV infection if the patient is engaging in unsafe sexual behavior, and it reduces the chance of the patient progressing to AIDS, which can result in an early death.
    • How: By identifying patients at risk of being LTFU requires timely analysis of patient visit schedules.

2

3 of 12

Reaching HIV Epidemic Control

Tactical approach: Understanding and addressing challenges in retention and LTFU requires engagement of multiple points of expertise including:

  • CLINICAL CARE: Ensure that any recommendations for addressing retention issues are aligned with other efforts to improve the quality of care along the clinical cascade.
  • SYSTEMS: Ensure that data collected and managed in existing systems, paper or digital, are described and implemented using standardized tools and data models and are appropriately staged based on a country’s current capability.
  • POLICY: Develop and identify the necessary policy, guidelines, and legal frameworks for critical issues involving patient confidentiality, data security, data sharing agreements, and related legal and legislative concerns.
  • DATA REUSE AND ANALYSIS: Data reuse and analysis: Ensure that the data systems support the ready reuse of data for a variety of purposes, such as monitoring and evaluation, improving the public health response, case surveillance, syndromic surveillance, and quality improvement initiatives.

3

4 of 12

Data Use Community- Engaging Multiple Expertise

4

5 of 12

Questions?

5

6 of 12

Uwe Wahser: openIMIS @ OpenHIE

6

05/11/2019

A global good for health financing operations

Uwe Wahser @ OpenHIE Community Meeting, Addis Abeba, 06.11.2019

7 of 12

What is openIMIS?

openIMIS is an

  • open source software for improving health financing operations by digitalizing the link between patients, providers and payers

Based on a

  • community of developers, users and implementers

With the joint mission to

  • increase and improve universal health coverage (UHC)

Uwe Wahser: openIMIS @ OpenHIE

7

05/11/2019

8 of 12

From MS IMIS to openIMIS

Uwe Wahser: openIMIS @ OpenHIE

8

05/11/2019

2012

IMIS for Tanzania CHF

by SwissTPH, �Exact Software,

MicroInsurance Academie

2014

IMIS Customization for Nepal

2013

IMIS Customization for Cameroon

2016

openIMIS Initiative

(SDC & GDC)

2018

openIMIS Community

Pilots in DRC, Chad

Various country assessments among them Cameroon, Rwanda

2017

openIMIS Master Version

(TZ+CM+NP)

2019

Modular Architecture Transformation & Community Building

2020

Continuous development & community Building

9 of 12

Slow Transition (Current Roadmap)

Uwe Wahser: openIMIS @ OpenHIE

9

05/11/2019

MS IMIS

Framework

openIMIS

Claiming

Facility Registry

(Module Y)

openHIE Integration

April 2019

October 2019

April 2020

Releases:

Claims Adjudication - AI

Indicator Dashboard

(Formal Sector Schemes)

10 of 12

Teams in Developers Committee

Uwe Wahser: openIMIS @ OpenHIE

10

05/11/2019

Continuity

Re-Architecture

Maintenance & Support

Modular Transformation

Digital Square Notice C1

SwissTPH

SolDevelo

BlueSquare

HISP India

SwissTPH

SolDevelo

Possible Health

Interoperability

Coordination Desk

GIZ

11 of 12

Integration into OpenHIE

Uwe Wahser: openIMIS @ OpenHIE

11

05/11/2019

BAHMNI

openIMIS

Odoo

OpenHIM

DHIS2

OpenMRS

OpenELIS

BlueSquare

SolDevelo

Possible Health

HISP India

OpenMRS

12 of 12

Vision: Integrated Workflows (e.g. Claiming)�

Uwe Wahser: openIMIS @ OpenHIE

12

05/11/2019

Insurance Mgmt

Insurance Adjudication

openIMIS

FHIR Data Store:�Hearth

Interop Layer:

OpenHIM

2

EMR:

OpenMRS

1

3

Client Registry:

Medic CR

5

Source: Carl Leitner @ AEHIN Conference 2018