One Health

Carry zoonotic notifications and counts between animal and public health DHIS2 instances, load AMR results and environmental readings.

One Health is defined by WHO, FAO, UNEP and WOAH as "an integrated, unifying approach that aims to sustainably balance and optimize the health of people, animals and ecosystems" (WHO). The One Health Joint Plan of Action organises the work into six action tracks:

  1. One Health capacities for health systems
  2. Emerging and re-emerging zoonotic epidemics
  3. Endemic zoonotic, neglected tropical and vector-borne diseases
  4. Food safety
  5. Antimicrobial resistance
  6. The environment

What reaches DHIS2

Three of the tracks become integration work around DHIS2:

  1. Zoonoses. Animal health and public health run separate DHIS2 instances, each with its own organisation unit hierarchy and its own codes. A zoonotic notification in the animal health instance has to reach public health, and weekly counts of zoonoses have to reach the public health surveillance data set.
  2. Antimicrobial resistance. Human, animal and food laboratories run WHONET, which exports aggregate statistics for DHIS2 data sets and isolate listings for DHIS2 event programs as files.
  3. The environment. Readings from a national source, such as the stations of a meteorological service, are posted as data values next to the health data.

Food safety needs no flow of its own, because foodborne outbreaks arrive as notifiable conditions through the normal surveillance path. Global climate datasets such as ERA5-Land and CHIRPS are imported by the DHIS2 Climate app itself.

Processing flow

When the built-in data exchange is enough

DHIS2 has an aggregate data exchange of its own, which copies aggregate data from one instance to another on a schedule. When only aggregate data moves between two DHIS2 instances and both use the same codes for the same organisation units and data elements, that exchange covers it and no integration is needed. The pages here are for the rest - case data in tracker programs, hierarchies and code sets that differ, and sources that are not DHIS2.

Pages in this section

PageWhat it covers
SetupTwo instances, their connections and the code mappings
Zoonotic notificationsAnimal health notifications carried to public health
Zoonosis countsWeekly counts into the public health data set
Antimicrobial resistanceWHONET exports loaded from each laboratory
Environmental dataDaily readings of a national source as data values

See also

FeatureWhat it does
DHIS2 overviewAll DHIS2 integration pages
Config tablesTranslate the codes of one party into another's
File transfer schedulesPick up files and invoke a service per file

Learn more