To be published in September 2017
During mid 2017 we conducted two surveys:
- of ongoing Android projects and their characterics
- Voting of DHIS2 Android features required by the community
1- Community Voting Process - results of voting (July 2017)
Community consultation of key features to be implemented on future Android app, ranked by voting score:
|Rank||Feature (organized by Score)||Voting score|
|01||17. Do not delete data when a user logs out.||55|
|02||39. Improve log in process||53|
|03||44. Analytic tools||53|
|04||42 Multi-language support interface and meta-data.||46|
|05||35. Encrypt data base||42|
|07||37. Lock app to prevent unauthorised access||42|
|08||18. Hierarchy as a tree||41|
|09||32. Send alarms through SMS from Android app||40|
|10||28. Images per Program stage, data element, options||40|
|11||22. Select GPS from Map||40|
|12||34. Access auditing||37|
|13||51. "Working lists" (operational reports)||36|
|14||21. Online search with bigger scope||35|
|15||23. Cascading drop downs for facility selection||34|
|16||45. Data analysis by user||34|
|17||40. Improve usability of "Complete/Incomplete"||34|
|18||47. Inter-stage dependencies||33|
|19||50. Task assignment||33|
|20||33. Show last value of a field in data entry screen||33|
|22||26. Force search before registering TEI||32|
|23||46. Health workers management||31|
|24||29. Multimedia library.||30|
|26||24. Critical Info per program||28|
|27||31. Sections in Enrollment||28|
|28||38. Multiple access Failure||27|
|29||30. Profile picture for tracked entity instances||26|
|30||19. Lock records after a number of days configured||26|
|31||25. Data Elements evolution chart||25|
|32||41. Color set and Icon customization||24|
|33||43. Splash screen customization||23|
|34||15. Changing programs from the patient dashboard||21|
|35||14. Create TEI from relationships||20|
|36||27. Hiding of completed and cancelled enrolments when searching for TEI||20|
|37||16. Description in Program Stage Section||18|
|38||36. Limited search results||15|
2- Ongoing Android Projects and characteristics
Results survey May-June 2017
Theses answers correspond to 54 projects. 67 % of them were ongoing, 29 % planned and 4 % were already finished.
Of those answers, 35% are run by Ministries of health and 34% by International NGOs
All ongoing projects are in the health domain. Android projects in other domains are present, but their representation is minimal.
Almost 50% of the projects are either medium size (up to 100 devices) or large (up to 250 devices). There is a significant number of Extra Large projects (more than 1,000 devices)
In the big majority of projects (67%) users do not share devices to collect data.
The most used DHIS2 Android App is Tracker Capture, which is used in 69% of the projects, followed by Event Capture (41%), Dashboard (39%) and Data Capture (30%).
22% of the organizations have developed their own Android Apps.
In 85% of the Tracker programs using Android, the tracked entity is a Person.
From all the projects who reported to be tracking people, 74% are health beneficiaries, clients or patients.
Only in 13 % of the projects, users report data from one single activity. In more than half of them (63%) data is collected from 2 to 5 different activities, while in 24 % the number of different activities is greater than 5.
In 32% of the projects users collect data from only one organisation unit. The most common case is collection across 2 to 5 organisation units.
Health Care Providers (67%) together with Community Health Workers (57%) represent the main users in current projects. Users from coordination positions are present in 43 % of the projects, followed by Laboratory technicians (19%).
All types of data collection are evenly represented across the surveyed projects. Projects working in Reactive mode are the less common, but still they constitute a 39% of the projects.