Clinic Management System With Scheduling For Cabuyao Animal Bite Clinic

PAGE
COLLEGE OF COMPUTING AND ENGINEERING
CLINIC MANAGEMENT SYSTEM WITH SCHEDULING

FOR CABUYAO ANIMAL BITE CLINIC
A Capstone Project Proposal

Submitted to the Faculty of
The College of Computing and Engineering
PAMANTASAN NG CABUYAO
City of Cabuyao, Laguna
In Partial Fulfillment
Of the Requirements for the Degree
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
By:
ALEGRE, MEL BERT O.
CANTILLAN, LAWRENCE ALBERT R.
December 2022
Pamantasan ng Cabuyao
PAGE
COLLEGE OF COMPUTER STUDIES
COLLEGE OF COMPUTING AND ENGINEERING ii
APPROVAL SHEET
In partial fulfillment of the requirements for the degree of Bachelor

of Science in Information Technology , this research proposal titled, Clinic
Management System With Scheduling for Cabuyao Animal Bite Clinic
has been prepared and submitted by Mel Bert O. Alegre , and Lawrence
Albert R. Cantillan is hereby recommended for approval and acceptance.
ASST PROF. MARVIN L. ATANACIO

Research Adviser
EDITOR
Edited and re-examined for final printing and submission to the
faculty of the College of Computing and Engineering, Pamantasan ng
Cabuyao.
DR. MA. CONSUELO L. DIMAYA

Language Editor
PANEL OF EXAMINERS
Approved by the committee on Oral Examination with the grade of
___
PROF. SHARMAINE JUSTYNE R. PROF. ARCELITO C. QUIATCHON

MAGLAPUZ
Member Member
DR. RAMIRO Z. DELA CRUZ

Chairman
Accepted and approved in partial fulfillment of the requirements for
the degree of Bachelor of Science in Information Technology.
ENGR. LUISITO LOLONG LACATAN, PhD, PCpE

Dean, College of Computing and Engineering
Date: _____________
PAGE
COLLEGE OF COMPUTING AND ENGINEERING iii
ACKNOWLEDGEMENT
First and foremost, the researchers would like to thank our Lord Jesus Christ
for giving them the strength and wisdom to complete the research.
To their family, Alegre, Cantillan and friends who unconditionally

supported them to stay positive and given moral, financial, and physical support.
Dr. Luisito Lolong Lacatan, Dean of College of Computing and

Engineering, for his passionate support and tremendous encouragement in completing
the requirements for this research.
We would like to express our deepest gratitude to our thesis adviser, Mr.
Marvin L. Atanacio, their thesis adviser, for his guidance, advice and moral support
that help us in the completion and success of this study. This capstone would not
have been possible without his support, supervison and perceptive advice.
Prof. Sharmaine Justyne R. Maglapuz, Prof. Arcelito C. Quiatchon and

Dr. Ramiro Z. Dela Cruz, their panelist for giving them important insights to further
improve the whole research.
Mr. John Patrick Ogalesco, their research instructor from Capstone Project
1, for his helpful suggestion, ideas and advice that aided in the progress of our
research.
Finally, we would like to extend our deepest gratitude to our classmates for
supporting us from up and downs, wonderful time we have had together. We look
PAGE
forward to your success and happiness in pursuit of your dreams and goals. Thank
you very much to everyone!
The Researchers
PAGE
COLLEGE OF COMPUTING AND ENGINEERING v
DEDICATION
First of all, The researchers would like this research to dedicate

to our almighty God for giving us guidance, strength, and protection
through the ups and downs as well as for supporting us to make this
research possible.
To our family who was there in our thick and thins and support
us no matter what track we follow in our lives. To our friends,
professors, and adviser who was there to guide and support us all
throughout our stay in Pamantasan ng Cabuyao.
To future researchers as well, the researchers hope that it could

help in their research that could contribute to the better development
of the community.
BERT
LAWRENCE
PAGE
COLLEGE OF COMPUTING AND ENGINEERING vi
ABSTRACT
Title : CLINIC MANAGEMENT SYSTEM WITH

SCHEDULING FOR CABUYAO ANIMAL BITE
CLINIC
Researchers : Mel Bert O. Alegre

Lawrence Albert R. Cantillan
Degree Program : Bachelor of Science in Information Technology
Adviser : Asst Prof. Marvin Atanacio
School : Pamantasan ng Cabuyao
The volume of paperwork that needs to be handled and managed is still

overwhelming many enterprises. Clinics must develop a management system to keep
up with the rapidly evolving digital world and transition from paper to digital records.
The way practices allocate their time and resources can be completely altered by
the capacity to automate a number of their administrative and management chores.
The design, development, and implementation of a clinic management system

that would track the records of patients receiving anti-rabies vaccinations and other
treatments will be the main emphasis of this study. It needs to be created to assist the
Cabuyao Animal Bite Clinic in automating its records so they can readily monitor
patient information and transaction data. Additionally, it will be very useful for
PAGE
tracking the records of patients who received doses of the anti-rabies vaccine and
retrieving records if a patient loses their copy of the vaccination card. Only the
employees and administration of the Cabuyao Animal Bite Clinic in Cabuyao are
permitted to utilize the system. As a result, the effectiveness of the system for
Cabuyao Animal Bite Clinic in overcoming their struggles in handling manual labor
such as storing and recording patient information. Our studies will document the
changes and improvements in Cabuyao Animal Bite Clinic in regard to their handling
and storing of patient records.
.
PAGE
COLLEGE OF COMPUTING AND ENGINEERING viii
TABLE OF CONTENTS
Title Page i
Approval Sheet ii
Acknowledgement iii
Dedication v
Abstract vi
Table of Contents viii
List of Tables x
List of Figures xi
CHAPTER
I THE PROBLEM AND ITS BACKGROUND Page

Introduction 1
Statement of the Problem 3
Conceptual Framework of the Study 5
Significance of the Study 8
Scope and Limitation of the Study 10
Definition of Terms 13
II REVIEW OF RELATED LITERATURE AND STUDIES

Synthesis 32
III METHODS AND PROCEDURES

Research Design 35
PAGE
COLLEGE OF COMPUTING AND ENGINEERING ix
Respondents of the Study 36

Data Gathering Tools 37
Data Gathering Procedures 38
Data Analysis Plan 39
System Development 40
IV RESULTS AND DISCUSSION

Problems Encountered by Cabuyao Animal Bite Clinic 80
Features of the Proposed System 82
Assessment of the Users 89
Assessment of the Experts 95
V SUMMARY OF FINDINGS, CONCLUSIONS, AND

RECOMMENDATIONS
Summary of Findings 99
Conclusions 103
Recommendations 104
REFERENCES 105
APPENDICES 111
PAGE
COLLEGE OF COMPUTING AND ENGINEERING x
LIST OF TABLES
Table Page
1 Respondents of the Study 36

2 Median for the Assessment of the
End User in Functionality of
the System 87
End User in Reliability of the System 89
End User in Efficiency of the System 90
End User in Usability of the System 91
Web Experts in Functionality of the System 93
Web Experts in Reliability of the System 95
Web Experts in Efficiency of the System 96
Web Experts in Maintaina bility of the System 98
PAGE
COLLEGE OF COMPUTING AND ENGINEERING xi
LIST OF FIGURES
Figure Page
1 Conceptual Framework of the Study 5

2 Class Diagram 42
3 Use Case Diagram for Patient
Management 44
4 Use Case Diagram for Employee
Management 45
5 Use Case Diagram for Supplies
Management 46
6 Use Case Diagram for Payment
Transaction 47
7 Use case Diagram for Report Management 48
8 Activity Diagram for View Patient
Information 49
9 Activity Diagram for Edit Patient Record 51
10 Activity Diagram for Edit Account 53
11 Activity Diagram for Add Employee
Record 55
12 Activity Diagram for Update Employee
Record 57
13 Activity Diagram for View Employee
Record 59
14 Activity Diagram for Add Supplies 61
15 Activity Diagram for Update Supplies 63
PAGE
COLLEGE OF COMPUTING AND ENGINEERING xii
16 Activity Diagram for View Supplies 65

17 Activity Diagram for Add Payment
Transaction 67
18 Activity Diagram for View Payment
Transaction 69
19 Activity Diagram for Update Payment
Transaction 71
20 Activity Diagram for Reports 73
21 Activity Diagram for Recording Patient
Post-Exposure Treatment 75
22 Entity Relationship Diagram 77
23 Patient 82
24 Treatment Records 83
25 Inventory 84
26 Reports 85
27 Payment 86
PAGE
COLLEGE OF COMPUTING AND ENGINEERING xiii
LIST OF APPENDICES
Appendix Page
A Survey Questionnaires 111

B User’s Manual 120
C Program Listing 130
D Curriculum Vitae 180
E Certificate of Originality 187
PAGE
CHAPTER I
THE PROBLEM AND ITS BACKGROUND
Introduction
Many organizations are still struggling to keep up with the

increasing amount of papers that must be handled and managed. Clinics
are among the organizations that must create a management system to
stay up with the fast-paced digital world and move from paper to
digital records.
The ability to automate a number of administrative and

management tasks can completely change the way practices allocate
their time and resources.
Inefficient time management is a big problem in the medical

industry. One of the biggest struggles healthcare professionals face
involves the ratio of time spent with patients as opposed to other
obligations – it is too low compared to the time spent dealing with
administrative tasks. This trend has been consistent for 50 years and,
until recently, there did not seem to be an easy solution.
Without an efficient and digitized system, it is easy for clinics to

get stuck in an endless cycle of filing, sorting, storing, and handling
PAGE
paperwork by administrative staff. With the innovations in clinic

software, this does not have to be the case any longer.
A medical practice management system is used to manage the

patients, the appointments, the doctors’ schedules, prescriptions,
manage inventory, etc. It makes the otherwise difficult task of
managing a clinic. These days, practice management systems come
with Android and iOS apps with which the doctors can check their
schedule, and patients can book appointments, manage prescriptions,
etc., and may provide SMS or email notifications regarding
appointments. They are more or less a lighter version of a hospital
management system, with more focus on the clinic’s specialization.
Clinics have shown to be popular among people suffering from

minor illnesses as well as those looking for expert care. They provide
people with convenient access to healthcare without requiring them to
attend clinics. Even if a clinic has a limited number of doctors, there is
a steady flow of patients, and it may be difficult to keep up with them.
It may be difficult to preserve patient records for extended periods at a
small-scale clinic. A clinic management system, often known as a
practice management system, provides a collection of functions that
make running a clinic straightforward.
Animal Bite Clinic was a healthcare facility providing trusted

quality anti-rabies vaccines to animal bite patients. The Animal Bite
Clinic is located at Unit 4 F.B. Bailon St, Brgy Sala, Cabuyao Laguna
and offers the following services: Anti-rabies (Pre & Post-exposure),
PAGE
Anti-tetanus, ERIG, Flu vaccine & Pneumococcal vaccine.
Although they are in the era of technologies, Animal Bite Clinic

still using the old ways of manual recording of their patient
information with the increase of their patients thus the records and
files get harder and harder to manage from getting the records of the
past patient to organize the new records of new patients, they also
struggling in recording their everyday transactions.
Because of said issues, the researchers decided to develop a

clinic management system for the Animal Bite Clinic in the hopes of
assisting the clinic in resolving its issues.
Statement of the Problem
The general problem of the study is how to develop a Clinic

Management System for the Animal Bite Clinic of Cabuyao that would
help them in recording and tracking the information of their everyday
operations.
Specifically, the study attempts to answer the following

questions:
1. What are the problems encountered by the business with

regards to:
a) monitoring patient schedule for vaccination;
PAGE
b) managing of supplies;
c) managing the information of the patients;
d) recording of the daily transactions; and
e) generating reports?
2. How the proposed system will solve the problems

encountered
by the Clinic with regards to:
a) monitoring patient schedule for vaccination;
b) managing of supplies;
c) managing the information of the patients;
d) recording of the daily transactions; and
e) generating reports?
3. What are the assessments of the experts regarding the

proposed
system in terms of:
a) functionality;
b) reliability;
c) efficiency; and
d) maintainability?
4. What are the assessments of the end-users regarding the

proposed system in terms of:
a) functionality;
b) reliability;
c) efficiency; and
PAGE
d) usability?
Conceptual Framework of the Study
The conceptual framework is a visual or written illustration of

the expected relationship between the variables under study. The
researchers will use the Input-Process-Output Model as the conceptual
framework of the study. The Input-Process-Output Model identifies the
inputs, outputs, and the process which is needed to transform the
inputs into outputs.
Input Process Output

Knowledge Requirements
Business Process
Programming Skills in HTML,
CSS, JS, and PHP
Knowledge in Database
Management
Software Requirements Agile SDLC
Sublime Text Editor Planning

Xampp Design Clinic Management System
webhost000 With Scheduling for
Development
Minimum Hardware Cabuyao Animal Bite Clinic
Requirements Testing
Maintenance
Personal Computer
Intel Core i3 3.40GHz or high
processor.
8192MB RAM.
Windows 7 or higher version.
EVALUATION
PAGE
Figure 1. Conceptual Framework of the Study
Figure 1 is composed of input, process, and output. The first

section of the IPO Model which is Input contains knowledge
requirements which are about the information, and skills that the
researchers need to make the study and develop a system. Also, it
includes software requirements and hardware requirements that are
needed for the testing of the developed system in the future.
For the process, Agile SDLC will be used by the researchers in

developing the system. The researchers’ reason for using this certain
methodology is because it gives a sense of flexibility where the
development is in a continuous cycle of improvement until the client is
satisfied with the system. This will allow the researchers to find the
bugs or errors in the system and fix them in each cycle. There are five
phases in Agile SDLC which are the following:
The Planning phase is where the researchers must gather the data
from the client that is needed for the development of the system. Then
after that, the researchers will proceed to the second phase which is the
Design and this is where the researchers discussed the required
functions and tools to be used in developing the system based on the
data gathered in the requirements phase. A prototype of the user
interface will also be designed in this phase. After the design phase,
the researchers will proceed to the next phase which is the
Development and this is the part where the researchers will begin to
PAGE
develop the system. The system will be developed in cycles where each
cycle contains an improvement for the system. Each cycle also
contains testing to find the bugs that might exist in the system and fix
them. After the development phase, the researchers will proceed to the
next phase which is the Testing when the development reaches its final
cycle the system will still be tested for bugs and if there are any, the
researchers will fix them immediately. Lastly, after the testing phase,
the researchers will proceed to the last phase which is Maintenance and
in this phase, the researchers will provide support to keep the system
running smoothly and resolve any new bugs.
Finally is the Output which serves as the actual result after

doing the Input and Process is developed. It represents that the Web-
based Clinic Management System for Cabuyao Animal Bite Clinic will
be developed after meeting all those requirements and applying the
appropriate process for the future actual system development of the
study.
PAGE
Significance of the Study
The study aims to provide a solution to the problems experienced

by the Cabuyao Animal Bite Clinic. The study is expected to be
beneficial to the following:
Administration. The proposed system would help the owner of

Animal Bite Clinic in terms of monitoring the records and organized
record storing of the patient’s information and accurate record
transaction process. With the help of the system, they can easily access
and record data through the master list feature. This system is user-
friendly which means the administrator can easily edit, and add any
information from patients, employees, and administrators’ accounts.
Employees. The benefit of the proposed system for the

employees was that it would help them when it comes to computerized
recording of patients' information, fast generation of reports, and
recording the transaction with ease. Employees have the access to edit
and add information with the help of the system which makes it a lot
easier to manage the patients and the clinic’s data, which opens
additional space in their schedule to help with the other clinic matters.
This system also is User-friendly and has time-efficient features or
more patient-centric care.
Patient. The benefit of the proposed system for the patient was
that it would help the patient in providing convenience in keeping
PAGE
records in the clinic for faster processing of transactions compared to

the manual process, the patients usually waited for some time to
process their transaction and accurate records of the patient. With this
system physicians who work in the clinic can take care of the patients
more with the easy access to the patient information and fast report
generation, they can create or plan what the patient needs.
Researchers . The study will help the researchers when it comes

to the proper application of knowledge and skills, they learned in the
degree program. Working on this study will be a great training ground
to improve the researcher’s skills in planning, designing, and
implementing the system’s capabilities which is necessary for their
future career as IT professionals.
Future Researchers . This study will serve as a way for students

in the future to develop their system based on the knowledge and skills
acquired in succeeding years. It will serve as a reference that will give
future researchers reliable information in working on a similar study.
Furthermore, it is also acting to give background and further
information for future researchers in creating their research about
clinic management systems.
PAGE
Scope and Limitation of the Study
The purpose of the study is to develop a Clinic Management with

Scheduling for animal bite clinics to help them in their daily
transactions and operations. One of the purposes of creating the said
system is to provide ease in the clinic and help them to provide the
best services to the clients. The research locale of the study will focus
only on the Animal Bite Clinic in Cabuyao Laguna. The research began
in January 2022 and will continue until December 2022, when it will
be completed.
The system will have the following features: Monitoring the

patient’s record which undergo anti-rabies vaccination session using
inputting the necessary information based on patient records that were
given by the animal bite clinic. Also, the administrator and employee
are the ones who can monitor the patient’s record that undergoes anti-
rabies vaccination session. Next is the dashboard that displays the total
number of registered patients, the number of employees, and total sales
of Cabuyao Animal Bite Clinic. Next is the patient management which
manages patient records and contains a list of registered patients’
information that undergo anti-rabies vaccination. Also, the
administrator and employee can perform add, edit and view the
registered patient’s records. Next is the scheduling, which contains the
list of patient information regarding the schedule for their vaccination
session. Also, the administrator or employee has access to it. Another
is account management, in the account management administrator or
PAGE
employees can edit their account information. Another is employee

management that handles managing of employee information. In the
employee management the administrator can perform add, edit and
view of employee information. Another feature is supplies management
that handles managing of supplies use by Cabuyao Animal Bite Clinic
in performing vaccination of anti- rabies and other services. In this
feature the administrator or employee can add, edit and view the
information of the supplies. Another feature is reports management
that handles managing of reports about transaction of the patients.
Also the administrator can access the reports. Last feature is the
transaction. In the transaction the administrator or employee can add,
edit, and view the transaction based on the patient’s needs.
The programming languages used on the system are: HTML as

the structure and foundation of the program, CSS are used for
decorative layout designs; JavaScript is used for making the website
interactive and PHP is used to create dynamic, interactive web pages.
It will be the server-side scripting language that will be used in the
development of the website. The researchers will use it to
communicate with the database and for the database is MySQL, which
will act as the system's database. Also, the researchers will use
Bootstrap framework to make the website responsive and web hosting
service which is a form of internet hosting service that allows client to
host their own websites online.
The researchers will use the IT principle of design which was

