THE DEVELOPMENT OF ELECTRONIC HEALTH RECORD FOR

ALDERSGATE COLLEGE SCHOOL CLINIC USING SCRUM FRAMEWORK

OF AGILE METHODOLOGY

A Capstone Project
Presented to the
Faculty of the College of Engineering, Informatics and Technology
Aldersgate College
Solano, Nueva Vizcaya

In Partial Fulfillment of the Requirements

for the Degree
Bachelor of Science in Information Technology

JOHN SAMU B. KOMURA

March 2022
 i
APPROVAL SHEET

This CAPSTONE PROJECT of JOHN SAMU B. KOMURA entitled “THE

DEVELOPMENT OF ELECTRONIC HEALTH RECORD FOR ALDERSGATE
COLLEGE SCHOOL CLINIC USING SCRUM FRAMEWORK OF AGILE
METHODOLOGY” prepared and submitted in partial fulfillment of the requirements for
the degree BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY has
been examined and approved by the Advisory Committee and is hereby recommended for
Capstone Oral Defense.

ERWIL DAVID A. PASION, MIT, MBA

Adviser

Date: March 2021

Approved by the Panel of Examiners in the Capstone Oral Defense.

MARLOU FELIX S. CUNANAN III, JAROM E. FRONDA Chairman

MIT, MBA Member

REV. DATON JONATHAN B. PALITAYAN

Research Coordinator

Accepted as partial fulfillment of the requirements for the degree BACHELOR OF

SCIENCE IN INFORMATION TECHNOLOGY.

ENGR. GODOFREDO M. BATARAO

Dean, College of Engineering, Informatics and Technology

PRESCILLA ESPERANZA A. SORIANO, PHD

President
 ii
ACKNOWLEDGEMENT

With deepest gratitude and appreciation, I humbly give thanks to the people who

helped with all they can in making my Capstone Project possible.

The faculty and staffs of the Informatics Department.

To my adviser, Mr. Erwil David A. Pasion for accepting me to be his advisee, for

the support, patience, advices, and guidance.

To Mr. Marlou Felix S. Cunanan III, for sharing his time and knowledge.

To Mr. Jarom E. Fronda, my Capstone Instructor and Informatics adviser, for the

time, support, patience, advice, guidance, who also pushes and motivates me to finish this

course, and for the friendship beside from being my professor.

To my friends, for giving me pieces of advice in making this project. To my

fellow students who helped me, for the friendship and pastimes we had.

To my family who is my inspiration, for their love and support, for helping me in

my financial needs, and for believing in me that I can.

To my wife, my number one supporter, who pushes and encouraged me to study,

for the love, support, and patience that motivates me.

To my lovely daughter, for giving me unlimited happiness and relieves my stress.

Above all, to our Almighty God, for his unconditional love, for giving me the gift

of wisdom, guidance and all the blessing he is showering upon us.

 iii
ABSTRACT

The Electronic Health Record for Aldersgate College School Clinic was built and

designed to help clinic staff to quickly assess students and facilitate the task of managing

records. The system is also secured and cannot be accessed by unauthorized persons. It

also includes a system activity log to monitor its activity. System functions include

managing student medical records, viewing and printing records, managing users, and

backing up and restoring data. The system also has a user-friendly Graphical User

Interface and can save more resources and expenses.

The Electronic Health Record for Aldersgate College School Clinic was developed

using SCRUM framework of AGILE methodology. It is a windows-based application that

is built using Visual Basic .Net and MySQL Server. The development of the system is

according to the quality criteria of ISO 9126 in terms of its functionality, usability,

reliability, and efficiency to meet the system requirements. It is also tested and evaluated

by a certain number of respondents to test its effectiveness.

Keywords: Health Assessment, Medical Record, Record Management

iv
Table of Contents

ACKNOWLEDGEMENT................................................................................................

ii

ABSTRACT......................................................................................................................iii

List of Tables................................................................................................................... vii

List of Figures...................................................................................................................
ix CHAPTER I

...................................................................................................................... 1

PROBLEM AND ITS BACKGROUND..................................................................... 1

Rationale .....................................................................................................................

1 Statement of the Problem............................................................................................

2 Conceptual Framework...............................................................................................

3 Objectives of the Study...............................................................................................

5 Scope and Delimitation...............................................................................................

5 Significance of the Study............................................................................................

6 Definition of

Terms..................................................................................................... 7

CHAPTER II..................................................................................................................... 9

REVIEW OF RELATED LITERATURE AND STUDIES...................................... 9

Related Literature........................................................................................................ 9

Related Studies.......................................................................................................... 11

Synthesis................................................................................................................... 16

CHAPTER III .................................................................................................................

17

v
RESEARCH METHODOLOGY ..............................................................................

17 Research

Locale ........................................................................................................ 17
 Research Design........................................................................................................

17 Description of

Participants........................................................................................ 18 Research

Tools.......................................................................................................... 18 Research

Instruments................................................................................................ 19 Research

Procedure................................................................................................... 21

Development Tools................................................................................................... 23

CHAPTER IV..................................................................................................................

25 RESULT AND FINDINGS OF THE STUDY..........................................................

25 System Overview...................................................................................................... 25

System Objectives..................................................................................................... 25

System Requirements................................................................................................ 26

Operational Diagram................................................................................................. 27

System Functions...................................................................................................... 28

Evaluation ................................................................................................................. 49

Interpretation of Data................................................................................................ 62

CHAPTER V ...................................................................................................................

64 SUMMARY, CONCLUSION AND RECOMMENDATIONS...............................

64 Summary................................................................................................................... 64

vi
Conclusion ................................................................................................................

66 Recommendations..................................................................................................... 66
References........................................................................................................................ 68

Purpose................................................................................................................... A-2

Development Costs................................................................................................ A-2

Operational Costs.................................................................................................. A-2

System Life Costs.................................................................................................. A-4

Return on Investment........................................................................................... A-4

Interview Questions.............................................................................................. C-2

User Stories.............................................................................................................E-2

Maintenance Plan...................................................................................................... N-2

Implementation Plan ................................................................................................ O-2

Appendices

A- Cost Benefit Analysis ......................................................................................... A-1

B- Flowchart ............................................................................................................ B-1

C- Interview and Observations ................................................................................ C-1

D- Document Review............................................................................................... D-1

E- User Stories..........................................................................................................E-1

F- Use Case Diagram................................................................................................F-1

G- Use Case Specification ....................................................................................... G-1

vii
H- Use Case Analysis............................................................................................... H-1

I- Entity Relationship Diagram.................................................................................I-1

J- User Manual..........................................................................................................J-1
 K- Data Dictionary................................................................................................... K-1

L- Product Backlog...................................................................................................L-1

M- Sprint Backlog ....................................................................................................M-

1 N- Maintenance Plan................................................................................................

N-1 O- Implementation Plan...........................................................................................

O-1 P- Curriculum

Vitae .................................................................................................P-1

List of Tables

Table 4.0 System Requirements .......................................................................................

26 Table 4.1 Likert Scale Values...........................................................................................

50 Table 4.2 Mean Score

Interpretation ................................................................................ 62 Table 4.3 Evaluation

Summary......................................................................................... 63 Table 5.0

Development Costs......................................................................................... A-2 Table 5.1

Existing Cost Yearly....................................................................................... A-3 Table

5.2 Proposed Cost Yearly ..................................................................................... A-3

Table 5.3 Benefits of the System Yearly ........................................................................ A-

3 Table 5.4 Flowchart Symbols and Functions..................................................................

B-2

viii
Table 5.5 Use Case Specification for Login ................................................................... G-

2 Table 5.6 Use Case Specification for View Users..........................................................

G-2 Table 5.7 Use Case Specification for Delete

User.......................................................... G-3 Table 5.8 Use Case Specification for Add

User ............................................................. G-4 Table 5.9 Use Case Specification for

Add Record ......................................................... G-5 Table 5.10 Use Case Specification

for View Records.................................................... G-6 Table 5.11 Use Case

Specification for Search Record ................................................... G-7 Table 5.12 Use

Case Specification for Delete Record.................................................... G-8 Table 5.13

Use Case Specification for Print Records..................................................... G-9 Table

5.14 Use Case Specification for Update Medical Evaluation............................... G-9

Table 5.15 Use Case Specification for View Medical Evaluation................................ G-

11 Table 5.16 Use Case Specification for Print Medical Evaluation ................................

G-12 Table 5.17 Use Case Specification for Add Student

Information ................................ G-13 Table 5.18 Use Case Specification for Update

Student Information............................ G-14 Table 5.19 Use Case Specification for View

Health Insurance.................................... G-15 Table 5.20 Use Case Specification for Add

Health History ......................................... G-16 Table 5.21 Use Case Specification for

Update Health History .................................... G-18 Table 5.22 Use Case Specification

for View Health History ....................................... G-19 Table 5.23 Use Case

