MEDITOR: Medical Monitoring System with Analytics

Monzon, Elvin Leonard Reyes

Lyceum of the Philippines
University Cavite Campus
Governor's Drive, General Trias,
Cavite
+639168535112
zangalama13@yahoo.com

Anis, Marc Joseph Morales

Lyceum of the Philippines
University Cavite Campus
Governor's Drive, General Trias,
Cavite
+639351528100
marcaniz@yahoo.com

Fortuna, Jan Ransell Rodriguez

Lyceum of the Philippines
University Cavite Campus
Governor's Drive, General Trias,
Cavite
+639051339108
wewfortuna@yahoo.com.ph

Cano, Kenniel Francis Albania

Lyceum of the Philippines
University Cavite Campus
Governor's Drive, General Trias,
Cavite
+639062046600
ken21mage@yahoo.com

Mendoza, Genson Poblete

Lyceum of the Philippines
University Cavite Campus
Governor's Drive, General Trias,
Cavite
+639478925639
wanderer_son@yahoo.com

ABSTRACT

1. INTRODUCTION

The MEDITOR: Medical Monitoring System with Analytics is a

system which is specifically intended for the Health Services
Department (HSD) of Lyceum of the Philippines University
Cavite Campus. It is a standalone system with three main features,
first is monitoring where it keeps track to all the patient records
within the university, second is the inventory that monitors all the
medical supplies and medicines, and lastly the analytical reports
that shows users the top five mostly used medicines and top five
mostly treated medical cases within the department. The
methodology used for the system is Prototyping because there was
only a period of a whole year given for the development of the
system.

The medical field is a vast and broad field of study where many
people find it fascinating. Today, the field of medicine is much
revolutionized and it keeps evolving as experts find new medical
breakthroughs. These breakthroughs bring the medical field to its
prime and on its highest point in our history, innovations in
machinery, medical equipment, treatments for incurable diseases
and other helpful inventions that could help the whole industry.
These innovations help people improve their ways of living and
prolonging their lives. Inventions help us to have more convenient
and pleasant life, thus there are people who devote themselves on
finding
and
crafting
new
ideas.

Tests were conducted for the system, wherein it was judged using
these four categories namely: functionality, content, reliability and
availability. From these categories the system gained a grand
mean of 3.21 having a good qualitative interpretation. For the
evaluation, it consists of seven categories namely: accuracy,
efficiency, reliability, security, user-friendliness, flexibility and
validity. From these categories the system gained the grand mean
of 4.18 and a 0.68 standard deviation with a qualitative
interpretation acceptable.

Categories and Subject Descriptor

H.2.3 [Database Management]: SQL; D.3.2 [Programming
Language]: C#

General Terms
Management, Security, Performance,
Standardization and Verification

Design,

Reliability,

The Lyceum of the Philippines University Cavite Campus

Health Services Department (HSD) is an essential part of the
university which is responsible for maintaining all the medical
and health conditions of all the staff, students and faculty
members of the whole university. They keep all the records,
monitor all health conditions of the patients who needs
medications and other issues which needs medical attention.
MEDITOR is a system which provides Lyceum of the Philippines
University Cavite Campus to track all records of the students,
staff and faculty members of the whole university. The system
also provides a small inventory system that monitors all the
medical supplies such as medicine and other medical supplies that
needs to be replenished or refilled in a regular time. Analytical
reports are also provided to show users the top five most treated
medical cases within the Health Services Department (HSD) and
also the top five medical supplies and medicines mostly consumed
and distributed to all patients.

Keywords
MEDITOR, Medical Monitoring, Analytics, Inventory, Health
Services Department, HSD

1.1 Project Context

Health Services Department (HSD) are the ones responsible for

all the medical concerns within the school. With a staff composed
of not more than ten, they are in charge of all the medical
concerns of thousands of students who have conditions which
should be treated sensitively.
Within the Health Services Department (HSD) all processes are
done manually. All records are made out of paper works and kept
within file cabinets. This process is the only way used by the
Health Services Department (HSD) to monitor all the records kept
within the department.
The researchers discovered from interviews that there are three
main problems of the Health Services Department (HSD). These
include data inaccuracy, data redundancy, and information
insufficiency. Data inaccuracy occurs when the data given by the
patients were incorrect, there arises the need to rewrite another
form and create another document. Next is data redundancy, this
problem occurs when a different user creates a patient profile for
the database of the department while another user had already
created a profile. The last problem is the information
insufficiency, this occurs when the patient did not supply enough
information and the medical staff forgets to remind the patient to
supply their complete information. The data that is insufficient
would now be neglected and be stored within the department.
Another issue is about the inventory of the supplies within the
department which is only monitored when the nurse checks if a
certain supply is available. Sometimes, when a particular
medicine is not available, the nurses only ask the patient to do a
kind of treatment that will help the patients to ease the pain they
are experiencing. As a normal approach, these would be a good
method, but it would be more advisable if they could provide a
good quality medicine that would act as a pain reliever for the
patient.

1.2 Project Description

Monitoring, inventory and analytical reporting are the main
features of the MEDITOR: Medical Monitoring System with
Analytics. Monitoring is concerned with keeping track of all the
patient records within the system. Inventory on the other hand
monitors all the medical supplies and medicines within the Health
Services Department. The analytical reports show the user which
medical cases are commonly treated and which medical supplies
and medicines are given out to patients.
Besides keeping track of the entire patients information,
monitoring is also concerned with maintaining all the records
accurately. It also helps in prioritizing patients who need more
medical attention and all medications that need to be regularly
stocked from the inventory by using analytical reports. The
inventory has a notification feature that shows the user which
medical supplies and medicine are nearly expired and decreasing
in number. This feature is shown within the home page so the user
can easily see if the inventory needs to be checked.
The analytical reports have filters that help the user to narrow
down the charts which show the information about the mostly
treated cases and mostly used medications. These reports could be
filtered by month and year to produce more accurate and more
relevant results.

From all these features, the system applies a complex user level
for all the users. Each user only sees the feature tailored for the
user level allotted to them. The administrator of the system is the
university physician. She is responsible for user account
management, adding colleges, major medical consultations and
prescriptions, and viewing all the reports within the system. The
nurse is responsible for all minor consultations, encoding all the
patient information, dispensing all kinds of medications and
inventory management. They are entitled to use the checkup and
medicine repository module based on their responsibilities and
user level. The dentist which is responsible for all the dental
consultations and prescriptions are entitled to use the dental
records module. The secretary is responsible for all the reports and
communications with the other departments within the university
who have concerns with the Health Services Department (HSD),
these tasks enables the secretary to use the reports module that
contains all the generated reports of the system.

1.3 Objectives of the Study

1.3.1. General Objectives
The objective of the study is to design MEDITOR: Medical
Monitoring System with Analytics with the features: add, edit,
update and delete medical records of all the patients within the
system; maintaining the system inventory by showing
notifications about the nearly expired medications and supplies
that are decreasing in number; generating analytical reports which
shows the user the mostly treated medical cases and mostly used
medications; create a system using C# programming and Navicat
Lite as its database manager; test the system using certain
criterion such as accuracy, efficiency, reliability, security, userfriendliness, flexibility and validity; and, finally to evaluate the
overall system by the above stated criterion.

1.3.2. Specific Objectives

Specifically, the system performance will be measured based on
the following criteria:
a)
b)
c)
d)
e)

f)
g)

accuracy the system should be able to produce good

