# Current and future features

**URL:** <https://community.dhis2.org/t/current-and-future-features/7618>\
**Category:** Support - Assistance technique\
**Created:** [11 March 2010 11:00 UTC](https://community.dhis2.org/t/current-and-future-features/7618 "2010-03-11T11:00:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Knut\_Staring](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/knut_staring/32/32549_2.png) [@Knut\_Staring](https://community.dhis2.org/u/Knut_Staring)\
**Post date:** [11 March 2010 11:00 UTC](https://community.dhis2.org/t/current-and-future-features/7618/1 "2010-03-11T11:00:43Z")

</div>

Hello everyone,

[http://www.sdmx-hd.org/wiki/monitoring/Monitoring\_Systems](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/features)

[http://dhis2.org/functionality](http://dhis2.org/functionality)

[https://blueprints.launchpad.net/dhis2/+milestone/2.0.4](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

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

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

5. Ability to define additional aggregation/disaggregation categories

6. Multi-lingual

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

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

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

10. Extensibility to other diseases and conditions

11. Extensibility to changing scenarios

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

13. Hierarchical control or import of forms and reports

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

15. Simple maintenance and management at the facility level

16. Database neutrality

More work needed:

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

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

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

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

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

6. Suppression of small counts in output, “smudging” of geography to prevent identification of individuals

7. Data interchange (especially via IXF3)

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

9. Audit trail

10. Highly responsive data entry, moderately reponsive report generation

11. System monitoring reports (timeliness, completeness)

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

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

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

---

<div class="post-metadata">

**Author:** ![Ngoc\_Thanh\_Nguyen](https://dhis2.b-cdn.net/letter_avatar_proxy/v4/letter/n/58956e/32.png) [@Ngoc\_Thanh\_Nguyen](https://community.dhis2.org/u/Ngoc_Thanh_Nguyen)\
**Post date:** [14 March 2010 06:25 UTC](https://community.dhis2.org/t/current-and-future-features/7618/2 "2010-03-14T06:25:21Z")

</div>

> Hello everyone,  
> More work needed:

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

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

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

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

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

> 1. Suppression of small counts in output, “smudging” of geography to prevent identification of individuals

> 1. Data interchange (especially via IXF3)

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

> 1. Audit trail

> 1. Highly responsive data entry, moderately reponsive report generation

> 1. System monitoring reports (timeliness, completeness)

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

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

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

Should we have a short session maybe half day discussing about the dhis2 patient module?

Thanh

> **···**
>
> On Thu, Mar 11, 2010 at 6:00 PM, Knut Staring [knutst@gmail.com](mailto:knutst@gmail.com) wrote:
> 
> > * * *
> > 
> > Mailing list: [https://launchpad.net/~dhis2-devs](https://launchpad.net/%7Edhis2-devs)
> > 
> > Post to : [dhis2-devs@lists.launchpad.net](mailto:dhis2-devs@lists.launchpad.net)
> > 
> > Unsubscribe : [https://launchpad.net/~dhis2-devs](https://launchpad.net/%7Edhis2-devs)
> > 
> > More help : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp)
> 
> –  
> Best regards,  
> Thanh
> 
> * * *
> 
> Center for HIS development  
> 957, 3/2 st., Dist 11, Hochiminh city  
> Tel: 08-956 0150  
> Cell: 098 221 8623
> 
> * * *