Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
···
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
This is great!
···
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Super!!
Le 4 juil. 2016 9:34 PM, “Lars Helge Øverland” lars@dhis2.org a écrit :
···
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Thank’s to DHIS2 development team
···
=========================
EKANI Guy
Le Lundi 4 juillet 2016 22h09, riddy ndoma riddyndoma@gmail.com a écrit :
Super!!
Le 4 juil. 2016 9:34 PM, “Lars Helge Øverland” lars@dhis2.org a écrit :
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Very interesting and important features. 
···
On 5 Jul 2016 03:09, “riddy ndoma” riddyndoma@gmail.com wrote:
Super!!
Le 4 juil. 2016 9:34 PM, “Lars Helge Øverland” lars@dhis2.org a écrit :
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Congra to the community and Devs team.
···
On Monday, July 4, 2016 10:34 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Screenshot 1 | 2 | 3 | 4 | Demo 1 | 2 | 3 | Docs
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
https://www.dhis2.org/downloads
You will find documentation and Javadocs here:
https://www.dhis2.org/documentation
You can read the upgrade notes and find upgrade script here:
https://www.dhis2.org/224-upgrade
The demo application can be found here:
Full list of features can be found at the Launchpad page:
https://launchpad.net/dhis2/+milestone/2.24
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Hi
Is translate feature for Options (dropdown answers) removed from 2.24? I don’t seem to find any button to translate dropdown answers. I can translate the Option Set but NOT the options.
Thank you
Deepali
International Medical Corps
···
On Tue, Jul 5, 2016 at 2:04 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
HI all,
This looks exciting.
Lars, can I ask if the reporting rates based on opening and closing dates is also permeated to respect opening and closing dates in other features within DHIS2 e.g. if you select a orgunitgroup as a denominator in an indicator does it only use open facilities for the period in the calculation? If not how do we add this?
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
···
From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Seth Okeyo
Sent: 04 July 2016 11:08 PM
To: Lars Helge Øverland; DHIS 2 Developers list; DHIS 2 Users list
Subject: Re: [Dhis2-devs] [Dhis2-users] dhis version 2.24 is released
This is great!
Sent from Samsung Mobile
-------- Original message --------
From: Lars Helge Øverland
Date:04/07/2016 11:34 PM (GMT+03:00)
To: DHIS 2 Developers list , DHIS 2 Users list
Subject: [Dhis2-users] dhis version 2.24 is released
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo * system.*
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Screenshot 1 | 2 | 3 | 4 | Demo 1 | 2 | 3 | Docs
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
https://www.dhis2.org/downloads
You will find documentation and Javadocs here:
https://www.dhis2.org/documentation
You can read the upgrade notes and find upgrade script here:
https://www.dhis2.org/224-upgrade
The demo application can be found here:
Full list of features can be found at the Launchpad page:
https://launchpad.net/dhis2/+milestone/2.24
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Thanks Lars and Dev Team.
Looking forward to test the data predictors!!
Alex
···
On Tue, Jul 5, 2016 at 12:27 PM, Elmarie Claasen elmarie@hisp.org wrote:
HI all,
This looks exciting.
Lars, can I ask if the reporting rates based on opening and closing dates is also permeated to respect opening and closing dates in other features within DHIS2 e.g. if you select a orgunitgroup as a denominator in an indicator does it only use open facilities for the period in the calculation? If not how do we add this?
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Seth Okeyo
Sent: 04 July 2016 11:08 PM
To: Lars Helge Øverland; DHIS 2 Developers list; DHIS 2 Users list
Subject: Re: [Dhis2-devs] [Dhis2-users] dhis version 2.24 is released
This is great!
Sent from Samsung Mobile
-------- Original message --------
From: Lars Helge Øverland
Date:04/07/2016 11:34 PM (GMT+03:00)
To: DHIS 2 Developers list , DHIS 2 Users list
Subject: [Dhis2-users] dhis version 2.24 is released
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo * system.*
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Alex Tumwesigye
Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie
IT Consultant (Servers, Networks and Security, Health Information Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant
"I don’t want to be anything other than what I have been - one tree hill "
Dear Lars,
Please add the WHO RMNCH Tracker program to the standard user role for admin account. It will not be visible in the Tracker capture for demo purposes.
I had to create my own user role with access to that program to see the system generated identifiers.
Thanks.
Alex
···
On Tue, Jul 5, 2016 at 2:16 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:
Thanks Lars and Dev Team.
Looking forward to test the data predictors!!
Alex
–
On Tue, Jul 5, 2016 at 12:27 PM, Elmarie Claasen elmarie@hisp.org wrote:
HI all,
This looks exciting.
Lars, can I ask if the reporting rates based on opening and closing dates is also permeated to respect opening and closing dates in other features within DHIS2 e.g. if you select a orgunitgroup as a denominator in an indicator does it only use open facilities for the period in the calculation? If not how do we add this?
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Seth Okeyo
Sent: 04 July 2016 11:08 PM
To: Lars Helge Øverland; DHIS 2 Developers list; DHIS 2 Users list
Subject: Re: [Dhis2-devs] [Dhis2-users] dhis version 2.24 is released
This is great!
Sent from Samsung Mobile
-------- Original message --------
From: Lars Helge Øverland
Date:04/07/2016 11:34 PM (GMT+03:00)
To: DHIS 2 Developers list , DHIS 2 Users list
Subject: [Dhis2-users] dhis version 2.24 is released
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo * system.*
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Alex Tumwesigye
Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie
IT Consultant (Servers, Networks and Security, Health Information Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant
"I don’t want to be anything other than what I have been - one tree hill "
Alex Tumwesigye
Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie
IT Consultant (Servers, Networks and Security, Health Information Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant
"I don’t want to be anything other than what I have been - one tree hill "
Hi all,
the dhis version 2.24 release page is now available on dhis2.org: https://www.dhis2.org/224
Cheers,
Matthieu
···
Matthieu Pinard
DHIS 2 Academy online | University of Oslo
On 4 July 2016 at 22:34, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Hey Deepali,
Thats my bad Will make sure it’s available later today. (It should obviously have been there)
···
On Tue, Jul 5, 2016 at 9:50 AM, Dipali Sahu dipali.sahu@gmail.com wrote:
Hi
Is translate feature for Options (dropdown answers) removed from 2.24? I don’t seem to find any button to translate dropdown answers. I can translate the Option Set but NOT the options.
Thank you
Deepali
International Medical Corps
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
–
On Tue, Jul 5, 2016 at 2:04 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Regards,
Mark Polak
Software developer, DHIS 2
University of Oslo
Thanks Mark…
One more question related to this…will the translated items show up (per locale and translation) in event and tracker forms. In 2.21 although we were able to translate the dropdown answers, the forms didn’t show up the translated names for the dropdown answers and hence we had to create for example 2 option sets with exactly same answers , one with options in English and other with options in French.
In one of the previous emails we got to know that translations not showing in Programs is an unimplemented feature and we are hoping (and counting on it for our implementations) that it is available in 2.24
Thanks in advance
Deepali
···
On Tue, Jul 5, 2016 at 1:44 PM, Mark Polak mark@dhis2.org wrote:
Hey Deepali,
Thats my bad
On Tue, Jul 5, 2016 at 9:50 AM, Dipali Sahu dipali.sahu@gmail.com wrote:
Hi
Is translate feature for Options (dropdown answers) removed from 2.24? I don’t seem to find any button to translate dropdown answers. I can translate the Option Set but NOT the options.
Thank you
Deepali
International Medical Corps
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Regards,
Mark Polak
Software developer, DHIS 2
University of Oslo
–
On Tue, Jul 5, 2016 at 2:04 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Hey Deepali,
I added translations for options. Should be available in the latest .war file (after the build is complete [1]).
If they show up in the dropdown in tracker i would not be able to say. You’d have to test it, or perhaps Abyot, Markus or Jiju could comment on this. There have been some changes to how translations are being provided though the api, so you might be lucky :).
[1] http://ci.dhis2.org/job/dhis2-2.24/14/
···
On Tue, Jul 5, 2016 at 4:13 PM, Dipali Sahu dipali.sahu@gmail.com wrote:
Thanks Mark…
One more question related to this…will the translated items show up (per locale and translation) in event and tracker forms. In 2.21 although we were able to translate the dropdown answers, the forms didn’t show up the translated names for the dropdown answers and hence we had to create for example 2 option sets with exactly same answers , one with options in English and other with options in French.
In one of the previous emails we got to know that translations not showing in Programs is an unimplemented feature and we are hoping (and counting on it for our implementations) that it is available in 2.24
Thanks in advance
Deepali
–
On Tue, Jul 5, 2016 at 1:44 PM, Mark Polak mark@dhis2.org wrote:
Hey Deepali,
Thats my bad
On Tue, Jul 5, 2016 at 9:50 AM, Dipali Sahu dipali.sahu@gmail.com wrote:
Hi
Is translate feature for Options (dropdown answers) removed from 2.24? I don’t seem to find any button to translate dropdown answers. I can translate the Option Set but NOT the options.
Thank you
Deepali
International Medical Corps
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Regards,
Mark Polak
Software developer, DHIS 2
University of Oslo
–
On Tue, Jul 5, 2016 at 2:04 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi all,
DHIS version 2.24 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
ANALYTICS FEATURES
GIS layers for elevation, population density and nighttime lights: DHIS 2 now supports map layers from Google Earth Engine, which includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. So far we support three datasets, but more layers will be added in the months to come. You find the Earth Engine layers in the top menu, next to the boundary layers. The elevation layer can be used to visualise the risk of Mosquito-borne disease. Select a color scale, minimum and maximum elevation, and the number of steps to divide your range in. The same options are available for the population and nighttime lights layers, which is also an indicator of where people live.
Place search in GIS: You can now search for places and regions on the GIS app. Click on the magnifier icon and type the name of the place. You will get suggestions as you type. Select a place in the list to see it marked on the map. Click the x-button in the search field to remove the marking.
Screenshot | Demo | Docs
Color scales for GIS thematic layers: Select among nice looking color scales from ColorBrewer when you visualise thematic layers. These scales create more accurate and user friendly maps, as the distances between colors are proportional to their perceived difference.
Reporting rates on time: The pivot table apps lets you view reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period. This number is configurable per data set. In the pivot table or data app, select Data > Data sets > Reporting rates on time or Actual reports on time and then select your data set.
Screenshot | Demo | Docs
Reporting rates by data set categories: Analytics now supports reporting rates broken down by data set categories. As an example, if your data set collects data for multiple projects modeled as data set categories, you can view the reporting rate for individual projects. Try it out on the demo by selecting the EPI Stock data set and the Project category.
Expected reports based on org unit opening and closed date: For reporting rates in analytics, the number of expected reports is now calculated based on whether the organisation units assigned to the data set were open or not for the aggregation period. As an example, if you ask for reporting rates for a district for June, and one of the facilities within the district was not open until August, that facility will not be included in the number of expected reports.
Expected reports based on category option start and end dates: For reporting rates which involve data set categories, the number of expected reports is now calculated based on start and end dates of the relevant category options. In other words, complete registrations for category options are only included if the aggregation period is within their start and end dates.
Pivot table filter title: The pivot table app now displays the items currently selected as filters as a title on top of the table.
GENERAL FEATURES
Improved maintenance app: Data sets, metadata attributes, constants and option sets are now supported in the Maintenance app.
Screenshot | Demo | Docs
Apps and object search from menu: You can now navigate directly to an object type from the App menu. For example, search for “group set” in the top menu, and navigate directly to the list of organisation unit group sets or indicator group sets, without navigating first to the maintenance app.
Improved data usage statistics: The Usage Analytics app now provides reports for the most viewed favorites by type (or example pivot table and chart) and number of data values stored per day.
Screenshot 1 | 2 | Demo | Docs
Ticket system: You can now set priority and status for feedback messages. This allows you to use the DHIS 2 messaging as a basic ticket system useful for managing user support. Each message can be treated as a ticket and go through a workflow (similar to e.g. Zendesk). You can also send internal messages, visible only to other ticket administrators. This requires membership to the “Feedback recipient” user group.
Screenshot 1 | 2 | Demo 1 | 2 | Docs
Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
Docs 1 | 2 | Screenshot
TRACKER FEATURES
Tabular data entry widget: Tracker capture has a new data entry widget that allows for tabular-style data entry. It displays the list of program stages as left-hand side labels. Events will be listed in table for repeatable program stage, and allows for in-line edits of event data values. The widget can be enabled from the tracker dashboard by going to gear icon > Show/hide icons and selecting “Tabular data entry”.
Screenshot | Demo | Docs
Open tracker dashboard from URL: Tracker dashboards can now be opened directly from URLs. This is useful e.g. in order for integration with other tracker apps. Security rules are still applied.
Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself. One such example is conditional mandatory fields. Check out the Antenatal care visit program program on the demo.
Screenshot 1 | 2 | Demo | Docs
System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity instances without risking duplicate IDs when syncing with the server. Have a look at the WHO RMNCH Tracker program on the demo.
WEB API FEATURES
Improved translations solution: The database translations solution has been completely rewritten and nows works while “traversing the object graph”. This means that you can navigate e.g. JSON documents from dataElement to groups and still get translated a displayName. This will also fix a range of issues where un-translated content appeared in the user interface of apps.
Data predictors: A new solution for generating predicted values have been introduced in the Web API. This component will be useful for generating thresholds for disease surveillance, population growth and more. We will provide a UI for this and more info in version 2.25.
Program messages: The Web API now features a new concept for program messages, which allows you to send messages to tracked entity instances, emails and SMS. This can be useful e.g. in order to send reminders about upcoming visits and notifications for awareness programs to people.
RELEASE INFO
You can download Live package, WAR file, sample data and source code here:
You will find documentation and Javadocs here:
You can read the upgrade notes and find upgrade script here:
The demo application can be found here:
Full list of features can be found at the Launchpad page:
Instructions for signing up for the DHIS 2 mailing lists here:
TESTIMONIALS
A big thanks goes to MSF and Thoughtworks for contribution to this release.
Enjoy the new features.
best regards,
the DHIS 2 development team
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Regards,
Mark Polak
Software developer, DHIS 2
University of Oslo