and correct amount of data that could really help the
users on their processes and tasks;
efficiency the system should give the users effective
solutions to their problems and difficulties;
reliability the users of the system should depend on
the automated processes run and executed by the
system;
security - the system must provide high level security to
its users and all the contents about patients within the
whole system;
user-friendliness the user regardless of their
knowledge about technology and automated systems
must feel at ease and comfortable when using the
system;
flexibility the system must be able to adapt in any
kind of situations that could be a threat or hindrance to
any of the processes within the system itself;
validity the system should be able to produce
authenticated results from all the authorized users of the
system.

1.4 Scope and Delimitation of the Study

The scope of the system includes monitoring all the patient

records in the form of record keeping, inventory management that
shows the complete list of nearly expired medications and
supplies that are decreasing in number, analytical reports that
filters the mostly treated cases and mostly dispensed medications
and supplies from the inventory.
As of now, the system is limited to all the data encoded by the
users. The researchers aim to connect to the university database to
lessen data entry processing. However, due to the presence of a
security threat, the university doesnt allow any system to connect
to its database according to university policies.

1.5 Significance of the Study

The researchers conducted this study for the benefit of the
following end users: the nurses, the university physician and
dentist, and the secretary.
The nurse handles all the processes and executes all the tasks that
directly affect the jobs of the physician, dentist and the secretary.
With the automation of the system that complements the manual
processes, the nurse could easily record all the important patient
information that would be later viewed by the physician/dentist
when they will conduct a checkup or give out prescriptions to the
patients. After this the nurse would now dispense the medical
supplies or medicines that would be given to the patient and now
be deducted from the automated inventory system. Hence, the
secretary will now compile and review all the reports concerning
all the processes done by the nurse, physician and dentist. From
these stated processes, it shows the benefits gained by each user
from the automated system made by the researchers.
All of these users have the benefit of using a system that is
specifically made to answer their needs or compliment their
current approach. For the developers, they have the benefit of
enhancing their skills in making a dynamic system using another
software that they have not yet encountered. This is another
experience that serves as the developers training ground in
making programs or systems that could help improve processes of
certain firms and companies.

2. REVIEW OF RELATED LITERATURE

AND STUDIES
Review of related literature and studies provides the researchers
with base of knowledge that will help them in building up
concepts and formulating ideas for the study. Referring to other
researchers works and studies will enable the researchers to
elaborate and understand more about the nature and scope of the
study. This will broaden their knowledge and will allow them to
relate the study with previous works. Moreover, this is significant
and will be helpful in constructing the study.

2.1 Review of Related Literatures

The review of related literatures is concerned with discussing all
kinds of articles that had relations with the researchers project.
The articles that will be mentioned below explains the reasons

why the developers chose to develop the whole project they

proposed.

2.1.1 Monitoring System

Offshore Magazine featured an article that shows a company
named Wintershall Noordzee and Dutch that uses a monitoring
system mainly concerned with reducing costs associated with all
the offshore platforms and improving the productivity and
effectiveness of the operations of their maintenance teams. The
system uses real time reporting to optimize the production from
the company reservoir to their exports. The data gathered from the
system features early detection of all oil wells that help the
engineers and operators make informed decisions to assist
operations. [1]
According to the article, a monitoring system is used to observe
certain kinds of production materials that are needed to create a
single product. The data gathering and storing process goes round
the clock and is saved up into the main module of the monitoring
system. After this all information about the production is compiled
and subjected to reviews and reports.
The system uses monitoring solely as a record keeping module. It
starts the monitoring process when patient records are encoded
within the system and it also has impact on the inventory module.
The inventory software uses the monitoring through the
notification feature which notifies the user which products are
almost empty and which products are nearly expired.

2.1.2 Computerized Record Keeping System

A computerized system and a manual system act the same when it
comes to a certain principle, but a computerized system automates
all the processes so it becomes faster and more accurate. MS
Money and Quicken are some examples of the programs that can
be used to eliminate manual processes. The users can easily input
information and assign a specific category where it is included so
the system could easily organize all its contents. [2]
The article states that using a computer on a record keeping
system revolutionizes all manual processes which hasten the
process of storing all kinds of data. It also increases the accuracy
of the user in editing, creating and making the information more
understandable and presentable. In relation to the system, record
keeping is the main concern of the monitoring system. All the
patients records are stored in the database which can still be
updated and edited without deleting the old record and creating a
new one. These are basic CRUD functions that are needed for a
simple system.

2.1.3 Standalone
A standalone system works properly without the help of another
program of software. An example is a television hooked up with a
TiVo Box that has the capacity of recording shows is a standalone

device, while a DVR needs to be connected to a digital cable box

is not a standalone device. Integrated devices are less expensive
but standalone devices allows the user have greater customization.
[3]

The system is a standalone software mainly because it does not

need other programs to execute its purpose and processes. All the
system needs a user that will guide the system which processes
will be done and made by the system.

2.1.4 How Inventory Management Systems

Work

An inventory management system

provides
customers satisfaction if the system is regularly
maintained. From a scale of big companies to
smaller businesses and vendors, an inventory
system is an essential part of the business. It
provides the business a way to easily manage and
maintain all their products. For the customers, the
owner of the business can easily show them which
of the products they need are available for purchase.
Faster production rates, proper organization of
products and having a wide variety of choices
between products are just few factors that may
affect the business. [4]
The system uses the inventory module as a supplement to the
monitoring module. The inventory module is used to store all the
information about all the medicines and medical supplies within
the Health Services Department. It also notifies the user whenever
there are supplies that are nearly empty and expired so the user is
able to know that they should update the inventory.

2.1.5 Applying advanced analytics in

consumer companies

Advanced analytics gives aid to businesses by

showing day-to-day analysis and it allows the
business to get the opportunity to make better and
faster decisions and improve their overall
performance. From advanced analytics businesses
easily determine even the most intricate information
that fits the consumers taste. Not just satisfying the

consumers satisfaction, but a business that

possesses advance analytics could also edge their
competitors in productivity and profitability. [5]

In relation, the system uses the analytical reports in

producing a more efficient way of addressing all the
cases and the distribution of the medications within
the Health Services Department (HSD). By analyzing
information through the analytical reports, the users
of the system can easily determine the cases that
they must give emphasis on and the type of
medications that need supply so it could be
distributed properly to all the patients.

2.2 Review of Related Systems

In this section, the related systems with the project of the
researchers is discussed, everything that has relation with the
project is cited and explained.

2.2.1 Medical Monitoring System

A monitoring system must include one apparatus, monitoring at
least one aspect of the patients physical condition and generating
at least one variable response to the monitoring. The system
should also be attached to at least one station distributor with a
single monitoring device also attached to a telephone line. It is
elaborated that a monitoring system is able to keep track of all the
health information of a patient by using an apparatus and sending
its results to a storage device. When the storing device receives
the information, it is the job of the personnel responsible for the
apparatus to interpret the results gathered from the patient. [6]
The article above states that the essence of the monitoring system
used by Arlinghaus requires a certain apparatus for each patient,
but in the system made the researchers, the essence of the
monitoring system basically keeps track of all the records of the
patients within the Health Services Department (HSD).

2.2.2 Record Keeping System

The record keeping data that is manually entered is
accompanied by the printed data to ensure that the
system is able to produce accurate amounts of
information. By applying this method, the system is
able to show all the information manually given by

the users and synchronize them with all the printed

information intended for the system. Each section
intended for the hand entered and printed data are
separated do the system can show the users where
to put as the exact information. [7]

It is stated above that Crawford made a system that

complies with the manual processes also done by a
certain system accompanying the automated
system. The same with the system developed by the
researchers, the manual approach currently
practiced by the Health Services Department (HSD)
is accompanied and supported by the MEDITOR
which is the automated system.

