DISI Reference Solution
This solution demonstrates two reference implementations to support data centralization and reporting, one for HIV case-based surveillance (CBS) and another which combines HIV CBS, HIV Program Monitoring and Patient Care Coordination and COVID19.
Code Repository
Core problem
There is a need for countries to centralize and report on data that is captured at the point of service systems to effectively measure and monitor the progression and outcome of HIV through case-based surveillance (CBS) sentinel events.
Commonly this is done ad hoc per country. DISI refers to the practice of centralizing and integrating HIV case-based surveillance data in a central repository for further reporting, analysis, and visualization.
DISI proposes to create a standards-based architecture that would allow multiple countries to adopt a similar framework for generating the reports that they require.
This would drive the re-use of components and allow countries to rapidly make progress based on what others have done before.
In addition, there is a need to measure and monitor individuals diagnosed with COVID19 and their status towards being up-to-date vaccinated.
All these links need to be updated to new product pages in the products database. Zane can help with this.
- Just add the links to latest document first.
- Then work on the user-centric pages for each product.
DISI Architecture
The following document describes the DISI architecture in detail as well as describes the set of technologies used in the DISI Reference solution.
The description of the conceptual architecture is the most important piece of information to read to gain an understanding of what the DISI architecture can provide.
There is a variety of additional documentation that is available if you would like to deep dive into the system specifications and the details of how everything works together. The following document help to provide those additional details:
Additional References
This document outlines the functionality needed for program management and patient care coordination.
- Descriptions of necessary components are not limited to specific technologies and implementations.
- These components together achieve the goal of integrating data from multiple sources while ensuring the availability of quality data in a manner that ensures privacy, security, and confidentiality.
HIV Minimum Datasets
The minimum dataset specifies the data points needed per sentinel event needed for CBS. Like the sentinel events, this dataset is the absolute minimum required and a good starting point for a CBS system. Countries may wish, and in many cases do, expand the minimum dataset to a more appropriate list meeting their use case.
HIV Program Monitoring and Patient Care Coordination
This dataset includes the necessary data points to support the program monitoring and care coordination use case.
COVID19 Minimum Datasets
Monitoring COVID19 Cases and Their Immunisation Status
This dataset includes the data points needed to monitor an individuals progress towards being up-to-date vaccinated. In addition, this dataset makes reference to key data points as defined by the HIV CBS minimum dataset to track COVID 19 cases within the HIV population.
FHIR Mapping
These spreadsheets map their minimum dataset data points to FHIR resources.
HIV Program Monitoring and Patient Care Coordination Initial
HIV Program Monitoring and Patient Care Coordination Extended
Functional and Non-Functional Requirements
The requirements specification document describes the DISI reference solution that is intended to specify and track the necessary information required to effectively define business, functional, and non-functional requirements to establish a CR and DR for HIV CBS, Patient care co-ordination and Program monitoring.
This document outlines the processes for patient matching and linking for the DISI Reference solution. The business processes are described using process flow diagrams.
This document describes:
- Data exchange processes and workflows,
- Bidirectional transactions between the components
- Boundaries of each system and their interaction.
Includes standard messaging formats with a recommended standard for the DISI Reference solution.
This document describes the technical solution designed for the DISI Reference solution to support the HIV case based surveillance use case. This is in line with the OpenHIE framework. The solution includes the high level patient record data structure on the Data Repository (DR) and how it is combined with the Client Registry (CR) data to be used for later analysis, reporting and visualization. Included is how the data from different source systems is managed so that a single longitudinal record is considered.
HIV Requirement Specifications
Analytics and visualisation specificationsThis document specifies case-based surveillance trends and outcomes typically by demographics or region, all geared towards informing the HIV epidemic. Dashboards are developed with this in mind and provide visual representations of this information.
Report Specifications
COVID19 Requirement Specifications
Analytics and visualisation specifications
Report Specifications
Integration documentation
There are two Implementation Guides, one for COVID and one for HIV.
HIV Implementation Guide
For details on how to integrate with the DISI HIV solution, see the FHIR Implementation Guide (IG) that has been created. It describes the message formats as well as the API endpoints to be used.
Postman Collections
Postman is an application that will allow you submit HTTP requests such as POST, PUT, GET, DELETE etc.
Postman collections are provided as an example of how to interact with the DISI Solution.
COVID19 Implementation Guide
For details on how to integrate with the DISI COVID solution, see the FHIR Implementation Guide (IG) that has been created. It describes the message formats as well as the API endpoints to be used.
For more information on how to submit data to the CDR, please refer to our Technical Documentation:
Once you have submitted messages to the CDR using Postman, you should be able to:
- View the transaction in the OpenHIM
- View the newly created patient in SanteMPI
- See the figure change in the HIV Dashboard in Kibana (HIV Only)
- See the figure change on the report in jsReport (HIV Only)
- See a data entry in Superset’s ClickHouse database (COVID19 Only)
Reference Implementation Technologies Used
- SanteMPI
- OpenHIM
- HapiFHIR
- FHIR
- jsReport
- Elastic stack
- Instant OpenHIE
- Superset
- Clickhouse
Solution Demonstration
HIV CBS Component URLs and Credentials
Component | Purpose | Username | Password | Link |
Kibana | Explore data, view live dashboards | elastic | dev_password_only | |
jsReport | Generate specific reports | admin | dev_password_only | |
SanteMPI | View client registry records and manage patient matches and links | Administrator | Mohawk123 | |
OpenHIM | View incoming transactions and history | root@openhim.org | instant101 |
HIV & COVID19 Packaged Component URLs and Credentials
Component | Purpose | Username | Password | Link |
Kibana | Explore data, view live dashboards | elastic | dev_password_only | |
jsReport | Generate specific reports | admin | dev_password_only | |
SanteMPI | View client registry records and manage patient matches and links | Administrator | Mohawk123 | |
OpenHIM | View incoming transactions and history | root@openhim.org | instant101 | |
SuperSet | Explore data, view live dashboards | admin | admin |
Key Technical Documentation
For information about how to setup the reference solution including other technical details, please review our DISI on Jembi Platform technical documentation for:
- HIV → DISI on Platform
- COVID19 -> CARES on Platform
Both of the aforementioned solutions are built as extensions to the Jembi Platform which provides a toolbox consisting of number of components which have been packaged such a way, that they can be easily deployed and scaled together.
For more information see the Jembi Platform docs.
Capacity Development/Support Documentation
MPI
Technical
- Docker & docker swarm: Meeting Recording
- Introduction to docker and docker swarm
- How to create and use a new FHIR Implementation Guide
Interoperability
- Interoperability Layer assessment process documentation
- Tool(s) for Interoperability Layer assessment - Rwanda specific
Data & Analytics
- Introduction to Logstash
- Logstash: Pipeline development technology
- Elasticsearch & Kibana: Component level explanations
- Elasticsearch & Kibana: Meeting Recording 1
- Elasticsearch & Kibana: Meeting Recording 2
- Elasticsearch & Kibana: Dev Tools to support debugging
- Introduction to JSreport
- JSreport: Meeting Recording
- JSReport: Steps to build reports
Backup & Disaster Recovery
Requirements Specification
Testing
Training
Community Pages
Content will be added when available.
Technical issue? Let us know