Key principles in the DHIS

1
Key principles in the DHIS

• Organisational hierarchy
• Organisational units and their grouping
• Data elements and their grouping
• Overview of the DHIS

2
The Organisational Hierarchy
Reporting unit
DHIS14 allows an infinite number of reporting
levels. The first level is in this case called
the reporting unit.
3
The Organisational Hierarchy

Parent body
Country
Health district


Facility


Parent body
Reporting unit
Reporting units belong to parent bodies, normally
arranged in a hierarchical structure.
4
Adding data to the org units

Parent body
Data that is collected is attached to reporting
units.




Parent body
Reporting unit
Semi-permanent data
5
Adding data to the org units

Parent body




Parent body
Reporting unit
Semi-permanent data

• Routine data set (mnthly, weekly, daily, etc)
• Data element 1
• Data element 2
• Data element 3

6
Adding data to the org units

Parent body




Parent body
Reporting unit
Semi-permanent data

• Routine data set (mnthly, weekly, daily, etc)
• Data element 1
• Data element 2
• Data element 3

• Survey data set
• ltSurvey_namegtData element 1
• ltSurvey_namegtData element 2
• ltSurvey_namegtData element 3

7
Adding data to the org units

Parent body
Data can be added to the other org units (i.e.
data can be captured at multiple levels)




Parent body
Reporting unit
Semi-permanent data

• Monthly data set
• Data element 1
• Data element 2
• Data element 3

• Survey data set
• ltSurvey_namegtData element 1
• ltSurvey_namegtData element 2
• ltSurvey_namegtData element 3

8
Understanding org units, org unit groups, and
org unit group sets
Org unit 1
Group 1
Group set 1
Org unit 2
Group 2 a
Org unit 3
Org unit 4
Group 2 b
Group set 2
Org unit 5
Group sets have specific properties of being
compulsory and/or exclusive. For instance,
whereas each of the OrgUnit types from 1.3 become
a separate group, the collection of those groups
will be defined as belonging to the group SET
"OrgUnitType". This set is then specified as
compulsory (all OrgUnits must belong to a group
type) and exclusive (no OrgUnit can belong to
MORE than ONE group - a facility cannot be a
clinic and a hospital at the same time). They
are defined in the maintenance menu under org
units.
Org unit 6
Group 2 c
Groups are defined in the lookup tables. They
define a characteristic about the org unit
(whether it is urban/rural, clinic/hospital,
provides maternity services, and/or emergency
services, and/or immunisation services
People are interested in a grouping in one way or
another
9
Understanding org units, org unit groups, and
org unit group sets
Org unit 1
Group 1
Group set 1
Org unit 2
Group 2
Org unit 3
Group 3a
Exclusive
Org unit 4
Group 3b
Group set 2
Compulsory
Org unit 5

• An example
• Org unit types
• Location

Org unit 6
Group 3c
10
Understanding org units, org unit groups, and
org unit group sets
Exclusive
Org unit 1
Group 1
Group set 1
Compulsory
Org unit 2
Group 2

• An example
• Accreditation
• Types of services

Org unit 3
Group 3a
Org unit 4
Group 3b
Group set 2
Org unit 5
Org unit 6
Group 3c
11
Importance of this function

• Health services are often in a state of flux
• Hard-coding these categories (constraints) become
  a constraint
• Enabling the user to determine these options
  increases functionality in an environment that is
  constantly changing
• Main purpose of these groupings is to allow
  analysis to be performed on certain groups
• This is a key aspect of the success of the DHIS,
  and is also its power

12
Understanding the data elements, and data element
categories

• Monthly data set
• Data element 1
• Data element 2
• Data element 3

Data element categories
Indicators
13
Understanding the data elements, and data element
categories

• Monthly data set
• Data element 1
• Data element 2
• Data element 3

Raw data
Data element categories
Processed information
Indicators
14
Understanding data elements, and data element
groups
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data element
Data Element Groups are defined in the lookup
tables. They group data elements that have some
characteristic in common ( a data entry form, a
programme/service, or agegroup)
People are interested in a grouping in one way or
another this is what we analyse
15
Understanding data elements, and data sets
Data element 1
Data set 1
Data element 2
Data element 3
Data element 4
Data element 5
Data element 6
Data set 2
The data base file contains a list of data
elements. Each data element can be assigned to
one or more datasets.
Each dataset can be completed for a set of
orgunits but it may not be necessary for all
org units to complete all datasets. When naming
data sets, be clear what the data set represents
(dont call it xxx form unless the data set is
linked to only one form).
16
Understanding data elements, and data sets
Data element 1
Data set 1
Data entry form 1
Data element 2
Data element 3
Data element 4
Data element 5
Data entry form 2
Data element 6
Data set 2
Data entry form 3

• A data entry form can be created to address the
  specific needs of
• A dataset, or
• An org unit.
• When naming data entry form, give it a name
  ending in form DC10 Form

17
Understanding data elements, and data sets
Data element 1
Data set 1
Data entry form 1
Org unit 1
Data element 2
Org unit 2
Data element 3
Org unit 3
Data element 4
Org unit 4
Data element 5
Org unit 5
Data entry form 2
Data element 6
Data set 2
Org unit 6
Data entry form 3
For routine data If org unit structures in Data
set 1 and 2 are the same, then the software will
ensure that the value for Data Element 4/5 in any
single period, will be the same in each dataset.
Each dataset can be completed for a set of
orgunits but it may not be necessary for all
org units to complete all datasets.
18
Useful Articles

• Braa, J., O. Hanseth, et al. (2005).
  "Standardisation of Health Information Systems in
  Developing Countries - flexible standards the
  "third way"."
• Braa, J. and C. Hedberg (2000). Developing
  District-based Health Care Information Systems
  The South African Experience. IRIS 23.
• Braa, J. and C. Hedberg (2002). "The Struggle for
  District Based Health Information Systems in
  South Africa." 18 113-127.
• Braa, J., E. Monteiro, et al. (2004). "Networks
  of Action Sustainable Health Information Systems
  Across Developing Countries." MIS Quarterly
  28(3) 337-362.
• Wilson, R., C. Hedberg, et al. (2003). South
  Africa's District Health Information System Case
  Study, EQUITY Project 17.
• HISP Websites (follow links from confluence)
• Manual on DHIS14
• Manual on DHIS13
• GIS User Manual