2.2.3 Inventory System using articles with

RFID Tags

The library uses an inventory system that puts RFID

tags into articles of books to monitor it status. This is
the process that is used by the library to know the
status of a certain book if it is already released or
returned back to the library. Also, this process also
shows all the necessary information of the person
who borrowed or used the book. The library uses a
patron self-checkout system that checks if the books
borrowed are returned through the exterior smart
book drop intended only for the system. If a book
was borrowed but not checked out, it is brought to
the interior smart book drops for shelving. The
uncirculated articles are stored on the shelves of the
library. The inventory is also periodically scanned
with an RFID scanner for updating the inventory
status. [8]

The system using RFID tags is much more developed

approach that is used by an inventory system for a
library, compared to the inventory system made by
the researchers. The researchers kept up with the
basic development steps in creating the inventory
module and used the fundamental parts for its
development.

2.2.4 Electronic Inventory System for Stacked

Containers
As a form of another inventory system, an electronic tag is used to
detect containers that are maintained by monitoring with GPS to
track where the exact location of the container is. A long range
transceiver and a short range transceiver are deployed to detect the
location of the electronic tag. When the containers are stacked or
stored in a nested position, the same method using the GPS
tracker is used to locate the containers. [9]
Same as the previous system, this system made by Guthrie uses a
device but it covers a much larger kind of materials being
contained in an inventory. With the system developed by the
researchers each medications and medical supplies is
accommodated within the inventory module so it can be kept track
when it comes to amount and the expiry dates.

2.2.5 System and Method for Automatic Transmission

of On-line Analytical Processing System Report
Output
An online system created to host the users needs about generating
analytical reports is made to cater any kind of topic that the user
needs. The user of the system has the pleasure of encoding all the
necessary information about their chosen topic and the system
will arrange and generate the needed output. When the user
encodes all the information, the system analyses the data, the
system creates probable analytical reports that the user could
request. In the event that the user requests a specific kind of
analytical reports, the system will now generate the report that the
user need. [10]
This system, the analytical reports are generated online by which
user needs a certain kind of information printed. The reports are
done automatically by the online system and it needs the user
interaction to print the output. When it comes to the system
developed by the researchers, the analytical reports are also
generated by the system, but the difference is that the system
made by the researchers is standalone. Besides, the information
generated by the system could also be filtered and customized as
what the user wants to see and need.

3. TECHNICAL BACKGROUND
In this section every specific term used by the researchers are
mentioned and discussed according to the definition set by the
project requirements. It is also here that the necessary input
process and output diagram are included and discussed.

3.1 Operational Definition

These are the specific terms that are used by the researchers to
further discuss the document and support the system development.
These terms show the things that are used by the system which
mostly came from the client interviews and the researchers data
gathering. These terms respectively are:
Analytics Reports show the user all the charts about the top five
mostly treated medical cases and top five mostly consumed,
distributed medical supplies and medicines within the system
Database a place where every patient, medical supplies and
medicine information are stored and queried by the system

Data Inaccuracy a kind of problem experienced by the Health

Services Department when a certain amount of data supplied by a
patient is inaccurate or invalid
Data Redundancy a kind of problem experienced by the Health
Services Department when a certain amount of data supplied by a
patient is registered twice or repeatedly
Dentist views the dental records of a patient and gives out
prescriptions according to the patients dental status
Dispensing the act when the nurse gives out the medicine
prescribed by the physician or dentist to the patient

do certain tasks within the system but with only a few menus
enabled for them

3.2 Process Design / Framework

This section includes the Input Output Diagram that shows the
users of the system all the possible information that they encode
within the system, what processes could occur within the system
and what will be the output of the said processes.

3.2.1 Input Output Diagram

Health Services Department (HSD) the main entity within the

Lyceum of the Philippines University Cavite Campus that is
concerned with all the medical issues within the university
Incurable diseases diseases that are impossible to cure and
cannot be easily treated by the Health Services Department
Information Insufficiency - a kind of problem experienced by the
Health Services Department when the data supplied by the patient
is not enough or doesnt cover up all the needed information by
the forms within the system
Medications the general category for medical supplies and
medicines
Monitoring concerned with record tracking, the system
monitoring keeps track of all the patient records within the whole
system; it is also concerned with monitoring the inventory of the
system
Nurses the user of the system that has the most number of tasks
done within the system, is also the one who takes care of almost
all the important processes within the automated system
Physician views the medical records of a patient and gives
prescription that would be given out by the nurses
Prioritizing setting a certain issue according to its importance to
the user
Prototyping the method used by the researchers in making the
system, it includes making the system from scratch and adding
features little by little as they present the system to critics and
evaluators
Restocking the method done by the nurse when a certain
medical supply and medicine needs to be added to the inventory
Researchers they are the one who underwent studies to produce
a result about a certain research topic
Security the level of safety given by the system for the files and
other information within the system
Standalone the system would work without the help of other
programs to execute all of its general processes and routines
Standardization changing the things that are unusual and setting
it to the most normal usage according to the number of users
Student Assistants other users of the system designated by the
authorized personnel of the Health Services Department (HSD) to

Figure 1. Input Output Diagram

Figure 1.0 shows all the needed input of the system from the users
which includes the knowledge requirements which is the process
of creating new patient information, the process of creating new
medical supplies information and the process of generating and
printing reports. The hardware and software requirements are also
specified.
For the process model, all the requirements are gathered, the first
build is executed and then tested, and then the system becomes
revised and tested again. After all these processes are done, all the
inputs were processed and it was transformed into the MEDITOR:
Medical Monitoring System with Analytics.

4. DESIGN AND DEVELOPMENT

In this chapter, the methods used by the researchers are discussed
and explained this answer the following question. This would be
helpful to the users when they need to understand how the
researchers made the system and when they need information
about improving the system by themselves. If the users seek to
create an improvement, they could consult this chapter so they
could hit on the points where the system needs more compliments
and improvements.

4.1 Project Development

The systems development life cycle (SDLC) is a process of
creating or altering information systems, and the models
and methodologies that people use to develop these systems. It
expresses how a certain system is done or which steps are
followed in creating the system properly with accordance to a
specific outline.

Evolutionary Prototyping Model

Figure 3. Functional Decomposition Diagram

Fi

A functional decomposition diagram is used to state which of

which the main menus of the system are. It states all menus from
the main menu to the sub menus.

gure 2. Evolutionary Prototyping Model

It refers to the activity of creating prototypes of software
applications, for example, incomplete versions of the software
program being developed. It is an activity that can occur in
software development. It used to visualize some component of the
software to limit the gap of misunderstanding between the
customer requirements by the development team. This will also
reduce the iterations that might occur in waterfall approach and
which is hard to be implemented due to inflexibility of the
waterfall approach. So, when the final prototype is developed, the
requirement is considered to be frozen.
For the first process which is the design, the researchers gathered
all the required information with regards to the development of
the system. From the client interview and consultations, the
researchers decided to go through with the design phase and onto
building the prototype. When building the prototype started, the
researchers started in making each module of the system one by
one and by slowly adding each module with one single function.
Each time a function is added, the researchers make sure that a
single user or the research adviser checks the progress of the
system. After the system was checked, the user or the research
adviser gives feedbacks and then the researchers study the given
feedback then decides to refine the system again. If a certain
feedback is done the system goes back to the checking until the
system gets flawless and perfect. After all these processes, the
researchers now produced a final product of the system meeting
all its functions, contents and requirements.

