1. Error Resolution in mUzima Introducing new Error resolution UI

2. To learn Muzima amrs modules overview Muzima data Processing workflow Resolving errors using new error resolution UI

3. Muzima modules Muzima has four major components/modules  Client side: Android apk  Server side mUzima forms omod(openmrs module)  Uploading, editing, tagging, & previewing form templates mUzima registration/encounter omod  Provides handlers for processing data Core mUzima omod  Depended upon by the other modules  Handles communication with client side  Receives and queues data for processing  Uses scheduler task to invoke suitable handler for each type of data  Provides error resolution UI

4. Managing form templates Types of form formats used in developing mUzima forms  XML : Older technology Data is sent from client side in xml format  HTML: Preferred technology Data is sent in json format Types of form templates  Registration Uses *-registration discriminator e.g xml-registration, html-registration, json-registration  Encounter Uses *-encounter discriminator e.g xml-encounter, json-encounter

5. Scheduler class  Uses org.openmrs.module.muzima.task.ProcessQueueDataTask Repeat Interval  Current setup runs every 30 seconds Setting up scheduler task

6. Client-Server Communication Workflow Server side Client side Cohorts, Form Templates, Concepts, Encounter data Registration and Encounter form data Authentication, Patient search

7. Data Processing work-flow Muzima Error Queue Muzima Data Queue Client side Errors resolved and re-queued Errors encountered during processing and thrown to the error queue Data processed successfully and stored into amrs database Form data sent from mUzima app

8. Unable to uniquely identify patient Identifier already in use by another patient Unable to find Provider Unable to find Encounter Location Common Processing Errors

9. Error Resolution – old UI Allows viewing and re-queuing data on error queue Limitation:  Does not provide interface to resolve errors Users have to update the payload and update directly in database  Does not detect all problems at once Users might have to resolve and re-queue data many times

10. Error Resolution – New UI Provides interface to edit payload so as to resolve issues Detects all problems in payload Validates the edited payload before requeuing

11. Error resolution: New UI A screenshot of Errors on Error queue: How to select an error to resolve Click on this icon to resolve

12. Error resolution: New UI Click on this icon to open the payload in edit mode A screenshot of selected Error expanded for viewing details : How to open section for editing payload to resolve the error.

13. Error resolution: New UI Edit the payload from here Use these buttons to validate and save modified payload, and queue it for processing A screenshot of selected Error expanded for editing : How to edit,validate, save and queue payload to resolve the error.

14. Testing notes Ensure you can edit, and validate payload Ensure errors can be requeued Ensure resolved errors can be successfully processed Ensure the whole data processing work-flow runs successfully. I.e  You can submit data from mUzima,  get it successfully processed,  confirm that the processed data can be accessed via other amrs interfaces. You should be able to view registered patient records, and observations for respective encounters

15. For End users Report any issues encountered in your daily use of the modules Report about common errors Ask for help whenever you encounter issues Report about any successes with the modules.

16. Conclusion Let's work together to make this mUzima better!