dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

Hello everyone,

http://www.sdmx-hd.org/wiki/monitoring/Monitoring_Systems

I would like to point to a new wiki page on the SDMX-HD site comparing
various applications - it needs input from us, starting from current
features:
http://dhis2.org/features
http://dhis2.org/functionality
https://blueprints.launchpad.net/dhis2/+milestone/2.0.4

There will be a workshop in Oslo from the 22nd to 26th of this month, with
participants from at least Tanzania, India, Djibouti, Ireland, Switzerland
and Norway (probably more).

As DHIS 2.0.4 is now right around the corner, this will be a good occasion
to step back a little bit and discuss some directions for the coming year.
Ola and I are working on a document incorporating current blueprints and
other feature requests that have been raised in various contexts, which we
will send to the list as background (there will certainly  be things we have
overlooked). Crucial discussions then need to be had around priorities and
sequencing.

As further background, I include below a list of general requirements for
monitoring and evaluation systems.

 Things we have:

1. Ability to accept manually entered data

2. Ability to define custom forms for manual data entry

6. Indicator frequency: day, week, month, quarter, semester, annual (and
aggregates thereof)

8. Ability to disaggregate indicators by geography (nested), age group
(nested), sex, direct/indirect

9. Ability to define additional aggregation/disaggregation categories

10. Multi-lingual

11. Role-based security with dimensions of job function, geography and
organizational affiliation

13. Tools for defining/generating reports, graphs (including longitudinal),
maps, pivot tables and combinations thereof, and permitting their being
saved as files

18. Flexibility to respond to changing reporting requirements of donors,
countries and others

19. Extensibility to other diseases and conditions

20. Extensibility to changing scenarios

21. Hierarchical control or import of code sets and data tables

22. Hierarchical control or import of forms and reports

23. Ability to maintain facility-level data for multiple facilities on a
single machine

24. Simple maintenance and management at the facility level

29. Database neutrality


More work needed:

3. Ability to accept data exported from an electronic data system or perform
an extraction therefrom

4. Support for the following types of indicators: count, ratio, %,
population rate, $, national currency, yes/no/unknown

5. Hierarchical indicator definition via inheritance or import at
(minimally) international, national and local level

7. Ability to aggregate indicators by donor, government agency, partner,
sub-partner, funding source, activity type, program area

12. Versioning of data (knowledge of latest date an element of an aggregate
was updated), release status (preliminary, validated, released, corrected)

14. Suppression of small counts in output, "smudging" of geography to
prevent identification of individuals

15. Data interchange (especially via IXF3)

16. Target, revised target and actual data (provides budget capability)

17. Audit trail

25. Highly responsive data entry, moderately reponsive report generation

26. System monitoring reports (timeliness, completeness)

27. Ability to store and forward text or attachments as identified items
(narrative reporting)

28. Ability to add adjustments to indicator values and their justifications
at each hierarchical level and to specify their allocation among
disaggregation categories

30. Reliable, ongoing customer support, including training, software and
documentation updates, etc.