4.2 Project Requirement Analysis / Specifications

In this section, most of the diagrams for the system will be shown
and it will be elaborated thoroughly. These diagrams will show the
researchers ways on making the system, the flow, and the needed
requirements for time, resources and other important component
for the whole system itself.

4.2.1

Operational Feasibility

4.2.1.1 Functional Decomposition Diagram

4.2.1.1.1 Checkup
This function is mainly concerned with adding the patient records
within the system. The main user of this function is the nurse, all
the patient information will be created in the system during the
interview or when the nurse decides to transfer the written
information from the forms to the system itself. The following are
the other contents of the checkup menu:

a)

Add client all the patient information will be inputted

to the forms within these function. This process
commonly occurs during or after the patient is
interviewed.

b)

General consultation when a patient is getting

treatment on a specific case all the consultation
information are recorded within this form.

c)

Annual checkup the health card of the patient is

included in this form, it will only be updated when
information on the health card is changed or removed.

d)

Clearance all the requirements needed for obtaining a

clearance for a patient is recorded in this function in a
form of a checklist. When this form is completed, the
patient can now gain a medical clearance.

4.2.1.1.2 Medical Records

This function shows the user all the encoded information that has
concerns with the patient information gathered through the
interview.

a)

View records the user can view, update, and edit the
patient information in this function.

b)

Medical exam records the user can view the medical

exam results taken by the patient during the registration
of the patient.

b)

Inventory breakdown the analytical report about the

top five most commonly used medicine and medical
supply are reported in this function

c)

Consultation breakdown same as the inventory

breakdown, but this function shows the top 5 commonly
treated medical cases in the Health Services Department
(HSD).

4.2.2

Technical Feasibility

The technical feasibility section shows all the specifications

needed or used by the researchers in making the whole system.
This section also shows the user information on which they will
use to properly run the system made by the researchers.

4.2.1.1.3 Dental Records

4.2.2.1 Software Specifications

All information with regards with the dental information are
recorded and viewed in this function.

a)

View dental records shows the user a dental chart that

can be edited when a patient needs dental checkup.

4.2.1.1.4 Medicine Repository

This function contains the inventory of the system that maintains
and stabilizes all the supplies within the Health Services
Department (HSD).

The list of the software the developers used is the following,

Navicat Lite, MySQL Server, Wamp, Visual Studio 2012 Express,
Gimp, and Notepad ++. Navicat Lite was used to store all the
database data within the system. MySQL Server and Wamp are
used by the researchers as the database compiler that runs and
connects all the data from the database up to the system itself. On
the other hand, Visual Studio 2012 is the main programming tool
that the researchers used for the C# programming language they
chose to create the system with. As the photo editing software,
Gimp was chosen simply because it is open source, easy to use
and install and because of the prior experience of the researchers
when it comes to the use of the said software. Lastly, Notepad ++
is used by the researchers in editing certain codes that has special
compatibility with this said software.
These programs were chosen by the users in accordance to the
needs of the system. These tools helped the researchers build and
create a system that is broad, fully functional and could last for
long.

4.2.2.2 Hardware Specifications

a)

View inventory this function shows all the medical

supplies and medicine registered in the system. This is
where the user can add, delete, update and edit all the
medical supplies and medicine information.

4.2.1.1.5 Reports
The reports function is where the user can view all the lists of the
content of the system. It will let the user review all the registered
information within the system.

a)

Inventory report in this function all the medical

supplies and medicine information are displayed within
a table.

The hardware needed for the project is currently considered at the

lower most specifications for a certain software. The software
made by the researchers could run on a Core 2 Duo processor with
2GB ram and even without a video card. This only means that the
system could run in lower specifications than expected. The first
time the researchers made the system, they did not expect that it
would run through a laptop or personal computer with low
specifications. But as the time progresses, the researchers
experimented and tried programming the software with low
specifications, the results from the experiment were good so the
researchers became determined that as of now, with our era with
personal computers and laptops, it could run in any environment
such as pc or laptops.
The system does not require any probable kind of other software
so it could run its full potential. Thus from this results, the
researchers determined the systems minimum required
specifications in this three categories, a processor with 1.5GHz
speed, a minimum of 1GB ram and it could even run without a
video card but it will hinder the smoothness of the graphical user
interface. As for the recommended system requirements, a
minimum of 2GHz processor speed, 2GB of ram, and a 1GB

video card would be good. These specifications will make the

system run faster and make the graphical user interface smoother
and more polished as it runs. For the operating system
requirements, the range is with Windows XP to Windows 8, any
of these operating systems will run the system smoothly and
properly. Mac is not recommended because the researchers did not
try to experiment using it as the systems operating system.

4.2.3

Table 1. Recurring Cost for Year 0 of Existing System

Schedule Feasibility

The schedule feasibility shows how the researchers managed to

make the whole system within the short time frame allotted for the
project. Gantt chart shows which activities were done, how long it
was done, and when it was finished. The chart will also help the
researchers to predict which activities they should alot more time
with and which activities they should disregard or change in the
course of developing the whole project.

B. Non-Recurring Cost
Table 2. Non-Recurring Cost for Year 0 of Existing System

Figure 4. Gantt Chart

The Gantt chart shows nine activities done by the researchers for
the span of ten months or two semesters. The longest activity done
which is the client interview lasted for nine months because every
time that there is progress in the system, the researchers present it
to the client. Data gathering and System Documentation lasted for
seven months because it was two parallel activities that go hand in
hand.

Cost Analysis for Year 1 of Existing System

A. Recurring Cost
Table 3. Recurring Cost for Year 1 of Existing System

While the system gets developed everything that was done is

documented so the researchers can keep track of their progress.
Title Proposal and Title Approval only lasted for the first month of
the Gantt chart because it only took days for the researchers to
accomplish these tasks.
The System Testing and Evaluation lasted for two months because
there was a total of two tests composed of almost fifty participants
raging from IT Experts, Medical Staffs, Students and simple
university students. The document proofreading lasted for a month
before the final defense. Then the Final Defense lasted for two
months because it started from the end of February to the first two
weeks of March. The last activity for the Gantt chart is the
revisions, binding and distribution of the documents for the
school.

4.2.4

B. Non-Recurring Cost
Table 4. Non-Recurring Cost for Year 1 of Existing System

Economic Feasibility

The economic feasibility is the Cost and Benefit Analysis. This

part shows which the researchers used as funds for the
development of the whole project. Besides this the CBA also
shows when the client will gain back the money they used for the
development of the whole project.
Cost Benefit Analysis
Cost Analysis for Year 0 of Existing System
A. Recurring Cost

Cost Analysis for Year 2 of Existing System

A. Recurring Cost

Table 5. Recurring Cost for Year 2 of Existing System

A. Recurring Cost
Table 9. Recurring Cost for Year 4 of Existing System

B. Non-Recurring Cost
Table 6. Non-Recurring Cost for Year 2 of Existing System

B. Non-Recurring Cost
Table 10. Non-Recurring Cost for Year 4 of Existing System

Cost Analysis for Year 3 of Existing System

Cost Analysis for Year 5 of Existing System

A. Recurring Cost

A. Recurring Cost

Table 7. Recurring Cost for Year 3 of Existing System

B. Non-Recurring Cost
Table 8. Non-Recurring Cost for Year 3 of Existing System

Table 11. Recurring Cost for Year 5 of Existing System

B. Non-Recurring Cost
Table 12. Non-Recurring Cost for Year 5 of Existing System

Cost Analysis for Year 0 of Proposed System

Cost Analysis for Year 4 of Existing System

