This document briefly describes the types of forms, the kind of form data handled by each form, form structure and the mechanisms of how the data is loaded into forms, and how the forms are serialized while saving.
Types of Form Data
Form data can be classified into two:
Have concept IDs defined within OpenMRS Concept dictionary. Examples include patient vitals, symptoms, medications dispensed etc.
Include patient demographics and encounter meta-data such as encounter date and encounter location. There are no concept IDs for this data.
Types of supported Forms
Currently, mUzima supports four types of forms:
1. Registration form:
For registration of new patients. Only capture patient demographics and encounter meta-data. All data collected is Non-Observation.
2. Demographics Update form:
For updating patient demographics information. It collects Non-Observations only
3. Encounter form:
Both Observations and non Observations. It doesn't collect demographic data.
4. Teleconsultation form:
Special type of encounter form. Both Observations and Non-Observations
Each of these forms has a corresponding handler within the server side forms processor module, to validate and process the data.
Ideally a project/organization that uses mUzima will have only one registration form (and probably one demographics update form and one Teleconsultation form) and one or more encounter forms.