The following document describes the DISI architecture in detail as well as describes the set of technologies used in the DISI MVP to create the 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:

Key DISI components

This document describes the components of the HIV CBS system, from a programmatic perspective. 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.

Minimum dataset

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.

FHIR Mapping spreadsheet

This spreadsheet maps the minimum data set to FHIR resources

The requirements specification document describes a minimal viable product (MVP) 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 CBS data.

This document outlines the processes for patient matching and linking for the DISI MVP. The business processes are described using process flow diagrams.

This document describes the data exchange processes and workflows, the bidirectional transactions between the components and the boundaries of each system and their interaction.  In addition, standard messaging formats are included with a recommended standard for the DISI MVP.

This document describes the technical solution designed for the DISI MVP 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.

This document describes the technical patient matching patterns, detailing the creating and updating of new HIV case report data as well as how to resolve possible duplicate records by linking and unlinking records.

The purpose of this document is to outline the use cases for all the components of the DISI MVP.

This 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.