A. Recurring Cost

Table 13. Recurring Cost for Year 0 of Proposed System

B. Non-Recurring Cost

B. Non-Recurring Cost
Table 19. Non-Recurring Cost for Year 5 of Proposed System

Table 14. Non-Recurring Cost for Year 0 of Proposed System

C. Software Cost
Table 15. Software Cost for Year 0 of Proposed System

Cost Analysis for Year 1 to 4 of Proposed System

A. Recurring Cost

C. Other Cost
Table 20. Other Cost for Year 5 of Proposed System

Payback Analysis
Table 21. Payback Analysis Table

Table 16. Recurring Cost for Year 1 to 4 of Proposed System

B. Other Cost
Table 17. Other Cost for Year 1 to 4 of Proposed System

Cost Analysis for Year 5 of Proposed System

A. Recurring Cost
Table 18. Recurring Cost for Year 5 of Proposed System

Figure 5. Payback Analysis Graph

This graph shows the payback analysis graph on where the client
can gain back all the costs they used for the development of the
whole system.

information,
information.

analyzed

information

and

generated

report

Because the nurse is the only one responsible in encoding through

the system, the second entity which is the physician and doctor
would only be able to receive consultant information from the
system.

4.3.1.2 Level 0 Diagram

Level 0 diagram is a more complicated and detailed explanation
of the system. This diagram shows the most specific functions of
the system that works to produce much efficient information.

Net Present Value

Table 22. Net Present Value Table

4.3 Project Design

The project design shows all the diagrams that have the
connection with the system flow and what data flows through the
whole system.

4.3.1. Requirements Modeling

Requirements modeling refer to the formal business process to be
supplied and to be a supported for the development of the study.

4.3.1.1 Context Diagram

Figure 7. Level 0 Diagram

The level 0 diagram shows the same information from the context
diagram but more detailed and it also shows the smaller processes
than the entities in the system. The level 0 diagram mainly has 5
processes, namely: the patient record management, conducts
health care service, medicine inventory management, view system
data analysis and last is the generate reports function.

4.3.1.3 Use Case Diagram

The context diagram shows a broad and simple explanation of the

system. It gives the main thought and idea of the system.

Figure 6. Context Diagram

The context diagram shows the main entities that interact with the
system. They are the people who contribute with all the processes
that occur within the system. The first entity which is the nurse
encodes in the system the updated medicine information, patient
information, patient ID number and the medicine information. In
return the system will give the nurse outputs such as medicine

Figure 8. Use Case Diagram

The use case diagram shows which user interacts with what
processes in the system. There may be one or more users that
interact with a single process but there are also processes that
cannot be interfered by other users.
The content, inventory, report and monitoring management are all
handled by the nurse. Besides the nurse two of the tasks done by
the nurse, which are the content and report management are
shared with the dentist and physician. The last three processes
which is the user, system and security management are only
handled by one user which is the admin. The admin is responsible
for the overall maintenance of the system.

4.3.2. Data Design

be affected when a medicine or medical supply will be given to a

patient. Lastly, the system will now store all the actions within the
system. In this last part, the analytics will now review all the
information and register the latest enacted action to the charts if it
comes close to the top five cases treated within the Health
Services Department or to the top five mostly used medical
supplies and medicine.

4.3.2.2 Data Dictionary

The data dictionary shows each information contained in the
database of the system. It explains how and why each and every
data within the system is essential.
Table 23. Action Log Table

Data Design includes the Entity Relationship Diagram (ERD) and

the Data Dictionary to further explain the relationship of every
table in a database works.

4.3.2.1. Entity Relationship Diagram (ERD)

The entity relationship diagram shows the connection between all
the modules within the system. It helps the user see how all the
modules interact with each other when they use the system.

The action log table shows who made or enacted actions within
the system. Besides from whom, it also shows when at what
action was done by the user.
Table 24. Checkups

The checkups table shows the basic information of the patient

through the health card.
Table 25. Clearance

The user sees each requirement that is needed by a patient to

obtain a medical clearance.
Table 26. Colleges

Figure 9. Entity Relationship Diagram

The first process is the interview to the patient done by the nurse,
after that the dentist and the physician will conduct checkups for
the patient. This is where the patient records will be created and
encoded to the system. It is also the part where the monitoring
module will act all the processes. The second process is the
prescription of the medicine for the patient or if the patient has a
certain sensitive case, it will be the deciding factor on which kind
of medications should be given to them. The second module will
then enact these processes because the inventory system will now

All the colleges are shown in this table and it is also shown which
is active and which is inactive.
Table 27. Courses

This table shows each course from every college registered in the
system.

Table 28. Dental Map

All the information in this table is concerned with the medicine
expiry date. The table shows the general information about the
medicines and of course the expiration date.
This table is concerned with the chart that shows all the possible
dental records of a single patient.

Table 29. Faculty Information

Table 33. Medicine Stocks

This table shows all the information of all registered faculty

members.
Table 30. General Consultation

This table shows all the stocks within the inventory and of course
all the medicine information.
Table 34. Medicines

This table shows the general information about medicines and it

also shows which disease the medicine could cure.
Table 35. Past Medical History

This table shows the content of all the forms filled up when a
patient undergoes checkup or consultation.
Table 31. Login Log

This table is the same as the action log but the difference is that
this table shows who used the login, when did they login and
which user level they are categorized.

This table shows all the possible recurring diseases the patient
has.
Table 36. Personal History

Table 32. Medicine Expiry Date

This table shows the information if the patient smokes, drinks or if

the patient is currently taking medication given by other doctors.

This table shows all the information encoded by the user to create
a user account in the system.

Table 37. Student Information

Table 41. Verification Code

This table shows all the verification codes used by the user to
register an account to the system. It also shows the verification
code if it is the verified or not.
Table 42. Archive

This table shows all the information of all registered students in

the system.
Table 38. User Accounts

This table shows the archive of all the information that is deleted
or removed from the system. All the discarded information go to
this database which can also be viewed by the users.
Table 43. Event Checkup

This table shows all the user accounts that used to login to the
system.
Table 39. Non-Teaching Personnel Information

This table shows all the needed information for the pre-event
checkups.
Table 44. Event Name

This table shows all the information of all registered non-teaching

personnel in the system.
Table 40. User Information

This table shows the list of all the event names within the system.
Table 45. Event Checkup Status

This table shows the status of the student who undergone checkup
for a specific event.

This form shows all the forms used to register and create patient
records within the system.

Table 46. Event Record

This table shows the list of all students and their status for the preevent checkup.

4.3.3 Output and User-Interface Design

Output and user-interface design is about all the forms, fields and
other things the users can encode their output data and register it
to the system.

Figure 12. Add College

This form shows how the user can add colleges and courses to the
registration tab.

4.3.3.1 Forms
This section shows all the forms that the user uses to interact with
the system.

Figure 13. Add Faculty

This form shows all the fields used for adding faculty members.
Figure 10. Add Annual Checkup
This form shows the information needed for the patients health
card.

Figure 14. Add General Consultation

This form shows all the fields that needs to be filled up when
undergoing consultations.

Figure 11. Add Client

Figure 15. Add Medicine and Medical Supplies

This form shows the user which information are needed in adding
medicines and medical supplies.

Figure 16. Add Student

This form shows all the fields used for adding students.

Figure 17. Add User

This form shows all the fields used for adding users of the system.

Figure 18. Update Clearance

This form shows the user which requirements are provided by the
patients to obtain a medical clearance.

Figure 19. Verification Code

This form shows how the users can add and verify verification
codes in the system.