called UX design. UX design is the method used by design teams to
PAGE
produce products that provide people with meaningful and relevant

experiences. The researchers will implement the said principle by
ensuring that the web design is aligned on given sets of principles in
order to cater the needs of the user of the system.
The software development methodology that the researchers will

be using is Agile Methodology. It is a software development process
that focuses on iterative development. It separates jobs into smaller
iterations or pieces that don't need to be planned out in advance. Each
emphasis' number of cycles, duration, and scope are all planned ahead
of time. The researchers choose it because it cuts down on overall
development time, suited for projects with fast-changing requirements
and changes in project specifications are simply addressed and
implemented with minimal influence on the time frame .
The proposed system will be evaluated by end users in terms of

functionality, reliability, usability and efficiency. The end users are
administrator and the employee of Animal Bite Clinic. Also, the
system will be evaluated by the web development experts in terms of
functionality, reliability, maintainability and efficiency. The web
development experts are the graduates of BSIT or other computing
courses who are in the field of web development for at least five years.
The limitation of the study is that the proposed system, the

researchers will not include computing of expenses, assests, liabilities,
and recording documents like balance sheets, income statements, and
cash flow statements however the system will compute only the profit
PAGE
of the clinic. Another limitation of the system is once the system is for
implementation process the researchers will not consider the level of
computer literacy of the user.
Definition of Terms
The following terms used in this study are operationally defined:
Administrator Person who had the authority

and privilege to manage the
system and perform necessary
actions.
Animal Bite Clinic Refers to a healthcare clinic

that specializes in providing
trusted quality anti-rabies
vaccines to animal bite
patients
Anti- rabies vaccination Refers to a process by means

of injecting the anti-rabies
vaccine.
Bootstrap A free and open source front

end development framework
for the creation of websites
PAGE
and web apps
Bug Refers to an error, fault or

flaw on software.
Clinic Management System A program which tracks of

patient’s record, appointments,
doctors' schedules,
prescriptions, inventory, and
so on.
CSS Cascading Style Sheets (CSS)

is a style sheet language used
to describe the presentation of
a document written in HTML
or XML
dashboard A dashboard is a type of

graphical user interface which
often provides at-a-glance
views of key performance
indicators
Database An organized collection of

structured information, or data,
typically stored electronically
in a computer system
PAGE
Efficiency the ratio of the useful work

performed by a machine
ERIG ERIG is equine RIG, products

contain antibodies specifically
made against rabies virus
Functionality the quality or state of being

functional a design that is
admired both for its beauty and
for its functionality especially
HTML is the standard markup

language for Web pages
IPO Input – Processing – Output.

These three steps describe the
basic principle and sequence of
data processing
Refers to a traditional way of

Manual Recording recording by means of using
papers.
Pneumococcal vaccine Vaccines help prevent

PAGE
pneumococcal disease, which

is any type of illness caused by
Streptococcus pneumonia
bacteria
Prototype Refers to a sample of initial

creation of a product design.
Reliability the quality of being

trustworthy or of performing
consistently well
Responsive web A design that will

automatically adjust for
different screen sizes
Time Frame Refers to a duration,

particularly in relation to some
activity or project.
Usability Refers to a measure of how

well a specific user in a
specific context can use a
product/design to achieve a
defined goal effectively
UX design Refers to a method used by

PAGE
design teams to produce

products that give people with
meaningful and relevant
experiences.
Webpage A hypertext document on the

World Wide Web
CHAPTER II
REVIEW OF RELATED LITERATURE AND STUDIES

PAGE
This chapter presents the relevant literature and studies that the
researchers considered in strengthening the claim and importance of
the present study.
Clinic Management System
Clinic is an organization that is responsible in providing a health

medication and treatment for all types of peoples. Surely, everyday
there are people that need to use the clinic services. But how can clinic
provide a faster and efficient services if they are still using the
traditional method on their daily operation? The traditional method
means the customers need to fill in their detail in registration form
manually and the information will only keep in files. After the
registration, the files will be place in the rack and this will cause
problems like taking a longer time to retrieve the information, make
mistakes during writing or misplaced the files [1].
Even though many organizations and sectors are transitioning

from manual to technological automation, most of the clinics people
visit still utilize manual systems to conduct their operations and
provide services such as analyzing patient medical records and
recording patients. The difficulty with manual methods is that they are
all in a document-based system, which may need more time and
physical space to monitor paper records, retrieve information, and
assure data security [ 2]. Moreover, the clinic management system is
highly valuable to a clinic or doctor. It relieves doctor and nurse
workloads and improves patient record management [ 3]. Thus, it
PAGE
improves performance and assists the clinic's daily operations, which

were previously done manually [ 4]. Also, clinic management system is
used to manage patients, consultations, physicians' schedules,
prescriptions, and inventories. They are a scaled-down version of a
hospital management system, with a greater emphasis on the clinic's
specialty [5].
According to Brownley [6], Clinic management system or office

management software offers additional adaptable capabilities that help
administration easier in a smaller healthcare organization . In addition,
it is designed to help the clinic's everyday operations, which were
previously done manually, and it will make data recording and
retrieval easier [7]. Lastly the system is developed due to the problems
that exist when using the manual system. Data inconsistency, data mix
with the other data and problem regarding reporting is the main
problem that the user is facing. Due to that this system is developed to
overcome the problems [8].
‌
Benefits of Clinic Management System
As patient medical records are becoming increasingly large in

healthcare services, and the complexity of exchanging patient records
PAGE
such as prescription detail, referral data, diagnosis status, and

appointment schedules between various clinic-units can be a problem
in the absence of a fully integrated system [ 9]. Hence, a clinic
management system offers benefits that might help the clinic provide
better services to its patients. Using this system, clinics may easily
save time and money on administrative and management activities.
Putting in place a clinic management system is a good move for any
clinic or health care institution. Implementing one of these systems
guarantees a trouble-free way to manage a clinic's day-to-day
operations [10]. In addition, it also improves operations, including as
patient administration, appointment scheduling, physician schedules,
prescription management, payments, transactions, invoicing, and
inventory [11].
Furthermore , it increases the business's effectiveness, all areas

of a healthcare system may be streamlined with the help of the system,
and it monitors finances and supplies. [1 2]. Likewise, it allows to
safely manage and collect information without danger of data theft or
harm. It makes it extremely hard for an unauthorized individual to gain
information to every patient's data and privacy [13]. Therefore, it was
beneficial to clinics because of its excellent management, which assists
in efficient patient record keeping and patient record administration, as
well as lowering clinic overhead expenses in general. It decreases the
need to physically keep patient records by eliminating paperwork.
Because to the growth of web-based services, patients may now
examine their health records online. It also reduces the time required
to retrieve patient records, making it more convenient for both clinic
PAGE
management and the doctor. Patients can arrange appointments online

with the use of web-based solutions [1 4]. Also, it helps healthcare
professionals to increase overall effectiveness, saves costs, decreases
medical mistakes, reduces time consumption, secures your data, and
improves care delivery quality [1 5].
In short, it makes easier for medical health practitioners, nurses,

administrators, and finance professionals to do their jobs. They manage
prescribed medication and help with the preparation of medical
documents. They can also manage finances from the point of payment
to the point of processing. Clinic Management Systems can even help
you make the most of your working hours. It also functions as a patient
tracking system in terms of referrals and appointments [1 6].
Effectiveness of Electronic Health Records in Clinics
An electronic health record (EHR) is a computerized copy of a

patient's medical record. EHRs are real-time, patient-centered records
that make information instantaneously and securely available to
authorized users. It is designed to go beyond traditional clinical data
collected in a provider's office and can provide a broader perspective
of a patient's care [1 7]. According to Dugar [1 8] electronic health
records aid in the delivery of effective treatment to patients while also
automating a range of activities for the practice. It allows a healthcare
provider to communicate information with one another remotely and in
real time, ensuring that any healthcare provider who interacts with a
patient has a current, complete, and accurate file. Moreover, it has also
PAGE
been shown to be a reliable means of moving patient files from paper

to computer.
Despite doing an excellent job of securely gathering and

preserving patient information, EHRs have evolved over time to
include more than simply records and files. [1 9]. Thus, many hospitals
are using the system. It was less than ten percent in 2008. According to
official data from the United States, it was approximately 84 percent in
2015. It would be helpful not just on the healthcare providers but also
the healthcare facility to provide better services to people [ 20].
Therefore, using electronic health records gave much best

control on healthcare facility and healthcare providers when it comes
on information security compared to paper records increasingly
difficult not just on outdated method of maintaining it, but it is prone
on tampering or alteration in which difficult to discover [21]. They
also allow the clinic's personnel and administrative officials to
communicate patient records without physically carrying the
documents because they are easily available at any time from the
clinic's database utilizing computer devices [2 2]. In addition, it is seen
as substantial and preferred to paper records since it enables
physicians to keep accurate track of patient data and monitoring
throughout time, minimizing mistakes and improving overall health
care quality. Once deployed, the Electronic health records system
could provide enormous benefits to doctors and outpatient clinical
health facilities, as well as patients and the broader health care system
[23]. As a result, EHR systems have been used in a health care facility
PAGE
throughout the world because to the benefits they give, most notably
increased security and cost-effectiveness. It is regarded as an essential
component of the healthcare industry since they give several benefits
to patients [24].
Essential F eatures of a Good Clinic Management Systems
Clinic management systems are composed of distinctive features

and needs to have a wide range of features to satisfy the needs of
today’s medical clinics. While there is an abundance of software
solutions available on the market, the provided functionality needs to
match up well with your practice’s needs.
One of these features is Scheduling with the technology

available today, it is inexcusable for medical practices to continue
wasting time by making appointments manually over the phone or at
the front desk. Modern medical clinic software allows you to
completely automate appointment scheduling tasks, making them as
simple as pressing a few buttons.
Instead of relying on spreadsheets or paper records, medical

clinics can have an all-in-one solution for all appointments. Health
clinic software can log new patient appointments according to the
schedules of each doctor, maintain a history of all past appointments,
send automated appointment reminders, and follow up with patients.
The software can assign a patient to the correct physician, exam room
and specialty equipment needed, preventing delays. Patients can also
PAGE
cancel or reschedule their appointments easily online. This not only

saves a lot of time but can also significantly reduce expenses. Missed
appointments can end up costing hundreds of billions of dollars to the
U.S. health care system. With the help of clinic management software,
clinics can reduce missed appointments. And according to the
departments at Central Washington University they have their own way
of scheduling appointments. Some created a HTML form that is
deployed in their department’s website, some have Microsoft Bookings
link in their website and lastly most of the departments are using
“appointment by calling” option, which considering the current
situation with the pandemic, all the lines are always busy, and it is
more difficult to contact the needed person. I worked as an Office
Assistant for the International Office before the pandemic, where I
used to schedule appointments by phone, or people used to come to the
front desk to schedule appointments, which makes the job harder that’s
why scheduling is essential in creating clinic management systems
[25].
Moreover, it has the potential to minimize medical errors,

increase readability, cut unnecessary healthcare costs, and boost
healthcare quality. The primary role is to gather, store, process, and
transfer information to clinical decision makers so that they may make
the best and most timely judgments possible. Because the healthcare
industry is a heterogeneous system comprised of disparate data silos
with a lack of standardization, healthcare providers are looking for a
way to modernize their existing systems that allow for the storage,
PAGE
management, and exchange of health information within and between

hospitals [26].
In addition, these systems also capture personal information such

as a patient’s name, address, contact information and insurance details.
By giving physicians access to a patient’s entire medical history, less
time is spent on background questions, allowing for more focus on
providing treatment. Suppose a patient switches providers for whatever
reason. In that case, their medical information can easily follow them,
enabling each clinician across a patient’s medical spectrum to connect
and share up-to-date, accurate data. Patients can update their personal
information online in addition to viewing lab results, requesting
prescription refills and communicating with their physician. Education
materials and preventative guidelines are often provided for patients as
well, allowing them to play a bigger role in their overall health care
and treatment process.
Next is reporting, the ability to quickly generate and store

reports in one place makes it easy to ensure effective communication
between the clinic, its patients and insurance companies. The leading
medical clinic management software systems have comprehensive
reporting functionality. Users can leverage pre-made reports or create
their own, compiling administrative data and patient information into
timely, easy-to-read reports.
PAGE
Reporting allows your staff members to extract data on financial

performance and a patient’s financial history to identify performance
gaps and trends as well as make financial estimates.
Many health clinic software come with built-in reports and

enable users to create their own customized reports. User-friendly
dashboards let you interpret data through visualizations such as graphs
and charts. In the case organization management reporting is time
consuming and it causes lots of manual work. However, the target of
management reporting is to provide relevant, dependable, and up to
date information about the financial situation of organization and to
support target setting, as well as adhering to the strategy. For effective
decision making it is relevant to receive online data of organizational
performance [27].
Inventory management in medical clinics can be a complicated

process. Making sure that numerous supplies, such as durable medical
equipment (DME) or pharmaceutical samples, are in stock and
conveniently stored can be a challenge. Clinic management software
can streamline the process by providing an efficient way to track
inventory orders, manage inventory storage and generate
comprehensive reports all without the need for manual data entry. The
cost containment features of the software allow tracking inventory
from purchase order to delivery to the patient. This provides valuable
data, helping make more accurate cost-per-patient predictions.
PAGE
Inventory management is an important aspect of any successful

business. It is the process of overseeing and controlling the flow of
inventory units a business uses in the production or manufacture of
goods for sale or distribution. Effective inventory management is
important as not only is inventory one of the most valuable assets to a
business; there is a direct link between inventory levels and company
profits. Inventory represents an investment that is tied up until either
the item is sold, or it is used in the production of another item that is
sold. Businesses are reliant on having items in stock; otherwise,
customers will simply go to a competitor who can provide what they
want [28].
Lastly is Communication an increasingly popular feature

regarding health clinic software revolves around patient-physician
communication. For patients, communication tools include instant
messaging, phone appointments and automatic reminders for check-ups
or preventative care visits. As increased patients demand increased
communication with their physicians, health care organizations must
do their best to meet this need. More recently, telehealth appointments
are becoming increasingly common. Think about it: why would you
schedule an in-office appointment with a physician just to ask for a
prescription refill? This not only wastes the patient’s time, but it
wastes the health care providers’ time as well. Physicians can
accomplish many more minor patient tasks electronically or over the
phone [29].
Challenges in Manual Data Management

PAGE
Even though we are in an era where technology continues to

evolve, other institutions are still using manual data management. As a
result, problems arise like lack of security because of using paper
document which became less secure and can cost a big amount if
confidential document was leak. Next is time consuming since manual
management is a difficult and time-consuming task. It is difficult to
manage and preserve each document carefully and it is not just about
security; it is also about distributing or handing out papers in various
location. Last is the increase in cost since in bigger firms, this can
build up a major expenditure, resulting in a drop in corporate profit
[30]. In fact, according to one research, over 68 percent of people feel
that doing business at the speed of paper is an inappropriate way to do
business. In addition, 46 percent of the respondents said that
eliminating paper from their operations was the most significant
productivity boost for most company procedures [31].
According to Stewart [32], there are challenges of data

management in financial industry: (1) manual data ingestion because
keeping track of and ingesting data from so many vendors can be
challenging and time-consuming. (2) Poor data quality because poor
data quality is just as terrible, if not worse. If you cannot trust your
data, you cannot trust your forecasts based on it. (3) slow data
production because financial institutions are still using outdated
software that is not designed for today's data volume. In fact, data
management issues can have a wide range of consequences like poor
risk management decisions, loss of data, security breaches,
PAGE
unauthorized access, data silos, noncompliance with regulations, an

uncontrolled environment, a restricted number of resources [33]. In
addition, in terms of data transparency, traceability, immutability,
audit, data provenance, flexible access, trust, privacy, and security,
today's healthcare data management systems confront major
challenges. Also, most current healthcare data management systems are
centralized, posing the risk of a single point failure in the case of a
natural disaster [34]. Moreover, it was determined that the paper-based
management systems used to retain patients' medical records were
unreliable and hence risky to use as the basis for prescribing medicine
to patients, highlighting the necessity for this complete solution to
solve the issue for successful health care delivery [35].
The inability to access patient data in real time, exchange and

share medical data, and follow a patient's health state are all
disadvantages of paper-based medical records. This has an adverse
effect on medical research and the ability to improve patient health.
Electronic medical records (EMR) may be able to overcome a variety
of shortcomings in traditional medical records. Standalone EMR
systems may not be able to entirely resolve some of the concerns with
paper records due to a lack of real-time access to patient data. Cloud
computing allows multiple health institutions to share selected patient
data at a lower cost by connecting EMR systems. Standalone EMR
systems may not be able to meet these needs due to a lack of real-time
access to patient data.
PAGE
Based on AmeriFlux As part of the AmeriFlux Management

Project, the AmeriFlux Data Team manages standardization, collection,
quality assurance / quality control and distribution of data submitted
by network members. To generate data products that are timely, and
repeatable, and have traceable provenance, they developed a semi-
automated data processing system. The new system consists of semi-
automated format and data checks. Results are communicated via on-
line reports as well as an issue-tracking system. Data processing time
has been reduced from 2-3 days to a few hours of manual review time,
resulting in faster data availability from the time of data submission.
Minor format errors. Data submissions that are formatted in the new
AmeriFlux can be queued for the data assessment, often with minimal
delay. Automated data checks identify and communicate potentially
erroneous data [36]. According to [37] , Mass-customization production
(MCP) companies faces with shop-floor uncertainty and complexity
caused by wide variety of product components. The research is
motivated by a typical MCP company that has experienced inefficient
scheduling due to paper-based identification and manual data
collection.
In addition, the accurate recording of issues and diagnoses in

health records is critical to safe and successful patient treatment, yet it
is frequently done incorrectly. Electronic health record systems vary in
functionality and convenience of use, and they are not optimally
intended for convenient capture and exchange of clinical information.
There is a dearth of professional consensus and guidelines on how
issues and diagnoses should be reported [38].
PAGE
Furthermore, the quality of manually collected information is

often insufficient for many analyses and scope often too narrow. And
based on the book Data Quality Assessment despite high automation,
much data is typed into databases by people through various forms and
interfaces. The most common source of data inaccuracy is that the
person entering the data just makes mistakes. By creating good data
forms and instruction mitigates this data problems. Data entry should
be easy to the user as much as possible [39].
Impact of Web Application Development
Nowadays, web applications play a vital role when it comes to

organizations' daily operations, and the increasing popularity of the
internet has resulted in an increase in the creation of web applications
in recent years. Businesses are discovering web apps to be the most
convenient method for their staff to work flexibly. The online apps
enable employees to complete their tasks regardless of where they are
[40]. Moreover, web applications integrate the flexibility of mobile
applications with the convenience of using a web browser to access
them. It can be used for ecommerce, banking, entertainment, education,
and everything in between. Web application development is one of the
world's most in-demand skills [41]. According to Fox [42],
organizations, from international corporations to small businesses, are
seeing the value of letting people work on their own schedules. This
tendency will further continue as mobile devices become more widely
available. A web-based solution provides more benefits than simply
PAGE
allowing your staff to work from multiple places. Web application

