Skip to end of metadata
Go to start of metadata

Background

All forms (including registration form) are being processed through queue data (module/muzima/view.list#/queues).  When there is an error for the registration form, it will be put into error data (module/muzima/view.list#/errors).  When there is no error for the registration form (no exception is identified), it will be put into view registration (module/muzimaregistration/view.list#/registrations). 

  • For case which existing record has been identified in the system by simple matching algorithm, the temporary UUID will be mapped with system assigned UUID.  Temporary UUID on device will be replaced by System Assigned UUID when synching cohort data next time.
  • For case which simple matching algorithm cannot identify existing record in the system, the system will create an assigned UUID and then mapped to temporary UUID.  Temporary UUID on device will be replaced by System Assigned UUID when synching cohort data next time.

All the records shown on view registration (module/muzimaregistration/view.list#/registrations), it's a comprehensive list for all the records created through mUzima app which the list includes the mapping of temporary UUID with system assigned UUID.

The common link between registration form and corresponding encounter form is the Temporary UUID.  Please see code on https://github.com/muzima/openmrs-module-muzimaregistration/blob/development/api/src/main/java/org/openmrs/module/muzimaregistration/handler/JsonEncounterQueueDataHandler.java#L161.

 

Workflow of mUzima Registration Form

registration form process

  • No labels