Specification for Print Health History ........................................ G-20 Table 5.24 Use

Case Specification for Backup Database............................................. G-21

 ix
Table 5.25 Use Case Specification for Restore Database............................................. G-

21 Table 5.26 Use Case Specification for View Activity Log ..........................................

G-22 Table 5.27 Use Case Specification for

Logout ............................................................. G-23 Table 5.28 Product

Backlog.............................................................................................L-2 Table 5.29 Sprint

Backlog ..............................................................................................M-2 Table 5.30

Installation and Deployment......................................................................... O-3

List of Figures

Figure 1.0 Conceptual Framework .....................................................................................

3 Figure 3.0 Scrum Process .................................................................................................

21 Figure 4.0 Operational

Diagram ....................................................................................... 27 Figure 4.1 Login

Form...................................................................................................... 28 Figure 4.2 Login

Code and Table user_accounts.............................................................. 29 Figure 4.3 Main

Form....................................................................................................... 29 Figure 4.4

Display Records Code and Table student........................................................ 30 Figure 4.5

Context Menu Strip ......................................................................................... 31 Figure

4.6 Context Menu Strip Click Events.................................................................... 32

x
Figure 4.7 Medical Evaluation Form................................................................................ 33

Figure 4.8 Medical Evaluation Code and Table student................................................... 34

Figure 4.9 Update Medical Evaluation Code and Table student ......................................

34 Figure 4.10 Manage Users

Form ...................................................................................... 35 Figure 4.11 Display Users

Code and Table user_accounts............................................... 35 Figure 4.12 Add User

Form.............................................................................................. 36 Figure 4.13 Add User

Code and Table user_accounts...................................................... 37 Figure 4.14 Activity

Log Form......................................................................................... 37 Figure 4.15 Activity

Log Code and Table activity_log .................................................... 38 Figure 4.16 Display

Activity Log Code and Table activity_log....................................... 38 Figure 4.17 Student

Information Form ............................................................................. 39 Figure 4.18 Add

Student Information Code and Table students_information.................. 40 Figure 4.19

Update Student Information Code and Table students_information............. 40 Figure 4.20

Health History Form...................................................................................... 41 Figure 4.21

Add Health History Code and Table health_history ..................................... 42 Figure

4.22 Update Health History Code and Table health_history................................. 43 Figure

4.23 View Record Form ........................................................................................ 44

Figure 4.24 View Record Codes and Tables ....................................................................

45 Figure 4.25 View Health Insurance

Form......................................................................... 46 Figure 4.26 View Health

Insurance Code and Table health_insurance............................ 47

xi
Figure 4.27 View Health History Form ............................................................................

47 Figure 4.28 View Health History Code and Table

health_history.................................... 48 Figure 4.29 Question No. 1 Respondents

Distribution Chart ........................................... 51 Figure 4.30 Question No. 2

Respondents Distribution Chart ........................................... 51 Figure 4.31 Question No.

3 Respondents Distribution Chart ........................................... 52 Figure 4.32 Question

No. 4 Respondents Distribution Chart ........................................... 52 Figure 4.33

Question No. 5 Respondents Distribution Chart ........................................... 53 Figure

4.34 Question No. 6 Respondents Distribution Chart ........................................... 53

Figure 4.35 Question No. 7 Respondents Distribution Chart ...........................................

54 Figure 4.36 Question No. 8 Respondents Distribution

Chart ........................................... 54 Figure 4.37 Question No. 9 Respondents

Distribution Chart ........................................... 55 Figure 4.38 Question No. 10

Respondents Distribution Chart ......................................... 55 Figure 4.39 Question No.

11 Respondents Distribution Chart ......................................... 56 Figure 4.40 Question

No. 12 Respondents Distribution Chart ......................................... 56 Figure 4.41

Question No. 13 Respondents Distribution Chart ......................................... 57 Figure

4.42 Question No. 14 Respondents Distribution Chart ......................................... 57

Figure 4.43 Question No. 15 Respondents Distribution Chart .........................................

58 Figure 4.44 Question No. 16 Respondents Distribution

Chart ......................................... 58 Figure 4.45 Question No. 17 Respondents

Distribution Chart ......................................... 59 Figure 4.46 Question No. 18

Respondents Distribution Chart ......................................... 59

xii
Figure 4.47 Question No. 19 Respondents Distribution Chart .........................................

60 Figure 4.48 Question No. 20 Respondents Distribution

Chart ......................................... 60 Figure 4.49 Question No. 21 Respondents

Distribution Chart ......................................... 61 Figure 4.50 Question No. 22

Respondents Distribution Chart ......................................... 61 Figure 5.0 Flowchart of the

Existing System.................................................................. B-3 Figure 5.2 Flowchart for

Main Form .............................................................................. B-4 Figure 5.1 Flowchart

for Login....................................................................................... B-4 Figure 5.5

Flowchart for Activity Log............................................................................ B-5 Figure 5.4

Flowchart for Print Records .......................................................................... B-5 Figure

5.3 Flowchart for Add Record............................................................................. B-5 Figure

5.7 Flowchart for Add User................................................................................. B-6 Figure

5.6 Flowchart for Manage Users ......................................................................... B-6

Figure 5.9 Flowchart for Backup Database .................................................................... B-

7 Figure 5.8 Flowchart for Restore Database ....................................................................

B-7 Figure 5.10 Flowchart for Select

Student ....................................................................... B-8 Figure 5.12 Flowchart for View

Health History............................................................. B-9 Figure 5.11 Flowchart for View

Health Insurance ......................................................... B-9 Figure 5.10 Flowchart for

View Record......................................................................... B-9 Figure 5.14 Flowchart for

Add Health History............................................................. B-10 Figure 5.13 Flowchart for

Add Student Information.................................................... B-10

xiii
Figure 5.17 Flowchart for Update Health History ........................................................ B-

11 Figure 5.16 Flowchart for Update Student Information ...............................................

B-11 Figure 5.15 Flowchart for Update

Record .................................................................... B-11 Figure 5.18 Student Information

Sheet........................................................................... D-2 Figure 5.19 Health History

Sheet.................................................................................... D-3 Figure 5.20 Medical

Evaluation Sheet............................................................................ D-4 Figure 5.21

Activity Approval Sheet.............................................................................. D-5 Figure 5.22

Use Case Diagram Administrator.................................................................F-2 Figure 5.23

Use Case Diagram User................................................................................F-3 Figure 5.24

Use Case Analysis Administrator................................................................ H-2 Figure

5.25 Use Case Analysis User............................................................................... H-3

Figure 5.26 Entity Relationship Diagram .........................................................................I-

2 Figure 5.27 User Manual for Installing MySQL

Server...................................................J-2 Figure 5.28 User Manual for Setup

Type .........................................................................J-2 Figure 5.29 User Manual for

Executing Installer .............................................................J-3 Figure 5.30 User Manual

for Installation..........................................................................J-3 Figure 5.31 User Manual

for Product Configuration........................................................J-4 Figure 5.32 User Manual

for Proceeding Configuration ..................................................J-4 Figure 5.33 User

Manual for Type and Networking.........................................................J-5 Figure 5.34 User

Manual for Authentication Method ......................................................J-5

xiv
Figure 5.35 User Manual for Root Password....................................................................J-6

Figure 5.36 User Manual for Windows Service ...............................................................J-

6 Figure 5.37 User Manual for Apply

Configuration ..........................................................J-7 Figure 5.38 User Manual for

Finishing Configuration .....................................................J-7 Figure 5.39 User Manual

for Configuration Complete.....................................................J-8 Figure 5.40 User Manual

for Installation Complete .........................................................J-8 Figure 5.41 User

Manual for Installing ACEHR..............................................................J-9 Figure 5.42 User

Manual for ACEHR Installation Warning ............................................J-9 Figure 5.43

User Manual for ACEHR Location Folder .................................................J-10 Figure

5.44 User Manual for ACEHR Confirm Installation...........................................J-10 Figure

5.45 User Manual for ACEHR Completing Installation .....................................J-11

Figure 5.46 User Manual for Login ................................................................................J-

12 Figure 5.47 User Manual for Sign In

Button ..................................................................J-12 Figure 5.48 User Manual for

Manage Users...................................................................J-13 Figure 5.49 User Manual for

Register New User ...........................................................J-13 Figure 5.50 User Manual

for Register New User Sign Up Button .................................J-14 Figure 5.51 User

Manual for Delete User.......................................................................J-14 Figure 5.52 User

Manual for Search by Name ...............................................................J-15 Figure 5.53

User Manual for Display Students by Course .............................................J-15 Figure

5.54 User Manual for Display Students by Date of Exam ..................................J-16

xv
Figure 5.55 User Manual for Records Print Preview......................................................J-16

Figure 5.56 User Manual for Print..................................................................................J-17

Figure 5.57 User Manual for View Activity Log ...........................................................J-

17 Figure 5.58 User Manual for Backup

