6. Research Methodology
6.11. Sensitivity Analysis
173 No of predicates: 30 (See Appendix B15)
Purpose: Common pool class for provision of routine functions
Description: This class contains all the common predicates, clauses and codes that are repeatedly required by other classes. Most of the important services provided by this routine are conversion services. This involves converting diseases, symptoms, signs, risk factors and treatment to codes and vice versa as it is programmatically safer to work with codes to ensure consistency, save memory demand and minimize errors.
3.9.4.15 main module Name of class/module: main
No of predicates: 2 (See Appendix B16)
Purpose: loads system executable file (.exe)
Description: The class loads CFRMFEDD executable file at startup.
Algorithm:
Display taskwindow Load main::run (Goal)
174 3.9.5.1 Input specification
The input design specifies the WHAT MUST input to the system and the interface through which such data input is made possible. In this dissertation, the design includes the screens or forms which are used to collect data from the user through text input, option buttons, check boxes and drop-down list boxes.
3.9.5.1.1 Input Mode
The input modeisthe channel through which communication to the system can be actualized. These include the following:
a) Use of keyboard or mouse
b) Use of Forms and Controls by typing, clicking or double-clicking. The controls include option buttons, check boxes, drop-down list boxes and command buttons.
c) Input Forms are evoked through interactive menu-driven navigation system.
3.9.5.1.2 User Input Interface Forms
The user input interface forms were designed using Visual Prolog 7.0 enterprise edition and the following input forms were designed:
a) Patient Registration Input Form(See Figure 3.33) b) Eye Disease Registration Input Form (See Figure3.34)
c) Eye Disease-Attributes Registration Input Form (See Figure 3.35) d) Eye Disease Delete Input Form (See Figure 3.36)
e) Patient Log-In Input Form (See Figure 3.37)
f) Admin/Doctor Input Log-In Form (See Figure 3.38) g) Visual Acuity Test Input Form (See Figure3.39)
175 h) Symptoms Checking Input Form (See Figure3.40) i) Change Password input Form (See Figure 3.41) 3.9.5.1.3 Patient Registration Input Form
The patient registration input form (See Figure 3.33) is used to register a new patient into the system.
The registration is done through the help of an assistant. The following information about the patient is registered:
a) Surname, b) First Name, c) Middle Name d) Sex
e) Age
f) Occupation
g) The user Type (auto-filled) h) Patient ID/Folder No (auto-filled)
176
Figure 3.33: Patient Registration Input Form 3.9.5.1.4 Eye Disease Registration Input Form
New eye disease is added into the database through this form (See Figure 3.34). The following disease information are entered into the system:
a) The Name of Eye disease b) The Symptoms of the disease c) The Signs of the disease d) The Risk factors of the disease
e) The Treatment regimen of the disease
f) The certainty factor associated with the disease g) The image of the disease
177
Only item (a) above is typed in as text, the rest of the input is done through selection from a pull down list. Selection of exact set of symptoms for already existing disease in the database is not allowed as this will tantamount to duplication of eye disease with another name. Only a system administrator or doctor has access to this form.
Figure 3.34: Add-New-Eye-Disease Input Form 3.9.5.1.5 Eye Disease-Attributes Registration Input Form
This form (See Figure 3.35) is used to register new disease attributes into the database. Such disease attributes include the following:
a) The Symptoms b) The Signs c) The Risk factors
d) The Treatment regimen
178
Duplication of any of the above attributes in the database is not allowed. Only a system administrator or doctor has access to this form
Figure 3.35: Add-New-Eye-disease-attributes Input Form 3.9.5.1.6 Eye Disease Delete Input Form
This form(See Figure3.36) is used to delete existing an eye disease from the database. Two levels of confirmatory warnings are presented to the used before the disease is finally deleted from the
database. Only a system administrator or doctor has access to this form
179
Figure 3.36: Delete-existing-Eye Disease Input Form 3.9.5.1.7 Patient Log-In Input Form
This form(See Figure 3.37) is used for logging-in a patient. For successful log-in to occur, the patient through the help of assistant must supply correctly the following information:
a) Surname, First Name and Middle Initial b) ID
The name is simply selected from a pull-down listwhile the ID No must be typed. When a user is logged-in as a patient, he will be given the following view/action privileges:-
a) Carry out visual acuity test
b) Participate in symptoms-checking
c) View eye disease pictures, signs, symptoms, risk factors and treatment options
180 d) View/Print test reports related to him/her only
Also a new patient is allowed to register by clicking the <New patient> button.
Figure 3.37: Patient Log- in Input Form 3.9.5.1.8 Admin/Doctor’s Log-In Input Form
This form(See Figure 3.38) is used for logging-in as system Admin/Doctor. For successful log-in to occur, the user through the help of assistant must supply correctly the following information:
a) Admin Password
When a user is logged-in as an Admin/Doctor, he will be given unrestricted privileges including:- a). Carry out visual acuity test
b) View eye disease pictures, signs, symptoms, risk factors and treatment options
181 c) View/Print test reports related to any patient d) Add or delete eye disease
Figure 3.38: Admin/Doctor‘s Log-In Input Form 3.9.5.1.9 Visual Acuity Test Input Form
The visual acuity test input form (See Figure 3.39) is used to receive patient‘s response during the measurement of visual acuity. Only users who log-in as patient can save the test result whereas other users can only use the test as a demo but cannot save the result. A saved result of the test is
automatically forwarded to symptoms-checker for further processing.
182
Figure 3.39: Visual Acuity Test Input Form 3.9.5.1.10 Symptoms Checking Input Form
The Symptoms checking input form (See Figure 3.40) is used to receive patient‘s symptoms. It serves as a consultation panel between the system and the patient. Only users who log-in as patient can view and save the result after consultation. However, users who log-in as Admin/Doctor can view and practice with the consultation panel as a learning tool but cannot save the result thereafter for diagnosis. Entering of symptom is simply through clicking of <YES> or <NO> button as a response to the diagnostic
question displayed by the system. Afterwards a <NEXT> button is clicked for more questions.
The following information are supplied by the user during a typical consultation session:
a) Symptoms complained by the user
b) Certainty factor associated with each symptom provided
183
Figure 3.40: Symptoms Checking Input Form 3.9.5.1.11 Change Password input Form
For security reasons, the doctor or system admin is allowed to change his/her password at will. This is to prevent unwarranted intrusion into the sensitive section of the database. The user must have to
successfully provide the old password and repeated new password before password change could be effected.
Figure 3.41: Change password input form
184 3.9.5.2 Output Specification
The output design specifies WHAT the system shall and MUST output and the interface through which such data output is made possible. In this dissertation, the output design includes the screens or forms which are used to output data from the system in form of test reports, screen displays and hard-copy print-outs.
The output from the system includes:
a) Displays, reports and print-outs
i. Test results, errors, warnings, messages and other instructions are displayed on the computer screen
ii. Test report is sent to Printer for print out iii. Test result is saved to database
b) The user selects output from the system through various Forms and Controls by typing, clicking or double-clicking.
c) Output Forms are evoked through interactive menu-driven navigation system and include the following:
i. Disease-Attributes Browsing Output Form ii. Eye Disease Browsing Output Form iii. Diagnosis Output Form
iv. Cumulative Test Report Output Form v. Welcome Page Output Form
185 3.9.5.2.1 Output interface Forms
The following output Forms were designed:
a) Disease-Attributes Browsing Output Form(See Figure 3.42).
b) Eye Disease Browsing Output Form(See Figure 3.43).
c) Diagnosis Report Output Form (See Figure 3.44).
d) Cumulative Test Report Output Form(See Figure 3.45).
e) Welcome Page Output Form (See Figure 3.46).
3.9.5.2.1.1 Disease-Attributes Browsing Output Form.
Disease-Attributes Browsing Output Form (See Figure3.42) is used to display the list of disease attributes from the database. Such disease attributes include the following:
a) The Symptoms list b) The Signs list c) The Risk factors list
d) The Treatment regimen list
Only users who log-in as doctor/Admin can view this form as the patients do not need to know this list in advance as to avoid supplying memorized information.
186
Figure3.42: Disease-Attributes Browsing Output Form 3.9.5.2.1.2 Disease Browsing Output Form.
Disease Browsing Output Form (See Figure3.43) is used to display the list of eye disease from the database. For each selected disease from the list, the following information is displayed:
a) The Symptoms of the disease b) The Signs of the disease c) The Risk factors of the disease
d) The Treatment regimen of the disease e) The picture of the disease
187
Viewing of this form is accessible to any user of the system as learning about eye diseases is one of the fundamental facility provided by CFRMFEDD.
Figure3.43: Disease Browsing Output Form 3.9.5.2.1.3 Diagnosis Report Output Form
Diagnosis report output form (See Figure3.44) is used to display final diagnosis made by CFRMFEDD.
The view of this form is only accessible to users who logged-in as patients and have also undergone eye test.
The following information is displayed:
a) The name of eye disease diagnosed with associated certainty factor (for single disease diagnosis) b) The names of eye diseases diagnosed with associated certainty factors (for multiple disease
diagnosis)
188
c) Inconclusive diagnosis when the certainty factor and/or visual acuity gotten from the patient do not yield to any known eye disease in the database.
Figure3.44: DiagnosisReport Output Form 3.9.5.2.1.4 Cumulative Test Report Output Form
Cumulative Test Report Output Form(See Figure 3.45) is used to display all the tests done by each patient in all his/her consultations with CFRMFEDD. The view of this form is only accessible to users who logged-in as either patients or Admin/doctor. A patient can only view those results that pertain to
189
him/her while the Admin/doctor has global view of all the results of the patients. This ensures information protection and security.
The following information is displayed:
a) Patient Name :Surname, First name, Middle Name b) Age,
c) Sex,
d) Occupation, e) Patient category f) Patient ID No
For each date of eye examination, the following information are also displayed:
a) Visual Acuity and vision status for Right eye b) Visual Acuity and vision status for Left eye
c) The symptoms complained an associated diagnosis made d) Recommendations/ Health Advice
190
Figure 3.45: Cumulative Test Report Output Form 3.9.5.2.1.5 Welcome Page Output Form
Welcome page output form (See Figure 3.46) is designed to be the first welcome portal to the user. Brief but necessary user instruction is displayed here. It gives the user a sense of direction on what he expects to do with CFRMFEDD.
191 Figure 3.46: Welcome page output form List of Nu