software development is undergoing tremendous technological
advancement [43]. In short, engaging in web application development
may help your firm grow its network, build effective communication
channels, and stay up with changing times . Web apps enable
enterprises and customers to connect in new ways and deliver better
responses to a variety of requirements. With an expanding number of
firms offering very low-cost web development services, there is no
reason not to try it [44]. Not to mention, Web apps have become an
essential part of our daily lives. As a result, many organizations were
adopting web applications to manage the data utilized as a part of their
business. This will allow them to quickly scan the needed material and
effortlessly complete their project. This will allow them to use the web
to page in a productive way and finish their tasks thoroughly. [45].
Synthesis
The Clinic Management System (CMS) is a tool that will aid

frontline workers in their work. The Clinic Management System papers
and articles aided the researchers in better understanding how CMS
works and why it is significant. The hospital/medical office will be
able to provide better patient care by using a CMS system. It also aids
in the improvement of patient communication. The technology will
also provide faster data access as well as clearer and better
documentation.
PAGE
Moreover, a clinic management system is a good move for any

clinic or health care institution, and it was beneficial to the clinics
because it allows to safely manage and collect information without
danger of data theft or harm. It makes it extremely hard for an
unauthorized individual to gain information to every patient's data and
privacy [13]. Compare to using manual data management that can
result to lack of security due to the usage of paper, which has become
less safe and can cost a significant amount if a private document is
leaked [30].
Businesses are discovering web apps to be the most convenient

method for their staff to work flexibly. Nowadays, web applications
play a vital role when it comes to organizations' daily operations. The
increasing popularity of the internet has resulted in an increase in the
creation of web applications [ 40]. As a result, engaging in web
application development may help your firm grow its network, build
effective communication channels, and stay up with changing times
[44].
Articles, journals, books, and research on the topic of this study

may be applied to the study's aims. Where the researchers hope to
assist doctors and nurses in expediting patient records, the researcher
will also help the patients to have an easier, quick and facilitate on
their check-up. The researchers will make a system way better than the
current system of their clinic. The patients just need to go online and
register. The online application makes the process more convenient and
PAGE
efficient not just for the patients but also for the people taking care of
the application .
CHAPTER III
PAGE
METHODS AND PROCEDURES
This chapter focuses on discussing the research methods and

procedures adhere to by the researcher to answer. Specifically, the
research design, respondents of the study, data gathering tools, data
gathering procedure, data analysis plan and system development of the
study.
Research Design
This study used descriptive research which describes the

population or phenomena that is being examined. This technique
emphasizes the "what" of the research topic rather than the "why" of
the study topic. The descriptive research approach focuses on
identifying the characteristics of a demographic group rather than
"why" a phenomena happens. In other words, it "describes" the
research topic without explaining "why" it occurs [47].
The data collection technique that the researchers will use in

gathering the primary data involves observations, interviews, and
survey questionnaire. In addition, the data collection technique that the
researchers would use in gathering the secondary data involves
literature review, library research and internet research. The
researchers will use Likert Scale for getting the response of the
respondents in the questionnaire. In addition, the researchers will also
use median for getting the average of the responses in the
PAGE
questionnaire.
Respondents of the Study
The researchers will use purposive sampling for the study.

Purposive sampling is a non-probability sample that is chosen based on
population characteristics and the study's goal. This kind of sampling
can be very effective in instances when you need to obtain a certain
sample rapidly and proportionality is not the primary goal [46]. The
researchers selected thirty end users and ten web development experts.
For this study, there are two groups of respondents. The first is the
end user, or the individuals who will use the system. The end-user is
consist of employees or owner of a Animal Bite Clinic. The second is the
web development experts who will inspect the design and functionality of
the system. The web development experts are graduates of BSIT or other
computing courses who are in the field of web development for at least
five years.
Table 1. Respondents of the Study
Category No. of Respondents

End Users 30
Web Development Experts 10
Total 40
PAGE
Table 1 shows the number of respondents for each category. The

researchers will gather data from at least thirty end user and ten web
development experts.
Data Gathering Tools
The researchers gathered data through interviews, internet

research and disseminating survey questionnaire are part of the data
gathering tools process. The researchers made sure that the instruments
are valid and reliable.
Internet research is a systematic process of information from

published articles and resources such as journals, articles, and relevant
studies available on the internet. The researchers ensure that the
information gathered from the internet is valid and related to the
research. The researcher applied the internet to collect more data about
the proposed system.
Observation is a data gathering approach in which researchers

observe certain subject areas. The researchers will used observation in
order to know the process of the Cabuyao Animal Bite Clinic and
identify the problems that they encountered on their daily transaction.
Interview is a communication approach that uses spoken

responses to analyze important details between one or more
respondents. Interviews enable people to communicate their concerns
with others from their own point of view and in their own terms. The
PAGE
interviews were undertaken to get additional information about the

problems encountered in the clinic.
Survey questionnaire is a series of questions provided to

respondents to be answered, allowing researchers to acquire
information about the situation in Cabuyao Animal Bite Clinic. The
questionnaire saves both the researcher and the respondents time while
gathering information compared to the interview.
Data Gathering Procedures
The researchers used different data gathering procedures on its

data gathering tools. The data gathering procedures used are more
convenient and the ease in gathering required details for the
researchers.
The researchers visited the client's office and conducted

interviews with clinic employees. In addition, the researchers
conducted an interview with the clinic's owner using the Messenger
app to ask relevant questions related to the study. The researchers
discovered enough about what must and must not be used for the
system by asking questions directly and through the Messenger app.
The researchers also requested a copy of forms used by the client in
their daily operations that are important for the development of the
software. Also the researchers made observation on the clinic in order
to know the process of their transaction and the problems that they
encountered.
PAGE
Internet research will be carried out by looking up and searching

the web. Because the internet contains with written articles and
materials, researchers ensure that the information acquired on the
internet is credible and related to the topic. It is important to have a
device and internet connectivity in order to perform online research.
Data Analysis Plan
The researchers will use a Likert scale to determine the responses

of the respondents in the questionnaire. Likert Scale is designed to assess
attitudes or opinions. Respondents are asked to score items based on their
level of agreement using this scale.
The format of the Likert Scale that will be used in the study is
presented below:
Options Code
Strongly Agree (SA) 5
Agree (A) 4
Undecided (U) 3
Disagree (D) 2
Strongly Disagree (SD) 1
For the statistical tool, the researchers will use the median to
determine the average responses and percentage to determine the
percentage of the responses to each item on the questionnaire. As a
PAGE
result, the researchers can determine responses, findings, and what

needs to be enhanced on the proposed system collected from the survey
respondents' responses.
System Development
The software development methodology that the researchers will

use is the Agile SDLC. Due to being simple to understand its phases,
the approach in developing business systems is much suited to the
study and become adaptable to whatever change comes. In addition it
is divided into five (5) phases: Planning, Design, Development ,
Testing, and Maintenance . These 5 phases will be the building blocks
for the researchers’ end system to be finalized.
In the planning phase t he researchers first identify the necessary

components that would help in building the system such as the
knowledge requirements, software requirements, hardware
requirements and software tools that the researchers would use. In
addition, the researchers perform observations, interviews in order to
gathered necessary information from the employees or owner of
Cabuyao Animal Bite Clinic in Cabuyao, Laguna that would be needed
in developing the system. Next is design phase the researchers must
first understand the requirements of the end user to visualize the final
output of the system that will be developed. Also, the researchers
created a data flow diagram to better understand the process or system
operation to discover potential problems, improve efficiency, and
develop better processes. In addition the researchers created a hand-
PAGE
drawn user interface sketch based on the requirements collected and

ensure that the design is aligned on the end-user requirements.
The different diagrams that will be the foundation for the system
will be included in this phase.
PAGE
Figure 2. Class Diagram of the Proposed System

PAGE
Figure 2 shows the class diagram of the proposed system which

specifies and presents the proposed system overview and structure in
terms of classes, characteristics, and methods, as well as the
relationships between them. In the class diagram of the proposed
system there is an abstract class name Employee which cannot be
directly instantiated and object cannot be created from it.
PAGE
Figure 3. Use Case Diagram for Patient Management
Figure 3 shows the Use Case for Patient Management. The

Administrator and employee has the same access. Both of them can view
patient records. They can both add new patient record, edit patient
records by changing the patient information. Also, they can both search
for patient records if they wanted to perform view patient records, edit
patient records.
PAGE
Figure 4. Use Case Diagram for Employee Management
Figure 4 shows Use Case for Employee Management. The

Administrator can manage the employee by means of add employee record
which consist of employee information. Also, the Administrator can edit
or apply changes to the employee record if needed to change. The
Administrator can view the employee record that has been created.
PAGE
Figure 5. Use Case Diagram for Supplies Management
Figure 5 shows the Use Case for Supplies Management. The

Administrator and employee has the same access. They can manage the
supplies by means of performing action such as: add supplies, edit
supplies, view supplies, and delete supplies. They can both search for
necessary supplies if they wish to view the supplies, edit supplies, and
delete supplies.
PAGE
Figure 6. Use Case Diagram for Payment Transaction
Figure 6 shows Use Case Diagram for Payment Transaction. The

Administrator and employee has the same access. Both of them can
perform add transaction, edit transaction and view transaction.
PAGE
Figure 7. Use Case Diagram for Report Management
This shows Use Case for Report Management. The Administrator

can show reports or can generate reports. The reports are consisting of
patient’s transaction details that happened in the clinic.
PAGE
Figure 8. Activity Diagram for View Patient Information
Figure 8 shows the process on how to view patient information

for Administrator and employee. The Administrator or employee will
search the patient record. Then the system will check if the patient
record that the Administrator looking is existing. Once it was found
the system will display the patient record found so that Administrator
or employee can view the display patient record however if the patient
PAGE
record was not found. It will display a message saying “No patient
record found”.
PAGE
Figure 9. Activity Diagram for Edit Patient Record
Figure 9 shows the process on how to edit patient record for

Administrator and employee. The Administrator or employee will
search the patient record. Then the system will check if the patient
record exists. Once it was found the system will display the patient and
the system will enabled the text fields where the administrator or
PAGE
employee can change the inputted information. Once they are satisfied
with the changes, the system will save the changes of patient record to
the database.
PAGE
Figure 10. Activity Diagram for Edit Account
Figure 10 shows the process of how to edit an account for

Administrator and employee. The administrator or employee will
request a viewing of the account information. The system will show the
account information, then the administrator or employee will modify
PAGE
the account information. The system will validate the account

information. If the account information is valid, then it will save the
account information in the database. The administrator and employee
can then view the updated account information. However, if the
account information is invalid, then the system will display an invalid
account information message and it will go back to the modify account
information process.
PAGE
Figure 11. Activity Diagram for Add Employee Record
Figure 11 shows the process of how to add an employee record

for Administrator. The Administrator will input the employee details.
Then the system will validate if the employee's details are valid or
invalid. Once the system validates that the employee details that were
inputted are valid, it will be automatically saved to the database. Then
PAGE
the administrator can now view the employee record that was
successfully added. On the other hand, if employee details are invalid,
the system will display invalid employee details and the process will
be terminated.

PAGE
Figure 12. Activity Diagram for Update Employee Record
Figure 12 shows the process on how to update employee record

for Administrator. The Administrator will search the employee record.
The system will show the employee record then the administrator will
PAGE
modify the employee record. The system will validate if the employee
record if the employee record is correct. Once the system validates that
the employee record that were inputted are valid, it will be
automatically saved to the database. Then the administrator can now
view the employee record that was successfully updated. On the other
hand, if employee record are invalid, the system will display invalid
employee record and it will go back to the modify employee record
process.
PAGE
Figure 13. Activity Diagram for View Employee Record
Figure 13 shows the process on how to view employee record.

The Administrator will search the employee record. Then the system
will check if the employee record exists. Once it was found the system
will display the employee record found so that Administrator can view
the displayed employee record. On the other hand, if the system does
PAGE
not find the employee record. The system will display message no
record found.
PAGE
Figure 14. Activity Diagram for Add Supplies
Figure 14 shows the process on how to add supplies for

Administrator and employee. The Administrator or employee will view
the supply information. Then the system will show the supply
information. The Administrator or employee will input the supply
PAGE
information. Then the system will validate the supplies information, if

the supply information is valid then the data will be saved in the
database. The Administrator or employee view the supply information
that was successfully added. However if the supply information is
invalid, it will display invalid supply information and go back to input
supply information process.
PAGE
Figure 15. Activity Diagram for Update Supplies
Figure 15 shows the process of how to update supplies for the

Administrator and employee. The Administrator or employee will
request a viewing of supplies information. Then the system will show
PAGE
the supply information. Then the administrator or employee will edit

supplies information. Then the system will validate the data if the
supply information is valid then the data will be saved in the database
and the system will exit. However if the supply information is invalid,
it will prompt an error message and return to modify supplies
information process.
PAGE
Figure 16. Activity Diagram for View Supplies
Figure 16 shows the process of how to view supplies for the

Administrator and employee. The administrator or employee will
search for supplies records. Then the system will check if the supplies
record exist. Once it was found the system will display the supplies
record found so that Administrator or employee can view the supplies
PAGE
record however if the supplies record was not found. It will display a
message saying “No patient record found”.
PAGE
Figure 17. Activity Diagram for Add Payment Transaction
Figure 17 shows the process on how to add payment transactions

for the Administrator and employee. The Administrator or employee
will input the payment transaction details. Then the system will
validate if the payment transaction details are valid or invalid. Once
the system validates that the payment transaction details that were
PAGE
inputted are valid, it will be automatically saved to the database. Then

the administrator or can now view the payment transaction details that
was successfully added. On the other hand, if payment transaction
details are invalid, the system will display invalid payment transaction
details and the process will be terminated.
PAGE
Figure 18. Activity Diagram for View Payment Transaction
Figure 18 shows the process of how to view payment

transactions for Administrator and employees. The administrator or
employee will search for payment transaction record. Then the system
will check if the payment transaction record record exist. Once it was
PAGE
found the system will display the payment transaction record found so
that Administrator or employee can view the supplies record however
if the payment transaction record was not found. It will display a
message saying “No payment transaction record exist ”.
PAGE
Figure 19. Activity Diagram for Update Payment Transaction
Figure 19 shows the process on how to update payment

transactions for Administrators and employees. The Administrator or
employee will request viewing of payment transaction information and
PAGE
if “yes” then the system will show the payment transaction

information. The administrator or employee will edit the payment
transaction information then the system will validate the information.
Once the information is valid then the system will save the information
to the database. On the other hand, if the information is invalid then
the system will show an error message and it will go back to edit
payment transaction process.
PAGE
Figure 20. Activity Diagram for Viewing of Reports
Figure 20 shows the process of the Reports for the

Administrator. The Administrator can input data. Then the system will
validate the inputted data if it is correct the system will process the
PAGE
data and generate it to display the report you need, if the inputted data
is incorrect it will prompt an error message and the process will be
terminated.
PAGE
Figure 21. Activity Diagram for Recording Patient Post-Exposure

Treatment
Figure 21 shows the process on how to record the patient post-

exposure treatment. The patient first will ask for post-exposure
treatment form. The nurse will give the post-exposure treatment form
to the patient to be fill up. The patient will fill up the form which
includes the personal information, biting animal, category of biting
animal (stray, pet, healthy, sick), category of exposure (I,II,III) and
etc. Then the nurse will receive the form and check if the information
PAGE
is complete. If the information is complete then the nurse will input

the information and the system will save the information. However if
the information was not complete then nurse will ask the patient to
complete the form and fill up the form again.
PAGE
Figure 22. Entity Relationship Diagram

PAGE
Figure 22 shows the entity relationship diagram, which shows

the relationships of entity sets stored in a database. It also shows
different entities that were present in the database and the relationship
between them. Also, it would serve as the blueprint of the database and
helps to organize the data.
For the development phase, It was during the development phase

that all of the code was written. To establish the overall system
architecture, the researchers constructed a prototype. The researchers
worked on the system design, project, requirements, and all of the
coding in buttons, forms, and all of the system's capabilities, such as
adding, updating, viewing, and searching for patients. Next is the
testing phase, it was assessed whether the developed system met the
requirements and whether there were any coding errors. The system
can be deployed and released to the client after functional and non-
functional testing is completed. System testing such as usability
testing, acceptance testing was also performed during this phase to
verify that the system would offer correct and dependable results.
For the maintenance phase, The system began the maintenance

phase as soon as it was tested and installed at the client. Following the
delivery of the system to the client, a maintenance and support
schedule will be established to guarantee that the system continues to
function as intended. Because the client may come up with
functionality enhancements to the produced system, the researchers
may need to make some alterations to the system. The researchers will
PAGE
provide the clients with a user manual on how to properly utilize the
system as well as some advice on how to improve and maintain it.
CHAPTER IV
RESULTS AND DISCUSSION

PAGE
This chapter presents the results and discussion of the

researchers. It also presents the answers to the statement of the
problem and tables or figures is used to present the findings.
Problems Encountered by the Cabuyao Animal Bite Clinic
Monitoring patient schedule for vaccination were done through

manual process. The staff on the clinic only relied on the copy of the
vaccination form that was fill up by the patient to monitor the schedule
of patient. The problem is that it would become time consuming since
it would be hard on the staff to know the patient schedule for
vaccination if they are going to manually check the vaccination form
one by one. In addition, when it comes to giving a schedule to the
patient, the staff is manually writing the dates on a white board for
them to know the following dates for the next anti-rabies vaccination
session of their patients .
Managing of supplies are also conducted manually in the clinic. Staffs

on the clinic usually wrote down the supplies that was available on the
clinic like anti-rabies and etc. In addition the staff find it difficult
when it comes on checking the supplies on the clinic if the data that
was written does not match to the exact number of supplies in the
clinic.
Managing the information of the patients on which the staff at the

clinic are manually doing it. The staff first give a form that the patient
PAGE
will fill up then after that the staff will going to collect the form and
place it in an envelope together with the previous form that other
patient filled up then place it in a cabinet. As a result the patient
record retrieval cost a lot of time, can be prone to damage and
misplaced. In addition the staff used MS Excel to encode the
information of the patients and etc.
Recording of the daily transactions are very hard and busier for the
staff of the clinic beca use they need to write down all the transactions
that happened in a log book. This requires time and effort since the
staff need to write the information of the patient, payment whenever
the patient go to the clinic for follow up schedule of anti-rabies
vaccination.
Generating reports are time-consuming because the staff on the clinic