Database..............................................................J-18 Figure 5.59 User Manual for Save

Backup File .............................................................J-18 Figure 5.60 User Manual for

Restore Database..............................................................J-19 Figure 5.61 User Manual for

Open Backup File.............................................................J-19 Figure 5.62 User Manual for

Add Record ......................................................................J-20 Figure 5.63 User Manual

for Register Student button....................................................J-20 Figure 5.64 User Manual

for Add Student Information .................................................J-21 Figure 5.65 User

Manual for Add Information Button...................................................J-21 Figure 5.66 User

Manual for Add Health History ..........................................................J-22 Figure 5.67

User Manual for Submit Button ..................................................................J-22 Figure

5.68 User Manual for View Record ....................................................................J-23

Figure 5.69 User Manual for Record Print Preview .......................................................J-

23 Figure 5.70 User Manual for Print

Record .....................................................................J-24 Figure 5.71 User Manual for

View Health Insurance.....................................................J-24 Figure 5.72 User Manual for

View Health History ........................................................J-25 Figure 5.74 User Manual

for Print Health History .........................................................J-26 Figure 5.75 User

Manual for Update Medical Evaluation..............................................J-26

xvi
Figure 5.76 User Manual for Update Button ..................................................................J-

27 Figure 5.77 User Manual for Update Student

Information.............................................J-27 Figure 5.78 User Manual for Update

Information Button ..............................................J-28 Figure 5.79 User Manual for

Update Health History .....................................................J-28 Figure 5.80 User Manual

for Update Button ..................................................................J-29 Figure 5.81 User

Manual for Delete ...............................................................................J-29 Figure 5.82

User Manual for Refresh .............................................................................J-30

1
CHAPTER I

PROBLEM AND ITS BACKGROUND

Rationale
 The use of computer these days is widely growing and it became part of our daily

lives. It has been very significant that we had to use it every day, in school, work, at

home, and others also use it for entertainment and enjoyment. The use of computer is

very convenient, it can help us ease our task and lessen the time we spent on our paper

works. That is why schools, companies, and even small businesses are taking the

advantage with the use of computer to lessen their task.

A health record or medical record is clinical information of a patient’s physical

and mental health. It contains the patient’s condition, medical examination, treatment,

physical findings, medical history, medications and etc. This medical record was kept and

maintained by the care providers like hospitals, schools and company clinics. According

to (Romm & Samuel, 1981) a medical record is the basis of information for the

assessment of the quality of care given to a patient. It also serves as a source of

information about patient visits for individual doctors, consultants, third-party payers,

lawyers, and clinical investigators. Despite this reliance on what is recorded, there have

been few examinations to confirm the recorded content against the verbal content of the

patient-doctor interaction.

Aldersgate College is a private school in Solano, Nueva Vizcaya. It was founded

and leaded by Mrs. Pilar D. Galima and Mr. Froilan B. Calata in 1965. The school offers

preschool, elementary, high school, senior high school, undergraduate level and graduate

level programs. Aldersgate College clinic has been recording patients’ or students medical

2
record with the use of a pen and a paper. The school nurse manually writes down the

student’s information and medical record. Then, these medical records are kept and

organized on a rack or a cabinet.

 Every year, Aldersgate College clinic is conducting a medical checkup for the

students to maintain their health. Until these days, the school clinic is conducting its

health assessment in the traditional way and pile their records in the storage area. This

manual process is resource and time-consuming for both the students and the school

clinic. Moreover, students’ record is not secured against damages and documents may be

lost, therefore, an automated system must be developed.

In this connection, the researcher proposed an electronic health record system that

can be used by the school nurse to assess the students and patients. This system can help

the school nurse lessen and ease the task. It can also lessen the time that the students spent

in waiting for their turn to be assessed.

Statement of the Problem

The school clinic has a manual system of assessing its students. The school nurse

will check whether a student already has medical records inside the school clinic.

Searching in a bunch of papers is time-consuming. If the student doesn’t have a record

yet, the school nurse will assess the student as a new patient. Moreover, the assessment is

done manually with the use of a pen and paper; hence, management and securing their

data could be difficult. The documents also require a space for storage which, when piled

up, will occupy a large area. It can also be prone to physical damages by pests, water, and

etc. Lastly, since

3
documents are written on paper, it could be lost or misplaced. With the scenario the

researcher specifically found this problem:

1. How will the researcher develop a system that will meet the requirements of the

client based on the problems of the school clinic?

 2. How will the system be dependable in terms of its functionality, usability,

reliability, and efficiency?

3. How will the system be evaluated and implemented?

Conceptual Framework

Figure 1.0 Conceptual Framework

4
The Input Process Output Framework was used for the analysis of the system.

Data gathering and evaluation tools are input. For the process procedure, Agile

Methodology is used by the researcher to develop an output, the Aldersgate College

Electronic Health Record.

The Input has two parts, data gathering, and evaluation tools. On the data

gathering procedure, the researcher will have a direct interview with the client to gather

information for the visualization of the needs of the system. After gathering data, the
researcher will review and analyze the information collected from the client for the

conception of the system. ISO 9126 will be used as a tool to set the software quality

standards.

For the Process procedure, SCRUM framework will be used for the system

development, a form of Agile Software Development and UML will also be used to

visualize the proposed system design. There are four phases in the scrum procedure,

inception phase, elaboration phase, construction phase, and transition phase. In the

inception phase, the researchers’ goal is to establish, prepare a preliminary project

schedule, and develop. In the second phase, the elaboration phase, the project team is

expected to capture most of the system requirements. However, the main goals of

Elaboration are to address the known risk factors and to establish and validate the system

architecture. The construction phase is the largest stage of the project. In this phase, the

rest of the system is based on the basics defined in the elaboration. System functions are

implemented in a series of short iterations with time frames. Each iteration leads to an

executable version of the software. The final phase of the project is the transition. In this

phase, the system is made available to the target users. Feedback from a first version (or

5
versions) can lead to additional improvements in several iterations of the transition phase.

System conversions and user training are also included in the transition phase.

The Output will be the Aldersgate College Electronic Health Record that would be

evaluated and implemented in the Aldersgate College Clinic.

Objectives of the Study

The researcher’s main objective of the study is to develop an automated medical

record management for Aldersgate College that could be used by the school clinic. The
system will make a better way to assess students. It can also help in managing and secure

the records of every student.

1. To design and create a system that records patients’ or students’ information, stores

documents and a system that has a virtual database wherein the records of students

will be easily viewed and retrieved.

2. To develop a system according to the quality criteria of ISO 9126 in terms of its

functionality, usability, reliability, and efficiency.

3. To evaluate and implement the Aldersgate College Electronic Health Record and

maintain the quality of the system.

Scope and Delimitation

The proposed computerized medical record system will be designed and develop

for Aldersgate College school clinic. The system will be used for managing the health

records of the students at Aldersgate College. It will allow the user to add, delete, update

and search a student’s record. The system will be saving the medical record and

6
information of the students, such as student’s height, weight, blood pressure, body

temperature, etc.

The system will be designed for Windows Operating System only. The system is

not online based system and doesn’t need an internet connection. Only the system

administrator and in charge personnel can use the system. The system will not allow

multiple registrations of patients to avoid problems. The system will not be monitoring

any medications or treatments of the students. The system is for Aldersgate College clinic

only.

Significance of the Study

The study is significant and beneficial to the following:

To Aldersgate College – The system will be beneficial to the Aldersgate College for

it can minimize the production of resources for the school clinic. With this, expenses

will be lessened.

To Aldersgate College Clinic – The system will be beneficial to the Aldersgate

College Clinic for it will have an organized system that will keep their documents

secured.

To The School Nurse or Authorized Personnel – The system will be beneficial to

the school nurse for it can help the school nurse to assess the students in an easier and

faster way.

To The Students – The system will be beneficial to the students for it can lessen the

time wasted by the students in waiting for their turn to be assessed.

To The Researcher – This will be beneficial to the researcher for it will add

knowledge about the project that they may apply in the future.

7
To The Future Researchers – This study may help future researchers and may serve

as a basis for their future researches and add some ideas and knowledge regarding this

matter.

Definition of Terms

For better understanding of the study, the following terms are defined:

AGILE – In software development, agile addresses development needs and solutions

through the collaborative effort of self-organized and cross-functional teams and their

end user.
ISO 9126 – (International Organization for Standardization) ISO 9126 is an

international standard for the evaluation of software and helps to create a solid

framework for software.

Microsoft Visual Studio – Microsoft Visual Studio is an integrated development

environment developed by Microsoft. It is used to develop software systems or

computer programs such as mobile applications, web applications, and computer

programs.

MySQL Server – MySQL is a relational database management system server or a

database server.

Navicat – Navicat is a graphical database management and development software for

MySQL, MariaDB, Mircrosoft SQL, etc. It has a graphical user interface and supports

multiple database connections to both local and remote databases.

8
SCRUM – It is a simple framework for effective team collaboration on complex

