MUzima FORMS Presented by Mary. Introduction to forms Important information What is HTML – hyper text markup language. its a constant standard markup.

mUzima FORMS mUzima FORMS

Presented by Mary Presented by Mary

Introduction to formsIntroduction to formsImportant information

• What is HTML – hyper text markup language. its a constant standard markup used to create web page.

• XML – Extensible markup language. Used to describe data.

• CSS - Cascading Styling Sheet.

• JS – Java Script.

• Meta Data- describes other data, it provides information about certain items content. E.g. image may include meta data that describes how large the picture is, the colour, depth, when it was created e.t.c

By the end of the presentation one should be able to understand the following.

a. Steps involved in form storage in mUzima system.b. Packaging and extraction of forms.c. Form Definition d. Who creates a form.e. Understand types of forms.f. Procedure for downloading form.g. Understand mode of forms used in mUzima system.h. Understand different types of forms used in mUzima.i. Differentiate between view logic and skip logic.j. Form management.k. Advantages and disadvantage of using Html and xml.l. Define a Tag.m. Define an attributes.

Objectives Objectives

Define a formDefine a form

• A form is a printed document with blank space for information to be inserted.

• In database context, a form is a window or screen that contains numerious fields or space to enter.

• Before creating any form in the system you should have a short description of how you want that form to look like such as Date, location, information and the providers information. It is done manually on hard copy then later after confirmation of all requisitions transfer to a soft copy.

• HTMLs forms are currently created by hand and (they do not support the inclusion of multimedia content such as Images and Videos)

• This document proposes a model that is used by a designer to create these forms.

Form Storage Form Storage

• A HTML form is created , this acts as the view component and contains all the input fields to be displayed and used for collection of data. This should be stored in a folder called “html”

• The logics are contained in a separate java scripts files.• We have two types of logics, i.e.

(i) View logic (ii) Skip logic

• The java scripts are store in a folder called “js”.• xml files called “xml forms” are store in the xml folder.

The xml files store Meta data about the form and must include the following information :-

i) Logical name of the formii) Author – name of the creator of the form.iii) Created date – date when the form was created.iv) modification date – latest time when the form was modified.v) version – version of the form.vi) form ID – a randomly generated vii) description – short description of a form.

• The multimedia contents are stored in a folder called “Multimedia” e.g. videos and media.

• The videos are stored in a folder called “collected” and the media “embedded”.

• Additional styling is contained in a separate css file.(cascading styling sheet) file. The css files are stored in a folder titled “css”.

Structure for a mUzima form package Root folder for form

html jscss xmlMultimedia

Form xmlembeddedCollected

videoImages videosImages

There are two types of skip logic :-1. Skip logic.2. View logic.Skip logic • This is based on a certain selection of a form field. The user is redirected

to alternative section of the form field. E.g male and female LMP filed, if the patient is a male then the skip logic will apply automatically at this point

Types of logicsTypes of logics

View logic • This is where the Html fields are hidden or disabled

on a user selection. This is base on a certain selection of a form field. The user can only view the field but you can’t click on it because it is already disabled e.g. cervical cancer test ordered will only be viewed under question applicable to female pts only.

The encounter date is disable i.e a view logic.

Packaging the forms Packaging the forms

• Once mUzima forms have been developed and all relevant files are stored in respective folders, the files should be packaged to a zip file. The file name for the zip file might have a .muz to assist programs and operating systems to correctly map or locate the file.

Extracting the mUzima form zip to a Extracting the mUzima form zip to a mUzima devicemUzima device

• mUzima form zip is created in a remote server and may be downloaded by a mUzima Android user.

• Once the mUzima user downloads the form, the following steps are processed to extract and store the form onto the mUzima device.

Procedure to follow when Procedure to follow when downloading forms downloading forms

- Login to mUzima using your user name and password then click in the login button.

Login button

• After logging in, you will be taken to the mUzima client dash board where you will see the Forms, cohorts and clients.