used the traditional way of generating of reports. The staff on the
clinic need to write the data on a paper then after that it would encode
to MS Excel to make an illustration out of the data gathered by the
clinic based on their daily transactions. Besides using excel can be
time consuming and data integrity can be compromised.
Features of the Proposed System
The purpose of this study is to develop a clinic management with

PAGE
scheduling for a animal bite clinic. The system aims is to help the
clinic find a solution to the problem such as m o n i t o r i n g p a t i e n t
schedule for vaccination, managing of supplies, managing the
information of the patients, recording of the daily transactions
and generating reports. In designing and developing the system,
the researchers used CSS, Bootstrap and JS for the interface and
design. In addition the researchers use PHP which serve as the
b a c k - e n d a n d to create dynamic, interactive web page.
Figure 23. Patient
Figure 23 shows the interface of patient that contains the record

of the patient including their personal information. This feature helps
the staff of the clinic with regards on managing the information of the
patient efficiently compared on traditional method that the clinic use
on their daily recording of patient information. The staff on the clinic
PAGE
can perform add or edit the record of the patient. Also, staff can add
or edit pertinent medical history, treatment records and post-exposure
records under the patient management tab.
Figure 24. Treatment Records
Figure 24 shows the treatment records of the patient. This

feature involves the scheduling of the patient depending on their
category on whether the patient is under the post exposure treatment
or pre-exposure treatment. This feature helps the staff when it comes
on scheduling the patient who are under the post-exposure and pre-
exposure treatment category for their next schedule of anti-rabies
vaccine. In comparison to the traditional way which involves listing
the dates in a white board by the staff of clinic for them to know the
dates that patient is schedule for anti-rabies vaccine. In addition it
shows the dates where the patient will go back to the clinic for their
PAGE
next schedule of anti-rabies vaccine and status whether the session is

completed or still pending.
Figure 25. Inventory
Figure 25 shows the interface for Inventory. It display the name

of the vaccine, description, quantity, category where it can be used and
its price. The staff of the clinic can perform operations such as add,
edit and delete. Aside from that the staff can also use search bar in
which they can easily find it. This feature helps the staff when it
comes on recording the vaccine that they used on their daily
transaction compared to their traditional method of recording the
vaccine that they used on their daily transaction.
PAGE
Figure 26. Reports
Figure 26 shows the interface for reports. This feature helps the
staff monitor the daily transaction that happened on the clinic. The
staff can see the name of the patient, vaccine used, quantity, payment
status, date when transaction happened and the amount that the patient
paid. Also, the staff can filter the date for them to see the past record
of transaction reports that happened on the clinic.
PAGE
Figure 27. Payment
Figure 27 shows the interface for payment transaction that

happened on the clinic. The system can add or edit the payment. This
feature helps the staff when it comes on recording the payment of the
patient efficiently wherein the staff just need to select what animal
bite category does the patient belong. Then the vaccine that will be
used and its corresponding price will be automatically display. In
comparison to the traditional method wherein the staff on the clinic
just need to write down the corresponding price of vaccine based on
the category of animal bite and the payment transaction that happened.
PAGE
Assessment of the Users
The Clinic Management System with Scheduling was evaluated

by thirty (30) end users based on various software quality criteria,
including functionality, reliability, efficiency, and usability . The
researchers used median in finding the average response and
percentage to find the percentage of response of the end user on the
questionnaire .
Table 2. Median for the Assessment of the End User in

Functionality of the System
Question SA A U D SD Total Median

Percentage
Q1 40% 60% 0 0 0 100% 4.0
Q2 37% 43% 20% 0 0 100% 4.0
Q3 40% 60% 17% 0 0 100% 4.0
Q4 63% 20% 17% 0 0 100% 4.0
Q5 40% 53% 7% 0 0 100% 4.0
Where:
Q1 - The clinic management system with scheduling can perform
patient management actions (add, edit and view of patient records).
Q2 - The clinic management system with scheduling can monitor
patient record that undergoes anti-rabies vaccination.
PAGE
scheduling for patients next anti-rabies vaccination session.

Q4 - The clinic management system with scheduling can display the
patient’s next vaccination schedule correctly.
Q5 - The clinic management system with scheduling can generate
payment transaction reports.
Based on the results in Table 2, all of the indicators received 4.0

as median. It implies that the end-users were (4.0) AGREE with
regards on the functionality of the system such as managing of patient,
payments, generating of reports and schedule for anti-rabies next
vaccination session. However, there are some end users who are
undecided when it comes on the functionality of the system since some
of them are beginner in using a system.
PAGE
Table 3. Median for the Assessment of the End User in Reliability

of the System

Percentage
Q1 50% 33% 17% 0 0 100% 4.0
Q2 40% 40% 20% 0 0 100% 4.0
Q3 40% 47% 13% 0 0 100% 4.0
Q4 60% 40% 0 0 0 100% 4.0
Q5 33% 40% 27% 0 0 100% 4.0
Where:
Q1 - You could easily access patient records .
Q2 - The reports on sales and inventory created by the system are
accurate and easy to understand.
Q3 - You can see the updated report about the inventory and sales of
the clinic real time.
Q4 - It is easy to fill up the patient information because the system
gives you error messages when leave or miss some important
information.
Q5 - You never duplicated a patient record because the system is able
to provide you information if the patient already has a record in the
system.
Table 3 shows the results of the end users evaluation in terms of

reliability. All of the indicators had obtained a median score of 4.0.
This means that the end users AGREE that the system is reliable in
PAGE
performing different task for the clinic. However, there are some end
users who are undecided when it comes on the reliability of the system.
Table 4. Median for the Assessment of the End User in Efficiency of

the System

Percentage
Q1 33% 47% 20% 0 0 100% 4.0
Q2 33% 47% 20% 0 0 100% 4.0
Q3 37% 53% 10% 0 0 100% 4.0
Q4 47% 53% 0 0 0 100% 4.0
Q5 43% 40% 17% 0 0 100% 4.0
Where:
Q1 - The clinic management system with scheduling responds quickly
on user interaction.
Q2 - The clinic management system with scheduling quickly displays
the schedule of the patient for next anti-rabies vaccination session.
Q3 - The clinic management system with scheduling performs end-
user’s requirements.
Q4 - The clinic management system with scheduling directly displays
the forms clicked or accessed by the end users.
Q5 - The clinic management system with scheduling immediately
responds to the user input.
PAGE
Table 4 shows the results of the end users evaluation in terms of

reliability. Q1, Q2, Q3,Q4 and Q5 had obtained a median score of 4.0.
This means that the end users AGREE that the system is efficient in
performing different task for the clinic. However, there are some end
users who are UNDECIDED when it comes on the efficiency of the
system.
Table 5. Median for the Assessment of the End User in Usability of

the System

Percentage
Q1 77% 23% 0 0 0 100% 4.0
Q2 70% 30% 0 0 0 100% 5.0
Q3 73% 27% 0 0 0 100% 5.0
Q4 23% 77% 0 0 0 100% 5.0
Q5 57% 43% 0 0 0 100% 5.0
Q6 57% 43% 0 0 0 100% 5.0
Where:
Q1 - The clinic management system with scheduling is easy to use.
Q2 - The user interface is easy to understand.
Q3 - The scheduling is easy to understand.
the forms clicked or accessed by the end use The user can easily see
the schedule for next vaccination session rs.
Q5 - The clinic management system with scheduling provides
PAGE
appropriate validation for user input.

Q6 - The clinic management system with scheduling can be navigated
easily.
Table 5 shows th at Q1, Q2,Q3,Q4 and Q5 had a obtained a

median score of 5.0. This means that the end users STRONGLY
AGREE on the five consecutive questions which refers to usability.
However, Q6 received 4.0 as median in which implies that the end
users AGREE that the system can be navigated easily.
PAGE
Assessment of the Web Experts
The Clinic Management with Scheduling was evaluated by ten

(10) web development experts based on various software quality
criteria, including functionality, reliability, efficiency, and
maintainability. T he researchers used median in finding the average
response and percentage to find the percentage of response of the end
user on the questionnaire .
Table 6. Median for the Assessment of the Web Experts in

Functionality of the System

Percentage
Q1 30% 50% 20% 0 0 100% 4.0
Q2 40% 40% 20% 0 0 100% 4.0
Q3 40% 30% 30% 0 0 100% 4.0
Q4 40% 50% 10% 0 0 100% 4.0
Q5 50% 30% 20% 0 0 100% 4.0
Where:
patient management actions (add, edit and view of patient records).
Q2 - The clinic management system with scheduling can monitor
patient record that undergoes anti-rabies vaccination.
scheduling for patients next anti-rabies vaccination session.
PAGE
Q4 - The clinic management system with scheduling can display the

patient’s next vaccination schedule correctly.
Q5 - The clinic management system with scheduling can generate
payment transaction reports.
Based on the results in Table 6, all of the indicators received

4.0 as a median. It implies that all of the Web experts where agree that
all of the required functionality of the system can be performed and
accomplished by the CMS.
PAGE

Reliability of the System

Percentage
Q1 40% 50% 10% 0 0 100% 4.0
Q2 50% 20% 30% 0 0 100% 4.0
Q3 30% 50% 20% 0 0 100% 4.0
Q4 40% 30% 30% 0 0 100% 4.0
Q5 40% 40% 20% 0 0 100% 5.0
Where:
Q1 - The clinic management system is able to handle all patient
records.
Q2 - The system reports about the clinic sales and inventory are
accurate.
Q3 - The system shows an accurate date for schedule suggestions .
Q4 - The patient records inputted are updated real time .
Q5 - The clinic management system is rarely to never malfunction
Based on the results in Table 7, only Q5 received 5.0 as median.

It implies that the web experts STRONGLY AGREE about the CMS to
rarely or never to malfunction.However, despite having 4.0 as median,
30.0% of the respondents were UNDECIDED in Q2. It implies that
some of the web experts were not sure if the CMS could accurately
provide the sales and inventory of the clinic.
PAGE

Efficiency of the System

Percentage
Q1 50% 40% 10% 0 0 100% 4.0
Q2 40% 30% 30% 0 0 100% 4.0
Q3 50% 40% 20% 0 0 100% 4.0
Q4 50% 50% 0 0 0 100% 4.0
Q5 40% 40% 20% 0 0 100% 5.0
Where:
Q1 - The clinic management system with scheduling responds quickly
on user interaction.
Q2 - The clinic management system with scheduling can be fixed when
defects are detected .
Q3 - The clinic management system with scheduling performs end-
user’s requirements..
the forms clicked or accessed by the end users..
Q5 - The clinic management system with scheduling immediately
responds to the user input.
Based on the results in Table 8, only Q5 received 5.0 as median.

It implies that the web experts STRONGLY AGREE about the
immediate respond of the CMS in the user inputs. However, despite
having 4.0 as median, 30.0% of the respondents were UNDECIDED in
PAGE
Q2. It implies that some of the web experts were not sure if the CMS
can be fixed when defects are detected.
PAGE

Maintainability of the System

Percentage
Q1 30% 50% 20% 0 0 100% 4.0
Q2 40% 40% 30% 0 0 100% 4.0
Q3 50% 40% 10% 0 0 100% 4.0
Q4 50% 40% 10% 0 0 100% 4.0
Q5 50% 50% 0 0 0 100% 5.0
Where:
Q1 - The clinic management system with scheduling can continuously
function when modification/ change is made.
Q2 - The clinic management system with scheduling can be fixed when
defects are detected.
Q3 - It is easy to edit or fix error inputs in the system.
Q4 - The system sorts and records all the information properly for an
easy access. .
Q5 - It is easy to view, edit and save all the transaction.
For the last criterion, Table 9 shows that 1 of the 5 question received
5.0 as median. It implies that the web experts STRONGLY AGREE
that the end-user can easily view, edit and save all the transactions.
PAGE
CHAPTER V
SUMMARY OF FINDINGS, CONCLUSIONS, AND

RECOMMENDATIONS
This chapter presents the summary of findings, the conclusions

made, and recommendations offered based on data analysis in the
previous chapter.
Summary of Findings
The purpose of the study was to design and develop a Clinic

Management System with Scheduling for Cabuyao Animal Bite Clinic.
In addition, the study aims to provide a solution to the problems
encountered by the clinic.
Based on the statement of the problem, the following results

were achieved.
1. The problems encountered by the business with regards to :
a. m o n i t o r i n g p a t i e n t s c h e d u l e f o r v a c c i n a t i o n . The
staff on the clinic only relied on the copy of the vaccination
form that was fil led up by the patient to monitor the schedule of
patient. The problem is that it would become time consuming
since it would be hard on the staff to know the patient schedule
for vaccination if they going to manually check the vaccination
form one by one. In addition, when it comes to giving a schedule
to the patient, the staff is manually writing the dates on a white
PAGE
board for them to know the following dates for the next anti-
rabies vaccination session of their patients .
b. m a n a g i n g o f s u p p l i e s - t h e s taffs on the clinic usually wrote
down the supplies that was available on the clinic like anti-rabies and
etc manually. In addition the staff find it difficult when it comes on
checking the supplies on the clinic if the data that was written does not
match to the exact number of supplies in the clinic.
c. m a n a g i n g t h e i n f o r m a t i o n o f t h e p a t i e n t s - The staff first
give a form that the patient will need to fill up then after that the staff
will going to collect the forms and place it in an envelope together
with the previous form that other patient filled up then place it in a
cabinet. As a result the patient record retrieval cost a lot of time, can
be prone to damage and misplaced. In addition the staff used MS Excel
to encode the information of the patients and etc.
d. r e c o r d i n g o f t h e d a i l y t r a n s a c t i o n s - T h e s t a f f s i n t h e
c l i n i c f i n d i t a s very hard and busier since they need to write down
all the transactions that happened in a log book. As result, it requires
time and effort since the staff need to write the information of the
patient, payment whenever the patient go to the clinic for follow up
schedule of anti-rabies vaccination.
e . g e n e r a t i n g r e p o r t s - T h e s t a f f s o n t h e c l i n i c f i n d i t as very
time-consuming because the staff on the clinic used the traditional way
of generating of reports. The staff on the clinic need to write the data
on a paper then after that it would encode to MS Excel to make an
illustration out of the data gathered by the clinic based on their daily
transactions. Besides using excel can be time consuming and data
integrity can be compromised.
PAGE
2. How the proposed system will solve the problems

encountered.
a. monitoring patient schedule for vaccination- In Clinic
management with scheduling, the staffs just need to input
the necessary information in the system then select the
date. Then the system will automatically generate the
following dates for the patient without relying to the
writings on the white board.
b. managing of supplies- The CMS provide a big help when it

comes on managing the supplies. The staff can be able to
add, edit and view the records of the supplies that was
stored in the system.
c. managing the information of the patients- The CMS can

securely records the information of the patients since only
the staffs who has an account and access to the system.In
addition it helps the staff save time since it can search the
record of the patient efficiently compare to the traditional
way of recording and managing of patient records.
recording of the daily transactions.
d. r e c o r d i n g o f t h e d a i l y t r a n s a c t i o n - CMS provide a big

help when it comes on recording the daily transactions
such as the payment of the client without relying on
traditional way by means of writing it on a log book.
PAGE
e. generating reports- The CMS provide a reports based on

the daily transactions happened inside the company. It can
also monitor transactions happened on the clinic.
3. The result of the end-users assessment on the proposed system

in terms of functional ity, efficiency, usability, and reliability
obtained 4.0 as median. It implies that the users agree that the
CMS comply to the needed requirements . However, there are
some who answered undecided which means some are not sure
whether the system features comply to the needed requirements.
4. The result of the web experts assessment on the proposed

system in terms of functional ity, efficiency, maintainability ,
and reliability obtained 4.0 as median. It implies that the web
experts agree that the CMS meet the needed criteria . However,
there are some who answered undecided which means some are
not sure whether the system features meet the needed criteria.
PAGE
Conclusions
The following conclusion is made based on the summary of findings:
1. The researchers identified the several challenges that currently

facing by the owner and employees of Cabuyao Animal Bite
clinic towards recording and storing patient information.
Despite of having options of different technologies there are
advantages and disadvantages in each of it. Moreover, the
current situation it is more advantageous to have an online
access to the sales reports and patient records.
2. The CMS developed by the researchers met the requirements

needed by the end-users. The employee and the admin were able
to access the website through smartphone or computer. Also,
the employees were able to easily view, edit and delete
different information and records. It concludes that the CMS is
somehow effective to use as additional business tool as long as
the device is connected to the internet .
3. The administrator and employees were able to access and use

the web-based CMS by means of owned device or gadget. The
researchers conclude that the proposed system achieve the
necessary functions for the end-users. However, just like in the
previous conclusion, there are some improvements needed.
PAGE
Recommendations
The researchers developed the following recommendations based on

the study's results and conclusions:
1. The researchers want to recommend the implementation of the

Clinic Management System with Scheduling for Cabuyao Animal
Bite Clinic as an additional business tool for the employees and
owner.
2. The researchers want to recommend to add autosave especially in

encoding data for inventory and patient records which will
automatically store the unsaved data when internet is lost.
3. The researchers want to recommend to add an option that can

generate printable reports based on the statistical illustration of
the clinic sales.
4. The researchers want to recommend to the future researchers the

improvement of the CMS in upgraded version that can surpass
the limitations of the research.
PAGE
REFERENCES:
[1] Teke, Aniket, Saurabh Londh, Piyush Oswal, and S. S. Malwade.

"Online Clinic Management System." International Journal
(Toronto, Ont.) 4, no. 2 (2019).
[2] P. Z. L. Huan, “Clinic Management System (Admin & Doctor’s

System),” eprints.tarc.edu.my , 2022.
https://eprints.tarc.edu.my/20379/.
[3] J A. Teke, S. Londh, P. Oswal, and P. S. S. Malwade, “Online

Clinic Management System,” Int. J. Adv. Sci. Res. Eng. Trends ,
vol. 4, no. 2, pp. 2–5, 2019,[Online].Available:
http://www.ijasret.com/VolumeArticles/FullTextPDF/317_1.Onli
ne_Clinic_Management_System.pdf.
[4] Chang Bing Hui and Mohd Najib Mohd Salleh, “Clinic
Management System for Hope Clinic Bukit Serdang”, aitcs, vol.
2, no. 2, pp. 1265–1274, Nov. 2021.
[5] Steve, “What is a clinic management system?,” Mocdoc.in, 2019.

https://mocdoc.in/blog/what-is-a-clinic-management-system.
[6] K. Brownley, “What is a Clinic Management System? A Brief

Overview & Definition,” Gov Health IT, Sep. 01, 2021.
https://www.govhealthit.com/what-is-a-clinic-management-
system-a-brief-overview-definition/ (accessed Apr. 11, 2022).
[7] A. H. V, “CLINIC MANAGEMENT SYSTEM,” 188.242, 2018,