products.

UML (Unified Modeling Language) – It is a standardized modeling language that

consists of an integrated set of diagrams and helps system and software developers to

specify, visualize, design and document artifacts of software systems as well as

commercial models and other non-software systems.

VB.NET – Visual Basic .NET is an object-oriented programming language,

implemented on the .NET Framework. It provides a graphical user interface that

allows the software developers to design the software and modify the code by

dragging and dropping the objects.

 9
CHAPTER II

REVIEW OF RELATED LITERATURE AND STUDIES

With the help of technology these days, many things just gotten better. It

contributed a lot in many fields such as education, medicine, business and many more.

Many companies and businesses have changed their traditional and manual way of

processing their works in to advanced and computerized process. In this chapter, different

research works and literature is showed that helped in developing the Aldersgate College

Electronic Medical Record.

Related Literature

Electronic Systems

According to (Electronic Tutorials, 2013), Electronic Systems have inputs and

outputs, and the outputs are generated when processing the inputs. In addition, the input

signals may cause the process to change, or they may cause the system to function.

Therefore, the entrance to a system is the cause of the change, while the result of the

action that occurs at the output of the system due to the cause is called effect, the effect is

a result of the cause. In other words, an electronic system can be classified as causal

because there is a direct connection between its input and output. The analysis of

electronic systems and the theory of process control are generally based on this analysis

of cause and effect.

Record Management System

As stated by (Techopedia, 2014), Record Management System (RMS) is the

management of records for an organization throughout the entire life cycle of records. The
 10
steps in this management may involve the systematic and efficient control of the

formation, maintenance, and disposal of records and associated business transactions. As

a key component of operational efficiency, the management of data records increases the

value of the company's information resources.

Compiled from an article with respect to (Alby, 2004), Record Management

Systems consist of certain sets of processes, tools and associated control functions, which

are combined to record and store all information related to the project or organization. The

project manager uses it to manage the contract, records and procurement documentation.

The system is saved in an easily accessible file. Not all documents are records. According

to the definition of project management, records are documents that are kept as evidence

of the implementation of a specific action. The Records Management System classifies

between records and non-records (such as duplicates and general designs) that do not

require formal administration. Once a document has been declared as a record, it cannot

be changed and can only be deleted according to the system rules.

Electronic Record Management System

The author (Essin, 2010) stated that Electronic Record Management System also

uses semi-structured documents that both contain an authenticated partial texts created by

the user and indicators to a verbal record that will be processed by transcribers. The

written material is detained in temporary storage until the writer reviewed and approved

the document. The approved document may be combined with the original authenticated

partial texts to produce a final authenticated document. In addition, the record

management system may include an instrument for allocating multiple contextual

meaning to a portion
 11
of the information items included in a document. The record management system,

therefore, enables a large number of coding patterns to be automatically superimposed on

each document. This offers the possibility of using the information for secondary

purposes, such as the creation of invoices (e.g. Medicare invoices) that must comply with

arbitrary sets of rules.

According to (Jacobson, 2010), an electronic record management system requires

a method, apparatus, and an article of manufacture to manage electronic records in a

computer network. The method provides the stages to create an electronic tag that has

unique identifiers that store and distribute an electronic record. The method continues the

steps of analyzing the specification of the workstation of a network user, analyzing the

profile of a network user and generating a reference code, in which the electronic label is

generated from the information generated by the specification of the network user's

workstation, the network user's profile, and the reference code.

Related Studies

Software-based Record Management System with Access to Time-line Ordered

Clinical Data Acquired by an Implanted Device

As indicated by (Chen, 2004), a software-based medical record management

system includes access to timed clinical data that has been captured or stored by at least

one implanted device. The system allows the management of data that is classified with

respect to the time at which cardiac events and events were recorded by at least one

implanted device. An interactive screen allows the user to review the therapy, diagnosis

and medical device data in a timely manner.

 12
Medical Record Management System and Process with Improved Workflow
Features

The researchers (Clark, Finley, Huska, Kabel, & Graham, 1999) stated that a

patient medical record system contains several nursing staff using a computer and a

patient records database with patient data linked to the caregiver’s computer provision of

access to patient data by one of the caregiver's computer that responds to a default set of

access rules. The default set of rules includes a rule that can be accessed a predetermined

part of the patient data by a first caregiver must be terminated before a second caregiver

can access the same predetermined part.

Knowledge Based Electronic Clinical Record for Dentistry

In the study of (Rhodes, 2012), the present invention is a clinical records

management system that includes the need for complete and accurate records while

reducing the time and effort required to record complete and accurate information.

Although the application uses the terminology used in dentistry, the division of

terminology into specific digital forms of the process is unique and forms a domain-

specific knowledge base. This organization represents algorithms that are also domain-

specific knowledge. When a selection is made from these forms and the application

automatically generates the notes that make up the patient's clinical records. The present

invention uses a configurable computer graphic user interface (GUI) to achieve an

efficient and uniform data input flow that can then be viewed in various ways or

converted into a variety of documents to share patient clinical information with other

providers of medical care.

13
Patient Information Management System for Clinical Evaluation and Content

Delivery

Based on the research of the author (Gottesman, 2005), the present invention is a

system and method of collection and delivery of medical content and related information

for patients, caregivers, and stakeholders’ third parties in predetermined terms. In

particular, the present invention relates to a system and method to provide relevant

medical and educational information patients and relief from remote medical visits.

Clinical Management System (CMS)

According to (Ping, 2004), the clinical management system is a user assistance

system that doctors and nurses can use to manage patient records. There are two main

modules that must be developed in CMS: the module for electronic patient records and the

module for reports. CMS not only offers a better solution by using a computer system but

also an efficient and systematic administration environment within the clinic. In addition,

this system can create a data repository and provide simplified reports to the user. Studies

have been conducted on the current manual process and a similar clinical management

system over the Internet to understand how to implement an effective computer system

for clinics.

Computerized Record Management System for Bayombong Polyclinic, Bayombong,

Nueva Vizcaya

As stated by (Garlitos, Torralba, Ruiz, & Manalo, 2015), the records management

system is designed and developed to improve the current system and address the needs

and problems of the Bayombong Polyclinic, especially when it comes to records

management.
 14
It aims to make services to collect, provide and manage patient records more efficiently

for owners and employees. The system is a client-server system with a central database in

which all patient information is stored, in which only the administrator and staff are

authorized to control the system. This reduces the problem of searching, storing,

retrieving data and sorting records.

Web-based Electronic Medical Record System for Dr. Thomas Sr. and Maria

Quilang Medical and Maternity Clinic

In the study of (Aguilar, Bimmulog, Pulao, & Umbalin, 2014), the Web-based

Electronic Medical Record System provides a digitized option for storing patient

information, medical history and invoices as well as employee profiles in the doctor and

maternity clinic of Dr. Thomas Sr. and Maria Quilang. This helps with the organization,

recovery, and data storage issues that the clinic encounter. The developed system can

manage patient records, prescriptions, categories of medication, medication, diagnostic

reports, appointments, the quota for beds, beds, bills, reports, departments, and user

accounts. System data can also be backed up and restored to avoid data loss.

Electronic Health Record System of Nueva Vizcaya Provincial Health Office

As indicated by (Antonio, Camannong, Deocaris, Eneja, & Lizada, 2015), the

Electronic Health Record System is a record system that is a LAN-based system. The

system can add, edit, update and store records of patients. It can also filter records and

produce necessary reports like medical certificates. The system can help the user place the

information of the patients easily by accessing the system on a web server through a LAN

connection. The system is developed to replace its manual system of record management.
 15
Record Management Information System for RHU Diadi

According to (Padilla, Pascua, Guinubang, Lannu, & Lannu, 2016), the

researchers designed and developed the record management system for the expansion

activities of the participants to improve the current system and address the essential and

doubtful circumstances of RHU Diadi, particularly when registering patient medical

records. It is a stand-alone system with a central database, in which all the information of

the participants is stored, which are the residents encrypted by the health personnel. This

reduces the dilemma of storing, retrieving data and sorting records.

A Computerized Patient Information System of Bayombong Rural Health Unit,

Bayombong, Nueva Vizcaya

As stated by (Alegre, Bonalos, Fulgencio, Quinones, & Tangonan, 2006), the

system was designed and developed for the Bayombong Rural Health Unit so that

employees can easily access, store and access patient records from the system. In addition,

in contrast to manual execution, report generation can also be faster and more presentable.

It is also a great advantage for patients who can be supported by RHU employees because

employees have more time to attend them.

An Online Medical Information System (OMIS) of Nueva Vizcaya State University,

Medical Clinic

In the study of (Ambatali, Domingo, Flores, & Verano, 2011), the system contains

the patient profile of the NVSU clinic; each record contains personal information of the

patient. It is deliberately done to have a convenient list of records to have a quick and easy
 16
search area that facilitates access, keep records intact while backing up those records. The

