DHIS2 to DIGIT Integration
Integration & Interoperability with DHIS2:
https://dhis2.org/integration/
Basic features
Data Capture
Validation
Analysis
Presentation
Points to explore
SDMX-HD and ADX standards for interoperability
SDMX: https://ec.europa.eu/eurostat/web/sdmx-infospace/trainings-tutorials
ADX: Aggregate Data Exchange
Modules of concern
DHIS2 Web API
DHIS2 Core
How can we use it?
It exposes REST API(s) over DHIS2 Core which we can utilise.
Web API Integration
https://docs.dhis2.org/en/full/develop/dhis-core-version-master/developer-manual.html
Authentication
DHIS2 provides Basic Auth, Two Factor Auth, Personal Access Token(PAT) and OAuth2. Basic Auth is the least secure and Two Factor Auth is for direct DHIS2 users.
PAT
By default PAT will have all the authorizations that the user has. This can be configured or a special user can be created having only the required permissions.
The token is configurable via API and only the constraints can be modified after a token is created.
Token key is returned only once when the token is generated.
Expiry of the token can be configured via Web API along with other constraints.
OAuth2
We can go with grant_type as password. This can be configured via Web API too. Grant_type password would involve sharing username and password. However, this will be in a POST call body.
Login Credentials
http://43.205.92.152/dhis-web-commons/security/login.action
User: admin
Pass: district
DHIS2 Fields and Mappings
List of the metadata which are required and there attributes
Note this data is extracted from the schemas endpoint of DHIS2
DHIS2 is District Health Information Software 2.
Some Details
The DHIS 2 is a routine data based health information system which allows for:
data capture,
aggregation,
analysis, and
reporting of data.
Data Model
The data model is generic in all dimensions in order to allow for capture of any item of data.
The model is based on the notion of a DataValue.
A DataValue can be captured for
any DataElement (which represents the captured item, occurrence or phenomena),
Period (which represents the time dimension), and
Source (which represents the space dimension, i.e. an organisational unit in a hierarchy).
Meta Data | Understanding on this | Remarks |
DataSet | The DataSet is a collection of DataElements for which there is entered data presented as a list, a grid and a custom designed form. A DataSet is associated with a PeriodType, which represents the frequency of data capture. | This is what is a campaign as per current understanding |
Data Element | Basically a Form Field | The data element often represents a count of something, and its name describes what is being counted, e.g. "BCG doses given" or "Malaria cases". |
Data Element Group | Group of Data Element |
|
Indicator | Allows for data analytics and reporting. It is basically output of data capture. An Indicator is basically a mathematical formula consisting of Data Elements and numbers. The formula is split into a numerator and denominator. |
|
IndicatorType | An Indicator is associated with an IndicatorType, which indicates the factor of which the output should be multiplied with.
A typical IndicatorType is percentage, which means the output should be multiplied by 100. |
|
OrgUnit | Source or manageable area under which the data is captured |
|
Category |
|
|
METADATA Diagram taken from the DHIS2 technical documentation
The diagram is taken from the core technical documentation for understanding the relationships between the DHIS2:
While adding dhis2 client https://github.com/dhis2/dhis2-java-client
Last updated
