We’re excited to announce the release of 4.18.0 of the CHT Core Framework
See below for some highlights, read the release notes for full details.
Following the CHT’s support policy, version 4.14.x is no longer supported. Projects running these versions should start planning to upgrade in the near future. For more details read the CHT software support documentation.
4.18.0 Highlights
Right to Left Language Support
Support for Arabic as a CHT language was added in 4.16.0. Now, the CHT can properly display content in a full RTL layout! This greatly improves the usability of the application for native RTL language speakers.
Replicate Primary Contacts Regardless of Depth
Controlling the data accessible to “offline” CHT users is essential. Often, the replication_depth configuration is used to limit how much of the contact hierarchy is visible to a user (and downloaded to their device) by preventing the replication of contacts/reports beyond a specified depth.
However, in some cases this configuration is not sufficient. For example, perhaps a CHW Supervisor needs to have access to the contact data for the CHWs they supervise (including the reports for those contacts), but should not have access to all the households/patients served by those CHWs. A typical hierarchy (as seen here) might have the CHW contact and the family household contacts both at the same depth level as children of the CHW Area. If the supervisor user is configured to have a replication depth of 1, they will not have access to the CHW contact. If the replication depth is set to 2, the supervisor will have access to all the household contacts.
In this case, the new replicate_primary_contacts configuration can be used to ensure the primary contacts of the places at the user’s deepest replication depth are also replicated (even if those contacts are technically located deeper in the hierarchy than the configured depth limit). So, with a replication depth of 1 and replicate_primary_contacts set to true, the supervisor user will have access to the CHW contact, but not the household contacts.
REST Endpoints for Getting Contacts and Reports
New REST endpoints have been added to the CHT API server for retrieving data about contacts and reports. The endpoints support getting the all the data for an identified contact/report. Additionally, an endpoint has been added for getting an array of contact identifiers filtered by contact type and/or a freetext search time. There is also a new endpoint for getting report identifiers filtered by a freetext search term.
And more…
We’ve also implemented loads of other improvements and fixed a heap of bugs.