system also has the capability to add, edit, delete, and search for records.

Synthesis

The researcher found that the literature and related studies mentioned are

applicable and parallel to the application and use of the Aldersgate College Electronic

Health Record. The benefits of implementing the proposed system at Aldersgate College

School Clinic are supported by implementing the proposed system, which is a better and

more reliable means of assessing students and manage records inside the school clinic.

They can also enhance their security in storing their records against damages and record

loss.

17
CHAPTER III

RESEARCH METHODOLOGY

This chapter discusses the research design, research environment, research

instrument, and description of participants, development tools, phases and the

methodology used in developing the proposed project – Aldersgate College Electronic

Health Record.

Research Locale

The study was conducted at Aldersgate College, Inc. School Clinic. The school is

located at Espino Street, Barangay Quirino, Solano, Nueva Vizcaya, Philippines near

Solano Public Market.

Research Design

In this research, Quantitative research method was used. Questionnaires are

answered by the participants and converted the results into a graph, and by calculating for

the mean score for each questions and the overall total.

Agile Methodology refers to a group of software development methodologies that

promotes continuous iteration of development and testing throughout the project software

development life cycle. Unlike the waterfall model, development and testing activities are

carried out simultaneously.

Scrum Framework is an agile method of managing a project, usually software

development. Scrum explains the collaboration, the work software, the self-administration

of the team and the flexibility to adapt to the new economic circumstances. The main role

18
of Scrum is the "Scrum Master". Scrum Master acts as an instructor, coach, or moderator

to oversee the team and user who creates a particular project that uses the Scrum method

correctly, and the team focuses on the assigned task.

"Scrum Sprint" is a regular and repeatable work cycle in the Scrum method, in

which the work is completed and prepared for review. Scrum sprints are basic

development units in the Scrum method. Scrum Sprint is led by a sprint planning

meeting, in which sprint tasks are defined and recognized and the estimated sprint goals

are created. The scrum sprint is followed by a sprint review that examines the task of

identifying lessons that can improve the next sprint.

Description of Participants

The success of the Aldersgate College Electronic Health Record can only be
achieved and achieved with the full participation of users, so that the system takes over

the full function.

School Nurse/Authorized Personnel – They are the ones in charge of accessing the

system and assessing the students that come to the clinic.

Student – They are the patients and the persons that are assessed in the

clinic. Research Tools

This section discusses the different tools that the researcher used that can help in

developing the Electronic Health Record for Aldersgate College School Clinic.

Direct Interview – The researchers conducted a direct interview on the current feed

procedure for the assessment of every student that comes into the clinic. The

researcher

19
determined the data collected and observed and used to generate insight system

functionality.

Observation – To validate the data collected from the interview, the researchers also

conducted observations on the site, to know the procedure followed by the students,

and the school nurse or clinic personnel.

Online Research – In order to make the system more responsive to client needs, the

researcher browsed the internet for better ways to present information that would be

useful to the client.

Documents Review – The researcher performed a document review on how the clinic

assess their students took a sample document on the processes involved at Aldersgate
 College School Clinic.

Questionnaire – To evaluate the effectiveness and the capabilities of system, the

researcher prepared a questionnaire that will be distributed to a certain number of

respondents.

Likert Scale – The researcher will use the Likert Scale to measure the effectiveness of

the software based on the responses of the respondents on the questionnaire. It is a

psychometric scale commonly included in studies that use questionnaires. This is the

most widely used approach for scaling responses in survey research.

Research Instruments

This section discusses the different instruments that the researcher used that can

help in the development of the proposed system.

20
ISO 9126 – The researcher used the ISO 9126 to meet the goals and objectives of the

study and as a basis for better software quality and development of the software. It can

help the researcher to set software standards such as its functionality, usability,

reliability, efficiency and meet the software requirements.

Functionality – It is a set of attributes that affect the existence of a set of

functions and their specified properties. The functions must meet the specified or

implied requirements.

Usability – It is a set of attributes that relate to the effort required for the use and

to the individual evaluation of this use by a specific or implicit group of users.

Reliability – It is a set of attributes that affect the ability of the software to

 maintain its level of performance under certain conditions for a period of time.

Effieciency – It is a set of attributes that affect the relationship between software

performance and the number of resources used under the specified conditions.

Unified Modeling Language – UML is a basic and traditional language for

identifying, visualizing, creating and checking the manufactured object of software

systems. In this study, the researcher used UML to provide a visual representation of

our design and system process.

Astah UML – Astah UML is a UML modeling tool. The researcher used this software

to create different UML diagrams.

21
Research Procedure

Figure 3.0 Scrum Process

In this study, the researcher used the Scrum Process, a form of agile software

development. Agile software development is used to relate the methods for incremental

software development. It is an alternative to conventional project management, in which,

in addition to continuous planning, testing, and integration, it is important to train

employees to participate and make team decisions. It is an analysis of approaches,

operations, methods and processes that have been selected to complete and achieve the
main idea and main objective of the proposed system. It refers to the data acquisition

techniques used in the research study of the proposed systems.

A Scrum process differs from other agile processes by specific concepts and

practices, which are divided into three categories roles, artifacts, and time boxes.

We use Scrum to create the Aldersgate College Electronic Health Record. The

development of this methodology comprises four main phases:

Inception Phase – In this phase, the researcher wrote a letter of request to the school

nurse at Aldersgate College. With the permission of the Aldersgate College school

22
nurse, the researcher collected information from the school clinic that could be useful

for conducting the study. The researcher conducted an interview and observation on

how they assess students and manage the records using the manual process, in

addition, the researcher also asked about the system requirements for the of

Aldersgate College Electronic Health Record. The researcher begins to identify

problems, set a goal and create a solution with scope and limitations.

Elaboration Phase – In this section, after investigating and analyzing the problem

domain, the researcher started working on the project and interpreted it in a complete

diagram that depicts the sequence of activities involved in managing the system. With

the use of UML, the researcher formulated sets of diagrams to visualize the proposed

system.

User Stories – These are the requirements from the user's perspective.

Use Case Diagram – It shows the functionalities and flow of the system. It

consists of actors, use cases and their relationships.

 Use Case Specification – It show the process and procedure of the system.

Use Case Analysis – The researcher used the use case analysis to identify the

system requirements.

Entity Relationship Diagram – It is a data model to delimit the properties of the

data or information and the existence of process requirements in a certain way,

which is suitable for a complete implementation in a database as a relational

database.

23
Construction Phase – In this phase, the researcher designed the prototype of the

Aldersgate College Electronic Health Record, and in this phase, the researcher began

coding the proposed system.

Test Plan – The researcher’s plan in testing the system with the presence of the

client.

Sprint Backlog – The researcher identifies the full task needed during sprint

planning. The researcher, select a task from the list that he/she can perform.

Transition Phase – In this phase, the researcher will deliver the system or bring it to

the client once the system has been developed. The researcher will support the client

in the administration and operation of the system.

Implementation Plan – This is planned and scheduled for various activities such

as software or hardware installation, user training, and system deployment.

Maintenance Plan – The planned procedure to maintain system quality and

technical issues.
Development Tools

This section discusses the different tools that the researcher used in developing the

Electronic Health Record for Aldersgate College, Nueva Vizcaya.

Microsoft Visual Studio – The researcher will use Microsoft Visual Studio to

develop the major and minor functions of the system. It is an integrated development

environment from Microsoft in which, is used to develop computer programs or

systems such as, mobile applications, web services, web applications, and websites.

24
VB.Net – Visual Basic .Net is the programming language that is chosen by the

researcher to develop the system.

Visual Basic Power Packs – is a Microsoft Visual Studio Extension. The researcher

will use this extension to make the Graphical User Interface more attractive.

Navicat – The researcher will use Navicat to build the system database. It is a series

of graphical database management and development software for MySQL, Microsoft

SQL Server, SQLite, Oracle, MariaDB, etc.

MySQL Server – The researcher will used this application as a server of the system.

It is a free, cross-platform, open-source server solution package developed by a

Swedish company, MySQL AB.

25
CHAPTER IV

RESULT AND FINDINGS OF THE STUDY

System Overview
 The Aldersgate College Electronic Health Record is a system that deals with the

assessment of students that comes into the school clinic. The proposed system was

developed using Visual Basic, Microsoft Visual Studio for the system design, MySQL

Server for the connection, and Navicat Premium for designing the system database. This

Windows Based Application handles the record of each student that is already assessed in

the inside the clinic. It allows the user to add, delete, update, and search for a student's

health record.

System Objectives

The implementation of Aldersgate College Electronic Health Record shall

primarily help the clinic personnel to assess the students faster and ease the task in

managing their records. The proposed system is also secured and cannot be accessed by

unauthorized persons. It also includes a system Activity Log to monitor the activity using

the system. The following are the features of the system includes managing student’s

health records, viewing and printing records, managing users, backup and restore data,

and monitors system activity.