By default all tabs will be selected Here you will be able to view different tabs i.e. downloaded forms, incomplete and compete forms.

• To be able to download a form , select one or more form templates that you are required to use from the list and click on it. Click on the download button on the top most part as shown below. A toss bar will then appear and the form will be downloaded in a minute. Then the form will be synced on the device.

Top most part

Toss bar

- To check on the downloaded form, click on the downloaded tab then you will see the downloaded form.

Downloaded tab

Click on the downloaded then you will see the downloaded form.

Complete and incomplete formComplete and incomplete form• There are two mode type of forms,

1.Complete form

2.Incomplete form

• After filling a form, there are two options to save a form as complete or incomplete.

• As complete:- on the client summary page, tab on forms, choose one of the forms template, fill out the form completely that has the correct data and then save as complete.. it should prompt a message to the user “complete data is saved successfully”. Saving tab

• As incomplete:- on the form page, tab on forms, choose one of the forms template, fill out the form not necessary to be complete, or you are not sure of the figures or data. you will save as draft, it should prompt a message to the user “save as draft”.

Incomplete form tab

Saving as a draft

Form Validation Form Validation • It is possible to validate a form.

• There are two groups of validating a form i.e.

1. Check boxes - for check boxes , there will be requirement to validate a value, will be selected as single selection , for example NONE, NORMAL etc.

2. Radio buttons – for radio buttons you select only ONE of a limited number of choice. i.e Yes or No options.

Types of forms Types of forms • So far we have four types of CDM forms i.e.

a.CDM Registration Form:- This form is used during the first encounter with the client.

b.CDM Chew Form:- This form is used to assist In tracking retained patients who are no shows.

c.CDM Dispensary Care Form:-d.CDM Chm form :-

• For on oncology there are five types . i.e.

a.Oncology Registration :-b.Oncology Dysplasia form c.Oncology breast cancer screening form:-d.Oncology histopathology:-This form is used to

capture data on tissues from the body under the microscope to spot the signs and characteristics of the diseases. Occasionally a histopathology report is also called a Biopsy.

a.Oncology pap smear form:-this form is used to test for the cervical cancer.

b.Oncology via form:-

Syncing a formSyncing a form

• When you want to sync a form you should ensure the internet or data source is ON.

• When syncing a complete form a toast appears “the form has been synced successfully”.

• After updating a form in the sever, a user should receive the updated form.

Similarities of html and xmlSimilarities of html and xml

• Xml and Html were both design with different goals i.e.

• Both xml and html were designed with different goals.

• They both have a markup language.

Attributes Attributes

• Attributes are used to provide information that is not a part of the content of xml document.

• Attributes are always contained within the start tag of an element.

• Usually attributes are used to provide information that is not part of the content of xml document. i.e

• < file type= “ gif ” >

Advantages of using an element vs Advantages of using an element vs attributes attributes

• Elements can contain multiple values attributes can’t.

• Attributes are not expandable for future changes.

• Attributes can not describe structure i.e like a child but an element can.

• Use element to describe your data and attributes only to provide information that is not relevant to the reader.

Tags Tags • Tags are the terms used to create or design a

form .• They are mostly created by programmers or

the Form and concept people.

• There are two types of Tags i.e.i) Opening tag ii) Closing tag.• Here are some example of an open tag • <img src = “computer. Gif”>•

Types of TagsTypes of Tags

• There are two types of Tags i.e.

i) Opening tag

ii) Closing tag.

• Here are some example of an open tag

<img src = “computer. Gif”>

• Here are some example of a close tag.

<option > </option>

Advantages of Xml and HtmlAdvantages of Xml and Html

• Html was designed to display data and to focus on how data looks.

• Html is about displaying information.

• The author can only use tags that are define in html standard.

• Xml was designed to describe data and to focus on what data the data is.

• Xml is about describing information.

• Xml allows the author to define his own tags

• Xml is self describing.

Xml and Html was both design with different goals i.e.