dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi, a quick update from SA:

HISP SA will in the new year start implementing DHIS 2 within the Botswana
ministry of health. According to the time-table a workshop will be held in
the second week of January and a pilot/test implementation should be running
by end of January. Customization of the software, meta-data, data entry
forms and reports in addition to training of administrators, managers and
users will take place over a 6-month period starting from January, followed
by a lower level of support for 12 months.

Botswana has relatively few "orgunits" and only 3 levels in the hierarchy.
The plan is to use a single on-line server running DHIS 2 including GIS at
the national level. Some facilities have had DHIS 1.4 installed for some
time and the transition for those will be done gradually.

Generally the latest inventions of DHIS 2 has been well received. A
lighter/more static version of the multi-dimensional model is proposed to be
included in DHIS 1.4. The upcoming SDMX/OpenMRS integration which we
hopefully can pull off soon is needed. I have not yet had time to
demonstrate the patient/community functionality but will do so soon.

HISP AS has appointed Crizelle Nel to be the DHIS 2 resource person i SA. We
have already had very constructive sessions with training and comparisons of
the two systems with regard to functionality, and she's picking up the new
ways of doing things in DHIS 2 very quickly. She will definitely be a very
valuable person in the process of "conveying" DHIS 2 to HISP SA.

As a result we have identified functionality which should be "ported" and
included in DHIS 2, as well as functionality which could be "ported" the
other way around. I have copied in links to blueprints for those interested
below. Additionally, there are lots of minor improvements under way which
didn't make it into blueprints, some of these have admittedly been discussed
before. Also, some functionality in 1.4 is not relevant to 2.0 due to
different approaches in some areas. The ambition is to reduce the "gap"
between the two applications to a minimum by the end of January.

cheers, Lars


https://blueprints.launchpad.net/dhis2/+spec/eliminate-duplicate-data-values
https://blueprints.launchpad.net/dhis2/+spec/merge-organisation-unit-data
https://blueprints.launchpad.net/dhis2/+spec/zero-is-insignificant-dataelement-attribute
https://blueprints.launchpad.net/dhis2/+spec/improve-dataentry-history-popup
https://blueprints.launchpad.net/dhis2/+spec/minmax-outlier-in-dataentry-validation
https://blueprints.launchpad.net/dhis2/+spec/progress-indicators
https://blueprints.launchpad.net/dhis2/+spec/follow-up-on-data-values
https://blueprints.launchpad.net/dhis2/+spec/archiving-data
https://blueprints.launchpad.net/dhis2/+spec/catchment-population-generation
https://blueprints.launchpad.net/dhis2/+spec/gap-analysis