The development of the proposed system was based on the quality criteria of ISO

9126 in terms of its functionality, usability, reliability, and efficiency. The ISO 9126 is a

template for an international software quality standard that helps create a strong

framework

26
for software evaluation. This model is used to represent cutting-edge research. It moves

into defining software properties with the primary purpose of verifying software quality

control, software quality assurance, and improving software performance. Using these

criteria, the researcher has come up with the following:

 1. A system that is capable of recording students’ information, stores documents and

has a virtual database wherein the records of students will be easily viewed and

retrieved. In addition, it can also backup and restore data.

2. A user-friendly Graphical User Interface (GUI) that can be easily understood by

the school clinic personnel to make the task easier.

3. A system that is reliable in terms of its security of data.

4. A more efficient system that saves more resources and expenses.

System Requirements

Table 4.0 System Requirements

Aldersgate College Hardware
Electronic Health
Record Processor: Minimum of 1.9GHz

Hard Disk: 500 GB

Memory: 2GB RAM

Keyboard and Mouse

Monitor

Software

Operating System: Windows XP,

Windows 7, 8 or 10

Connection: MySQL Connector

27
Operational Diagram
 Figure 4.0 Operational Diagram

The diagram shows the architecture and the flow of the project. The user will log

in to the windows application. From the windows application, it will deliver the data to

the MySQL server where all the data will be stored. From the MySQL server, it will be

transferred again to the application to display and be accessible by the user. As the data

are now accessible by the user, the application can print records from the database.

28
System Functions

Login
 Figure 4.1 Login Form

The Login form is the first form that shows when a user opens the system. It

enables the user to login and gains access to the system. It includes a Username textbox,

Password textbox, and a Sign In button wherein the user will enter its registered

username and password and checks its validity from the database by clicking the Sign In

button if the user is registered to the system. In addition, it also has Restore Database in

case a data is lost and needed to restore a database before a user can log in and a close

“X” label on the upper right corner of the form to exit the application.

29

igure 4.2 Login Code and Table user_accounts

The table above is the database table and code that is used to login into the system.

It will help the system to verify whether the user is registered and authorized or not and
will restrict unregistered users that will login into the system. This code will verify the

data entered into the username and password textbox from the database table if the user is

registered or not.

Main Form

Figure 4.3 Main Form

The Main form allows the user to manage student health records, manage users,

restore and backup database, and monitor the activity of the system. It also has a context

menu strip that can let the user view, update, and delete records. However, the Activity

30
Log, Manage User, Restore Database, and Backup Database can only be accessed by an

Administrator. It also includes Add Record that will allow the user to enter the Medical

Evaluation form for a new assessment, Print Records to print all displayed record in the

main form, Search Textbox for entering a name to search for a record, Courses Dropdown

List Box to search by courses, From/To Date Picker, Activity Log to view the activity of

the system, Manage Users to enter the Manage Users form, Restore and Backup Database,

Logout that allows the user to logout and back to the login form, and a close label on the

upper right corner of the form to exit the application.

 F

igure 4.4 Display Records Code and Table student

The Table shows the code and the database table that is used in the Data Grid

View from the Main form to display records from the database. This allows the user to

view the students that are registered in the system. The code will get the data from the

database table which is categorized by Name, Gender, Age, Course, Date of Exam, and

Number and displays it in the Data Grid View in the Main form.

31
Context Menu Strip

Figure 4.5 Context Menu Strip

The Context Menu Strip only appears when the user clicks in the data grid view in

the main form. It contains most of the functions of the system. This allows the user to

manage the student’s Medical Evaluation, Manage Student Information and, Manage
Health History. However, updating and deleting records are only accessible by the System

Administrator. It includes View Record, View Health Insurance and View Health History

for viewing the record of a student, Student Information and Health History to enter the

Student Information form and Health History form, Update Medical Evaluation, Update

Student Information and Update Health History to enter Medical Evaluation form, Student

Information form, and Health History form whenever an update to a student record is

needed, Refresh to refresh the main form, and Delete for deleting a selected student

record. The figure below shows the click events of the Context Menu Strip.

s u

n i

32
i

6.

r
33
Medical Evaluation

Figure 4.7 Medical Evaluation Form

The Medical Evaluation form allows the user to register a new student health

record, the same form that will show if the user clicks on the Update Medical Evaluation.

If the user clicks on the Update Medical Evaluation, the Register Student button will be

replaced with Update button. It will require the user to enter the Last Name, First Name,

Middle Name, Birthdate, Gender, Educational Stage, and Course or Grade Level. It also

contains the physical exam which is done during the medical evaluation, it composed of

checkboxes that will determine the student’s physical status and, Rich Textboxes for

student’s immunization, daily medications and, description of a student’s abnormalities or

disabilities. It also includes a Register Student button to register a student medical

evaluation and store the data to the database while on the Update Medical Evaluation, the

Update button will update the current record of a student, a Cancel button to go back to

the Main form, and a close label on the upper right corner of the form to exit the

application.

34
 F

igure 4.8 Medical Evaluation Code and Table student

The Medical Evaluation Code and Table student are used on recording medical

evaluations. On the Register Student button, the query was used to record the data of a

student into the database nevertheless, upon clicking the register button, it will determine

whether the student already has a record or a new record. If a student already has an

existing record, it will restrain the registration of the student.

igure 4.9 Update Medical Evaluation Code and Table student

On the Update Medical Evaluation, the Update Medical Evaluation Code was used

to update the existing record of a student from the database. Upon clicking the Update

Medical Evaluation from the Context Menu Strip, the Medical Evaluation form will show

with the existing record of the selected student from the Main form.

35
Manage Users
 Figure 4.10 Manage Users Form

The Manage Users form allows the System Administrator to manage all the

registered users. It has a Data Grid View wherein it displays the list of users that is

registered to the system and it is categorized by User Number, Name of the users,

Username and, Position. It also provides the registration of new user accounts to log in to

the system. It also can delete registered users and can only be accessed by an

Administrator. It includes the Register button that allows the Administrator to open Add

User form, Delete button to delete a selected user, a Close button to close the Manage

Users form and go back to the Main form, and a close label on the upper right corner of

the form to exit the application.

Figure 4.11 Display Users Code and Table user_accounts

36
The table above shows the database table and the code that is used to display all

registered users from the database. All the data from the user accounts is displayed on the

Data Grid View.

Add User

Figure 4.12 Add User Form

The Add User form allows the System Administrator to register a new user. It

requires user information such as first name, middle name, last name, username, and

password to register. It includes first name textbox, middle name textbox, last name

textbox, username textbox, password textbox and, confirm password textbox wherein the

System Administrator will enter the information given by the new user and, a Sign Up

button to register the data of the user into the database, and Back button to close the form

and go back to Manage Users form.

37

igure 4.13 Add User Code and Table user_accounts

The Add User Code is used to determine whether the registration is a new user or

not. New users of the system is recorded to the database table user_accounts. Upon
clicking the Sign Up button, the system will determine whether the username is already

registered or not, if it does, the system will restrict the registration of the new user.

Activity Log

Figure 4.14 Activity Log Form

38
The Activity Log form is where all the activity is done is recorded and can only be

accessed by an Administrator. It also allows the Administrator to view the recorded

activity in the system from a Data Grid View that is categorized by User type, Name,

Activity and, Date and Time. It also has a close label on the upper right corner of the

form to close the form.

F
igure 4.15 Activity Log Code and Table activity_log

This table shows the code that is used to record the activity of the system to the

database table activity_log. The query will send the data into the database table.
 F

igure 4.16 Display Activity Log Code and Table activity_log

This table shows the code that is used to display the activity log of the system. The

query will get the data from the database and displays all the record in the Data Grid

View.

39
Student Information

Figure 4.17 Student Information Form

This form allows the user to add student information to a registered student, the

same form that will show if the user clicks on the Update Student Information. If the

System Administrator clicks on the Update Student Information, the Update Information
button will replace the Add Information button. However, Update Student Information is

only accessible by a System Administrator. It contains Birth Place, Religion, Permanent

Address, Guardian Information, Father’s Name, Mother’s Name, Physician’s Name,

Dentist’s Name, and Health Insurance of a student. The Add Information button allows

the user to register the information entered in the text boxes and checkboxes while the

Update Information button updates the existing student information of a student, a Cancel

button

40
to go back to the Main form, and a close label on the upper right corner of the form to exit

the application.

Figure

4.18 Add Student Information Code and Table students_information

The Add Student Information query is used to enter data into the database table

students_information. The query delivers the data from the form to the database table.

Upon clicking Add Information button, the system will restrict invalid entry for the Home

and Cellphone number, and will not accept the registration if the required fields such as

Birth Place, Religion, Address, Guardian’s Name, Father’s Name, Mother’s Name, and

the Checkboxes for Health Insurance, Dental Insurance, preferred Physician and Dentist

if left empty.
 Figure