doi: http://hdl.handle.net/123456789/10725 .
[8] J. Muhammad, “Web-based Clinic Management System (CMS),”

vol. 8, no. 05, pp. 131–135, 2019.
[9] AKARSH, HV. "CLINIC MANAGEMENT SYSTEM." (2019).

PAGE
http://14.99.188.242:8080/jspui/bitstream/
123456789/10725/1/cdcms_111.pdf
[10] M. E. Ltd, “What is Clinic Management System? Features &

Benefits of Clinic Management Software,” Jun. 21, 2021.
https://margcompusoft.com/m/what-is-clinic-management-
software/ (accessed Apr. 12, 2022).
[11] P. Vinkel, “What are the advantages of Clinic Management

software?,” CompanionLink Blog , Sep. 27, 2020.
https://www.companionlink.com/blog/2020/09/what-are-the-
advantages-of-clinic-management-software/.
[12] T. Scribner, “What Do Dentists Need in a Clinic Management

System?,” Scholarly Open Access 2022 , Mar. 23, 2022.
https://scholarlyoa.com/clinic-management-system/.
‌ [13] Knowlab, “Clinic Management Software: 17 Reasons you should

spend on this,” Knowlab, Oct. 12, 2019.
https://knowlab.in/clinic-management-software-17-reasons-you-
should-spend-on-this/ (accessed Apr. 12, 2022).
[14] H. Edwards, “Benefits and Common Features of Clinic

Management Software,” NonCount.com , Jan. 28, 2021.
https://www.noncount.com/clinic-management-software/.
[15] Muhammad Arham, Tahir, R. Muhammad, and Raja Tassaduq,

Abbas, “Doctors Clinic,” Umt.edu.pk, 2017, doi:
http://hdl.handle.net/123456789/2088.
[16] X. Labis, “What can a Clinic Management System do for Your

Business?,” PxTrack, Sep. 20, 2021.
https://www.pxtrack.tech/patient-tracking-system/clinic-
management-system-business/
‌ [17] HealthIT.gov, “What is an electronic health record

(EHR)?,” Healthit.gov , Sep. 10, 2019.
https://www.healthit.gov/faq/what-electronic-health-record-ehr.
PAGE
[18] D. Dugar, “Benefits of Electronic Health Records | EHR

Advantages in 2020,” Selecthub.com , Sep. 16, 2019.
https://www.selecthub.com/medical-software/benefits-of-ehr-
systems/.
[19] J. Morency, “How Does an EHR Improve Patient Care?,” Hello

Health, Jan. 28, 2021. https://hellohealth.com/blog/how-does-an-
ehr-improve-patient-care/
[20] S. Sinhasane, “12 Ways Electronic Health Records Can Improve

Patient Care,” Mobisoft Infotech, Mar. 07, 2019.
https://mobisoftinfotech.com/resources/blog/how-electronic-
health-records-improve-patient-care/.
[21] S. O’Connor, “5 Reasons Why Electronic Health Records are

Better than Paper Records,” www.adsc.com , Jan. 15, 2020.
https://www.adsc.com/blog/reasons-why-ehr-software-is-more-
secure-than-paper-based-records.
[22] Sheetal Mahendher, “Electronic Health Record System - Benefits

And Challenges: A literature Review,” ResearchGate, Jul. 28,
2020.
https://www.researchgate.net/publication/343254459_Electronic_
Health_Record_System_-
_Benefits_And_Challenges_A_literature_Review
[23] S. Albagmi, “The effectiveness of EMR implementation

regarding reducing documentation errors and waiting time for
patients in outpatient clinics: a systematic
review,” F1000Research , vol. 10, p. 514, Oct. 2021, doi:
10.12688/f1000research.45039.2.
[24] A. Shahnaz, U. Qamar, and A. Khalid, “Using Blockchain for

Electronic Health Records,” IEEE Access, vol. 7, pp. 147782–
147795, 2019, doi: 10.1109/access.2019.2946373.
‌ [25] G. Noori, “Appointment Scheduling System,” Undergraduate

Honors Theses, Jan. 2021, [Online]. Available:
https://digitalcommons.cwu.edu/undergrad_hontheses/33
PAGE
[26] M. Islam, T. N. Poly, and Y.-C. J. Li, “Recent Advancement of

Clinical Information Systems: Opportunities and Challenges,”
Yearbook of Medical Informatics, vol. 27, no. 1, pp. 83–90, Aug.
2018, doi: 10.1055/s-0038-1667075.
[27] R. Vilander, “Business Intelligence and Developing Management

Reporting,” pp. 1–70, 2020.
[28] S. M. Chaubey. (2019). DEVELOPMENT OF INVENTORY

MANAGEMENT SYSTEM FOR ESTABLISHMENTS IN
REPUBLIC OF INDIA. 10.13140/RG.2.2.36044.97922.
[29] S. Sarkar, “Best Medical Clinic Management Software 2022 |

Key Features,” Nov. 10, 2021.
https://www.selecthub.com/medical-software/practice-
management/essential-features-medical-clinic-software/
[30] B. Joseph, W. A., N. Maigana, and A. E., “Design and

Implementation of a Secured Web based Medical Record
Management System: A Case Study of Federal University Wukari
(FUW) Clinic,” Int. J. Comput. Appl. , vol. 177, no. 41, pp. 27–
33, 2020, doi: 10.5120/ijca2020919908.
[31] A. Kumar, “Disadvantages of Manually Management

System,” ArcBrain - ERP software in India , Aug. 22, 2017.
https://www.arcbrain.in/automation/manually-working-
disadvantages/.
[32] U. Etim, “6 Manual Data Entry Challenges Businesses Face and

How You Can Overcome Them,” Utibe Etim - Business Plans,
Funds, and Opportunities , Jan. 22, 2021.
https://utibeetim.com/6-manual-data-entry-challenges-
businesses-face-and-how-you-can-overcome-them/ (accessed
Apr. 26, 2022).
[33] M. Stewart, “The 3 Most Common Data Management Challenges

in the Financial Industry,” Code Willing Blog , Jan. 30, 2020.
https://www.codewilling.com/blog/the-3-most-common-data-
management-challenges-in-the-financial-industry/ (accessed Apr.
25, 2022).
PAGE
‌[ 34] H. A. Malak, “11 Data Management Challenges and

Solutions,” Information Management Simplified , Dec. 06, 2021.
https://theecmconsultant.com/data-management-challenges/c.
[35] I. Yaqoob, K. Salah, R. Jayaraman, and Y. Al-Hammadi,

“Blockchain for healthcare data management: opportunities,
challenges, and future recommendations,” Neural Computing and
Applications , Jan. 2021, doi: 10.1007/s00521-020-05519-w.
[36] A. Azameti, G. Koi-Akrofi, N. Agbodo, and J. Amegadzie, “A

Model-Driven Optical Clinic Management Systems: Systematic
Software Engineering Approach,” EAI Endorsed Transactions on
Pervasive Health and Technology , vol. 8, no. 30, p. 173610,
Mar. 2022, doi: 10.4108/eai.16-3-2022.173610.
‌[ 37] D. S. Christianson et al., “AmeriFlux Data Processing:

Integrating automated and manual data management across
software technologies and an international network to generate
timely data products,” NASA ADS, vol. 2017, pp. IN44B03, Dec.
2017, [Online]. Available:
https://ui.adsabs.harvard.edu/abs/2017AGUFMIN44B...03C/abstr
act
[38] A. D. Shah et al., “Recording problems and diagnoses in clinical

care: developing guidance for healthcare professionals and
system designers,” BMJ Health & Care Informatics, vol. 26, no.
1, p. e100106, Dec. 2019, doi: 10.1136/bmjhci-2019-100106.
[39] F. L. F. Almeida, “Benefits, Challenges and Tools of Big Data

Management,” J. Syst. Integr. , vol. 8, no. 4, pp. 12–20, 2017,
doi: 10.20470/jsi. v8i4.311.
‌[ 40] M. Roomi, “5 Advantages and Disadvantages of Web Application

| Drawbacks & Benefits of Web
Application,” www.hitechwhizz.com , Apr. 17,
2021.https://www.hitechwhizz.com/2021/04/5-advantages-and-
disadvantages-drawbacks-benefits-of-web-application.html.
PAGE
[41] H. A. is the Founder et al., “Web Application Development –

The Definitive Guide for 2020,” Moveo Apps, Jul. 13, 2020.
https://www.moveoapps.com/blog/web-application-development-
guide/.
‌[ 42] L. Fox, “Advantages And Disadvantages - Web Apps - Objective

Computing Ltd,” Objective Computing Ltd , Mar. 13, 2019.
https://objectiveit.com/blog/the-advantages-and-disadvantages-
of-web-apps/.
[43] S. S. A. Bukhari, M. Humayun, S. A. A. Shah, and N. Z. Jhanjhi,

“Improving Requirement Engineering Process for Web
Application Development,” IEEE Xplore, Nov. 01, 2018.
https://ieeexplore.ieee.org/abstract/document/8628422 (accessed
Apr. 22, 2022).
[44] A. Davis, “Why Web Application Development Has Become

Vital for Businesses,” The Web Writer Spotlight |
@writerspotlight, Jan. 18, 2020.
https://webwriterspotlight.com/web-application-development-
has-become-vital-for-businesses-why.
[45] S. S. Patni, and M. V. Vaidya, “Survey on Web Application

Vulnerability,” Helix, vol. 9, no. 3, pp. 4941–4946, 2019, doi:
10.29042/2019-4941-4946.
[46] A. Crossman, “What you need to understand about purposive

sampling,” ThoughtCo, Mar. 19, 2020.
https://www.thoughtco.com/purposive-sampling-3026727
[47] A. Bhat, “Descriptive Research: Definition, Characteristics,

Methods, Examples and Advantages |
QuestionPro,” QuestionPro , 2018.
https://www.questionpro.com/blog/descriptive-research/.
APPENDIX A – QUESTIONNAIRE
PAGE
CLINIC MANAGEMENT SYSTEM WITH SCHEDULING FOR

CABUYAO ANIMAL BITE CLINIC
Name: Date:
Questionnaire for Web Experts
The main purpose of this study is to develop a CLINIC MANAGEMENT

SYSTEM WITH SCHEDULING FOR CABUYAO ANIMAL BITE CLINIC. This
questionnaire seeks your feedback on the proposed software in terms of several
software quality standards criteria. Rest assured that any information that you give
shall be treated confidential and anonymous in line with Data Privacy Act of 2012.
Thank you for your cooperation.
- Mel Bert O. Alegre
- Lawrence Albert R. Cantillan
Please check the box that corresponds to your answer.
5 - Strongly Agree (SA)
4 – Agree (A)
3 – Undecided (U)
2- Disagree (D)
1- Strongly Disagree (SD)
CRITERIA SA A U D SD
5 4 3 2 1
PAGE
FUNCTIONALITY
1. The system can perform patient

management actions (add, edit and
view of patient records).
2. The system can view the medical
history of a patient that will undergo
anti-rabies vaccination.
3. The system can perform scheduling
for patients next anti-rabies
vaccination session.
4. The system can display the patient’s
next vaccination schedule correctly.
5. The system can generate payment
transaction reports.
RELIABILITY
1. The system are able to handle all

patient records.
2. The system generating of reports
about the clinic sales and inventory
are accurate.
3. The system shows an accurate date
for schedule suggestions.
4. The patient records inputted are

updated real time.
5. The system can handle human error.
PAGE
EFFICIENCY
1. The system can respond quickly on

user interaction.
2. The system can quickly displays the
schedule of the patient for next anti-
rabies vaccination session.
3. The system can perform end-user’s

requirements (e.g., add patient
record, creation of patient schedule
for vaccination).
4. The system can immediately shows

the forms clicked or accessed by end
users.
5. The system can responds to the user

input.
MAINTAINABILITY
1. The system can continuously

function when minor changes is
made.
2. The system can be fixed when
defects are detected.
3. It is easy to edit or fix error inputs in

the system.
PAGE
4. The system can sort and record all the

information properly for an easy
access.
5. It is easy to view, edit and save all
the transaction.
CLINIC MANAGEMENT SYSTEM WITH SCHEDULING FOR

CABUYAO ANIMAL BITE CLINIC
PAGE
Name (Optional): Date:
Type of User Employee Admin
Questionnaire for End Users
The main purpose of this study is to develop a CLINIC MANAGEMENT

SYSTEM WITH SCHEDULING FOR CABUYAO ANIMAL BITE CLINIC. This
questionnaire seeks your feedback on the proposed software in terms of several
software quality standards criteria. Rest assured that any information that you give
shall be treated confidential and anonymous in line with Data Privacy Act of 2012.
Thank you for your cooperation.
- Mel Bert O. Alegre
- Lawrence Albert R. Cantillan
Please check the box that corresponds to your answer.
5 - Strongly Agree (SA)

4 – Agree (A)
3 – Undecided (U)
2- Disagree (D)
1- Strongly Disagree (SD)
CRITERIA SA A U D SD
5 4 3 2 1
PAGE
FUNCTIONALITY
1. The system can perform
patient management
actions (add, edit and view
of patient records).
2. The system can view the
medical history of a patient
that will undergo anti-
rabies vaccination.

scheduling for patients next
anti-rabies vaccination
session.
4. The system can display the
patient's next vaccination
schedule correctly.
5. The system can generate

payment transaction
reports.
RELIABILITY
1. You could easily access

patient records.
PAGE
2. The reports on sales and

inventory created by the
system are accurate and
easy to understand.
3. You can see the updated

report about the inventory
and sales of the clinic real
time.
4. It is easy to fill up the

patient information
because the system gives
you error messages when
leave or miss some
important information.
5. You never duplicated a

patient record because the
system is able to provide
you information if the
patient already has a
record in the system.
EFFICIENCY
1. The system can responds

quickly on user interaction.
PAGE
2. The system can quickly

displays the schedule of the
patient for next anti-rabies
vaccination session.

end-user’s requirements.
4. The system can

immediately shows the
forms clicked or accessed
by end users.
5. The system can

immediately responds to
the user input.
USABILITY
1. The system is easy to

use.
2. The user interface is

easy to understand.
3. The scheduling is easy

to understand.
4. The user can easily see

the schedule for next
vaccinati on.
PAGE
5. The system provides

appropriate validati on
for user input.
6. The system can be

navigated easily.
APPENDIX B – USERS’S MANUAL

PAGE
How to use:
This section contains the screenshots of Clinic Management System with

Scheduling for Cabuyao Animal Bite Clinic that were captured by the researchers and
explain how this feature of the system operates.
Step 1: The Administrator or staff of the clinic must enter first their
username and password.
After login they can see the dashboard wherein it contains the total
number of employees, patient, sales and report.
PAGE
Step 2: Go to Patients tab and Click “Add Patient Button” to add

record of the patient.
PAGE
After that Administrator or staff must input the fields for patient
information and click “Save” button once they finished then click
“Next” Button.
Step 3: Proceed to Pertinent Medical History then Click “Add Patient

Record” button.
PAGE
After that click the dropdown button to select the patient then
Administrator or staff must input the fields for patient pertinent
medical history and click “Save” button once they finished then click
“Next” Button.
Step 4: Proceed to Post-Exposure Treatment then Click “Add Post-

Exposure Treatment” button.
PAGE
Administrator or staff must input the fields for post exposure treatment
and click “Save” button once they finished then click “Next” Button.
PAGE
Step 5: Proceed to Treatment Records
Administrator or staff must input the date for schedule of pre-
exposure vaccinated record if the patient case is pre-exposure.
However if the patient case is post-exposure, input dates for schedule
of post-exposure vaccinated record. Once it was done click “Save”
button.
PAGE
Step 6: Proceed to Boosters then Click “Add Booster Record”

PAGE
Administrator or staff must input the dates for schedule for booster.
Then click “Save” button once finished.
Step 7: Go to Payment Tab then click “Add Payment” for new

transaction.
PAGE
After that click the dropdown button to select the patient name, status
of payment, service and category of animal bite. Once it was done
click “Save” button.
PAGE
Step 8: Go to Reports Tab to view the reports of payment transactions