Figure 20. Admin Page

This form shows the view of the admin page that has three menus,
mainly the home, administration and reports menu.

Figure 21. Annual Checkup

The annual checkup form shows the user the search bar they could
use to search for a specific user. The user could also edit and view
all the annual checkup records in this form.

Figure 22. Clearance

The clearance form will allow the user to see all the patients that
requested for clearance.

Figure 23. Colleges

This form shows which colleges are available and if it is active or
inactive

Figure 24. Consultation Breakdown

The consultation breakdown form shows the user the data of the
top five most treated cases by the Health Services Department
(HSD).

Figure 25. Dental Records

The dental records form all has the search bar so the user can
easily identify the patient record that they need. It could also show
the users how to use the dental records chart.

Figure 26. General Consultation

The general consultation form shows the search bar for the
patients that would lead you to the add consultation form.

Figure 27. Home Page

This form is the home page of the system that shows the six main
menus plus the notification menu. The five menus respectively
are, home, checkup, medical records, dental records, and medicine
repository and reports menu.

Figure 28. Inventory Report

The inventory report form shows all the medicines and medical
supplies that are registered in the system.

Figure 29. Login

The login form is the first form that is encountered by the user. Of
course it is used to get into the system.

Figure 30. Medical Record

This form lets the user search for the medical records of a certain
patient.

Figure 31. Add Non-Teaching Personnel

This form shows all the fields used for adding non-teaching
personnel of the system.

Figure 32. Notification Expired

This form shows the table of all the expired medicines.

Figure 33. Medicine Count Notification

This form shows the table of all the nearly diminished medicines.
Figure 36. Update Medicine
This form lets the user to update the medical supplies and
medicine status.

Figure 34. Print Preview

This form shows the print preview of each printable file in the
system.

Figure 37. User Management

The user management form shows the user all the other users that
are available in the system.

Figure 35. Supplies Breakdown

The supplies breakdown form shows the user the data of the top
five most used medical supplies and medicines by the Health
Services Department (HSD).
Figure 38. Verification Code
This form lets the user access the verification code generator.

Figure 39. Add Event Checkup

This form shows all the needed information of the Health Services
Department (HSD) for the pre-event checkups.

Figure 40. Add Event Participants

This form allows the user add all the event participants manually.

Figure 41. Add Event View

This form allows the user filter all the information about the
events held in the university. The information can be filtered
according to program, year level, event and status.

Figure 42. Archive

This form shows all the deleted medicine information from the
system.

Figure 43. Consultation Reports

This form shows all the consultation reports made by the
university physician and dentist.

Figure 44. Delete Record

This form allows the user to delete the information of the patient
that backed out on a certain event.

Figure 45. Pre-event Reports

This form is has the same filtering feature as the add event view
form, but it has the added print feature.

Figure 46. Consultation Reports Print Preview

This form shows the user a print preview of the consultation
reports form.

Figure 47. Event Checkup Reports Print Preview

This form shows the user a print preview of the event checkup
reports form.

Figure 48. View Annual

This form allows the user view the annual patient consultation
records.

Figure 49. View Consultation

This form allows the user view the old to the latest patient
consultation records.

Figure 50. View Dental Records

This form allows the user view the patient dental records.

for the user level the user is entitled with is shown and the system
applications that the user can use and encode information into.
The second level is the application level that has all the
applications servers. When a certain user interacts with the
system, they will be interacting with the back end of the system
that has all the servers. All the interactions made by the user are
synchronized with the servers. The last level from the figure
above is the database level. The database level acts together with
the application level so the users that needs information could
easily have what they need. All the information encoded by the
users is stored in this level, while the system is always ready to
retrieve all the information needed by the user.

5. IMPLEMENTATION AND EVALUATION

Project implementation and evaluation is the part when the system
will be tested by the researchers. It means that the system will be
tested by the client and it will also be evaluated according to the
objectives of the project.

5.1 Project Implementation Plan

Project implementation plan states the outline how the system
should be handed out to the client. It shows both the researchers
and the client the steps in executing the project according to the
planned actions and rules.

Figure 51. View Medical Exam Records

This form allows the user view patient medical exam records.

5.1.1 Description
Project implementation plan includes the list of activities when
the system of deployed to the client.

4.3.4 System Architecture

System architecture describes the structure of the proposed
system. It also gives an overview of its design and contents and
aids in designing its various components.

After the whole system and documents are finished, it would be

given to the client which is the Health Services Department. The
target users are the nurses, physician, dentist and the students
assistants assigned by the HSD themselves. They will be testing
and incorporating the system to their daily tasks and processes.
Another target is if the system could marginalize the most
common problems and mistakes made by the department.
All the requirements and needed components of the system must
be present so the system would work properly. If all this said
requirements are available, the system should work perfectly and
agree with the said outlines and rules.

5.1.2 IT Infrastructure
IT Infrastructure states all the needed components of the system
so it could properly work. The hardware and software
requirements are properly stated and given to the client so they
could provide the sufficient materials in working with the system.

Fi
gure 52. System Architecture
The figure above shows all the infrastructures that the users can
interact with when they are using the system. The first level that
they interact with is the interface level that includes the Metro
form, which is the form that is used to login into the system; the
Home Page, where all the features of the system that is enabled

The researchers have enumerated all the hardware and software

requirements for the system. For the hardware, a minimum of a
Core 2 Duo processor and a 2GB ram could run the system. So it
simply means that anything higher than those specifications could
run the system smoothly. For the software, the system software, a
Navicat lite database and Wamp for compiling the database files.
Because the system is standalone, it doesnt need any network
connections within the Health Services Department (HSD). It runs
within a single computer within the department and integrates all
its information within its databases.

5.1.3 Deployment Plan

During the deployment, the researchers should be able to finish all

the required parts of the system. All the documents that help the
user understand the system should all be included. The
deployment plan should be able to guide the client how to
properly learn the usage of the system.
Before all the deployment plans, all the attributes and parts of the
IT infrastructure should be done and developed already. All the
hardware and software requirements must be provided by both the
researchers and the client.
Procedures:
a. Install Navicat in the client pc.
b. Install MEDITOR: Medical Monitoring System with Analytics
c. Prepare the database.
d. Run the MEDITOR: Medical Monitoring System with
Analytics.
f. Check if the all the functions and processes of the system is
working properly.

5.1.4 Implementation Contingency

The implementation contingency will be occurring a as
presumption on the things that could happen during the
deployment of the system. The researchers should be able to learn
to adapt to all the possible errors and be on call whenever the
system has bugs or problems.

5.1.5 Risk Management

Risk management is the capacity of the researchers to take the
impacts of the risks that could affect the system and the
deployment. The researchers should be able to assess and guide
the client on how to properly respond to the distress the system
may undergo.

5.2 Project Testing and Evaluation

Project and testing and evaluation are the parts where the system
made by the researchers will be criticized and tested. All the
functions must be working excellently.

5.2.1 Operation and Test Procedures

The operation and test procedures are the step by step guide on
how the users will use the system. The stated procedures will help
the users to understand how the system works and which
processes should be done first before another process is done.
Operation Procedure
1. The first process is the login phase where the user can either
choose to login as a user or as the administrator. Both user levels
have different menu views, the admin page has only two menus,
but the other user accounts can see five menus which has different
content and purposes.
The admin account can manage the user accounts, generate the
verification codes for the user registration, add user accounts
manually or whenever another user is needed, and lastly activating
and deactivating colleges that would be used in the registration of
the patient records. These submenus are all under the
administration menu.
2. The second menu that the admin uses are the reports menu,
from this menu, the first submenu is the inventory report that
shows the admin all the medicine and the medical supplies that
are used within the Health Services Department (HSD). The
second submenu is the action log that shows the admin who