4.19 Update Student Information Code and Table students_information

On the Update Student Information, the user cannot enter the Update Student

Information form if the selected student doesn’t have student information recorded yet in

the database, if the selected student does have student information recorded, the existing

41
student information of a selected student will be displayed in the fields in the form. Upon

clicking the Update Information button, it will update the existing student information if

all the require fields are filled up.

Health History

Figure 4.20 Health History Form

The Health History form allows the user to add the health history and family

health history of a registered student. This form will also show if the System

Administrator clicks on the Update Health History, and the Submit button will be
replaced with Update button. However, only the System Administrator can access Update

Health History. It includes checkboxes which will determine if the student has any

medical conditions and a Rich Textboxes for other diseases, an explanation for all the

“Yes” answers and, discussion if there is anything the student or parent wanted to discuss

with the nurse. It also allows the user to record any medication of a student that is needed

to be done in school. The Submit

42
allows the user to register the student’s health history while the Update button allows the

user to update the existing Health History of a student, a Cancel button to go back to the

Main form, and a close label on the upper right corner of the form to exit the application.

igure 4.21 Add Health History Code and Table health_history

The table shows the code and database table that is used in adding health history
of a student. Upon clicking the Submit button, the Add Health History Query will record

the data to the the database table health_history. However, all the questions answered by

Yes or No must be filled up to successfully register the student’s health history.

43

Figure 4.22 Update Health History Code and Table health_history

The code and database table above it used on updating the recorded health history

of a student. The Update Health History Query will update the current record of a student

from the database table health_history.

44
View Record
 Figure 4.23 View Record Form

This form allows the user to view the record of a selected student from the Main

form. It contains the medical evaluation and information of the student. It includes the

Print button that will allow the user to print what is displayed in the View Record form

and a Back button to close the form and go back to the Main form.

45
 Figure 4.24 View
Record Codes and Tables

46
The table above is the list of database table and vodes that is used to display the

record of a selected student from the main form. It gets the data from the database and

sends it to View Record form to display.

View Health Insurance

 Figure 4.25 View Health Insurance Form

This form allows the user to view if a student has health insurance, dental

insurance. It also contains the name of the preferred physician or dentist in case of an

emergency. A Back button is included to close the form and go back to the Main form.

47

igure 4.26 View Health Insurance Code and Table health_insurance

The View Health Insurance Code is the query that is used to get the recorded

health insurance of a selected student from the database table health_insurance. It

retrieves the data from the database and sends it to the View Health Insurance form to

display.

View Health History

 Figure 4.27 View Health History Form

48
This form allows the user to view the health history and family history of a

selected student from the Main form. It includes a Print button that will allow the user to

print the health history of the student and back button to close the form and go back to

the Main form.

 Fi

gure 4.28 View Health History Code and Table health_history

The View Health History Code is used to get the recorded health history from the

database table health_hitory of a selected student. The query retrieves the data from the

database and sends it to the View Health History form to display.

49
Evaluation

Software evaluation has been an established practice for improving software

development. Not only to evaluate in the sense of exercising the code using examples but

also to evaluate in the sense of taking a development step and then reflecting on the

results of the step to see if they were really what that was expected. In this research, the

idea of evaluation is adopted as an integral part of the software development process

which is carried out at all stages in order to satisfy the users' needs.

The development of any new system requires a solid foundation which in this case
is the system requirements. These requirements must be expressed in the most precise

way possible to avoid any failure of the system to occur. We refer to the requirement as a

condition or ability necessary for a user to solve a problem or achieve a goal. The system

requirements are a description of the environment in which the system will operate, as

well as a list of the requirements that the system must meet.

A Likert scale is a 5 or 7 point scale, used to describe how much people agree or

disagree with a particular statement. According to (Boone, Jr. & Boone, 2012), the Likert

scale consists of a series of four or more Likert-type items that are combined into a single

composite score or variable during the data analysis process. These elements are used in

combination to provide a quantitative measure of a personality or personality trait.

Researchers are generally only interested in composite scores that represent personality or

personality traits. To properly analyze the Likert data, you need to understand the

measurement scale that each one represents. The numbers assigned to Likert-type items

represent "greater than" relationships. However, it doesn't mean it's much bigger than that.

50
Likert scale data, on the other hand, is analyzed on an interval measurement scale. Likert

scale items are created by calculating a composite score (sum or average) of four or more

types of Likert-type items. Therefore, the composite score of the Likert scale must be

analyzed on the interval measurement scale. Recommended descriptive statistics for items

on the interval scale include the mean of central tendency and the standard deviation of

variation.

To test and improve the system’s effectiveness, the researcher prepared a Likert

Scale Questionnaire that is based on the quality criteria of ISO 9126 in terms of its

Functionality, Reliability, Usability, and Efficiency which has responded by twenty (20)

respondents.
Likert Scale:

Table 4.1 Likert Scale Values

Value Level of Satisfaction

1 Not at all satisfied

2 Not so satisfied

3 Neutral

4 Very satisfied

5 Extremely satisfied

51
Question No. 1 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE ADD RECORDS?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 3 5 11 Figure 4.29 Question No. 1 Respondents Distribution

Chart

The chart shows the distribution of respondents in Question No. 1. It indicates that

55% of the respondents are extremely satisfied, 25% are very satisfied, 15% neutral, and

5% are not so satisfied, with a total of 100% of respondents. This proves that the system is

effective and extremely satisfactory in adding records.

Question No. 2 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE UPDATE RECORDS?
 Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 6 12 Figure 4.30 Question No. 2 Respondents Distribution

Chart

In the Question No. 2 chart, the rating and distribution of respondents on how

satisfactory the system on updating records shows that 60% of the respondents are

extremely satisfied, 30% are very satisfied, 5% neutral, and 5% for not so satisfied, with a

total of 100%. This proves that the system is effective and extremely satisfactory in

updating records.

52
Question No. 3 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW THE SOFTWARE SEARCH FOR A RECORD?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 0 1 10 9 Figure 4.31 Question No. 3 Respondents Distribution

Chart

The presentation of Question No. 3 chart tells that, the rating and distribution of

respondents on how satisfactory the system on searching on a record is 45% are extremely

satisfied, 50% are very satisfied, and 5% for neutral, with a total of 100% respondents.

This proves that the system is effective and very satisfactory in searching for a record.
Question No. 4 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW THE SOFTWARE PRINT RECORDS?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 6 12 Figure 4.32 Question No. 4 Respondents Distribution

Chart

The chart for Question No. 4 shows the rating and distribution of respondents on

how satisfactory the system on printing records. 60% answered extremely satisfied, 30%

answered very satisfied, 5% neutral, and 5% not so satisfied, with a total of 100%. This

proves that the system is effective and extremely satisfactory in printing records.

53
Question No. 5 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW THE SOFTWARE DELETE A RECORD?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 2 2 6 10 Figure 4.33 Question No. 5 Respondents Distribution

Chart

In the chart for Question No. 5, the rating and distribution of respondents on how

satisfactory the system in deleting a record presents that 50% are extremely satisfied, 30%

are very satisfied, 10% are neutral, and 10% not so satisfied, with a total of 100%. This
proves that the system is effective and extremely satisfactory in deleting for a record.

Question No. 6 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW THE SOFTWARE RECORDS THE ACTIVITY O F THE SYSTEM?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 0 2 7 11 Figure 4.34 Question No. 6 Respondents Distribution

Chart

The rating and distribution of respondents on how satisfactory the system on

recording its activity is shown in Question No. 6 chart. It tells that 55% of the respondents

answered extremely satisfied, 35% are very satisfied, and 10% are neutral, with a total of

100%. This proves that the system is effective and extremely satisfactory in recording its

activity.

54
Question No. 7 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE PERFORM THE TASK ASSIGNED?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 1 0 2 5 12 Figure 4.35 Question No. 7 Respondents Distribution

Chart

The chart presents the distribution of respondents in Question No. 7. It shows that
60% of the respondents are extremely satisfied, 25% are very satisfied, 10% neutral, and

5% not at all satisfied, with a total of 100% of respondents. This proves that the system is

effective and extremely satisfactory in performing the assigned tasks.

Question No. 8 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE PRODUCE EXPECTED RESULTS?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 2 1 4 13 Figure 4.36 Question No. 8 Respondents Distribution

Chart

The chart shows the rating and distribution of respondents in Question No. 8. It

presents that 65% of the respondents are extremely satisfied, 20% are very satisfied, 5%

neutral, and 10% are not so satisfied, with a total of 100%. This proves that the system is

effective and extremely satisfactory in producing expected results.

55
Question No. 9 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE SECURITY OF OUR SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 4 7 8 Figure 4.37 Question No. 9 Respondents Distribution

Chart
 The rating and distribution of respondents on how satisfactory the security of the

system is presented in this chart. It presents that, 40% answered extremely satisfied, 35%

are very satisfied, 20% for neutral, and 5% not at all satisfied, with a total of 100%. This