happened.
PAGE
APPENDIX C – CODE LISTING
MedicalRecordController.php
<?php alse"','required','before:'.date('m
/d/Y'),'after:01/01/2020'],
namespace App\Http\ 'comorbidity' =>
Controllers; ['exclude_if:is_comorbidity,"fal
use App\Models\Patient; se"','required'],
use App\Models\MedicalRecord;
use Illuminate\Http\Request; 'previous_arv_injection_date' =>
use Illuminate\Validation\Rule; ['exclude_if:is_previous_arv,"fa
use Illuminate\Support\Facades\ lse"','required','before:'.date('m/
DB; d/Y')],
class MedicalRecordController 'allergies' =>
extends Controller ['exclude_if:is_allergy,"false"','r
{ equired'],
// 'date_of_incident' =>
public function index(){ ['required','before_or_equal:'.dat
$patient_data = e('m/d/Y')],
Patient::all(); 'time_of_incident' =>
return ['required'],
view('medical_record.medical_r 'place_of_incident' =>
ecord',compact('patient_data')); ['required'],
} 'nature_of_incident' =>
public function ['required']
create(Request $request){ ],
//dd($request- [
>is_covid_vaccine=="true"); 'covid_vaccine_date.required'
$request->validate([ => "Please specify COVID-19
'patient_id' => Vaccine Date.",
['required'], 'comorbidity.required'
'covid_vaccine_date' => => "Please specify
['exclude_if:is_covid_vaccine,"f comorbidities.",
'previous_arv_injection_date.req
PAGE
uired' => "Please specify 'new_data' =>

previous Anti-Rabies Vaccine $new_data,
Date.", 'message' => $success ?
'previous_arv_injection_date.bef 'Medical record successfully
ore' => "Invalid Anti-Rabies added.' : 'Failed to add new
Vaccine Date.", medical record!'
'allergies.required' => ]);
"Please specify allergies." }
]); public function read(Request
$new_id = $request,$patient_id = 0){
MedicalRecord::create($request- $get_patient_id =
>all())->id; $request->patiend_id;
$success = $new_id > 0; $medical_records =
$new_data = $success ? DB::table('medical_records')
DB::table('medical_records') ->join('patients',
->join('patients', 'medical_records.patient_id', '=',
'medical_records.patient_id', '=', 'patients.id')
'patients.id') ->select(
->select( 'medical_records.*',
'medical_records.*', 'patients.first_name',
'patients.first_name',
'patients.middle_name', 'patients.middle_name',
'patients.last_name', 'patients.last_name',
'patients.birthdate', 'patients.birthdate',
'patients.address', 'patients.address',
'patients.gender', 'patients.gender',
'patients.sr_citizen_no'
) 'patients.sr_citizen_no'
- )
>where('medical_records.id', ->when($get_patient_id>0,
$new_id) function ($query) use
->get()->first() : []; ($get_patient_id) {
return response()- return $query-
>json([ >where('medical_records.patient
'success' => $success, _id', $get_patient_id);
PAGE
}) public function
->get(); update(Request $request){
return response()- $request->validate([
>json(["data" => 'patient_id' => ['required'],
$medical_records]); 'covid_vaccine_date' =>
} ['exclude_if:is_covid_vaccine,"f
public function alse"','required','before:'.date('m
readSingle(Request $request){ /d/Y')],
$get_patient_id = 'comorbidity' =>
$request->patiend_id; ['exclude_if:is_comorbidity,"fal
$medical_records = se"','required'],
DB::table('medical_records') 'previous_arv_injection_date' =>
->join('patients', ['exclude_if:is_previous_arv,"fa
'medical_records.patient_id', '=', lse"','required','before:'.date('m/
'patients.id') d/Y')],
->select( 'allergies' =>
'medical_records.*', ['exclude_if:is_allergy,"false"','r
'patients.first_name', equired'],
'date_of_incident' =>
'patients.middle_name', ['required','before_or_equal:'.dat
'patients.last_name', e('m/d/Y')],
'patients.birthdate', 'time_of_incident' =>
'patients.address', ['required'],
'patients.gender', 'place_of_incident' =>
'patients.sr_citizen_no' ['required'],
) 'nature_of_incident' =>
- ['required']
>where('medical_records.patient ],
_id', $get_patient_id) [
->get(); 'covid_vaccine_date.required'
return response()- => "Please specify COVID-19
>json(["data" => Vaccine Date",
$medical_records]); 'comorbidity.required'
} => "Please specify
comorbidities",
PAGE
'previous_arv_injection_date.req ]);
uired' => "Please specify }
previous Anti-Rabies Vaccine public function
Date", delete(Request $request){
'previous_arv_injection_date.bef $success =
ore' => "Invalid Anti-Rabies MedicalRecord::find($request-
Vaccine Date", >id)->delete();
'allergies.required' => return response()->json([
"Please specify allergies" 'success' => $success,
]); 'message' => $success ?
$success = 'Record successfully deleted.' :
MedicalRecord::find($request- 'Failed to delete record!'
>id)->update($request->all()); ]);
return response()->json([ }
'success' => $success, }
'message' => $success ?
'Record successfully updated.' :
'Failed to update record!'
*
PatientsController *@return \Illuminate\Http\
<?php Response
*/
namespace App\Http\ public function index()
Controllers; {
use App\Models\Patient; $patient_data=
use App\Models\MedicalRecord; Patient::all();
use Illuminate\Http\Request; return
//use Illuminate\Database\ view('patient.patient',compact('p
Eloquent\Relations\MorphTo; atient_data'));
class PatientsController extends }
Controller public function read(){
{ $patient_data =
/** Patient::withCount(['medical_re
* Display a listing of the cords','post_exposure_treatment
resource.
PAGE
s','treatments','boosters'])- $request-
>get(); >validate($validation_rules);
return response()- $success =
>json(["data" => Patient::create($request->all());
$patient_data]); return response()->json([
} 'success' => $success,
/** 'message' => $success ?
* Show the form for creating 'Patient successfully added.' :
a new resource. 'Failed to add new patient!'
* ]);
* @return \Illuminate\Http\ }
Response /**
*/ * Display the specified
public function resource.
create(Request $request) *
{ * @param int $id
$validation_rules = [ * @return \Illuminate\Http\
'first_name' => Response
['required'], */
'last_name' => public function show($id)
['required'], {
'contact_number' => [], //
'birthdate' => }
['required','before:'.date('m/d/Y' /**
)], * Show the form for editing
]; the specified resource.
if(!empty($request- *
>contact_number)){ * @param int $id
array_push($validation_ * @return \Illuminate\Http\
rules['contact_number'],'numeric Response
'); */
array_push($validation_ public function
rules['contact_number'],'digits:1 update(Request $request){
1'); $request->validate([
}
PAGE
'first_name' => public function

['required'], delete(Request $request){
'last_name' => $success =
['required'], Patient::find($request->id)-
'birthdate' => >delete();
['required','before:'.date('m/d/Y' return response()->json([
)], 'success' => $success,
]); 'message' => $success ?
$success = 'Patient successfully deleted.' :
Patient::find($request->id)- 'Failed to delete patient!'
>update($request->all()); ]);
// $new_patient_data = }
Patient::find($request->id)- }
>withCount(['medical_records','
post_exposure_treatments','treat InventoryController.php
ments'])->get();
<?php
return response()->json([
'success' => $success, namespace App\Http\
// 'new_data' =>
Controllers;
$new_patient_data,
'message' => $success ? use App\Models\Inventory;
'Patient successfully updated.' : use Illuminate\Http\Request;
'Failed to update patient!'
use Illuminate\Validation\Rule;
]);
} class InventoryController
/** extends Controller
* Remove the specified {
resource from storage.
* //
* @param int $id public function index(){
* @return \Illuminate\Http\ $inventory_data =
Response
Inventory::all();
*/
PAGE
return $request-
view('inventory.inventory',comp >merge(['category' =>
act('inventory_data')); implode(",",$request-
} >category)]);
public function read(){ $success =
$inventory_data = Inventory::create($request-
Inventory::all(); >all());
return response()- // $inventory_model = new
>json(["data" => Inventory;
$inventory_data]); // $inventory_model-
} >vaccine_name = $request-
public function >input('vaccine_name');
create(Request $request){ // $inventory_model-
$request->validate([ >description = $request-
'vaccine_name' => >input('description');
['required','string','unique:invent // $inventory_model-
ories'], >quantity = $request-
'quantity' => 'numeric', >input('quantity');
'category' => 'required| // $success =
array| $inventory_model->save();
in:none,category_1,category_2,c // $return_data =
ategory_3', $success ? ['message' =>
'price' => 'required| 'Supply successfully added.'] :
numeric| ['error_message' => 'Failed to
between:1,9999999999.99' add new supply!'];
]); // return redirect()-
>back()->with($return_data);
PAGE
return response()->json([ // $return_data =

'success' => $success, $success ? ['message' =>
'message' => $success ? 'Supply successfully updated.'] :
'Supply successfully added.' : ['error_message' => 'Failed to
'Failed to add new supply!' update new supply!'];
]); // return redirect()-
} >route('Inventory')-
public function >with($return_data);
update(Request $request){ return response()->json([
$request->validate([ 'success' => $success,
'vaccine_name' => 'message' => $success ?
['required','string',Rule::unique(' 'Supply successfully updated.' :
inventories')->ignore($request- 'Failed to update supply!'
>id)], ]);
'quantity' => ['numeric'], }
'category' => 'required|array| public function
in:none,category_1,category_2,c delete(Request $request){
ategory_3', $success =
'price' => 'required|numeric| Inventory::find($request->id)-
between:1,9999999999.99' >delete();
]); // $return_data = $success ?
$request->merge(['category' => ['message' => 'Supply
implode(",",$request- successfully updated.'] :
>category)]); ['error_message' => 'Failed to
$success = update new supply!'];
Inventory::find($request->id)-
>update($request->all());
PAGE
// return redirect()- * Display a listing of the

>route('Inventory')- resource.
>with($return_data); *
return response()->json([ * @return \Illuminate\Http\
'success' => $success, Response
'message' => $success ? 'Supply */
successfully deleted.' : 'Failed public function index()
to delete supply!' {
]); $employees =
} DB::table('users')->count();
} $patients =
DB::table('patients')->count();
DashboardController.php $sales = DB::table('bill')
<?php // -
>select(DB::raw("SUM(bill_ite
namespace App\Http\ m.price) as total"))
Controllers; ->leftJoin('bill_item',
use Illuminate\Http\Request; 'bill.id', '=', 'bill_item.bill_id')
use Illuminate\Support\Facades\ -
DB; >where('bill.payment_status','pa
use Illuminate\Support\Facades\ id')
Validator; ->sum('bill_item.price');
class DashboardController return
extends Controller view("dashboard.dashboard")
{ ->with("employees",
/** $employees)
PAGE
->with("patients", $apr = $this-

$patients) >getSalesByMonth(4,$year);
->with("sales",$sales); $may = $this-
} >getSalesByMonth(5,$year);
public function $jun = $this-
getSalesChart($year){ >getSalesByMonth(6,$year);
$input = [ $jul = $this-
'year' => $year, >getSalesByMonth(7,$year);
]; $aug = $this-
$validator = >getSalesByMonth(8,$year);
Validator::make($input, [ $sept = $this-
'year' => 'required| >getSalesByMonth(9,$year);
digits:4|integer|min:1900|max:'. $oct = $this-
(date('Y')+1) >getSalesByMonth(10,$year);
]); $nov = $this-
>getSalesByMonth(11,$year);
if($validator->fails()){ $dec = $this-
return response()- >getSalesByMonth(12,$year);
>json( ['message'=>'invalid $data=[];
year'] ); $data['jan'] = $jan;
} $data['feb'] = $feb;
$jan = $this- $data['mar'] = $mar;
>getSalesByMonth(1,$year); $data['apr'] = $apr;
$feb = $this- $data['may'] = $may;
>getSalesByMonth(2,$year); $data['jun'] = $jun;
$mar = $this- $data['jul'] = $jul;
>getSalesByMonth(3,$year); $data['aug'] = $aug;
PAGE
$data['sept'] = $sept; public function

$data['oct'] = $oct; getPatientsChart($year){
$data['nov'] = $nov; $input = [
$data['dec'] = $dec; 'year' => $year,
return response()- ];
>json( $data ); $validator =
} Validator::make($input, [
public function 'year' => 'required|
getSalesByMonth($month,$year) digits:4|integer|min:1900|max:'.
{ (date('Y')+1)
return DB::table('bill') ]);
- if($validator->fails()){
>select(DB::raw("IFNULL(SUM return response()-
(bill_item.price), 0) as total")) >json( ['message'=>'invalid
->leftJoin('bill_item', year'] );
'bill.id', '=', 'bill_item.bill_id') }
- $jan = $this-
>whereRaw("YEAR(bill.created >getPatientsByMonth(1,$year);
_at) = $year") $feb = $this-
- >getPatientsByMonth(2,$year);
>whereRaw("MONTH(bill.creat $mar = $this-
ed_at) = $month") >getPatientsByMonth(3,$year);
- $apr = $this-
>whereRaw("bill.payment_statu >getPatientsByMonth(4,$year);
s = 'paid'") $may = $this-
->get(); >getPatientsByMonth(5,$year);
}
PAGE
$jun = $this- return response()-

>getPatientsByMonth(6,$year); >json( $data );
$jul = $this- }
>getPatientsByMonth(7,$year); public function
$aug = $this- getPatientsByMonth($month,
>getPatientsByMonth(8,$year); $year){
$sept = $this- return DB::table('bill')
>getPatientsByMonth(9,$year); -
$oct = $this- >select(DB::raw("COUNT(DIST
>getPatientsByMonth(10,$year); INCT(bill.patient_id)) as
$nov = $this- total"))
>getPatientsByMonth(11,$year); ->leftJoin('patients',
$dec = $this- 'bill.patient_id', '=',
>getPatientsByMonth(12,$year); 'patients.id')
$data=[]; -
$data['jan'] = $jan; >whereRaw("YEAR(bill.created
$data['feb'] = $feb; _at) = $year")
$data['mar'] = $mar; -
$data['apr'] = $apr; >whereRaw("MONTH(bill.creat
$data['may'] = $may; ed_at) = $month")
$data['jun'] = $jun; ->get();
$data['jul'] = $jul; return response()-
$data['aug'] = $aug; >json( $bills );
$data['sept'] = $sept; }
$data['oct'] = $oct; /**
$data['nov'] = $nov; * Show the form for creating
$data['dec'] = $dec; a new resource.
PAGE
* * @return \Illuminate\Http\
* @return \Illuminate\Http\ Response
Response */
*/ public function show($id)
public function create() {
{ //
// }
} /**
/** * Show the form for editing
* Store a newly created the specified resource.
resource in storage. *
* * @param int $id
* @param \Illuminate\Http\ * @return \Illuminate\Http\
Request $request Response
* @return \Illuminate\Http\ */
Response public function edit($id)
*/ {
public function store(Request //
$request) }
{ /**
// * Update the specified
} resource in storage.
/** *
* Display the specified * @param \Illuminate\Http\
resource. Request $request
* * @param int $id
* @param int $id
PAGE
* @return \Illuminate\Http\ namespace App\Http\

Response Controllers;
*/ use Illuminate\Http\Request;
public function use Illuminate\Support\Facades\
update(Request $request, $id) DB;
{ use Illuminate\Support\Facades\
// Validator;
} class ReportsController extends
/** Controller
* Remove the specified {
resource from storage. /**
* * Display a listing of the
* @param int $id resource.
* @return \Illuminate\Http\ *
Response * @return \Illuminate\Http\
*/ Response
public function destroy($id) */
{ public function index()
// {
} return
} view("reports.reports");
}
public function
ReportsController.php getPayments(Request $request){
<?php $request->validate([
'date_from' =>
'date_format:"Y-m-d"|required',
PAGE
'date_to' => -
'date_format:"Y-m-d"|required' >whereDate("bill.created_at","<
]); =",$request->date_to)
$bills = DB::table('bill') ->get();
- return response()-
>select('bill.*',DB::raw("CONC >json( $bills );
AT(patients.last_name,', }
',patients.first_name) as /**
full_name, * Show the form for creating
bill_item.vaccine_name, a new resource.
bill_item.quantity, *
bill_item.price, * @return \Illuminate\Http\
bill.payment_status, Response
DATE_FORMAT(bill.created_at */
,'%b/%d/%Y') as public function create()
transaction_date") {
) //
->leftJoin('bill_item', }
'bill.id', '=', 'bill_item.bill_id') /**
->leftJoin('patients', * Store a newly created
'bill.patient_id', '=', resource in storage.
'patients.id') *
- * @param \Illuminate\Http\
>whereDate("bill.created_at","> Request $request
=",$request->date_from) * @return \Illuminate\Http\
Response
*/
PAGE
public function store(Request //

$request) }
{ /**
// * Update the specified
/** *
* * @param int $id
* @param int $id * @return \Illuminate\Http\
Response */
*/ public function
public function show($id) update(Request $request, $id)
{ {
// //
} }
/** /**
* Show the form for editing * Remove the specified
the specified resource. resource from storage.
* *
* @param int $id * @param int $id
* @return \Illuminate\Http\ * @return \Illuminate\Http\
Response Response
*/ */
public function edit($id) public function destroy($id)
{ {
PAGE
// return
} view('treatment.treatment',comp
} act('patient_data'));
}
TreatmentController.php public function read(Request
<?php $request,$patient_id = 0){
$get_patient_id =
namespace App\Http\ $request->patiend_id;
Controllers; $treatments =
use App\Models\Patient; DB::table('treatments')
use App\Models\MedicalRecord; ->join('patients',
use App\Models\Treatment; 'treatments.patient_id', '=',
use Illuminate\Http\Request; 'patients.id')
use Illuminate\Validation\Rule; ->select(
use Illuminate\Support\Facades\ 'treatments.*',
DB; 'patients.first_name',
class TreatmentController 'patients.middle_name',
extends Controller 'patients.last_name',
{ 'patients.birthdate',
// 'patients.address',
public $validation_rules = []; 'patients.gender',
public $validation_messages patients.sr_citizen_no'
= []; )
public function index(){ ->when($get_patient_id>0,
$patient_data = function ($query) use
Patient::all(); ($get_patient_id) {
PAGE
return $query- $both_filled = true;

>where('treatments.patient_id', }else{
$get_patient_id); $this-
}) >setValidationRules($request);
->get(); $create_array =
return response()- $request->all();
>json(["data" => $treatments]); if(empty($request-
} >pre_day_0)){
public function
create(Request $request){ $create_array['pre_day_0_status
$both_filled = false; '] = "";
if((!empty($request- $create_array['pre_day_0_lot'] =
>pre_day_0) && (! "";
empty($request->post_day_0)
|| !empty($request->post_day_3) $create_array['pre_day_7_status
|| !empty($request->post_day_7) '] = "";
|| !empty($request- $create_array['pre_day_7_lot'] =
>post_day_14) || ! "";
empty($request->post_day_30))) $create_array['pre_day_28_statu
|| s'] = "";
(!empty($request-
>post_day_0) && (! $create_array['pre_day_28_lot']
empty($request->pre_day_0) || ! = "";
empty($request->pre_day_7) || ! }
empty($request->pre_day_28)))) if(empty($request-
{ >post_day_0)){
$success = false;
PAGE
}
$create_array['post_day_0_statu return response()->json([
s'] = ""; 'success' => $success,
$create_array['post_day_0_lot'] 'both_filled' =>
= ""; $both_filled,
$create_array['post_day_3_statu 'message' => $success ?
s'] = ""; 'Treatment record successfully
$create_array['post_day_3_lot'] added.' : 'Failed to add new
= ""; treatment record!'
]);
$create_array['post_day_7_statu }
s'] = ""; public function
update(Request $request){
$create_array['post_day_7_lot'] $both_filled = false;
= ""; if((!empty($request-
$create_array['post_day_14_stat >pre_day_0) && (!
us'] = ""; empty($request->post_day_0)
$create_array['post_day_14_lot' || !empty($request->post_day_3)
] = ""; || !empty($request->post_day_7)
$create_array['post_day_30_stat || !empty($request-
us'] = ""; >post_day_14) || !
$create_array['post_day_30_lot' empty($request->post_day_30)))
] = ""; ||
} (!empty($request-
$success = >post_day_0) && (!
Treatment::create($create_array empty($request->pre_day_0) || !
); empty($request->pre_day_7) || !
PAGE
empty($request->pre_day_28))))
{ $update_array['post_day_0_stat
$success = false; us'] = "";
$both_filled = true; $update_array['post_day_0_lot']
}else{ = "";
$this- $update_array['post_day_3_stat
>setValidationRules($request); us'] = "";
$update_array = $update_array['post_day_3_lot']
$request->all(); = "";
if(empty($request- $update_array['post_day_7_stat
>pre_day_0)){ us'] = "";
$update_array['post_day_7_lot']
$update_array['pre_day_0_statu = "";
s'] = ""; $update_array['post_day_14_sta
$update_array['pre_day_0_lot'] tus'] = "";
= ""; $update_array['post_day_14_lot'
$update_array['pre_day_7_statu ] = "";
s'] = ""; $update_array['post_day_30_sta
$update_array['pre_day_7_lot'] tus'] = "";
= "";
$update_array['pre_day_28_stat $update_array['post_day_30_lot'
us'] = ""; ] = "";
$update_array['pre_day_28_lot'] }
= ""; $success =
} Treatment::find($request->id)-
if(empty($request- >update($update_array);
>post_day_0)){ }
PAGE
return response()->json([ 'patient_id' =>

'success' => $success, 'required',
'both_filled' => 'pre_day_0' => [
$both_filled, Rule::requiredIf(function ()
'message' => $success ? use ($request) {
'Treatment record successfully return (!empty($request-
updated.' : 'Failed to update >pre_day_0_lot_no) || !
treatment record!' empty($request-
]); >pre_day_0_status) ||
} !empty($request->pre_day_7)
public function || !empty($request-
delete(Request $request){ >pre_day_28)) &&
$success = empty($request->post_day_0);
Treatment::find($request->id)- })
>delete(); ],
return response()->json([ 'pre_day_0_lot_no' => [
'success' => $success, Rule::requiredIf(function () use
'message' => $success ? ($request) { return !
'Treatment record successfully empty($request->pre_day_0)
deleted.' : 'Failed to delete && $request->pre_day_0_status
treatment record!' == "Completed";
]); })
} ],
public function 'pre_day_0_status' =>
setValidationRules($request){ Rule::requiredIf(function () use
$this->validation_rules = [ ($request) {
PAGE
return !empty($request- Rule::requiredIf(function () use

>pre_day_0); ($request) {
}), return !empty($request-
'pre_day_7' => [ >pre_day_7);
Rule::requiredIf(function () use }),
($request) { function ($attribute, $value,
return (!empty($request- $fail) use ($request) {
>pre_day_7_lot_no) || ! if ($value ==
empty($request- "Completed" && $request-
>pre_day_7_status) || >pre_day_0_status !=
! "Completed") {
empty($request->pre_day_0) || ! $fail('You must
empty($request->pre_day_28)) complete the previous vaccine
&& empty($request- first.');
>post_day_0); }
}) }
], ],
'pre_day_7_lot_no' => 'pre_day_28' => [
Rule::requiredIf(function () use Rule::requiredIf(function () use
($request) { ($request) {
return !empty($request- return (!empty($request-
>pre_day_7) && $request- >pre_day_28_lot_no) || !
>pre_day_7_status == empty($request-
"Completed"; >pre_day_28_status) ||
}), !empty($request->pre_day_0)
'pre_day_7_status' => [ || !empty($request->pre_day_7))
PAGE
&& empty($request- ],
>post_day_0); 'post_day_0' => [
})
], Rule::requiredIf(function () use
'pre_day_28_lot_no' => ($request) {
Rule::requiredIf(function () use return (!empty($request-
($request) { >post_day_0_lot_no) || !
return !empty($request- empty($request-
>pre_day_28) && $request- >post_day_0_status) ||
>pre_day_28_status == !empty($request->post_day_3) ||
"Completed"; !empty($request->post_day_7) ||
}), !empty($request->post_day_14)
'pre_day_28_status' => [ || !empty($request-
Rule::requiredIf(function () use >post_day_30)) &&
($request) { empty($request->pre_day_0);
return !empty($request- })
>pre_day_28); ],
}), 'post_day_0_lot_no' =>
function ($attribute, $value, Rule::requiredIf(function () use
$fail) use ($request) { ($request) {
if ($value == "Completed" && return !empty($request-
$request->pre_day_7_status != >post_day_0) && $request-
"Completed") { >post_day_0_status ==
$fail('You must complete the "Completed";
previous vaccine first.'); }),
}
}
PAGE
'post_day_0_status' => 'post_day_3_lot_no' =>

Rule::requiredIf(function () use Rule::requiredIf(function () use
($request) { ($request) {
return !empty($request- return !empty($request-
>post_day_0); >post_day_3) && $request-
}), >post_day_3_status ==
'post_day_3' => [ "Completed";
}),
Rule::requiredIf(function () use 'post_day_3_status' => [
($request) {
return (! Rule::requiredIf(function () use
empty($request- ($request) {
>post_day_3_lot_no) || ! return !
empty($request- empty($request->post_day_3);
>post_day_3_status) || }),
! function ($attribute,
empty($request->post_day_0) $value, $fail) use ($request) {
|| !empty($request->post_day_7) if ($value ==
|| !empty($request- "Completed" && $request-
>post_day_14) || ! >post_day_0_status !=
empty($request->post_day_30)) "Completed") {
&& empty($request- $fail('You must
>pre_day_0); complete the previous vaccine
}) first.');
], }
}
],
PAGE
'post_day_7' => [ Rule::requiredIf(function () use

Rule::requiredIf(function () ($request) {
use ($request) { return !empty($request-
return (!empty($request- >post_day_7);
>post_day_7_lot_no) || ! }),
empty($request- function ($attribute,
>post_day_7_status) || $value, $fail) use ($request) {
! if ($value ==
empty($request->post_day_0) "Completed" && $request-
|| !empty($request->post_day_3) >post_day_3_status !=
|| !empty($request- "Completed") {
>post_day_14) || ! $fail('You must
empty($request->post_day_30)) complete the previous vaccine
&& empty($request- first.');
>pre_day_0); }
}) }
], ],
'post_day_7_lot_no' => 'post_day_14' => [
Rule::requiredIf(function () use Rule::requiredIf(function ()
($request) { use ($request) {
return ! return (!empty($request-
empty($request->post_day_7) >post_day_14_lot_no) || !
&& $request- empty($request-
>post_day_7_status == >post_day_14_status) ||
"Completed"; !empty($request->post_day_0) ||
}), !empty($request->post_day_3) ||
'post_day_7_status' => [ !empty($request->post_day_7) ||
PAGE
!empty($request->post_day_30)) $fail('You must

&& empty($request- complete the previous vaccine
>pre_day_0); first.');
}) }
], }
'post_day_14_lot_no' ],
=> Rule::requiredIf(function () 'post_day_30' => [
use ($request) { Rule::requiredIf(function () use
return !empty($request- ($request) {
>post_day_14) && $request- return (!empty($request-
>post_day_14_status == >post_day_30_lot_no) || !
"Completed"; empty($request-
}), >post_day_30_status) ||
'post_day_14_status' => !empty($request->post_day_0)
[ || !empty($request->post_day_3)
|| !empty($request->post_day_7)
Rule::requiredIf(function () use || !empty($request-
($request) { >post_day_14)) &&
return ! empty($request->pre_day_0);
empty($request->post_day_14); })
}), ],
function ($attribute, 'post_day_30_lot_no'
$value, $fail) use ($request) { => Rule::requiredIf(function ()
if ($value == use ($request) { return !
"Completed" && $request- empty($request->post_day_30)
>post_day_7_status != && $request-
"Completed") {
PAGE
>post_day_30_status == 'pre_day_7.date_equals'
"Completed"; => "Date must be 7 days from
}), day 0.",
'post_day_30_status' => 'pre_day_28.date_equals' =>
[ "Date must be 28 days from day
0.",
Rule::requiredIf(function () use 'post_day_3.date_equals' =>
($request) { "Date must be 3 days from day
return ! 0.",
empty($request->post_day_30); 'post_day_7.date_equals' =>
}), "Date must be 7 days from day
function ($attribute, 0.",
$value, $fail) use ($request) { 'post_day_14.date_equals' =>
if ($value == "Date must be 14 days from day
"Completed" && $request- 0."
>post_day_14_status != 'post_day_30.date_equals' =>
"Completed") { "Date must be 30 days from day
$fail('You must 0."
complete the previous vaccine ];
first.'); if(!empty($request-
} >pre_day_0)){
} array_push($this-
], >validation_rules['pre_day_7'],'
]; date_equals:'.date("Y-m-
$this->validation_messages = [ d",strtotime($request-
'patient_id.required' => "Please >pre_day_0.' +6 days')));
select patient.",
PAGE
array_push($this- array_push($this-
>validation_rules['pre_day_28'], >validation_rules['post_day_14'
'date_equals:'.date("Y-m- ],'date_equals:'.date("Y-m-
d",strtotime($request- d",strtotime($request-
>pre_day_0.' +27 days'))); >post_day_0.' +13 days')));
}else{ array_push($this-
array_push($this- >validation_rules['post_day_30'
>validation_rules['post_day_0'], ],'date_equals:'.date("Y-m-
'required'); d",strtotime($request-
$this- >post_day_0.' +29 days')));
>validation_messages['post_day }
_0.required'] = "Please fill up $request->validate($this-
either Pre-Exposure or Post- >validation_rules,$this-
Exposure vaccination >validation_messages);
treatment."; }
}if(!empty($request- public function
>post_day_0)){ getPatientsAllRecords(Request
array_push($this- $request){
>validation_rules['post_day_3'], $patient_id = $request-
'date_equals:'.date("Y-m- >patient_id;
d",strtotime($request- $patient =
>post_day_0.' +2 days'))); Patient::find($patient_id);
array_push($this- $medical_record =
>validation_rules['post_day_7'], DB::table('medical_records')
'date_equals:'.date("Y-m- ->join('patients',
d",strtotime($request- 'medical_records.patient_id', '=',
>post_day_0.' +6 days'))); 'patients.id')
PAGE
->select( 'patients.gender',
'medical_records.*', 'patients.sr_citizen_no'
'patients.first_name', )
'patients.middle_name', ->where('patient_id',
'patients.last_name', $patient_id)
'patients.birthdate', ->get();
'patients.address', $success = !
'patients.gender', empty($patient) || !
'patients.sr_citizen_no' empty($medical_record) || !
) empty($post_exposure_record);
->where('patient_id', return response()->json([
$patient_id) 'success' => $success,
->get(); 'data' => [
$post_exposure_record = 'patient' => $patient,
DB::table('post_exposure_treat 'medical_record' =>
ments') $medical_record,
->join('patients', 'post_exposure_record' =>
'post_exposure_treatments.patie $post_exposure_record
nt_id', '=', 'patients.id') ],
->select( 'message' => $success ?
'Patients record found.' : 'Failed
'post_exposure_treatments.*', to find patients record!'
'patients.first_name', ]);
'patients.middle_name', }
'patients.last_name', }
'patients.birthdate',
'patients.address', BoosterController.php
PAGE
<?php $boosters =
DB::table('boosters')
namespace App\Http\ ->join('patients',
Controllers; 'boosters.patient_id', '=',
use App\Models\Booster; 'patients.id')
use App\Models\Patient; ->select(
use Illuminate\Http\Request; 'boosters.*',
use Illuminate\Validation\Rule; 'patients.first_name',
use Illuminate\Support\Facades\
DB; 'patients.middle_name',
class BoosterController extends 'patients.last_name',
Controller 'patients.birthdate',
{ 'patients.address',
// 'patients.gender',
public function index(){
$patient_data = 'patients.sr_citizen_no'
Patient::all(); )
return -
view('booster.booster',compact(' >where('boosters.patient_id',
patient_data')); $get_patient_id)
} ->get();
public function return response()-
getPatientsBoosterRecords(Requ >json(["data" => $boosters]);
est $request){ }
public function
$get_patient_id = saveUpdateBoosters(Request
$request->patient_id; $request){
PAGE
// dd($request);
$this- 'booster_day_3_lot_no' =>
>setValidationRules($request); $request['booster_day_3_lot_no
_'.$i],
$booster_ctr = $request-
>booster_ctr; 'booster_day_3_status' =>
$added_ctr = 0; $request['booster_day_3_status_
$updated_ctr = 0; '.$i]
for($i=0; $i<$booster_ctr; ];
$i++) {
$booster_data = [ if(empty($request['booster_id_'.
'patient_id' => $i])){//insert
$request->patient_id, $added_ctr +=
'treatment_id' => Booster::create($booster_data)-
$request->treatment_id, >id > 0 ? 1 : 0;
'booster_day_0' => }else{//update
$request['booster_day_0_'.$i], $updated_ctr +=
Booster::find($request['booster_
'booster_day_0_lot_no' => id_'.$i])->update($booster_data)
$request['booster_day_0_lot_no ? 1 : 0;
_'.$i], }
}
'booster_day_0_status' => $success = ($added_ctr+
$request['booster_day_0_status_ $updated_ctr) > 0;
'.$i], return response()->json([
'booster_day_3' => 'success' => $success,
$request['booster_day_3_'.$i],
PAGE
'message' => $success ? return !

'Booster record successfully empty($request['booster_day_0_
added.' :'Failed to add new lot_no_'.$i]) || !
booster record!' empty($request['booster_day_0_
]); status_'.$i]) ||
} !
public function empty($request['booster_day_3_
setValidationRules($request){ lot_no_'.$i]);
$booster_ctr = $request- })
>booster_ctr; ];
$this->validation_rules = $this-
[]; >validation_rules['booster_day_
$this- 0_lot_no_'.$i] = [
>validation_messages = [];
for($i=0; $i<$booster_ctr; Rule::requiredIf(function () use
$i++) { ($request,$i) {
// return !
if(empty($request['booster_id_'. empty($request['booster_day_0_
$i])){ '.$i]) &&
// continue; $request['booster_day_0_status_
// } '.$i] == "Completed";
$this- })
>validation_rules['booster_day_ ];
0_'.$i] = [ $this-
>validation_rules['booster_day_
Rule::requiredIf(function () use 0_status_'.$i] = [
($request,$i) {
PAGE
lot_no_'.$i]) || !
Rule::requiredIf(function () use empty($request['booster_day_3_
($request,$i) { return ! status_'.$i]) || !
empty($request['booster_day_0_ empty($request['booster_day_0_
'.$i]); '.$i]);
}) })
]; ];
$this- $this-
>validation_messages['booster_ >validation_rules['booster_day_
day_0_'.$i.'.required'] = "Please 3_lot_no_'.$i] = [
input day 0.";
$this- Rule::requiredIf(function () use
>validation_messages['booster_ ($request,$i) { return !
day_0_lot_no_'.$i.'.required'] = empty($request['booster_day_3_
"Please input day 0 lot '.$i]) &&
number."; $request['booster_day_3_status_
$this- '.$i] == "Completed";
>validation_messages['booster_ })
day_0_status_'.$i.'.required'] = ];
"Please input day 0 status."; $this-
$this- >validation_rules['booster_day_
>validation_rules['booster_day_ 3_status_'.$i] = [
3_'.$i] = [
Rule::requiredIf(function () use
Rule::requiredIf(function () use ($request,$i) {
($request,$i) { return !
empty($request['booster_day_3_
PAGE
return ! $this-
empty($request['booster_day_3_ >validation_messages['booster_
'.$i]); day_3_status_'.$i.'.required'] =
}), "Please input day 3 status.";
function ($attribute,
$value, $fail) use ($request,$i) if(!
{ empty($request['booster_day_0_
if ($value == '.$i])){
"Completed" && array_push($this-
$request['booster_day_0_status_ >validation_rules['booster_day_
'.$i] != "Completed") { 3_'.$i],'date_equals:'.date("Y-m-
$fail('You must d",strtotime($request['booster_d
complete the previous vaccine ay_0_'.$i].' +2 days')));
first.'); $this-
} >validation_messages['booster_
} day_3_'.$i.'.date_equals'] =
]; "Date must be 3 days from day
$this- 0.";
>validation_messages['booster_ }
day_3_'.$i.'.required'] = "Please }
input day 3."; $request->validate($this-
$this- >validation_rules,$this-
>validation_messages['booster_ >validation_messages);
day_3_lot_no_'.$i.'.required'] = }
"Please input day 3 lot public function read(Request
number."; $request,$patient_id = 0){
PAGE
$get_patient_id = ->get();
$request->patiend_id; return response()-
$boosters = >json(["data" => $boosters]);
DB::table('boosters') }
->join('patients', public function
'boosters.patient_id', '=', create(Request $request){
'patients.id') $this-
->select( >setValidationRules2($request);
'boosters.*', $success =
'patients.first_name', Booster::create($request->all());
return response()->json([
'patients.middle_name', 'success' => $success,
'patients.last_name', 'message' => $success ?
'patients.birthdate', 'Booster record successfully
'patients.address', added.' : 'Failed to add new
'patients.gender', booster record!'
]);
'patients.sr_citizen_no' }
) public function
- update(Request $request){
>when($get_patient_id>0, $this-
function ($query) use >setValidationRules2($request);
($get_patient_id) { $success =
return $query- Booster::find($request->id)-
>where('boosters.patient_id', >update($request->all());
$get_patient_id); return response()->json([
}) 'success' => $success,
PAGE
'message' => $success ? 'booster_day_0_lot_no'

'Booster record successfully => [
updated.' : 'Failed to update
booster record!' Rule::requiredIf(function () use
]); ($request) {
} return !
public function empty($request-
delete(Request $request){ >booster_day_0) && $request-
$success = >booster_day_0_status ==
Booster::find($request->id)- "Completed";
>delete(); })
return response()->json([ ],
'success' => $success, 'booster_day_0_status'
'message' => $success ? =>
'Booster record successfully [ Rule::requiredIf(function ()
deleted.' : 'Failed to delete use ($request) {
booster record!' return !
]); empty($request-
} >booster_day_0);
public function })
setValidationRules2($request){ ],
$validation_rules = [ 'booster_day_3' =>
'patient_id' => [ Rule::requiredIf(function ()
'required', use ($request) { return !
'booster_day_0' => empty($request-
'required', >booster_day_3_lot_no) || !
empty($request-
PAGE
>booster_day_3_status) || ! >booster_day_0_status !=
empty($request- "Completed") {
>booster_day_0); $fail('You must
}) complete the previous vaccine
], first.');
'booster_day_3_lot_no' }
=> [ }
]
Rule::requiredIf(function () use ];
($request) { $validation_messages = [
return !
empty($request- 'booster_day_0.required' =>
>booster_day_3) && $request- "Please input day 0.",
>booster_day_3_status == 'booster_day_0_lot_no.required'
"Completed"; => "Please input day 0 lot
}) number.",
], 'booster_day_0_status.required'
'booster_day_3_status' => "Please input day 0 status.",
=> [ Rule::requiredIf(function 'booster_day_3.required' =>
() use ($request) { return ! "Please input day 3.",
empty($request- 'booster_day_3_lot_no.required'
>booster_day_3); => "Please input day 3 lot
}), number.",
function ($attribute, 'booster_day_3_status.required'
$value, $fail) use ($request) { => "Please input day 3 status."
if ($value == ];
"Completed" && $request-
PAGE
if(!empty($request- use Illuminate\Support\Facades\

>booster_day_0)) DB;
{ array_push($validation_rules[' class
booster_day_3'],'date_equals:'.d PostExposureTreatmentControll
ate("Y-m-d",strtotime($request- er extends Controller
>booster_day_0.' +2 days'))); {
$validation_messages['booster_ //
day_3.date_equals'] = "Date public function index(){
must be 3 days from day 0."; $patient_data =
} Patient::all();
$request- return
>validate($validation_rules, view('post_exposure.post_expos
$validation_messages); ure',compact('patient_data'));
} }
} public function read(Request
$request,$patient_id = 0){
PostExposureTreatmentRecor $get_patient_id =
d.php $request->patiend_id;
<?php $post_exposure_treatments
=
namespace App\Http\ DB::table('post_exposure_treat
Controllers; ments')
use App\Models\Patient; ->join('patients',
use App\Models\ 'post_exposure_treatments.patie
PostExposureTreatment; nt_id', '=', 'patients.id')
use Illuminate\Http\Request; ->select(
use Illuminate\Validation\Rule;
PAGE
$post_exposure_treatments =
'post_exposure_treatments.*', DB::table('post_exposure_treat
'patients.first_name', ments')
'patients.middle_name', ->join('patients',
'patients.last_name', 'post_exposure_treatments.patie
'patients.birthdate', nt_id', '=', 'patients.id')
'patients.address', ->select(
'patients.gender',
'patients.sr_citizen_no' 'post_exposure_treatments.*',
) 'patients.first_name',
->when($get_patient_id>0,
function ($query) use 'patients.middle_name',
($get_patient_id) { 'patients.last_name',
return $query- 'patients.birthdate',
>where('post_exposure_treatmen 'patients.address',
ts.patient_id', $get_patient_id); 'patients.gender',
}) 'patients.sr_citizen_no'
->get(); )
return response()- -
>json(["data" => >where('post_exposure_treatmen
$post_exposure_treatments]); ts.patient_id', $get_patient_id)
} ->get();
public function return response()-
readSingle(Request $request){ >json(["data" =>
$get_patient_id = $request- $post_exposure_treatments]);
>patiend_id; }
PAGE
public function 'erig_ml' =>

create(Request $request){ ['exclude_if:is_erig,"false"','req
// dd($request- uired'],
>is_covid_vaccine=="true"); 'anti_tetanus' =>
$request->validate([ ['required']
'patient_id' => ],
['required'], [
'biting_animal' => 'hrig_ml.required' =>
['required'], "Please input HRIG dosage.",
'animal_status' => 'erig_ml.required' =>
['required'], "Please input ERIG dosage.",
'animal_health' => 'animal_status.required'
['required'], => "Please specify if stray or
'category_exposure' => pet.",
['required'], 'animal_health.required'
'weight' => ['required'], => "Please specify if healthy or
'date_treatment_started' sick.",
=> ['required'], 'regimen.required' =>
'rabies_vaccine_used' "Please choose if intramascular
=> ['required'], or intradermal."
'regimen' => ]);
['required'], $success =
'hrig_ml' => PostExposureTreatment::create(
['exclude_if:is_hrig,"false"','req $request->all());
uired'], return response()->json([
'success' => $success,
PAGE
'message' => $success ? 'hrig_ml' =>

'Post-treatment record ['exclude_if:is_hrig,"false"','req
successfully added.' : 'Failed to uired'],
add new post-treatment record!' 'erig_ml' =>
]); ['exclude_if:is_erig,"false"','req
} uired'],
public function 'anti_tetanus' =>
update(Request $request){ ['required']
$request->validate([ ],
'patient_id' => [
['required'], 'hrig_ml.required' =>
'biting_animal' => "Please input HRIG dosage.",
['required'], 'erig_ml.required' =>
'animal_status' => "Please input ERIG dosage.",
['required'], 'animal_status.required'
'animal_health' => => "Please specify if stray or
['required'], pet.",
'category_exposure' => 'animal_health.required'
['required'], => "Please specify if healthy or
'weight' => ['required'], sick.",
'date_treatment_started' 'regimen.required' =>
=> ['required'], "Please choose if intramascular
'rabies_vaccine_used' or intradermal."
=> ['required'], ]);
'regimen' => $success =
['required'], PostExposureTreatment::find($r
PAGE
equest->id)->update($request-
>all()); namespace App\Http\
return response()->json([ Controllers;
'success' => $success, use App\Models\Patient;
'message' => $success ? use App\Models\Inventory;
'Post-treatment record use App\Models\Bill;
successfully updated.' : 'Failed use App\Models\BillItem;
to update post-treatment record!' use Illuminate\Http\Request;
]); use Illuminate\Support\Facades\
} DB;
public function class PaymentController extends
delete(Request $request){ Controller
$success = {
PostExposureTreatment::find($r /**
equest->id)->delete(); * Display a listing of the
return response()->json([ resource.
'success' => $success, *
'message' => $success ? * @return \Illuminate\Http\
'Post-treatment record Response
successfully deleted.' : 'Failed */
to delete post-treatment record!' public function index()
]); {
} $patients = Patient::all();
} $inventory =
Inventory::all();
PaymentController.php $bills = DB::table('bill')
<?php
PAGE
->leftJoin('bill_item', *
'bill.id', '=', 'bill_item.bill_id') * @param \Illuminate\Http\
->get(); Request $request
* @return \Illuminate\Http\
return Response
view('payment.payment') */
->with("patients", public function store(Request
$patients) $request)
->with("vaccines", {
$inventory) $request->validate([
->with("bills", 'patient_id' => 'required|
$bills); exists:patients,id',
} 'payment_status' =>
/** 'required|
* Show the form for creating in:pending,paid,cancelled',
a new resource. 'service' => "required|
* in:anti_rabies,erig_/_hrig,pneum
* @return \Illuminate\Http\ ococcal_vaccine,flu_vaccine"
Response ]);
*/ $bill = new Bill();
public function create() $bill->patient_id =
{ $request->patient_id;
// $bill->payment_status =
} $request->payment_status;
/** $bill->service = $request-
* Store a newly created >service;
resource in storage.
PAGE
$bill->category = $request- 'message' => $result ?

>category; 'Employee successfully added.' :
$result = $bill->save(); 'Failed to add new employee!'
$bill_id = $bill->id; ]);
foreach ($request->data as }
$key => $value) { public function getBills(){
billItem::create([ $bills = DB::table('bill')
"bill_id" => $bill_id, -
"inventory_id" => >select('bill.*',DB::raw("CONC
$value['id'], AT(patients.last_name,',
"vaccine_name" => ',patients.first_name) as
$value['vaccine_name'], full_name,
"description" =>
$value['description'], DATE_FORMAT(birthdate,'%b/
"quantity" => %d/%Y') as birthdate,
$value['quantity'],
"category" => SUM(bill_item.price) as total,
$value['category'],
"price" => $value['price'] DATE_FORMAT(bill.created_at
]); ,'%b/%d/%Y') as
} transaction_date")
// $request->merge([ )
// 'password' => ->leftJoin('bill_item',
Hash::make($password) 'bill.id', '=', 'bill_item.bill_id')
// ]); ->leftJoin('patients',
return response()->json([ 'bill.patient_id', '=',
'success' => $result, 'patients.id')
PAGE
- *
>groupBy('bill_item.bill_id') * @param int $id
->get(); * @return \Illuminate\Http\
return response()- Response
>json( $bills ); */
} public function edit($id)
public function {
getBillItem($id){ //
return response()- }
>json( billItem::where('bill_id', /**
$id)->get() ); * Update the specified
/** *
* * @param int $id
Response */
*/ public function
public function show($id) update(Request $request)
{ {
// $bill = Bill::find($request-
} >id);
/**
* Show the form for editing $data = $request-
the specified resource. >validate([
PAGE
'patient_id' => 'required| "bill_id" => $request-

exists:patients,id', >id,
'payment_status' => "inventory_id" =>
'required| $value['id'],
in:pending,paid,cancelled', "vaccine_name" =>
'service' => "required| $value['vaccine_name'],
in:anti_rabies,erig_/_hrig,pneum "description" =>
ococcal_vaccine,flu_vaccine" $value['description'],
]); "quantity" =>
$result = false; $value['quantity'],
if($bill!=null){ "category" =>
$bill->patient_id = $value['category'],
$request->patient_id; "price" =>
$bill->payment_status = $value['price']
$request->payment_status; ]);
$bill->service = }
$request->service; }
$bill->category = //END:: IF
$request->category; return response()->json([
$result = $bill->save(); 'success' => $result,
$bill_item = 'message' => $result ?
billItem::where('bill_id', 'Payment has been updated.' :
$request->id); 'Failed to update Payment!'
$bill_item->delete(); ]);
foreach ($request->data }
as $key => $value) { /**
billItem::create([
PAGE
* Remove the specified /**

resource from storage. * Display a listing of the
* resource.
* @param int $id *
* @return \Illuminate\Http\ * @return \Illuminate\Http\
Response Response
*/ */
public function destroy($id) public function index()
{ {
// //
} return
} view('admin.user_access');
}
AdminUserAccessController.p /**
hp * Show the form for creating
<?php a new resource.
*
namespace App\Http\ * @return \Illuminate\Http\
Controllers; Response
use Illuminate\Http\Request; */
use App\Models\UserAccess; public function create()
use Illuminate\Support\Facades\ {
DB; //
class }
AdminUserAccessController /**
extends Controller * Store a newly created
{ resource in storage.
PAGE
* */
* @param \Illuminate\Http\ public function show($id)
Request $request {
* @return \Illuminate\Http\ //
Response }
*/ /**
public function store(Request * Show the form for editing
$request) the specified resource.
{ *
// * @param int $id
} * @return \Illuminate\Http\
public function Response
getUserAccess(){ */
return response()- public function edit($id)
>json( DB::table('user_access') {
->leftJoin('users', //
'user_access.username', '=', }
'users.username') /**
->get() ); * Update the specified
/** *
* * @param int $id
Response */
PAGE
public function $this->checkVal($request-

update(Request $request) >post_exposure_records),
{ 'reports' =>
$data = $request->validate([ $this->checkVal($request-
'username' => 'required' >reports),
]); 'treatment_records' => $this-
$update = array( >checkVal($request-
'dashboard' => >treatment_records)
$this->checkVal($request- );
>dashboard), $result =
'boosters' => UserAccess::where('username',
$this->checkVal($request- $request->username)
>boosters), ->update($update);
'inventory' => return response()->json([
$this->checkVal($request- 'success' => $result,
>inventory), 'message' => $result ?
'User Access successfully
'medical_history' => $this- updated.' : 'Failed to update
>checkVal($request- employee!'
>medical_history), ]);
'patients' => }
$this->checkVal($request- function checkVal($val){
>patients), return ($val=="on") ? 1 : 0 ;
'payment' => }
$this->checkVal($request- /**
>payment), * Remove the specified
'post_exposure_records' => resource from storage.
PAGE
* {
* @param int $id //
* @return \Illuminate\Http\ }
Response }
*/
public function destroy($id)
APPENDIX D – CURRICULUM VITAE
CURRICULUM VITAE
ALEGRE, MEL BERT ODANG

CAMELLA BERMUDA HOMES BRGY. BANLIC CABUYAO LAGUNA
PAGE
[email protected]
09471033714
Education
Baccalaureate: Bachelor of Science in Information Technology

Katapatan Homes, Brgy. Banay-Banay Cabuyao, Laguna
2018 -2023
Secondary: Pulo National High School

Brgy. Pulo, Cabuyao Laguna
2012 - 2016
Elementary: Banlic Elementary School

Brgy. Banlic, Cabuyao, Laguna
2006 – 2012
Professional Work Experience(s)
POSITION: Service Crew

Company Name: Jollibee
Company Address: Pulo Cabuyao Laguna
Inclusive Dates 2022
Duties and Responsibilities:
 Assisting the customer with regards on their concern.

 Serving the customer with respect and honesty.
 Ensure restaurant cleanliness daily by clearing tables, returning trays to the
kitchen, sweeping and mopping floors, washing and sanitizing kitchen
utensils, and servicing restrooms.
Conference(s), Training(s), Seminar(s) Attended
Example:
PAGE
“IoT – Internet of Things”, Webinar of Integrated Southern Tagalog Association

of Information Technology Education, December 19,2020
“Industrial Revolution 4.0”, Webinar of Integrated Southern Tagalog Association

of Information Technology Education, December 19,2020
Research Interest(s)
- Cybersecurity,
- Health IT,
- Networking
- Web Development
Research(es) and Publication(s)
- Addiction Of Grade 12 Students To Technology And Academic Performance

- Preparedness Of Ict Students For Employment
- IRIX Operating System
- Clinic Management System with Scheduling for Cabuyao Animal Bite Clinic
Eligibility
Computer System Servicing NC2

Date Renewed: April 8, 2018
Date Expired: March 11, 2022
Award(s) and Commendation(s)
- SHS Graduate with Honors (2016-2018)
Skill(s)/Talent(s)
PAGE
- Time Management
- Adaptability
- Computer literate
- Effective communication
- Problem-solving
- Work ethic
- Basic Encoding
References
Name: Asst. Prof. Arcelito Quiatchon

Position: Department Chairperson
Company: Pamantasan ng Cabuyao (University of Cabuyao)
Address: Katapatan Subd., Bgy Banay-banay City of Cabuyao, Laguna
I hereby certify that the above information is true and correct.I understand that
any misinterpretation, falsification or omission of material facts of whatever nature
required by this application shall be considered sufficient cause for dismissal at
anytime during my employment with Pamantsan ng Cabuyao.
I hereby bind myself to follow all the rules and regulations of Pamantasan ng
Cabuyao in the duration of my employment.

MEL BERT O. ALEGRE DEC 6, 2022
PRINTED NAME OVER SIGNATURE DATE
PAGE
CURRICULUM VITAE
CANTILLAN, LAWRENCE ALBERT R.

342 Brgy. Niugan, City of Cabuyao, Laguna
[email protected]
09950348977
Education
PAGE
Baccalaureate: Bachelor of Science in Information Technology

Katapatan Homes, Brgy. Banay-Banay Cabuyao, Laguna
2018 -2023
Secondary: Cabuyao National High School

Limcaoco, Subdivision, Cabuyao, 4025 Laguna
2012 - 2016
Elementary: Niugan Elementary School

Brgy. Banlic, Cabuyao, Laguna
2006 - 2012
Conference(s), Training(s), Seminar(s) Attended
“IoT – Internet of Things”, Webinar of Integrated Southern Tagalog

Association of Information Technology Education, December 19,2020
“Industrial Revolution 4.0”, Webinar of Integrated Southern Tagalog

Association of Information Technology Education, December 19,2020
Research Interest(s)
Human Computer Interaction

Systems and Networking
Cybersecurity
Web Development
Research(es) and Publication(s)
Clinic Management System with Scheduling for Cabuyao Animal Bite Clinic
Skill(s)/Talent(s)
PAGE
- Time Management
- Adaptability
- Computer literate
- Effective communication
- Problem-solving
- Work ethic
- Basic Encoding
References
Name: Asst. Prof. Arcelito Quiatchon

Position: Department Chairperson
Company: Pamantasan ng Cabuyao (University of Cabuyao)
Address: Katapatan Subd., Bgy Banay-banay City of Cabuyao, Laguna
I hereby certify that the above information is true and correct.I understand that
any misinterpretation, falsification or omission of material facts of whatever nature
required by this application shall be considered sufficient cause for dismissal at
anytime during my employment with Pamantsan ng Cabuyao.
I hereby bind myself to follow all the rules and regulations of Pamantasan ng
Cabuyao in the duration of my employment.

LAWRENCE ALBERT R. CANTILLAN DEC 6, 2022
PRINTED NAME OVER SIGNATURE DATE
PAGE
APPENDIX E – CERTIFICATE OF ORIGINALITY
Certificate of Originality
This is to certify, that the research paper submitted is the result of our
independent and original work. This research has not been submitted for any degree
or other purposes.
We certify that the content of this research is the product of our own work, and that
we have fully credited all of the sources from which the ideas were derived in
developing this research and sources.
Alegre, Mel Bert O.
Cantillan, Lawrence Albert R.

PAGE

Clinic Management System With Scheduling For Cabuyao Animal Bite Clinic

Uploaded by

Copyright:

Available Formats

Clinic Management System With Scheduling For Cabuyao Animal Bite Clinic

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Clinic Management System With Scheduling For Cabuyao Animal Bite Clinic

Uploaded by

Copyright:

Available Formats

PAGE

COLLEGE OF COMPUTING AND ENGINEERING

CLINIC MANAGEMENT SYSTEM WITH SCHEDULING

A Capstone Project Proposal

In partial fulfillment of the requirements for the degree of Bachelor

ASST PROF. MARVIN L. ATANACIO

DR. MA. CONSUELO L. DIMAYA

PROF. SHARMAINE JUSTYNE R. PROF. ARCELITO C. QUIATCHON

DR. RAMIRO Z. DELA CRUZ

ENGR. LUISITO LOLONG LACATAN, PhD, PCpE

To their family, Alegre, Cantillan and friends who unconditionally

Dr. Luisito Lolong Lacatan, Dean of College of Computing and

Prof. Sharmaine Justyne R. Maglapuz, Prof. Arcelito C. Quiatchon and

First of all, The researchers would like this research to dedicate

To future researchers as well, the researchers hope that it could

Title : CLINIC MANAGEMENT SYSTEM WITH

Researchers : Mel Bert O. Alegre

Degree Program : Bachelor of Science in Information Technology

Adviser : Asst Prof. Marvin Atanacio

School : Pamantasan ng Cabuyao

The volume of paperwork that needs to be handled and managed is still

The design, development, and implementation of a clinic management system

I THE PROBLEM AND ITS BACKGROUND Page

II REVIEW OF RELATED LITERATURE AND STUDIES

III METHODS AND PROCEDURES

Respondents of the Study 36

IV RESULTS AND DISCUSSION

V SUMMARY OF FINDINGS, CONCLUSIONS, AND

1 Respondents of the Study 36

1 Conceptual Framework of the Study 5

16 Activity Diagram for View Supplies 65

A Survey Questionnaires 111

THE PROBLEM AND ITS BACKGROUND

Many organizations are still struggling to keep up with the

The ability to automate a number of administrative and

Inefficient time management is a big problem in the medical

Without an efficient and digitized system, it is easy for clinics to

paperwork by administrative staff. With the innovations in clinic

A medical practice management system is used to manage the

Clinics have shown to be popular among people suffering from

Animal Bite Clinic was a healthcare facility providing trusted

Anti-tetanus, ERIG, Flu vaccine & Pneumococcal vaccine.

Although they are in the era of technologies, Animal Bite Clinic

Because of said issues, the researchers decided to develop a

Statement of the Problem

The general problem of the study is how to develop a Clinic

Specifically, the study attempts to answer the following

1. What are the problems encountered by the business with

2. How the proposed system will solve the problems

3. What are the assessments of the experts regarding the

4. What are the assessments of the end-users regarding the

Conceptual Framework of the Study

The conceptual framework is a visual or written illustration of

Input Process Output

Sublime Text Editor Planning

Figure 1. Conceptual Framework of the Study

Figure 1 is composed of input, process, and output. The first

For the process, Agile SDLC will be used by the researchers in

Finally is the Output which serves as the actual result after