enacted a certain action or task within the system. It determines

who will be responsible for such actions done within the system.
The last two submenus which is inventory and consultation
breakdown show the admin which medicine are commonly given
to patients, which medicine are expiring and decreasing in count.
The consultation breakdown part shows all the most common
treated medical cases within the Health Services Department
(HSD).
3. If a simple user logs in the system, they will see five menus.
The first of the five menus is the checkup menu that has also five
submenus. First of which is the add client which is used to add the
patient records that will be stored within the system. Second is the
general consultation that is used for each time a patient goes to the
Health Services Department (HSD) and asks for an appointment
to be checked up and tested. The annual checkup deals with the
health card of the patient. Last is the clearance submenu that is
concerned with the requirements in order to accomplish and
obtain a clearance for a certain patient.
4. The second menu is the medical records. The first of the two
submenus is the view record submenu which enables the user to
view and edit patient records that is already in the system. The
second submenu is the medical examination record menu that
shows the user the results of the medical exam taken by the
patient when they are first interviewed by the nurse in the Health
Services Department (HSD).
5. The third menu is the dental records that only contain one
submenu which is the view dental records. View dental records
submenu, it also allows the user to search a certain record and edit
the contents directly from the form.
6. The fourth menu for the user is the medicine repository that
also has a single submenu which is view inventory. View
inventory is responsible for all the medicines and medical supplies
that is included in the inventory within the Health Services
Department (HSD).
7. The fifth and last menu for the user is the reports menu. The
reports menu is like the reports menu in the admin page, it shows
the inventory report that is concerned with the statistical review of
the medical supplies and medicines within the Health Services
Department (HSD).
8. The notifications menu only shows up when certain medicine or
medical supplies are going to expire or there are supplies that are
decreasing in number. The users can immediately edit and update
the inventory information within this notification menu.

5.2.1.1 System Testing

Integration testing is the test that is done if the system could
properly adapt to the manual system done by client. If the client
could comply with all the requirements of the system all of the
systems process will flow smoothly and properly running without
errors.
To achieve the best results, the alpha and the beta testing are done.
The alpha tests are done by the researchers, while the beta tests
are done by exactly thirty five participants, they consist of five
medical staffs, five IT Experts, five student assistants and twenty
university students.

Table 46. Test Procedure Undertaken by the Researcher

Alpha Test
System
Component or
Test Conducted
Module
Tested if all the buttons within the form
Login and logout are working and the user can properly
login and logout.
Tested if the search bar are able to search
all the inputted data that is queried in the
Monitoring
database.
Tested if all the forms are able to register
and save data about all the patients.

Inventory

Analytics

Reports

Printing

Tested if the search bar are able to search

all the inputted data that is queried in the
database.
Tested if all the forms are able to register
and save data about all the medical supplies
and medicines.

Tested if the data projected by the

analytical reports are accurate and it is
what is shown in the system database.
Tested if all the data shown in the reports
are present and accurate in the database
of the system.
Tested if the printed outputs are the same
with what is shown within the print
preview option of the system.

Table 47. Test Procedure Undertaken by the User

Beta Test
System
Component or
Test Conducted
Module
Tested if the account used is in
Login and logout accordance with the user level provided
by the system.
Tested if creating patient data information
will be registered in the system.
Monitoring
Tested if searching, editing and updating
patient information are consistently
working within the system.
Tested if adding medical supplies and
medicines will be registered in the
system.
Inventory
Tested if searching, editing and updating
medical supplies and medicine data are
consistently working within the system.
Tested if the analytical charts are in
synced with the data within the reports of
the system.
Analytics
Tested if the monthly and yearly filtering
are properly working and showing the
accurate data.
Tested if all the reports shown is accurate
Reports
with all the information encoded by the
user.

Printing

Tested if the system are able to print accurate

data and if the printed output is the same
shown with the print preview option.

5.2.2 Evaluation Instrument

An evaluation instrument is the testing instrument that is used to
measure all the system processes and features in accordance to
categories that will ensure the system is working properly.
To measure and assess the effectiveness of the system, the
researchers used a survey questionnaire. Thirty five respondents
were selected to evaluate the system, respectively they are five
medical staffs, five IT experts, five student assistants and twenty
university
students.
All of the respondents were given the chance to test the system by
themselves and check the survey according to the requested tests.
From the evaluation arise seven criteria namely: accuracy,
efficiency, reliability, security, user-friendliness, flexibility and the
last criteria is validity. From these criteria the system garnered a
grand mean of 4.01 with the standard deviation of 0.70 with the
interpretation acceptable. These results indicates that the system
passed the evaluation and satisfied all the people that tested the
system.

5.2.3 Statistical Treatment

The statistical treatment shows the collection of all the results of
the evaluation. The results then will be computed and presented in
a manner that shows which gets the highest to the lowest score.
This also helps the researchers reach a clarified solution to all the
tests conducted for the system.
Two statistical treatments were used to describe the data namely
the mean and standard deviation. These two statistical treatments
describe the effectiveness of the system and the positive feedbacks
given by the respondents.
5.2.3.1 Mean
The mean is the average of all values given in a set of data. The
values from the set is added and then divided into the total count
of the values given. The formula for mean is:

Where:
X = Summation of weighs
n = Total number of participants

5.2.3.2 Standard Deviation

Standard deviation is a measure of dispersion that has relation to
the mean or the average of all data given in a set. If the standard
deviation is low, the result of the data is close, but if the standard
deviation is high, the result of the data is broad. The formula for
standard deviation is:

6. RESULTS AND DISCUSSION

This section shows all the collected results from the test and
evaluation instrument used by the researchers to measure the
effectiveness and overall accuracy of the system. Besides the
collection of results, each and every table is explained and
elaborated about all the contents that interpret the scores given by
all the evaluators.

6.1. Test Results

6.2.2

Systems Efficiency

Efficiency shows how the system produces results that are all
correct and positive. It means that all the systems inputs are used
and nothing is discarded. Before the users encode all the
information in the system, everything is filtered and the
unimportant information is removed.

The test results signifies the rating of the system according to four
categories that are carefully chosen to specifically measure the
performance of the system. The mean of all the four categories are
computed and also given their own interpretation.

Table 48. Systems Efficiency

Table 46. Test Results

6.2.3

Systems Reliability

Consistency is the main concern of reliability. It means that the

system can always perform whenever it is needed and still
produces the same result. The users can rely to the system even if
a certain manual process has a problem; the system could be a
backup that they could still use to continue their processes.
From the tests conducted for the system there were four criteria
that were set in evaluating the system. These tests were conducted
by five medical staffs, five IT experts and five student assistants.
First of which is the functionality where the system gained a total
mean of 3.12 with the qualitative interpretation which is good. It
got the third place from the four criteria which mean that overall
functionality of the system was user-friendly.
The second criterion which is content gained 3.35 mean with the
qualitative interpretation good, this criteria got the first place in all
four criterias. It means that all the contents of the system are
accurate and made according to the outline set by the client for the
system. The third criteria is reliability, the system garnered 3.25
mean and the qualitative interpretation good that got the second
place on all four categories. This only means that the client can
rely on systems processes without hesitation and doubt.
The last criteria that got the last place were availability, it gained a
total of 3.10 mean but it still entered the qualitative interpretation
that is good. It may be the lowest criteria of the four categories but
it still shows that the system is complete, it performs according to
the set specifications and provides the user enough security to
ensure the safety of all the files within the whole system.