proves that the system is effective and extremely satisfactory in terms of its security.

Question No. 10 Respondents Distribution

HOW SATISFIED ARE YOU ON THE EFFECTIVENESS OF THE SOFTWARE IN ST ORING DATA?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 8 10 Figure 4.38 Question No. 10 Respondents Distribution

Chart

The chart presents the rating and distribution of respondents in Question No. 10. It

shows that 50% of the respondents are extremely satisfied, 40% are very satisfied, 5%

neutral, and 5% not at all satisfied, with a total of 100%. It proves that the system is

effective and extremely satisfactory in storing data.

56
Question No. 11 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE BACKUP AND RESTOR E DATA?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 2 3 14 Figure 4.39 Question No. 11 Respondents Distribution

 Chart

With the rating and distribution of respondents in Question No. 11, 70% of the

respondents are extremely satisfied, 15% are very satisfied, 10% are neutral, and 5% not

at all satisfied, with a total of 100%. This proves that the system is effective and

extremely satisfactory in backing up and restoring data.

Question No. 12 Respondents Distribution

HOW SATISFIED ARE YOU ON HOW DOES THE SOFTWARE HANDLE ERRORS?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 0 4 7 9 Figure 4.40 Question No. 12 Respondents Distribution

Chart

In the Question No. 12, the rating and distribution of respondents on how

satisfactory the system in handling errors is distributed 45% for extremely satisfied, 35%

for very satisfied, and 20% for neutral, with a total of 100%. The chart proves that the

system is effective and extremely satisfactory in handling errors.

57
Question No. 13 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE RELIABILITY OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied
 Number of Respondents 0 1 1 6 12 Figure 4.41 Question No. 13 Respondents Distribution

Chart

The chart presents the rating and distribution of respondents in Question No. 13. It

shows that 60% of the respondents answered extremely satisfied, 30% are very satisfied,

5% neutral, and 5% not so satisfied, with a total of 100%. The chart proves that the

system is extremely satisfying in terms of its reliability.

Question No. 14 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE INTERFACE OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 11 7 Figure 4.42 Question No. 14 Respondents Distribution

Chart

The Question No. 14 chart presents the rating and distribution of respondents on

how satisfactory the User Interface. It shows that 35% of the respondents answered

extremely satisfied, 55% are very satisfied, 5% neutral, and 5% not so satisfied, with a

total of 100%. The chart tells that the system’s interface is very satisfactory.

58
Question No. 15 Respondents Distribution

HOW EASILY DOES THE SOFTWARE CAN BE UNDERSTOOD?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
 Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 2 0 5 13 Figure 4.43 Question No. 15 Respondents Distribution

Chart

This chart is proof of the rating and distribution of respondents in Question No.

15. It shows that 65% of the respondents are extremely satisfied, 25% are very satisfied,

and 10% are not so satisfied, with a total of 100%. This proves that the system can be

easily understood.

Question No. 16 Respondents Distribution

HOW EASILY DOES THE SOFTWARE CAN BE LEARNED?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 0 3 7 10 Figure 4.44 Question No. 16 Respondents Distribution

Chart

In Question No. 16, the rating and distribution of respondents on how easily the

system can be learned are distributed 50% are extremely satisfied, 35% are very satisfied,

and 15% are neutral, with a total of 100%. The chart proves that the system can be learned

easily.

59
Question No. 17 Respondents Distribution

HOW WELL DOES THE SOFTWARE CAN BE OPERATED WITH MINIMAL EFFORT?

Extremely satisfied
 Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 9 9 Figure 4.45 Question No. 17 Respondents Distribution

Chart

The chart shows the rating and distribution of respondents on how satisfactory the

system can be operated with minimal effort. It is indicated that 45% of the respondents

answered extremely satisfied, 45% are very satisfied, 5% neutral, and 5% not so satisfied,

with a total of 100%. This proves that the system is extremely satisfactory nor very

satisfactory in operating with minimal effort.

Question No. 18 Respondents Distribution

HOW SATISFIED ARE YOU ON THE ATTRACTIVENESS OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 1 10 8 Figure 4.46 Question No. 18 Respondents Distribution

Chart

The rating and distribution of respondents with the attractiveness of the system is

presented in this chart. It shows that 40% of the total respondents answered extremely

satisfied, 50% are very satisfied, 5% neutral, and 5% not so satisfied, with a total of

100%. It proves that the system’s attractiveness is very satisfactory.

60
Question No. 19 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE RESPONSE TIME OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 2 4 13 Figure 4.47 Question No. 19 Respondents Distribution

Chart

The chart shows the rating and distribution of respondents in Question No, 19. It is

indicated that 65% of the respondents are extremely satisfied, 20% are very satisfied, 10%

are neutral, and 5% not so satisfied, with a total of 100%. This proves that the response

time of the system is extremely satisfactory.

Question No. 20 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE NUMBER OF RESOURCES SAVED OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 0 2 7 11 Figure 4.48 Question No. 20 Respondents Distribution

Chart

The rating and distribution of respondents on how satisfactory the system in

saving resources is proven in this chart. It shows that 55% of the respondents are

extremely satisfied, 35% are very satisfied and 10% are neutral, with a total of 100%.

This proves that the system is effective and extremely satisfactory in saving resources.
 61
Question No. 21 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE EFFICIENCY OF THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 1 0 7 12 Figure 4.49 Question No. 21 Respondents Distribution

Chart

The chart presents the rating and distribution of respondents in Question No. 21. It

presents that 60% of the respondents are extremely satisfied, 35% are very satisfied, and

5% for not so satisfied, with a total of 100%. This proves that the system is effective and

extremely satisfactory in terms of its efficiency.

Question No. 22 Respondents Distribution

HOW SATISFIED ARE YOU WITH THE SOFTWARE?

Extremely satisfied
Versy satisfied
Neutral
Not so satisfied
Not at all satisfied
0 2 4 6 8 10 12 14 16 18 20

Not at all satisfied Not so satisfied Neutral Versy satisfied Extremely satisfied

Number of Respondents 0 2 0 5 13 Figure 4.50 Question No. 22 Respondents Distribution

Chart

The chart shows the rating and distribution of respondents on how satisfactory the

system is. It shows that 65% of the respondents are extremely satisfied with the system,

while 25% are very satisfied, and 10% are not at all satisfied, with a total of 100%. This
proves that the system is effective and extremely satisfactory.

62
Interpretation of Data

In this section, results, analysis, and interpretation of data gathered in the study are

presented. The mean score in each question will be the basis to determine the quality of

the developed system Electronic Health Record for Aldersgate College School Clinic.

To calculate for the mean score, get the sum of Number of Respondents multiplied

by the value of the responses in each level of responses, divided by the total number of the

respondents [(NoR*1)+(NoR*2)+(NoR*3)+(NoR*4)+(NoR*5)]/20.

To determine the minimum and maximum length of the 5-point Likert scale, the

range is calculated as (5-1 = 4) and divided by 5. This is the maximum value of the scale

(4/5 = 0.80). Then a minimum of 1 was added to the scale to identify the maximum of this

cell. The length of the cell depends on the following factors:

Table 4.2 Mean Score Interpretation

Range Value Quality

1 to 1.80 Very Poor

1.81 to 2.60 Below Average

2.61 to 3.40 Average

3.41 to 4.20 Above Average

4.21 to 5 Excellent
 63
Table 4.3 Evaluation Summary
Questi 1 2 3 4 5 Mean Quality
on No. Not at Not so Neutral Very Extreme
all satisfied satisfied ly
satisfied Satisfied

1 1 3 5 11 4.3 Excellent

2 1 1 6 12 4.25 Excellent

3 1 10 9 4.4 Excellent

4 1 1 6 12 4.45 Excellent

5 2 2 6 10 4.2 Above
Average

6 2 7 11 4.45 Excellent

7 1 2 5 12 4.35 Excellent

8 2 1 4 13 4.4 Excellent

9 1 4 7 8 4.1 Above
Average

10 1 1 8 10 4.35 Excellent

11 1 2 3 14 4.5 Excellent

12 4 7 9 4.25 Excellent

13 1 1 6 12 4.45 Excellent

14 1 1 11 7 4.2 Above
Average

15 2 5 13 4.45 Excellent

16 3 7 10 4.35 Excellent

17 1 1 9 9 4.3 Excellent

18 1 1 10 8 4.25 Excellent

19 1 2 4 13 4.45 Excellent
 20 2 7 11 4.45 Excellent

21 1 7 12 4.5 Excellent

22 2 5 13 4.45 Excellent

The table shows summary of responses and the mean score in each questions.

Based on the evaluation and the responses of the respondents to the questionnaire that is

based on the quality criteria of ISO 9126, the developed software, Electronic Health

Record for Aldersgate College School Clinic has met the standards in terms of the

systems Functionality, Reliability, Usability, and Efficiency which is proven by the charts

that is presented.