Expansion of the two-way texting approach for male circumcision post-operative care in South Africa
The direct-to-client (D2C), two-way texting (2wT) app supports automated, interactive telehealth via direct-to-client messaging between voluntary medical male circumcision (VMMC) nurses and clients. You can learn more about it in another CHT Forum post here.
Updates on the client performance / apdex work
Are CHWs and Supervisors experiencing any slowness in their apps? Care Team presented how CHT telemetry can be used to track that information. CHT records telemetry for a bunch of system actions for example loading the task page. This information can help you know minimum time to load the page, maximum time to load the page, total of all time it took, and others. With such data you can understand how things work in your CHT app. You can also compare such information with multiple CHWs in the same CHT app to understand the performance distribution. Industry standard way of capturing user level of satisfaction is via Application Performance Index (APDEX). It is based on measuring the response time of webpages.For example, if a webpage takes 12 seconds or more then users are very likely to get frustrated. Based on this, CHT will break down those telemetry data into different categories of APDEX. For example count of frustrated, tolerated, and satisfied. For more details you can look at the recording.
Onboarding best practices - including password changes reporting
We have added a whole new documentation on securely on-boarding users. This documentation covers a password reset by leveraging magic links (aka token login) . The documentation also covers how you can find whether users have changed their passwords. If you have instructed all users to manually change their password, CHT administrators can search their server logs to see which users have made the update. Learn more about it by checking CHT documentation on - Onboarding best practices.
New user devices API
It is important to track and know whether software is old and outdated in the devices that use CHT. This includes information like android version, cht version, apk version, and others. Running old and outdated versions can make the devices vulnerable. We are excited to share that a new endpoint is added which you can easily query and get back the report in the json document with those version information. Please find more information about this API on the CHT doc website - New user devices API.
Updates on CHT Sync and the CHT - OpenMRS interop efforts
- Product ecosystem team has been working on an enhancement i.e. CHT Sync which allows copying data from CHT to an analytics database. This makes it easier for users to query the data from the analytics database.
- Also the team shared that, Superset will no longer be bundled with the CHT Sync docker configuration.
- The team learnt from deployment that utilizing incremental tables is a better way to pull the data much more seamlessly. Hence, they will be utilizing incremental tables.
- The team is also working on interoperating CHT with OpenMRS which will be based on FHIR standards. Find more about these updates in the recording.
Please do not hesitate to reach out if you have any questions. Thanks to our presenters @michael , @jkuester, and @Philip_Mwago for sharing these updates. We have next CHT Round-up call on Thursday, April 11 at 4:00 PM EAT/ 1:00 PM GMT/ 6:45 PM NPT. We look forward to seeing you.