6.2 Evaluation Results

This section shows the complete collection of all the evaluation
results, each table is explained according to all the contents of the
evaluation tool. The system is measured by seven categories,
namely: accuracy, efficiency, reliability, security, userfriendliness, flexibility and validity.

6.2.1

Table 49. Systems Reliability

6.2.4

The main reason for security is for the files within the system to
be safe and protected. All the files that are in the system should be
well secured and properly organized. The security of the system is
still shared through user levels that have different views for each
user.
Table 50. Systems Security

6.2.5

Table 47. Systems Accuracy

Systems User-Friendliness

This concept shows if the system is able to make the user feel
comfortable when using the system. The user must feel at ease
and not be confused. They should be able to execute all processes
and tasks without flaws and errors. Besides this, the system should
be able to guide the user and dictate how the user will go through
the system.

Systems Accuracy

Accuracy means that the system is functioning well and according

to the set guidelines of developing the whole system. The table
below shows how the system performs with precision and without
errors according to four criteria.

Systems Security

Table 51. Systems User-Friendliness

6.2.6

Systems Flexibility

The system should be able comply with all the possible cases that
the user encodes. The system must also be able to comply

whenever a certain requirement changes and varies from the

users compliance.
Table 52. Systems Flexibility

6.2.7

7.2 Conclusions

Systems Validity

This category means that all the input, processes and output of the
system is satisfactory. The system should be able to satisfy all the
needs of the users and produce all the users expected results.
Table 53. Systems Validity

6.3 Summary of Evaluation

The summary of evaluation contains all the total scores form all
the seven categories. The mean and the standard deviation were
used to measure the total qualifications and contents of the whole
system. The total of both was expressed through the Grand Mean
and the total of the Standard Deviation.
Table 53. Summary of Evaluation

The developers were able to design the MEDITOR: Medical

Monitoring System with Analytics including all the proposed
features and other features which provided the system with better
performance. The programs and software used for the
development of the system are maximized and studied before
using to provide the system with all its requirements. Also, the
system passed all the tests and evaluations that are given to
determine the overall performance and capacity of the whole
system.
The researchers were able to achieve all the objectives set for the
system. They provided a system that is tailored and customized to
the needs of the client which is the Health Services Department of
the Lyceum of the Philippines University Cavite Campus. They
also ensured the client that the system can easily adapt to
changing environment and technology so the system can easily
perform its programmed tasks and capabilities.

7.3 Recommendations

The system reached a tolerable level of 4.18 as the mean and 0.68
as the standard deviation. The category that got the first place was
validity with the mean of 4.43 and standard deviation of 0.61. The
second place was caught by the accuracy with the mean of 4.29
and the standard deviation of 0.58. For the third place, reliability
garnered a total of 4.18 mean and the standard deviation of 0.75.
Fourth category is the flexibility which gained a mean of 4.16 and
the standard deviation of 0.69. The fifth and second to the last
category is user-friendliness had the total of 4.09 as the mean and
the 0.72 as its standard deviation. The sixth and seventh categories
tied with the mean of 4.06 but differed with the standard deviation
0.68 for the efficiency and 0.73 for the security. These data means
that the system is ready for use and deployment to the client.

7.
SUMMARY,
CONCLUSION,
RECOMMENDATION

by accuracy (4.29 mean and 058 SD), reliability (4.18 mean and
0.75 SD), flexibility (4.16 mean and 0.69 SD), user-friendliness
(4.09 mean and 0.72 SD), efficiency (4.06 mean and 0.68 SD),
and lastly security (4.06 mean and 0.73 SD). To summarize the
results the Grand Mean for the evaluation is 4.18 and the total
Standard Deviation is 0.68 with the interpretation acceptable.

AND

7.1 Summary of Findings

The stated information below was gathered from the all the results
of the evaluation done by the set of people set for the system test:
Out of the thirty-five (35) respondents, each divided equally. They
varied from the IT Experts, Medical Staff, Student Assistants, and
simple students.
Considering the effectiveness of the system, the category that
ranked number one is validity (4.43 mean and 0.62 SD), followed

The recommendations stated below are based on the summary of

findings. These recommendations are meant for the future
researchers and for the succeeding years of the system. These
recommendations are:
Conduct a system checkup. The researchers recommend that the
future developers should perform a monthly system checkup. It
will act as there guide in determining the points of improvement
for the system.
Connect the university database to the system database. The
researchers recommend to the future developers that they should
find a way to connect the university database to the system
database. They could provide an agreement with the school and
amend the processes of the two systems.

ACKNOWLEDGEMENT
The researchers would like to show their deepest and most sincere
gratitude to the following people:
To Lyceum of the Philippines University Cavite Campus Health
Services Department for letting us conduct the development of the
thesis in their respective department
To Ms. Lynette Cortez our Capstone 1 thesis adviser who guided
us through time and motivated us to pursue our project; To Mr.
Genson Mendoza for helping us in every way he can as our
Capstone 2 adviser
To all the people that took part on evaluating the system; to all the
35 people from the medical staff, IT experts, student assistants and

plain students of the Lyceum of the Philippines University

Cavite Campus
To the researchers families who gave them courage and strength
every time they need to do a certain task which regards with the
thesis; to all friends, classmates and loved ones that openly
accepted the whole group when doing overnight work and
supporting them with everything they have
Lastly and most importantly, the one that gave who researchers
enough knowledge and strength to carry on with making the
whole study possible, the Almighty God.

[5] Breuer, P., Moulton, J., Turtle R. (2013). Citing

Websites. Applying advanced analytics in consumer
companies. Retrieved February 26, 2014, from
http://www.mckinsey.com/insights/consumer_and_ret
ail/applying_advanced_analytics_in_consumer_comp
anies

[6] Arlinghaus Jr., F. (1996). Citing Websites. Medical

monitoring system. Retrieved February 26, 2014,
from http://www.google.com/patents/US5579378

REFERENCES
[1] Offshore Oil and Gas Operations Digital Magazine (2010).
Citing Websites. Remote monitoring system aids Dutch
production. Retrieved
February
26,
2014,
from http://www.offshore-mag.com/articles/2010/09/remotemonitoring.html
[2] Daily, F. (2013). Citing Websites. Choosing the Right Business
Record-Keeping System. Retrieved February 26, 2014, from
http://www.nolo.com/legal-encyclopedia/choosing-right-businessrecord-keeping-32277.html
[3] TechTerms.com (2013). Citing Websites. Standalone.
Retrieved
February
26,
2014,
from
http://www.techterms.com/definition/standalone
[4] Crosby, T. (2013). Citing Websites. How Inventory
Management Systems Work. Retrieved February 26,
2014, from http://money.howstuffworks.com/howinventory-management-systems-work.htm

[7] Crawford, D. (1995). Citing Websites. Record keeping system.

Retrieved February 26, 2014, from
http://www.google.com/patents/US5458378
[8] Bowers, J., Clare, T. (1999). Citing Websites. Inventory system
using articles with RFID tags. Retrieved February 26, 2014, from
http://www.google.com/patents/US5963134
[9] Guthrie, W. (1996). Citing Websites. Electronic inventory
system for stacked containers. Retrieved February 26, 2014, from
http://www.google.com/patents/US5565858
[10] Yost, K., Wilding, P., Trenkamp, R. (2001). Citing Websites.
System method for automatic transmission of on-line analytical
processing system report output. Retrieved February 26, 2014,
from http://google.com/patents/US6173310