Digitizing Patient Record For Mary Angels Diagnostic Clinic Document

Republic of the Philippines
RIZAL TECHNOLOGICAL UNIVERSITY

Cities of Mandaluyong and Pasig
COLLEGE OF ENGINEERING AND ARCHITECHTURE
Digitizing Patient’s Record for Mary Angels Diagnostic Clinic

A Capstone Project & Research 2
Presented to the Faculty of Engineering and Architecture
Brgy. Malamig, Boni Avenue
Mandaluyong City
In Partial Fulfillment of the Requirements for the Degree of
Bachelor of Science in Information Technology
Department of Information Technology
by
Adornado, Raymond Anthony L.
Quintans, Alfred Jhunnell A.
Barbon, Daniel Louis O.
Salamante, Christoper Phillip D.
April 2023
APPROVAL SHEET
This Capstone Project 2 entitled, “Digitizing Patient’s Record for Mary Angels
Diagnostic Clinic”, prepared and submitted by Adornado Raymond Anthony L., Barbon Daniel
Louis, Quintans Alfred Jhunnell A., Salamante Christopher Phillip in partial fulfillment of the
course requirements for the degree of BACHELOR OF SCIENCE IN INFORMATION
TECHNOLOGY, has been examined and recommended for acceptance and approval for Oral
Examination.
Prof. Kenneth Martinez
Adviser
Approved by the Committee of Oral Examination in April 2023 with a grade of ____.
Dr. Jaevier A. Villanueva
Program Chair, BSIT
Ms. Marthea Andrea O. Daluyon, DIT(CAR) Engr.Ramil N. Madriaga, MSIT
Technical / IT Expert Local Panelist
Engr. Greta A. Rosario, MSIT
Capstone Professor
Accepted as partial fulfillment of the course requirements for the degree in Bachelor of
Science in Information Technology.
DR. CORLETO R. BRAVO
Dean, College of Engineering, Architecture Technology
Date: ________
ii | P a g e
DEDICATION
This capstone project is dedicated to my family, who are always there to help me,
and who understand that this capstone meant a lot to me. To myself that gave me motivation
when I feel doubt about my abilities and to my group mates and advisers who helped us
and pushed me to surpass my limit.
Raymond Anthony Adornado
This capstone is the fruit of countless and arduous sacrifices. Through the
researchers’ effort, I dedicated this work proudly and heartily to my parents and to all the
people who served as my motivations and inspirations.
Christoper Phillip Salamante
This capstone project is dedicated to my family, who supported me in everything I
need. To my friends who helped me even if they would not get benefits from this project.
To myself, this project is the fruit of all those sleepless nights and stress that I’ve been
through. And lastly, to my mother.
Alfred Jhunnell Quintans
With sincere appreciation and respect, we dedicate this work to our Almighty God,
who has led and never left us in the completion of this capstone project. I also dedicate this
to my parents, loved ones, and group members who gave us the strength to finish this
project in spite of the challenges we encountered.
Daniel Louis Barbon
iii | P a g e
ACKNOWLEDGMENT
We thank God, the Almighty, for His numerous favors that enabled us to effectively
finish the research.
To Engr. Greta M. Rosario, our subject adviser provided us with all the assistance
we needed and continuously reminded us of how professional ethics can help us become
better people while also offering suggestions to make this project simpler to complete.
For each group member who worked together to make this study a success, we
would not be able to complete the project without the brilliant minds of each one of us.
To Prof. Kenneth Martinez, who served as our capstone adviser and gave us all the
knowledge we required, always reminded us to be keen in helping us grow as people, and
gave us advice on how to accomplish this research more efficiently.
Lastly, to our Panelists, Dr. Marthea Andrea Daluyon, Engr. Greta M. Rosario, Dr.
Jaevier Villanueva, Engr. Ramil Madriaga and Prof. Kenneth Martinez, we would like to
thank them for their comments and suggestions that guided us to make this project on the
right track and reliable.
iv | P a g e
ABSTRACT
Reporting health data using a traditional way also takes more time, resulting in
significant delays and inaccurate information. This may prevent patients from fully
understanding their health status, causing misinterpretation of prescriptions and doctors’
instructions due to poor handwriting. As a result, there is also a difference in creating
strategies to address primary healthcare problems and reduce conflict in healthcare access.
To address such problems, the researchers will create a desktop application digitally storing
patients' information in this study. It serves as the primary storage for information about a
patient's medical care. Patient information is stored in a centralized system. It includes
information about the patient's demographics and medical condition. It is intended to
replace paper medical charts and should adhere to the standard of the clinic. In this
application, doctors and clinic staff can manually add, edit and search patients' records
from a single database.
Keywords: Patient Record, Clinic, Database, SMS Notifier, Digitized, Java, SMS API
v|Page
TABLE OF CONTENTS
TITLE PAGE ..................................................................................................................... i
APPROVAL SHEET ........................................................................................................ ii
DEDICATION.................................................................................................................. iii
ACKNOWLEDGMENT ................................................................................................. iv
ABSTRACT ....................................................................................................................... v
LIST OF FIGURES ......................................................................................................... ix
LIST OF TABLES ............................................................................................................ x
CHAPTER I ...................................................................................................................... 1
BACKGROUND OF THE STUDY ............................................................................................ 1
PROJECT CONTEXT ................................................................................................................. 2
PURPOSE AND DESCRIPTION OF THE PROJECT ............................................................... 2
OBJECTIVES OF THE PROJECT ............................................................................................. 4
SIGNIFICANCE OF THE STUDY............................................................................................. 6
SCOPE AND LIMITATION ....................................................................................................... 7
CONCEPTUAL THEORETICAL FRAMEWORK .................................................................... 8
OPERATIONAL DEFINITION OF TERMS............................................................................ 10
CHAPTER II ................................................................................................................... 11
REVIEW OF RELATED LITERATURE AND STUDIES ...................................................... 11
CHAPTER III ................................................................................................................. 20
THE TECHNICALITY OF THE PROJECT ............................................................................. 20
DETAILS OF THE TECHNOLOGY TO BE USED ................................................................ 20
HOW THE PROJECT WILL WORK ....................................................................................... 21
CHAPTER IV.................................................................................................................. 24
REQUIREMENT SPECIFICATIONS ...................................................................................... 24
FISHBONE DIAGRAM ........................................................................................................ 24
FUNCTIONAL DECOMPOSITION DIAGRAM ................................................................ 25
TECHNICAL FEASIBILITY .................................................................................................... 26
vi | P a g e
RELEVANCE OF THE TECHNOLOGIES.......................................................................... 27

SCHEDULE FEASIBILITY ..................................................................................................... 28
Project Timeline ..................................................................................................................... 28
ECONOMIC FEASIBILITY ..................................................................................................... 29
REQUIREMENTS MODELING .............................................................................................. 31
Data and Process Modeling ....................................................................................................... 31
Context Diagram .................................................................................................................... 32
Data Flow Diagram ................................................................................................................ 33
SYSTEM / PROGRAM FLOWCHART ............................................................................... 34
USE CASE DIAGRAM ......................................................................................................... 37
CLASS DIAGRAM ............................................................................................................... 38
SEQUENCE DIAGRAM....................................................................................................... 39
RISK ASSESSMENT/ANALYSIS ........................................................................................... 41
DESIGN OF SOFTWARE SYSTEMS PRODUCTS AND / OR PROCESSES ...................... 42
OUTPUT AND USER-INTERFACE DESIGN ........................................................................ 42
Forms ..................................................................................................................................... 43
Reports ................................................................................................................................... 54
DATA DESIGN ......................................................................................................................... 60
Data Dictionary ...................................................................................................................... 60
SECURITY ................................................................................................................................ 68
DEVELOPMENT ...................................................................................................................... 68
SOFTWARE SPECIFICATION............................................................................................ 68
HARDWARE SPECIFICATION .......................................................................................... 69
PROGRAM SPECIFICATION ............................................................................................. 70
Test Plan ................................................................................................................................ 72
TESTING ................................................................................................................................... 72
Unit Testing ........................................................................................................................... 72
Integration Testing ................................................................................................................. 74
vii | P a g e
System Testing ....................................................................................................................... 84

PROGRAM PROPERTIES ....................................................................................................... 85
FUNCTION PROPERTIES ....................................................................................................... 87
IMPLEMENTATION PLAN .................................................................................................... 88
CHAPTER V ................................................................................................................... 91
CONCLUSION .......................................................................................................................... 91
RECOMMENDATION ............................................................................................................. 93
REFERENCES ................................................................................................................ 94
APPENDICES ................................................................................................................. 97
Relevant Source Codes .............................................................................................................. 98
Other Relevant Documents ...................................................................................................... 142
Turnitin Result ......................................................................................................................... 148
Copyright Certificate ............................................................................................................... 148
User’s Guide ............................................................................................................................ 149
Documentation ......................................................................................................................... 153
Approval Form ......................................................................................................................... 156
Curriculum Vitae of the Researchers ....................................................................................... 157
viii | P a g e
LIST OF FIGURES
Figure 1…………………………………………………………………………………………… 8
Figure 2…………………………………………………………………………………………… 9
Figure 3………………………………………………………………………………………... 22
Figure 4………………………………………………………………………………………….. 24
Figure 5………………………………………………………………………………………….. 26
Figure 6………………………………………………………………………………………….. 28
Figure 7………………………………………………………………………………………….. 29
Figure 8………………………………………………………………………………………….. 31
Figure 9………………………………………………………………………………………….. 32
Figure 10………………………………………………………………………………………… 33
Figure 11………………………………………………………………………………………… 34
Figure 12………………………………………………………………………………………… 35
Figure 13………………………………………………………………………………………… 36
Figure 14………………………………………………………………………………………… 37
Figure 15………………………………………………………………………………………… 38
Figure 16………………………………………………………………………………………… 39
Figure 17………………………………………………………………………………………… 40
Figure 18………………………………………………………………………………………… 41
Figure 19………………………………………………………………………………………… 43
Figure 20………………………………………………………………………………………… 44
Figure 21………………………………………………………………………………………… 45
Figure 22………………………………………………………………………………………… 46
Figure 23………………………………………………………………………………………… 47
Figure 24………………………………………………………………………………………… 48
Figure 25………………………………………………………………………………………… 49
Figure 26………………………………………………………………………………………… 50
Figure 27………………………………………………………………………………………… 51
Figure 28………………………………………………………………………………………… 52
Figure 29………………………………………………………………………………………… 53
Figure 30………………………………………………………………………………………… 54
Figure 31………………………………………………………………………………………… 55
Figure 32………………………………………………………………………………………… 56
Figure 33………………………………………………………………………………………… 57
Figure 34………………………………………………………………………………………… 58
Figure 35………………………………………………………………………………………… 59
Figure 36………………………………………………………………………………………… 71
ix | P a g e
LIST OF TABLES
Table 1……………………………………………………………………………………………26
Table 2……………………………………………………………………………………………27
Table 3……………………………………………………………………………………………30
Table 4……………………………………………………………………………………………60
Table 5……………………………………………………………………………………………61
Table 6……………………………………………………………………………………………61
Table 7……………………………………………………………………………………………62
Table 8……………………………………………………………………………………………62
Table 9……………………………………………………………………………………………63
Table 10…………………………………………………………………………………………..63
Table 11………………………………………………………………………………………….. 64
Table 12………………………………………………………………………………………….. 64
Table 13…………………………………………………………………………………………..66
Table 14………………………………………………………………………………………….. 67
Table 15………………………………………………………………………………………….. 67
Table 16…………………………………………………………………………………………..70
Table 17………………………………………………………………………………………….. 70
Table 18………………………………………………………………………………………….. 72
Table 19…………………………………………………………………………………………..74
Table 20………………………………………………………………………………………….. 75
Table 21………………………………………………………………………………………….. 76
Table 22…………………………………………………………………………………………..76
Table 23………………………………………………………………………………………….. 76
Table 24………………………………………………………………………………………….. 77
Table 25………………………………………………………………………………………..…77
Table 26………………………………………………………………………………………….. 77
Table 27………………………………………………………………………………………….. 78
Table 28…………………………………………………………………………………………. 78
Table 29………………………………………………………………………………………… 79
Table 30………………………………………………………………………………………….. 79
Table 31…………………………………………………………………………………………..81
Table 32………………………………………………………………………………………….. 82
Table 33………………………………………………………………………………………….. 83
Table 34…………………………………………………………………………………………..84
Table 35 …………………………………………………………………………………………. 87
Table 36………………………………………………………………………………………….. 88
x|Page
Table 37…………………………………………………………………………………………..89
xi | P a g e
CHAPTER I
INTRODUCTION
This chapter includes the background of the study, which summarizes the system
on which the researchers will concentrate, as well as the importance, scope, and limitations
of the study.
BACKGROUND OF THE STUDY
A medical record contains a person's health-related details, such as age, gender,
weight, and test results, including prescriptions and allergies. The utilization of technology
has been widespread in the 21st century, making life easier and faster compared to
traditional methods. Digital medical records are necessary in this digital age to safeguard
confidential health data from unauthorized disclosure. In clinics, organizing patient
information into an organized and relevant report has traditionally been challenging.
Manual paper-based record keeping can result in inaccuracies, damage, and manipulation
due to poor handwriting and unclear acronyms. Using traditional methods to report health
data takes more time, causing significant delays and inaccurate information. Creating
solutions to address primary healthcare problems and reducing healthcare access conflict
differs due to this issue. The researchers will develop a desktop application to store patients'
information digitally. It will act as the primary storage for a patient's medical care
information. The system includes demographic and medical information, and it aims to
replace paper-based medical charts by adhering to clinic standards. In this application,
1|Page
doctors and clinic staff can manually add, edit and search patients' records from a single
database.
PROJECT CONTEXT
The Mary Angels Diagnostic Clinic used the traditional way of admitting patients
for the longest time. Using the manual method of storing and managing patient records
resulted in the said clinic, a lot of damage in terms of data management. Implementing
digitized patients’ record will resolve the problem. A desktop application that stores
patients' medical records containing different forms derived from Mary Angels Diagnostic
Clinic admitting section form. The application will also provide a user-friendly graphical
interface to access specific records.
The system allows the doctors and clinic staff to manually add, edit, delete, and
search patients' records from a single database. It will also allow the doctor and staff to
keep track of their upcoming appointments with patients. The system will have a secure
login system where doctors and staff can create an account to log in to the system to provide
additional security.
PURPOSE AND DESCRIPTION OF THE PROJECT
As medical research advances, the population's life expectancy rises. Although this
development leads to positive outcomes, such as the elimination of some diseases, and the
discovery of new treatments for others, other challenges arise more frequently. However,
as medical knowledge grows, advancements in other fields, like computer programming,
2|Page
emerge that can assist physicians in addressing these issues. Healthcare providers currently
generate and store medical and non-medical data in large quantities. These records may
include drug prescriptions, treatment records, general check-up information, physician's
notes, and medical information.
The Field Health Service Information System (FHSIS) is the Philippine Department
of Health's official recording and reporting system. The FHSIS, which was conceived in
1987 and implemented nationally in 1989, is now in its fourth revision. The FHSIS collects
information systems on priority government programs designed to track healthcare
delivery using key indicators. However, not all programs, such as those for rabies control
and noncommunicable diseases, are included. It is a manual, paper-based system in which
midwives and nurses at primary care level health centers record and report on health
services provided at the front lines (RHU or city local health centers). Data must be
aggregated at several levels of the health system, including the health facility, the City or
Provincial Health Office (CHO/PHO), the DOH's regional offices, and the DOH's National
Epidemiology Center. Adopting computer-based patient records will improve access to
medical records in a clinic. It has been repeatedly stated that medical practice can be
improved by reducing medical errors that occur during treatment. Most errors occur as a
result of incomplete medical records, transcription errors, or a failure to correlate medical
histories with current treatment decisions. Furthermore, while paper-based records are
easier to create, they are challenging to search, as demonstrated in one study where
3|Page
physicians were unable to find relevant information about the patient in traditional paper-
based records in 80% of outpatient visits.
OBJECTIVES OF THE PROJECT
The developers are working to create a computer application that stores patient
records for small clinics that still use traditional paper-based record systems. The
application aims to reduce the time spent locating and retrieving patients' session histories.
The application should be able to;
1. Allow the doctor and clinic staff to create an account and log in.
2. Allow the clinic staff to record patient data such as;
a. Name
b. Age
c. Birthday
d. Address
e. Contact No.
f. Weight and Height
g. Blood Pressure
h. Pulse Rate
4|Page
i. Temperature
j. Allergies
k. Prescription
l. Diagnosis
3. Allow the clinic staff to access patient records.
a. Name
b. Age
c. Birthday
d. Address
e. Contact No.
f. Weight and Height
g. Blood Pressure
h. Pulse Rate
i. Temperature
j. Allergies
k. Prescription
5|Page
l. Diagnosis
4. Allow the doctor and clinic staff to make an appointment.
SIGNIFICANCE OF THE STUDY
The study aims to convert the traditional way of patient records into digital files
and easy access to patients' medical records.
Doctors and Nurses. With the help of the system, the accessibility of a patient's history
will help the doctors and nurses to come up with a prescription that is suited to the patient
(will not cause any allergic reactions).
Clinic Staff. The system helps the clinic staff track and keep the patient’s medical record.
Patient. The system will accelerate the process of finding the patient's history, allowing
the consultation to proceed without the need to sort through piles of paper to locate the
patient's file.
Future Researchers. The future researchers will benefit in this study as they can use it as
an additional reference for their study.
6|Page
SCOPE AND LIMITATION
SCOPE
The developers aim to develop a system that will ease the keeping and tracking of
patient data in small clinics that still use a paper-based method. The system consists of
software connected to a database that stores the patient's data and medical history. The
programming language that the developers plan to use is Java.
1. Software
It is a portable software application that can manage and track medical records for
patients.
2. Database
This serves as a way to store patients' information, such as their details and medical
history.
LIMITATION
1. This project is limited to small clinics that use paper-based records of
patients.
2. Only the doctors and clinic staff can access the software.
3. The system is for offline use.
7|Page
CONCEPTUAL THEORETICAL FRAMEWORK
Figure 1
In figure 1, the developers' perception of how the system will operate for the user
to convert the patient records into digital files. The admin, doctor, and staffs at the clinic
are the system's administrators, and they can only log in to the system.
The admin will be given an account to access the system and is required to provide
their contact number for the OTP. The clinic admin is the only one who can add, select
roles, update the user’s details, and archive its information from the user table.
8|Page
As for the doctors and staff, after they have been given an account by the admin,
they can log on to the system and will receive an OTP for security purposes. They will be
given different access to the system.
Figure 2
Figure 2 shows the input, process, and output. The input is the login credentials of
the admin, doctor, and clinic staff, OTP, and the patient's information through the system.
The process is to add, edit, and archive. The output is exported or printed patient record
and SMS Notifier.
9|Page
OPERATIONAL DEFINITION OF TERMS
For a better understanding of the study, the following terms are defined:
Admin - the person that provides clerical support to our managers and employees and
coordinates all daily
Appointment - an arrangement to meet someone at a particular time and place.
Computer-based - this is the application that only is based on the computer/PC
Database - storage of the data or information of the patient.
Short Messaging Service (SMS) - a messaging system that is most commonly used on
cell phones.
Digital Files -it is an electronic file stored in the computer
Notifier - A person or thing which notifies or provides notification.
OTP - is an automatically generated numeric or alphanumeric string of characters that
authenticates a user for a single transaction or login session.
Patient - a person receiving or registered to receive medical treatment.
SMS API - is a set of protocols and tools that allows software developers to integrate SMS
messaging functionality into their applications or websites.
10 | P a g e
CHAPTER II
REVIEW OF RELATED LITERATURE AND STUDIES
This chapter discusses the literature developers can use to help them create the
suggested system. This section provides traits and capabilities from recent studies that are
comparable to the suggested computer-based patient record.
With the advancement of technology, many industries have integrated its use as a
productivity tool. One of these industries is the medical industry. This integration now
leads to many health information systems (HISs) and electronic health records (EHR).
FOREIGN LITERATURE
ELECTRONIC HEALTH RECORDS
According to CMS.gov (2021), a digitized patient record is a digital copy of a
patient's medical record that is stored by a clinic or hospital. The data may include the
patient's demographic profile, evaluations, diagnoses, prescriptions, symptoms, histories
of medication, vaccination records, as well as the outcomes of lab tests and radiology
reports, may all be included in the data. The EHR can also directly or indirectly support
other care-related activities through various interfaces, such as quality control, outcomes
reporting, and evidence-based decision support.
11 | P a g e
CONVERTING FROM PAPER-BASED TO ELECTRONIC RECORD KEEPING
Even though electronic data is available, 75% of businesses will still rely on manual
data collection in 2020, according to Advantive (2019). Although manually implementing
quality and safety systems on paper may appear to be a cost-effective option, it is inefficient
and error-prone. Data collection mistakes can result in lost or deleted records, which can
lead to delays, missed opportunities, and dissatisfied employees. In addition, in accordance
with 21 CFR Part 11, the FDA requires electronic recordkeeping for the pharmaceutical,
medical device, and food and beverage industries to guarantee customer safety and
compliance. Manufacturers must effectively manage documentation and records regarding
traceability, recalls, corrective and preventive action (CAPA), and food safety audit
standards in order to comply with regulations and guarantee the safety of their customers.
In 2018, Pierce, MD noted that the transition from paper-based records to electronic
ones can be challenging for managers and employees alike. It is suggested that a gradual
strategy be formulated to alleviate this. Additionally, collaborating with software
developers can simplify the initially daunting process of converting paper documents into
electronic forms. It is possible to effectively implement the ideal solution and increase the
likelihood of success by seeking their guidance.
12 | P a g e
IMPACT OF ELECTRONIC HEALTH RECORDS ON INFORMATION PRACTICES
According to Kariotis et al (2022), the health record is an essential tool for
documenting and organizing information and plays a crucial role in modern healthcare,
particularly mental health care. When providing care to service users, medical workers rely
on health records for a variety of information practices like searching for, utilizing,
documenting, and sharing information. By enhancing information quality and accessibility,
EHRs are a significant tool for improving healthcare quality. EHRs, in any case,
additionally present new practices and work processes, for example, organized information
passage frames that can disrupt the assortment of story information. EHRs have many
advantages, but their global adoption has been more sluggish than in other health settings
for mental health care.
According to Yonwanda Bullock's article from 2021, clinics' financial performance
and sustainability can be negatively impacted if computerized accounting systems are not
implemented correctly. This is especially concerning given that the majority of workers in
the United States work for small businesses, but only 30% of them last for the long term,
and 50% fail within five years. A beauty salon successfully implemented a computerized
accounting system to address this issue and enhance its financial performance.
The article portrays a subjective different case research concentrates on the pre-
owned Davis' innovation reception hypothesis to examine the methodologies involved by
entrepreneurs of beauty parlors in Baltimore to embrace mechanized bookkeeping
13 | P a g e
frameworks and grow their tasks past five years. Through semi-structured interviews and
corporate records, the study gathered information from six beauty salon owners and
analyzed it thematically. There were four major themes found in the study: expansion of
the business, operation of a good accounting system, financial management with a good
accounting system, and computer education and expertise. According to the study, clinic
owners should immediately seek the assistance of financial professionals to establish
computerized accounting systems for their businesses. Positive effects on social
development and economic viability in local communities resulting from the small clinic
owners' potential to foster growth, enhance financial stability, and act as business mentors
for aspiring medical professionals.
UTILISATION OF ELECTRONIC HEALTH RECORDS FOR PUBLIC HEALTH
Dornan et al. (2019) state that in recent years, the use of electronic health records
(EHRs) in medical practice has significantly increased in recent years. EHR systems give
us a great chance to improve health surveillance and service delivery, which could lead to
better public health management and promotion. The majority of doctors, according to the
findings, use the information to look at the patient's overall condition, make clinical
decisions, and communicate with patients' care teams.
Errors cannot be avoided in the current manual healthcare delivery method. In the
dental consideration area, strategy development is critically expected to resolve this issue,
as stressed by Salazar (2019). Exact well-being data given by patients is vital for dental
14 | P a g e
clinicians, yet research shows that such data is misreported in around 15% to 30% of dental
records. To fill in these gaps, we need a healthcare system that works together. Policies
that make it easier to integrate dental and medical records can improve the quality of care
given to dental patients with underlying medical conditions.
The utilization of mobile personal health record (mPHR) systems has become
increasingly important in healthcare delivery as it has the potential to enhance healthcare
outcomes. According to Part et al (2023), patient volume, a younger patient age group, and
the proportion of inpatients and outpatients with cancer and hypertension were found to be
significantly associated with the adoption of mPHR systems by hospitals. Earlier studies
have also suggested that individuals with chronic diseases such as diabetes and
hypertension are more likely to adopt mPHR. However, some study findings were slightly
inconsistent and require further investigation, such as inpatients with hypertension and
diabetes. To promote the adoption of mPHR systems nationwide, many healthcare
organizations and government agencies are developing strategies. While the study's results
may not apply widely, they provide valuable information and recommendations for
decision-makers seeking to hasten the implementation of mPHR systems in hospitals.
15 | P a g e
LOCAL LITERATURE
HEALTH INFORMATION SYSTEM
A management information system (MIS) is a crucial tool for storing data,
according to Maguire (2019), who distinguishes between two types of it. The first type,
which requires using paper and a pen, is unreliable because it runs the risk of being
damaged and takes a long time to find information. The second type is computer-generated,
and it has become more common in the 21st century because it makes data management
easier and more efficient. This shift towards innovation is a reaction to the quick
development and arising issues confronting the MIS industry. Because of this, MIS has
grown in popularity in almost every industry, including finance, medicine, education,
manufacturing, business, and manufacturing. For instance, banks wouldn't be able to
process payments, supermarkets wouldn't be able to track transactions, and governments
wouldn't be able to meet people's needs.
BARRIERS AFFECTING THE ADOPTION OF ELECTRONIC MEDICAL

RECORDS IN THE PHILIPPINES
The healthcare system in the Philippines is attempting to determine the most
effective method for providing each Filipino with high-quality medical care. As a result,
technology plays a crucial role in giving the medical industry a chance to innovate and
adapt to the needs of healthcare. This technological advancement in healthcare centers
digitizes patients' medical records (R. Ebardo & N. Celis, 2019). However, some healthcare
facilities' adoption of healthcare technologies is influenced by a variety of factors.
16 | P a g e
As indicated by the paper composed By Ebardo and Celis, there are three (3) classes
or settings that partition these elements, Technology, Organization, and Environment, the
team likewise gave a potential method for resolving the issues relying upon their
classifications. Under the Technology context, the barriers that one medical care facility
may face, weak infrastructure, and poor interface design. By strengthening the vendor's
cooperation with healthcare providers, these obstacles can be overcome.
The organizational barriers are user resistance and unskilled IT staff, given that the
management influences these internal barriers, relevant interventions could include greater
compensation for the IT employees as well as enhanced resource allocation for training
medical professionals on the advantages of EMR technology. Last but not least, the
environmental barriers are privacy regulation compliance, and medical school orientation,
governmental entities should take into account a clear public policy and focused guidelines
specifically for EMRs to support the automation of EMR records. On the other hand, the
higher education sector needs to implement curriculum revision to incorporate
technologies in medical practice. To overcome such issues, the healthcare industry's
stakeholders should work cooperatively to maximize the advantages of electronic medical
records to improve and sustain the delivery of healthcare services.
17 | P a g e
ELECTRONIC MEDICAL RECORDS IN THE PHILIPPINES
The Community Health Information Tracking System (CHITS), as stated by the
Development Academy of the Philippines (2020), is a free, locally developed EMR system
in the Philippines. Reduced patient wait times, secure access to patient records, and
efficient data entry and storage are among its features. It makes it easier for health centers
and rural health units (RHUs) to schedule appointments, allocate resources, and provide
better services.
CHITS makes it possible for local health offices to create the necessary health
reports that are connected into the Department of Health's (DOH) official recording and
reporting system. In order to facilitate inter-health center integration, resource allocation,
and outbreak detection, the system provides up-to-date information from RHU on the
ground. Because CHITS is connected to offices of the Philippine Health Insurance
Corporation (PHIC) and the Department of Health (DOH), it makes it easier for DOH to
better monitor the administrative performance of local offices and health programs.
According to instructions, it has been electronically submitting claims to PHIC since 2016.
In 2004, CHITS began as a research project at the University of the Philippines
Manila (UP Manila) on computer-based information systems. At that point, it was just
being executed in two well-being places in Pasay City. By the end of 2010, fifty health
facilities across the nation, ranging from Batanes in the north to the Zamboanga Peninsula
in the south, had begun using CHITS for their government health facilities. Real-Time
18 | P a g e
Monitoring of Maternal, Child Health, and Governance Indicators (rCHITS), a tool
designed to improve health information system management in geographically
disadvantaged and isolated areas (GIDA), was added to CHITS in 2011. CHITS adopted
the more well-known Open Medical Records System (OpenMRS) as its new base system
in 2012. It also started using an LGU dashboard and a mobile reporting tool to better
collect, store, and analyze community health data. There were already 208 CHITS-using
local health facilities at the time. rCHITS was able to integrate a mobile midwife platform
in 2014 with the assistance of a non-governmental organization that extended funding for
Philippine government eHealth projects. This platform was able to capture aggregate
patient data at the barangay level and send patient alerts via SMS through Synchronized
Patient Alert. CHITS is used in a store-and-forward manner in the RxBox, a telemedicine
device for diagnosing common medical issues that is one of the UPM-NTHC's products.
19 | P a g e
CHAPTER III
TECHNICAL BACKGROUND
THE TECHNICALITY OF THE PROJECT
The researchers gathered all the relevant technologies that could possibly be used
in the proposed project, as the project is still ongoing. The researchers are still searching
for tools and software that can help them improve the development of the system.
The proposed project is a desktop application system with the ability to assist clinics
in storing, checking, and editing patient records without the need for the traditional method.
Because the project will be an IT-related study, some phrases or terminologies will be
understood solely by IT students/people in the IT business. Eclipse, MySQL, Java, Java
Swing XAMPP, PHP MyAdmin, and Figma are some of the terms used. The researchers
employ these terms to construct the project.
DETAILS OF THE TECHNOLOGY TO BE USED
For the desktop application to be created, the proponents used the software and
programming languages that are listed below:
● Eclipse - is a free development platform based on Java that is well-known for its
plugins, which enable programmers to develop and test code written in other
programming languages.
20 | P a g e
● JAVA – an object-oriented programming that is used to create software for a
variety of platforms.
● Java Swing - used to make window-based applications. It contains elements such
as a button, a scroll bar, a text field, and so on.
● MySQL – an open-source database management system that provides a database
for use in web applications
● XAMPP - a free cross-platform to create a local web server host and interpret
scripts written in PHP scripts.
● Figma – a web-based application that lets users collaborate to create a design for
user interface and an interactive prototype.
● PHPMyAdmin - a free platform written in PHP intended to handle the
administration of MySQL using an internet browser.
● SMS API - an SMS API, or SMS Application Programming Interface, is a set of
protocols and tools that allows software developers to integrate SMS messaging
functionality into their applications or websites.
HOW THE PROJECT WILL WORK
The Mary Angels Diagnostic Clinic is hoping to benefit from the computer-based
patient record system by having real-time access to patient records and appointment
schedules. This system will make it much simpler for the clinic doctor and staff to search
for and retrieve patient records as well as to add change and archive information.
Additionally, it reduced the risk of data loss.
21 | P a g e
Figure 3
The system has 3 users, the admin doctor, and the clinic staff. The admin
will be given an account to access the system, and is required to provide their contact
number for the OTP. The admin will be given an account to access the system and is
required to provide their contact number for the OTP. The clinic admin is the only one
who can add, select roles, update the user’s details, and archive its information from the
user table.
22 | P a g e
As for the doctors and staff, after they have been given an account by the admin, they can
log on to the system and will receive an OTP for security purposes. They will be given
different access to the system.
After logging in, the doctor or the staff can add, edit, and view patients' information;
the doctor or staff can also export a soft copy or print the records if the patient requests a
hard copy. Another feature was adding, editing, viewing, or removing sessions for follow-
up check-ups if needed, the day before the set appointment, the patient will receive an
automated message containing the scheduled follow-up check-up.
23 | P a g e
CHAPTER IV
METHODOLOGY
REQUIREMENT SPECIFICATIONS
The purpose of this document is to build a digitization system to manage traditional
documents from the clinic and to ease the processing management of their health
appointment. It provides possible ways to come up with a solution to a problem. The
proposed system must meet all the requirements and must be flexible enough for future
changes to be easily made. It has the following requirements:
● The system needs to keep records of patients.
● System needs follow-up appointments for the follow-up sessions of patients.
● System needs to add, update, and print the record.
● System needs SMS notification for the patient’s appointment.
FISHBONE DIAGRAM
Figure 4
Fishbone Diagram
24 | P a g e
In this figure, the researchers investigate how fishbone diagrams can be used to
show the entirety of the body of data with numerous outcomes.
The fishbone diagram will assist readers in understanding the conceptualization of
the review and complex findings in a straightforward, concise, and understandable manner.
Finding the optimal way to convey the risks and advantages of digitizing the traditional
patient record is crucial since making informed decisions requires an accurate
understanding of the positive and negative impacts of the project.
FUNCTIONAL DECOMPOSITION DIAGRAM
The functional decomposition diagram below displays the process and performance
of the system. It helps the developers to properly create a system by identifying each
component that needs to perform a certain function. By constructing a functional
decomposition diagram. Developers can easily assess, understand, and handle issues.
25 | P a g e
Figure 5
Functional Decomposition Diagram
TECHNICAL FEASIBILITY
Table 1
26 | P a g e
Table 2
RELEVANCE OF THE TECHNOLOGIES
27 | P a g e
SCHEDULE FEASIBILITY
A project timeline is given to illustrate and measure the time required to conduct
this study. It provides an overview of the schedule of the project
Project Timeline
Figure 6
Project Timeline (2022)
28 | P a g e
Figure 7
Project Timeline (2023)
ECONOMIC FEASIBILITY
The developers should consider the financial aspects of the project. Although it may
technically be possible to develop a specific desktop application, it may require a fair
amount of investment and offer fewer benefits. The economic feasibility of the proposed
system is analyzed to determine the possible expenses associated with the Digitized Patient
Record System's development.
29 | P a g e
Cost and Benefit Analysis
Table 3
This table shows the breakdown of expenses for the system accomplishment
As for the breakdown of the cost, Laptop takes the biggest part which comes to
₱26,000 because it is being used to create the system. Followed by SQL Database with a
cost of ₱8,000. Next is the Internet with a cost of ₱2,000 for a fast Internet connection and
browsing. And SMS API takes the lowest part with a cost of ₱200. As we categorize the
cost or the expenses of the project, we can able to accomplish the system from its assumed
timeline schedule and we are able to meet the expected output.
30 | P a g e
REQUIREMENTS MODELING
Figure 8
Requirements Modeling
Figure 8 shows the input, process, and output. The input is the login credentials of
the admin, doctor, and clinic staff, OTP and the patient's information through the system.
The process is to add, edit, and archive. The output is exported or printed patient record
and SMS Notifier.
Data and Process Modeling
These are used to digitize the traditional patient record and transform it into a
simple, clear presentation of the data process during the system development.
The Digitizing Patients Record was explained by the proponents using an array of
graphic techniques that they had examined. The context diagram, the data flow diagram
31 | P a g e
(DFD), and the system and program flow diagram are the diagrams that are used for data
and process modeling.
Context Diagram
Figure 9
Context Diagram
Figure 9 Shows the entire system's process and interaction to the user is depicted
in the context diagram, which may be seen in the image up above. The entire system's
workflow is displayed, starting with administration and moving through the database and
system software.
32 | P a g e
Data Flow Diagram
The Level 1 Data Flow Diagram is shown in the diagrams below. Context Diagram
of Proposed System Process in an Exploded Diagram. The process of digitizing patient
records and the interactions between the various entities are depicted in this diagram.
Figure 10
Data Flow Diagram
The data flow diagram above provides a clear overview of the entire system
program and how it interacts with the patient, doctor, clinic staff, and database. The
patient's information and appointment will be stored by the computer and loaded into the
database so that it can be read. The doctor and clinic staff will update the database and add
new information, while also adding records and reports about the patient's data.
33 | P a g e
SYSTEM / PROGRAM FLOWCHART
System flowcharts show how data is transferred throughout a system and how decisions
are made to direct events. Symbols are used to show this. To show how data is used and
saved, these are linked.
Figure 11
System Flow Chart (Admin)
34 | P a g e
Figure 12
System Flow Chart (Staff)
35 | P a g e
Figure 13
System Flow Chart (Doctor)
OBJECT MODELING
Approach to software development and modeling. It is a technique for developing
object-oriented programs and supporting object-oriented systems. It was created as a
software development tactic.
36 | P a g e
USE CASE DIAGRAM
Figure 14
Use Case Diagram
The connection between the clinic staff and the patient and the system application
is shown in the use case diagram. The doctor/nurse will store the patient’s information in
the database. The administrative tasks include adding and updating the patient's
information in the database, as indicated above. The user or patient will have all the
information needed for the admin to record it. the patient will need their information and
countenance to proceed with the appointing schedule.
37 | P a g e
CLASS DIAGRAM
Figure 15
Class Diagram
The Class Diagram shows how our system came to be; it is made up of 5 classes
with separate divisions. This would be crucial in demonstrating how the modeling process
flows. As presented above the illustration, the researchers let the clinic staffs process the
registration of the patient’s information and store it in the DB Server, which also allows
38 | P a g e
them to access the data, enabling the server to produce the digitized information for the
patients.
SEQUENCE DIAGRAM
Figure 16
Sequence Diagram
Figure 16 is the sequence diagram of the doctor's view for Digitizing the Patient
Record System. A sequence diagram shows the object interactions arranged in a time
sequence.
39 | P a g e
Figure 17
Clinic Staff
40 | P a g e
Figure 18
Admin
RISK ASSESSMENT/ANALYSIS
One potential risk is the possibility of data breaches and security breaches. As the
system stores sensitive patient information electronically, there is a risk of this information
being accessed by unauthorized individuals or organizations. This can result in identity
41 | P a g e
theft, financial fraud, or other forms of harm to patients. Another risk associated with the
system is the potential for errors or inaccuracies in the data. While electronic health records
are designed to reduce errors, they are not foolproof. There is a risk that errors could occur
during data entry, coding, or interpretation, leading to incorrect treatment.
DESIGN OF SOFTWARE SYSTEMS PRODUCTS AND / OR PROCESSES
This section defines the design process of the computer-based patient record
system. The proponents discussed the inputs, processes, and outputs that were included in
the process for creating a solution to the current system at Mary Angels Diagnostic Clinic.
It also illustrates the different interfaces for each system component.
OUTPUT AND USER-INTERFACE DESIGN
The developer developed a simple design to allow the user to understand and
operate the system. The clinic's traditional method of handling patient records is addressed
by the design of Digitizing Patients Records, which is primarily meant for patients who
would schedule an appointment there. The design concept should benefit the clinic and the
interface should be simple to use.
42 | P a g e
Forms
The following figures are screenshots of all the forms used in the system. The
figures are labeled for clarity for readers and researchers. A brief explanation will be
discussed following each screenshot.
Figure 19
Login Form
Figure 19 is the login form of Mary Angels Diagnostic Clinic. Users will choose if
they will login as admin, doctor or staff. Users must fill out the login form by entering their
43 | P a g e
username and password. In addition, a ‘Login’ button for users to click will check their
login credentials for the security of the system.
Figure 20
Add Doctor Form
Figure 20 is the add doctor form of Mary Angels Diagnostic Clinic. After logging
on to the admin’s account, the admin can add a doctor. This will require the doctor’s name,
contact number, username, and password. It will also require and OTP to verify the doctor’s
number.
44 | P a g e
Figure 21
Add Staff Form
Figure 21 is the form for adding staff. Admin users can add staff, and it will require
the staff’s name, contact number, username, and password. It will also require an OTP to
verify the staff’s contact details.
45 | P a g e
Figure 22
Edit Doctor Account
Figure 22 is the form for editing the doctor’s account. Whenever the doctor forgets
his/her account they can request a password/email reset to the admin. Admin can edit
doctor’s information.
46 | P a g e
Figure 23
Edit Staff Account Form
Figure 23 is the form for editing the clinic staff’s account. Whenever the staff
forgets his/her account they can request a password/email reset to the admin. Admin can
edit doctor’s information.
47 | P a g e
Figure 24
Add Session Form
Figure 24 is the add patients’ session form. In this form, the clinic staff can schedule
patients’ next session which will be sent through SMS notification.
48 | P a g e
Figure 25
Edit Session Info
Figure 25 is the edit patients’ session form. In this form, the clinic staff can edit the
schedule patients’ next session if the patient decides to reschedule it.
49 | P a g e
Figure 26
Add Patient Info
Figure 26 is the add patient form. In this form, the clinic staff can add patients’
personal information by filling up the provided information.
50 | P a g e
Figure 27
Edit Patient Info
Figure 27 is the edit patients’ information form. In this form, the clinic staff can
edit patients’ personal information if patients decide to update their information.
51 | P a g e
Figure 28
Check-up Form
52 | P a g e
Figure 29
Figure 28 and Figure 29 is the check-up form. In this form, the clinic doctor can
add laboratory testing results, diagnoses, and prescriptions to the patients.
53 | P a g e
Reports
The digitized patient record system generates reports for a list of appointments and
patients. A brief explanation will be discussed following each screenshot.
Figure 30
Doctor’s List
Figure 30 is the Doctor’s List of Mary Angels Diagnostic Clinic. The clinic admin
can view the list of doctors' accounts registered in the clinic. The admin can also edit or
archive a certain doctor.
54 | P a g e
Figure 31
Staff List
Figure 31 is the Staff List of Mary Angels Diagnostic Clinic. The clinic admin can
view the list of staff accounts registered in the clinic. The admin can also edit or archive a
certain staff.
55 | P a g e
Figure 32
Session List
Figure 32 is the Session List of Mary Angels Diagnostic Clinic. The clinic staff can
view the list of sessions that have been scheduled at the clinic. The staff can also edit or
remove a certain session.
56 | P a g e
Figure 33
Patient List
Figure 33 is the Patient List of Mary Angels Diagnostic Clinic. The clinic staff can
view the list of patients that have been admitted to the clinic. The staff can also edit a
patient’s personal information.
57 | P a g e
Figure 34
Medical Records
Figure 34 shows the Medical Records of Mary Angels Diagnostic Clinic. The clinic
doctor can view the list of medical record that has been stored in the clinic’s database. The
doctor can also issue a medical certificate and print a medical record if the patient needs it.
58 | P a g e
Figure 35
Prescription
Figure 35 shows the list of the given prescriptions of Mary Angels Diagnostic
Clinic. The clinic doctor can view the list of prescriptions that have been given to the
patients. The doctor can also print the prescription to avoid errors because of bad
handwriting.
59 | P a g e
DATA DESIGN
The process of creating a detailed data model for a database. The physical storage
properties and every logical and physical design option required to create a design in the
data set that can then be used to create a database are all contained in this data model.
Data Dictionary
A data dictionary is a set of names, definitions, and attributes about the data
elements used in the Digitized Patient Record System. Mary Angels Diagnostic Clinic
database has three (12) tables, namely, admin, archdoc, archstaff, diagnosis, doctor, lab
sample, labtest, medhist, patientinfo, prescription, session, and staff.
Table 4
60 | P a g e
Table 5
Table 6
61 | P a g e
Table 7
Table 8
62 | P a g e
Table 9
Table 10
63 | P a g e
Table 11
Table 12
64 | P a g e
65 | P a g e
Table 13
66 | P a g e
Table 14
Table 15
67 | P a g e
SECURITY
The "Data Privacy Act of 2012" in the Philippines, also known as Republic Act No.
10173, will be compiled with and implemented by the Digitizing Patient Record System.
In terms of security, due to the constant changes in the world of technology that cause
variability in exposure and uncertain impact on the system and the user’s safety, we have
implemented the OTP security that acts as the wall in the user login, edit users, and add
users.
DEVELOPMENT
Software, Hardware, and Program Requirements for the Application
Implementation.
SOFTWARE SPECIFICATION
Software specification refers to the software utilized in constructing an application-
based Digitizing Patient Record System employing Java It outlines the system's operation
and details the user interaction that the program must enable. The list of specific software
utilized in the system, together with its specifications, may be seen below:
68 | P a g e
HARDWARE SPECIFICATION
Hardware specifications are system requirements that include suggested electronic
components for system development.
69 | P a g e
Table 16
Table 17
PROGRAM SPECIFICATION
The proposed system has the following specifications:
● The system can keep records of patients.
● The system has follow-up appointments for the scheduling of patients.
● System can edit, update, delete, and print the record.
● System can send SMS notifications for the patient’s appointment.
70 | P a g e
Deployment Diagram
Figure 36
Deployment Diagram
This figure shows the system application of Digitizing Patient Record System
deployment process. It has a workstation pc on the doctor and clinic staff Server where it
can input, manage, manage, and view patient records within the desktop application that is
stored in the MySQL database (data). The database server serves as the bridge between the
desktop application and Desktop Server for it has to link. The execution environment is the
minimum requirement of the Windows version, Windows 7, and the desktop application
deploy the resources for executing the Java package. Overall, this is the cycle that happens
to the user of the desktop application for the clinic and is able to use it afterward.
71 | P a g e
Test Plan
A test plan was created by the developers for the proposed system's testing. The
part of the system that will be tested, the purpose of that page, the expected result, and the
actual test result are all included in the proposed system's test plan. The system's
capabilities were examined and evaluated by the developers.
TESTING
Unit Testing
Table 18
Test Case Type Test Steps Expected Result Status
Application ● Logging into ● successfully Passed

Functionality the application logged in to the
as an admin application as an
admin
Passed
● Creating a ● successfully
new user created new user
account account Passed
● Adding patient ● successfully

information added patient
information Passed
● Editing patient
information ● successfully
edited patient Passed
information
● Printing ● successfully
patient printed patient Passed
information information
● Searching ● successfully
72 | P a g e
patient searched a patient Passed
● Adding patient ● successfully

session added a patient Passed
session
● Editing patient
appointment ● successfully
edited a patient Passed
● Removing appointment
patient session ● successfully
● Searching remove a session Passed
session ● successfully
searched for a
● Sending sms session Passed
notification to ● successfully sent
the patients an sms
notification to Passed
patients
Usability Check if the application Successfully run Passed

runs without glitches without errors.
and errors
73 | P a g e
Integration Testing
Table 19
74 | P a g e
Module 1
Table 20
75 | P a g e
Table 21
Table 22
Test Scenario
Table 23
76 | P a g e
Module 2
Table 24
Table 25
Table 26
77 | P a g e
Test Scenario
Table 27
Module 3
Table 28
78 | P a g e
Table 29
Table 30
S# Prerequisites Test Data
1 add patient ● patient name =

Raymond Adornado
● age =20
● sex = m
● weight = 50kg
● height = 150cm
● civilstatus = single
● birthdate = 2000-07-07
● contactnum =
09123456789
● address = Mandaluyong
● bloodpressure =
140/90mmHg
● temperature = 35°C
● pulserate = 60bpm
● allergies = none
● midhist = none
● diagnosis = Fever
● prescription =
paracetamol
2 edit patient’s record ● patient name =
79 | P a g e
Raymond Adornado
● age =21
● sex = m
● weight = 50kg
● height = 150cm
● civilstatus = single
● birthdate = 2000-07-07
● contactnum =
09123456789
● address = Mandaluyong
● bloodpressure =
140/90mmHg
● temperature = 37°C
● pulserate = 60bpm
● allergies = none
● midhist = none
● diagnosis = Fever
● prescription =
paracetamol
3 delete patient’s record ● delete button
4 add appointment ● patient name =

Raymond Adornado
● purpose = follow-up
check-up
● contactnum =
09123456789
● time = 11:30
● date = 2022-11-30
5 edit appointment ● patient name =

Raymond Adornado
● purpose = follow-up
check-up
● contactnum =
09123456789
● time = 11:30
● date = 2022-11-28
6 delete appointment ● delete button
80 | P a g e
7 search patient ● patient name =

Raymond Adornado
8 search appointment ● time = 11:30

● date = 2022-11-30
Test Scenario
Table 31
Step # Step Details Expected Actual Pass / Fail /

Results Results Not executed /
Suspended
1 Add patient’s Patient’s As Pass

information and click data added to expected
the add button the table
2 Edit patient’s Patient’s As Pass

information and click data is expected
the edit button updated in
the table
3 Delete patient’s Patient’s As Pass

information and click data is expected
the add button deleted from
the table
4 Add patient’s Patient’s As Pass

appointment and click appointment expected
the add button is added to
the
appointment
table
5 Edit patient’s Patient’s As Pass

appointment and click appointment expected
the edit button is updated in
81 | P a g e
table
6 Remove the patient’s Patient’s As Pass

appointment and click session is expected
the add button removed
from the
table
7 Enter the patient’s Shows the As Pass

name and click the patient’s expected
search button record
8 Click the calendar and Shows the As Pass

choose the time and chosen date expected
date you want to show and time of
appointment
Compatibility Testing
The table below shows the results of the system's compatibility testing with various
hardware and software.
Table 32
82 | P a g e
Performance, Load, and Stress Testing
Table 33
83 | P a g e
System Testing
Table 34
84 | P a g e
PROGRAM PROPERTIES
85 | P a g e
86 | P a g e
FUNCTION PROPERTIES
The table below shows the function of each property of the proposed system:
Table 35
87 | P a g e
IMPLEMENTATION PLAN
Implementation Checklist
Table 36
88 | P a g e
Implementation Contingency
Table 37
89 | P a g e
Infrastructure/Deployment
For the Infrastructure/Deployment, doctor and clinic staff of Mary Angles
Diagnostic Clinic will be users of the system which can be installed in the PC clinic. Users
are not required to have internet because the system is made is offline and it Desktop
application. The system has some feature like they can input and managing the data also it
has an appointment feature where the user can set follow-up appointment with the patient
and notifies the patient via SMS notification.
The main function of the system is to transfer a patient's medical documents into
digital documents. They are digital patient records that authorized users can access in real-
time.
90 | P a g e
CHAPTER V
CONCLUSION AND RECOMMENDATION
CONCLUSION
A Patient Record System is designed and developed by the proponents to transfer
traditional patient records into digital form at Mary Angels Diagnostic Clinic. This
application system manages patient records and uses MySQL to store information in a
database. It uses Java and Java Swing to provide a user-friendly graphical interface and
display data to its user. The system also has a follow-up appointment system that doctors
and clinic staff can access through their PC clinic, and it has an SMS API notifier that
notifies patients when their scheduled follow-up appointment is near.
The proponents gather all the information needed by the clinic to build the proposed
system and conduct an online interview with Mrs. Corazon Carancite, the clinic owner,
regarding the clinic's system, Mary Angels Diagnostic Clinic. They found out that the clinic
still uses paper records for their patient files. The proponents came up with a solution and
developed this study. They analyzed and gathered data to identify the problems to be solved
and the clinic's needs. The proponents created the system design that has features and
functions based on the information needed by Mrs. Carnacite. The proponents decided to
use MySQL, Java, and other tools to create and maintain the clinic's information
management system.
91 | P a g e
After the researchers came up with the design and features of the system, they began
to develop a system in which the researchers programmed the system's functionalities and
created a database to store all the records of the diagnostic clinic patients. They run the
system and test it to see if it meets the requirements of the clinic. Proponents conducted
testing methods to ensure the system's functionality and quality. They used software testing
to test the accuracy and effectiveness of the Digitizing Patient Record System in storing
records. They included the doctor and the clinic staff in the testing phase so they could see
if it fits the clinic's needs. The researchers guided the doctor and clinic staff on how to use
and run the system.
The following are the functionalities of Digitizing the Patient Record System:
● Login - The system only allows authorized personnel to access the system. The
users need to specify their username, password, and assigned role. After clicking
the button, the system will check their login credentials for security purposes.
● Appointments - The assistant of the clinic can add, remove and update the follow-
up appointment of patients.
● Patients - Doctors can access the patients’ table, wherein they can add, edit, and
print the patient’s information. They must provide all the necessary details like the
patient’s personal information.
● Admin - The admin has the right to add, edit, and archive users.
92 | P a g e
● Doctor - The doctor has access to the medical records of the patients. The doctor
can add diagnosis, prescription, laboratory reports and can also print the patient’s
medical record.
● Staff - The staff has the access to add and edit patient information. The staff can
also schedule or update the patient's next session.
● OTP - The system has a one-time password for user verification.
● SMS Notifier - The system can notify patients through SMS.
RECOMMENDATION
For further recommendations to the Mary Angles Diagnostic Clinic;
● It is advised to the clinic to expand the system online if the clinic is expanding or
branching to other places to easily transfer the data to another clinic branch.
● Clinic billings could be added as a new feature to the system.
● Clinic is advised to make a website of their clinic to know more about clinic
information.
● Patients can set initial appointments in the system.
● Clinic is advised to make an Android / IOS Application to easily communicate with
the patient.
93 | P a g e
REFERENCES
Electronic Health Records | CMS. (n.d.). https://www.cms.gov/Medicare/E-
Health/EHealthRecords
Prictor, M., & Gray, K. (2022). Impact of Electronic Health Records on Information
Practices in Mental Health Contexts: Scoping Review. Journal of Medical
Internet Research, 24(5), e30405. https://doi.org/10.2196/30405
Dornan, L., Pinyopornpanish, K., Jiraporncharoen, W., Hashmi, A., Dejkriengkraikul, N.,
& Angkurawaranon, C. (2019). Utilisation of Electronic Health Records for
Public Health in Asia: A Review of Success Factors and Potential Challenges.
BioMed Research International, 2019, 1–9. https://doi.org/10.1155/2019/7341841
Ebardo, R., & Celis, N. J. (2019). Barriers to the Adoption of Electronic Medical Records
in Select Philippine Hospitals. https://doi.org/10.1145/3330482.3330503
What Is a Data Dictionary? | UC Merced Library. (n.d.).
https://library.ucmerced.edu/data-
dictionaries#:~:text=A%20Data%20Dictionary%20is%20a,part%20of%20a%20r
esearch%20project
Bullock, Y. (n.d.). Strategies Used to Transition from Manual to Computerized
Accounting in Small Businesses. ScholarWorks.
https://scholarworks.waldenu.edu/dissertations/10027/
94 | P a g e
Manual Data Processing: The Secrets of Automation. (n.d.).
https://www.solvexia.com/blog/manual-data-processing-the-secrets-of-automation
Advantive. (2023, March 16). 4 Steps to Convert from Paper-Based to Electronic Record
Keeping | Advantive. Advantive. https://www.infinityqs.com/blog/january-
2019/4-steps-to-convert-from-paper-based-to-electronic
View of Health information system of St. Paul University Philippines. (n.d.).
https://ojs.aaresearchindex.com/index.php/spuprd/article/view/429/81
Adibi, S., Li, M., De Los Reyes-Gavilán, C. G., Seferovic, D., Kookal, K. K., Holland, J.
N., Walji, M. F., & Farach-Carson, M. C. (2020). Medical and Dental Electronic
Health Record Reporting Discrepancies in Integrated Patient Care. JDR Clinical
and Translational Research, 5(3), 278–283.
https://doi.org/10.1177/2380084419879387
Park, Y., Park, H., Lee, J. M., & Choi, B. K. (2023). Hospitals’ Adoption of Mobile-
Based Personal Health Record Systems and Patients’ Characteristics: A Cross-
Sectional Study Analyzing National Healthcare Big Data. NQUIRY: The Journal
of Health Care Organization, Provision, and Financing, 60, 004695802311608.
https://doi.org/10.1177/00469580231160892
Advantive. (2023b, March 16). 4 Steps to Convert from Paper-Based to Electronic
Record Keeping | Advantive. Advantive. https://www.advantive.com/blog/4-steps-
to-convert-from-paper-based-to-electronic-record-keeping/
95 | P a g e
Manual Data Processing: The Secrets of Automation. (n.d.-b).
https://www.solvexia.com/blog/manual-data-processing-the-secrets-of-automation
Admin. (2021, June 27). Community Health Information Tracking System (CHITS) -
DAP. DAP. https://coe-psp.dap.edu.ph/compendium-innovation/community-
health-information-tracking-system-chits-2/
96 | P a g e
APPENDICES
97 | P a g e
Relevant Source Codes

1.0. LOGIN
package AdminControl;
import java.awt.Color;
import java.awt.EventQueue;
import java.awt.Font;
import java.awt.event.FocusAdapter;
import java.awt.event.FocusEvent;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Random;
import javax.swing.ImageIcon;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JOptionPane;
import javax.swing.JPanel;
import javax.swing.JPasswordField;
import javax.swing.JTextField;
import javax.swing.SwingConstants;
import javax.swing.Timer;
import javax.swing.border.LineBorder;
import com.twilio.Twilio;
import com.twilio.rest.api.v2010.account.Message;
import com.twilio.type.PhoneNumber;
import javax.swing.JComboBox;
import javax.swing.JCheckBox;
@SuppressWarnings("serial")
public class Login extends JFrame {
private JPanel contentPane;
private JTextField username;
private JPasswordField password;
private JTextField oTP;
private int otp;
private Timer timer;
98 | P a g e
private String ACCOUNT_SID = "ACc1f9454af11d0bf1890b7813b6099589";

private String AUTH_TOKEN = "7ada8ec6153572e0eae5ebacf24f7d6f";
private String TWILIO_NUMBER = "+12545664427";
private JCheckBox showPass;
/**
* Launch the application.
*/
public static void main(String[] args) {
EventQueue.invokeLater(new Runnable() {
public void run() {
try {
Login frame = new Login();
frame.setVisible(true);
} catch (Exception e) {
e.printStackTrace();
}
}
});
}
/**
* Create the frame.
*/
public Login() {
setUndecorated(true);
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
setBounds(100, 100, 630, 400);
contentPane = new JPanel();
contentPane.setBackground(new Color(232, 252, 255));
contentPane.setBorder(null);
setContentPane(contentPane);
contentPane.setLayout(null);
JPanel panel = new JPanel();

panel.setBorder(new LineBorder(new Color(0, 0, 0)));
panel.setBackground(new Color(232, 252, 255));
panel.setBounds(338, 137, 224, 40);
contentPane.add(panel);
panel.setLayout(null);
JComboBox<String> user = new JComboBox<String>();
99 | P a g e
user.setFont(new Font("Segoe UI Semibold", Font.PLAIN, 20));

user.setBounds(338, 77, 189, 40);
user.addItem("Admin");
user.addItem("Doctor");
user.addItem("Staff");
contentPane.add(user);
username = new JTextField();

username.setBackground(new Color(232, 252, 255));
username.addFocusListener(new FocusAdapter() {
@Override
public void focusGained(FocusEvent e) {
if(username.getText().equals("Username")) {
username.setText("");
}
else {
username.selectAll();
}
}
@Override
public void focusLost(FocusEvent e) {
if(username.getText().equals("")) {
username.setText("Username");
}
}
});
username.setBorder(null);
username.setFont(new Font("Segoe UI Emoji", Font.PLAIN, 20));
username.setText("Username");
username.setBounds(10, 11, 204, 18);
panel.add(username);
username.setColumns(10);
JPanel panel_1 = new JPanel();

panel_1.setBorder(new LineBorder(new Color(0, 0, 0)));
panel_1.setLayout(null);
panel_1.setBackground(new Color(232, 252, 255));
panel_1.setBounds(338, 198, 225, 40);
contentPane.add(panel_1);
100 | P a g e
password = new JPasswordField();

password.setBackground(new Color(232, 252, 255));
password.addFocusListener(new FocusAdapter() {
@SuppressWarnings("deprecation")
@Override
if(password.getText().equals("Password")) {
password.setText("");
}
else {
password.selectAll();
}
}
@Override
if(password.getText().equals("")) {
password.setText("Password");
}
}
});
password.setBorder(null);
password.setText("Password");
password.setFont(new Font("Segoe UI Emoji", Font.PLAIN, 20));
password.setBounds(10, 11, 177, 24);
panel_1.add(password);
showPass = new JCheckBox("");

showPass.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent e) {
if (showPass.isSelected()) {
password.setEchoChar((char) 0);
} else {
password.setEchoChar('●');
}
}
});
showPass.setBounds(193, 11, 26, 21);
101 | P a g e
panel_1.add(showPass);
JPanel panel_send = new JPanel();

panel_send.addMouseListener(new
PanelButtonMouseAdapter(panel_send) {
@Override
public void mouseClicked(MouseEvent e) {
otp = new Random().nextInt(899999)+100000;
String User = username.getText();
String getUser = (String) user.getSelectedItem();
panel_send.setEnabled(false);
panel_send.setBackground(new Color(255, 0, 0));
timer = new Timer(15000, new ActionListener() {
@Override
public void actionPerformed(ActionEvent e) {
panel_send.setEnabled(true);
timer.stop();
}
});
timer.setRepeats(false);
timer.start();
if(getUser.equals("Admin")) {
try {
Class.forName("com.mysql.jdbc.Driver");
Connection conn=
DriverManager.getConnection("jdbc:mysql://localhost:3306/maryangels", "root", "");
String sql = "Select * from admin Where
username = '"+User+"'";
Statement sta = conn.createStatement();
ResultSet rs= sta.executeQuery(sql);
if(rs.next()) {
String connum
=rs.getString("contact");
Twilio.init(ACCOUNT_SID,
AUTH_TOKEN);
Message message = Message.creator(new
PhoneNumber(connum), new PhoneNumber(TWILIO_NUMBER),
"Your OTP is "+ otp +"." ).create();
}else {
JOptionPane.showMessageDialog(null,"username doesn't exist!!");
102 | P a g e
}
conn.close();
}catch(Exception exc) {
JOptionPane.showMessageDialog(null,
exc);
}
}else if(getUser.equals("Doctor")) {
try {
Connection conn=
String sql = "Select * from doctor Where
if(rs.next()) {
String connum
AUTH_TOKEN);
}else {

}
conn.close();
exc);
}
}else if(getUser.equals("Staff")) {
try {
Connection conn=
String sql = "Select * from staff Where
if(rs.next()) {
103 | P a g e
String connum
AUTH_TOKEN);
}else {

}
conn.close();
exc);
}
}
}
});
panel_send.setBorder(new LineBorder(new Color(0, 0, 0), 2));
panel_send.setBounds(483, 256, 88, 40);
contentPane.add(panel_send);
panel_send.setLayout(null);
JLabel lblNewLabel_1_2 = new JLabel("Send");

lblNewLabel_1_2.setHorizontalAlignment(SwingConstants.CENTER);
lblNewLabel_1_2.setForeground(Color.WHITE);
lblNewLabel_1_2.setFont(new Font("Segoe UI Black", Font.PLAIN, 23));
lblNewLabel_1_2.setBounds(10, 10, 69, 18);
panel_send.add(lblNewLabel_1_2);

panel_3.setBorder(new LineBorder(new Color(0, 0, 0)));
panel_3.setBounds(338, 256, 134, 40);
oTP = new JTextField();

oTP.setText("OTP");
oTP.setFont(new Font("Segoe UI Emoji", Font.PLAIN, 15));
104 | P a g e
oTP.addFocusListener(new FocusAdapter() {
@Override
if(oTP.getText().equals("OTP")) {
oTP.setText("");
}
else {
oTP.selectAll();
}
}
@Override
if(oTP.getText().equals("")) {
oTP.setText("OTP");
}
}
});
oTP.setColumns(10);
oTP.setBorder(null);
oTP.setBackground(new Color(232, 252, 255));
oTP.setBounds(10, 11, 103, 18);
panel_3.add(oTP);
setLocationRelativeTo(null);
JPanel panel_login = new JPanel();

panel_login.addMouseListener(new
PanelButtonMouseAdapter(panel_login) {
@Override
String User=username.getText();
String pass=password.getText();
String text = oTP.getText();
String getUser = (String) user.getSelectedItem();
if(text.equals("OTP")) {
text = null;
}
int confOTP= Integer.parseInt(text);
if(User.equals("")) {
105 | P a g e
JOptionPane.showMessageDialog(null,"Username
can't be empty!!","Login Error", JOptionPane.ERROR_MESSAGE);
}else{
if(pass.equals("")) {
JOptionPane.showMessageDialog(null,"Password can't be empty!!","Login

Error", JOptionPane.ERROR_MESSAGE);
}else {
if(confOTP != otp) {
JOptionPane.showMessageDialog(null,"OTP is incorrect!!","Login Error",

JOptionPane.ERROR_MESSAGE);
}else {
if(getUser.equals("Admin")) {
try {
Connection conn=
Statement sta =
conn.createStatement();
String sql =
"SELECT * from admin WHERE username= '"+ User +"' and password='"+ pass +"'";
ResultSet rs =
sta.executeQuery(sql);
if(rs.next()) {
JOptionPane.showMessageDialog(null,"Login Successfully...");
adminDB
dashboard= new adminDB();
setVisible(false);
dashboard.setVisible(true);
}else {
JOptionPane.showMessageDialog(null,"Invalid Username or Password","Login

Failed!", JOptionPane.ERROR_MESSAGE);
}conn.close();
JOptionPane.showMessageDialog(null, exc);
106 | P a g e
};
}else if(getUser.equals("Doctor")) {
try {
Connection conn=
Statement sta =
String sql =
"SELECT * from doctor WHERE username= '"+ User +"' and password='"+ pass +"'";
ResultSet rs =
if(rs.next()) {
doctorDB
dashboard= new doctorDB();
setVisible(false);
}else {

}conn.close();
};
}else if(getUser.equals("Staff")) {
try {
Connection conn=
Statement sta =
String sql =
"SELECT * from staff WHERE username= '"+ User +"' and password='"+ pass +"'";
107 | P a g e
ResultSet rs =
if(rs.next()) {
staffDB
dashboard= new staffDB();
setVisible(false);
}else {

}conn.close();
};
}
}
}
}
}
});
panel_login.setBorder(new LineBorder(new Color(0, 0, 0), 2));

panel_login.setBackground(new Color(0, 160, 152));
panel_login.setBounds(309, 306, 253, 40);
contentPane.add(panel_login);
panel_login.setLayout(null);
JLabel lblNewLabel_1 = new JLabel("LOGIN");

lblNewLabel_1.setForeground(new Color(255, 255, 255));
lblNewLabel_1.setFont(new Font("Segoe UI Black", Font.PLAIN, 24));
lblNewLabel_1.setHorizontalAlignment(SwingConstants.CENTER);
lblNewLabel_1.setBounds(54, 11, 141, 18);
panel_login.add(lblNewLabel_1);
JLabel lblx = new JLabel("X");

lblx.addMouseListener(new MouseAdapter() {
108 | P a g e
@Override
if(JOptionPane.showConfirmDialog(null, "Are you sure
you want to close this
application?","Confirmation",JOptionPane.YES_NO_OPTION)==0)
Login.this.dispose();
}
@Override
public void mouseEntered(MouseEvent e) {
lblx.setForeground(Color.RED);
}
@Override
public void mouseExited(MouseEvent e) {
lblx.setForeground(Color.black);
}
});
lblx.setVerticalAlignment(SwingConstants.BOTTOM);
lblx.setHorizontalAlignment(SwingConstants.TRAILING);
lblx.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lblx.setBounds(589, 0, 31, 28);
contentPane.add(lblx);

panel_2.setBounds(0, 0, 253, 400);
JLabel lblNewLabel = new JLabel("");

lblNewLabel.setBounds(77, 144, 100, 100);
lblNewLabel.setIcon(new
ImageIcon(Login.class.getResource("/res/marylogo 100px.png")));
panel_2.add(lblNewLabel);
JLabel lblNewLabel_2 = new JLabel("LOGIN");

contentPane.add(lblNewLabel_2);
JLabel lblNewLabel_3 = new JLabel("");
109 | P a g e

contentPane.add(lblNewLabel_3);
lblNewLabel_3.setIcon(new
ImageIcon(Login.class.getResource("/res/person.png")));
JLabel iconpassword = new JLabel("");

iconpassword.setBounds(291, 198, 61, 40);
contentPane.add(iconpassword);
iconpassword.setHorizontalAlignment(SwingConstants.CENTER);
iconpassword.setIcon(new
ImageIcon(Login.class.getResource("/res/lock.png")));
}
public class PanelButtonMouseAdapter extends MouseAdapter{

JPanel panel;
public PanelButtonMouseAdapter(JPanel panel) {
this.panel=panel;
}
@Override
if(panel.isEnabled())
}
@Override
panel.setBackground(new Color(0,160,152));
}
@Override
public void mousePressed(MouseEvent e) {
}
@Override
public void mouseReleased(MouseEvent e) {
110 | P a g e
}
}
}
1.1. Admin Dashboard

import javax.swing.border.EmptyBorder;
import javax.swing.JButton;
import javax.swing.UIManager;
import javax.swing.border.BevelBorder;
public class adminDB extends JFrame {

private addDoctor addDoctor;
private addStaff addStaff;
private docList docList;
private staffList staffList;
private JPanel panel_addstaff;
private JLabel lbl_addStaff;
/**
*/
public void run() {
111 | P a g e
try {
adminDB frame = new adminDB();
}
}
});
}
/**
* Create the frame.
*/
public adminDB() {
setBounds(100, 100, 1244, 935);
contentPane.setBorder(new EmptyBorder(5, 5, 5, 5));


panel.add(lblNewLabel);
ImageIcon(adminDB.class.getResource("/res/marylogo 100px.png")));
addDoctor = new addDoctor();

addDoctor.setBounds(0, 0, 1300, 800);
addStaff = new addStaff();
addStaff.setBounds(0, 0, 1300, 800);
docList = new docList();
docList.setBounds(0, 0, 1300, 800);
staffList = new staffList();
112 | P a g e
staffList.setBounds(0, 0, 1300, 800);

@Override
adminDB.this.dispose();
}
@Override
}
@Override
});
JPanel panel_Doctor = new JPanel();

panel_Doctor.addMouseListener(new
PanelButtonMouseAdapter(panel_Doctor) {
@Override
menuClicked(addDoctor);
}
});
panel_Doctor.setLayout(null);
panel_Doctor.setBorder(new BevelBorder(BevelBorder.LOWERED, null,
null, new Color(0, 0, 0), null));
panel_Doctor.setBackground(new Color(0, 160, 152));
113 | P a g e
panel_Doctor.setBounds(35, 172, 193, 44);

panel.add(panel_Doctor);
JLabel lbl_Doctor = new JLabel("ADD DOCTOR");

lbl_Doctor.setHorizontalAlignment(SwingConstants.CENTER);
lbl_Doctor.setForeground(Color.WHITE);
lbl_Doctor.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_Doctor.setBounds(10, 5, 173, 39);
panel_Doctor.add(lbl_Doctor);
panel_addstaff = new JPanel();

panel_addstaff.addMouseListener(new
PanelButtonMouseAdapter(panel_addstaff) {
@Override
menuClicked(addStaff);
}
});
panel_addstaff.setBounds(35, 227, 193, 44);

panel.add(panel_addstaff);
panel_addstaff.setLayout(null);
panel_addstaff.setBorder(new BevelBorder(BevelBorder.LOWERED,
null, null, new Color(0, 0, 0), null));
panel_addstaff.setBackground(new Color(0, 160, 152));
lbl_addStaff = new JLabel("ADD STAFF");

lbl_addStaff.setHorizontalAlignment(SwingConstants.CENTER);
lbl_addStaff.setForeground(Color.WHITE);
lbl_addStaff.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_addStaff.setBounds(10, 0, 173, 41);
panel_addstaff.add(lbl_addStaff);
JPanel panel_docList = new JPanel();

panel_docList.addMouseListener(new
PanelButtonMouseAdapter(panel_docList) {
@Override
menuClicked(docList);
}
});
114 | P a g e
panel_docList.setBounds(35, 282, 193, 44);

panel.add(panel_docList);
panel_docList.setLayout(null);
panel_docList.setBorder(new BevelBorder(BevelBorder.LOWERED,
null, null, null, null));
panel_docList.setBackground(new Color(0, 160, 152));
JLabel lbl_docList = new JLabel("DOCTOR LIST");

lbl_docList.setHorizontalAlignment(SwingConstants.CENTER);
lbl_docList.setForeground(Color.WHITE);
lbl_docList.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_docList.setBounds(10, 5, 173, 36);
panel_docList.add(lbl_docList);
JPanel panel_staffList = new JPanel();

panel_staffList.addMouseListener(new
PanelButtonMouseAdapter(panel_staffList) {
@Override
menuClicked(staffList);
}
});
panel_staffList.setBounds(35, 337, 193, 44);

panel.add(panel_staffList);
panel_staffList.setLayout(null);
panel_staffList.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_staffList.setBackground(new Color(0, 160, 152));
JLabel lbl_staffList = new JLabel("STAFF LIST");

lbl_staffList.setBounds(44, 5, 115, 36);
panel_staffList.add(lbl_staffList);
lbl_staffList.setHorizontalAlignment(SwingConstants.CENTER);
lbl_staffList.setForeground(Color.WHITE);
lbl_staffList.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
JPanel panel_logout = new JPanel();

panel_logout.addMouseListener(new
PanelButtonMouseAdapter(panel_logout) {
@Override
115 | P a g e
if(JOptionPane.showConfirmDialog(null,"Are you sure you

want to sign out?")==0) {
Login login = new Login();
login.setVisible(true);
adminDB.this.dispose();
}
}
});
panel_logout.setLayout(null);
panel_logout.setBorder(new LineBorder(new Color(0, 0, 0), 3, true));
panel_logout.setBackground(new Color(0, 160, 152));
panel_logout.setBounds(35, 718, 193, 44);
panel.add(panel_logout);
JLabel icon_logout = new JLabel("");

icon_logout.setHorizontalAlignment(SwingConstants.CENTER);
icon_logout.setBounds(5, 0, 41, 44);
panel_logout.add(icon_logout);
icon_logout.setIcon(new
ImageIcon(adminDB.class.getResource("/res/logout.png")));
JLabel lbl_logout = new JLabel("LOGOUT");

lbl_logout.setBounds(56, 0, 127, 44);
panel_logout.add(lbl_logout);
lbl_logout.setHorizontalAlignment(SwingConstants.CENTER);
lbl_logout.setForeground(Color.WHITE);
lbl_logout.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
JLabel lblNewLabel_1 = new JLabel("Reports");

lblNewLabel_1.setBackground(new Color(232, 252, 255));
panel.add(lblNewLabel_1);
JLabel lblNewLabel_1_1 = new JLabel("Total Doctors :");

lblNewLabel_1_1.setBackground(new Color(232, 252, 255));
panel.add(lblNewLabel_1_1);
116 | P a g e
JLabel lblNewLabel_1_1_1 = new JLabel("Total Staff :");

lblNewLabel_1_1_1.setForeground(Color.WHITE);
lblNewLabel_1_1_1.setFont(new Font("Segoe UI Black", Font.PLAIN,
17));
lblNewLabel_1_1_1.setBackground(new Color(232, 252, 255));
lblNewLabel_1_1_1.setBounds(20, 577, 120, 42);
panel.add(lblNewLabel_1_1_1);
JLabel ttlDoc = new JLabel("0");

ttlDoc.setHorizontalAlignment(SwingConstants.CENTER);
ttlDoc.setForeground(Color.WHITE);
ttlDoc.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
ttlDoc.setBackground(new Color(232, 252, 255));
ttlDoc.setBounds(150, 515, 75, 42);
panel.add(ttlDoc);
JLabel ttlStaff = new JLabel("0");

ttlStaff.setHorizontalAlignment(SwingConstants.CENTER);
ttlStaff.setForeground(Color.WHITE);
ttlStaff.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
ttlStaff.setBackground(new Color(232, 252, 255));
ttlStaff.setBounds(150, 577, 75, 42);
panel.add(ttlStaff);
JButton updatebtn = new JButton("Update");

updatebtn.addMouseListener(new MouseAdapter() {
@Override
try {
Connection conn=
String sql = "SELECT COUNT(*) from doctor";
ResultSet rs = sta.executeQuery(sql);
while (rs.next()) {
int count = rs.getInt(1);
ttlDoc.setText(Integer.toString(count));
}conn.close();
117 | P a g e
};
try {
Connection conn=
String sql = "SELECT COUNT(*) from staff";
while (rs.next()) {
ttlStaff.setText(Integer.toString(count));
}conn.close();
};
}
});
updatebtn.setBackground(new Color(255, 255, 255));
updatebtn.setFont(new Font("Segoe UI Black", Font.PLAIN, 15));
updatebtn.setBounds(140, 470, 88, 36);
panel.add(updatebtn);
//get total of doctors

try {
Connection conn=
String sql = "SELECT COUNT(*) from doctor";
while (rs.next()) {
ttlDoc.setText(Integer.toString(count));
}conn.close();
};
//get total staff

try {
118 | P a g e
Connection conn=
String sql = "SELECT COUNT(*) from staff";
while (rs.next()) {
ttlStaff.setText(Integer.toString(count));
}conn.close();
};
JPanel panel_main = new JPanel();

panel_main.setBackground(new Color(232, 252, 255));
panel_main.setBounds(268, 0, 1920, 800);
contentPane.add(panel_main);
panel_main.setLayout(null);
panel_main.add(addDoctor);
panel_main.add(addStaff);
panel_main.add(docList);
panel_main.add(staffList);
menuClicked(docList);
}
//for navigation
public void menuClicked(JPanel panel) {
docList.setVisible(false);
addDoctor.setVisible(false);
addStaff.setVisible(false);
staffList.setVisible(false);
panel.setVisible(true);
}
//panel-button mouse interaction
JPanel panel;
119 | P a g e

this.panel=panel;
}
@Override
@Override
}
@Override
}
@Override
}
}
}
1.2. Doctor Dashboard
import java.text.DateFormat;
import java.text.SimpleDateFormat;
import java.util.Date;
120 | P a g e
import javax.swing.AbstractButton;
public class doctorDB extends JFrame {

private JPanel panel_medhist;
private JLabel lbl_medhist;
private JPanel panel_prescription;
private docsession session;
private medhist medhist;
private prescription pres;
private String today;
protected JLabel records;
/**
*/
public void run() {
try {
doctorDB frame = new doctorDB();
}
}
});
}
/**
* Create the frame.
121 | P a g e
*/
public doctorDB() {
setBounds(100, 100, 1244, 935);
session = new docsession();

session.setBounds(0, 0, 1300, 800);
medhist = new medhist();
medhist.setBounds(0, 0, 1300, 800);
pres = new prescription();
pres.setBounds(0, 0, 1300, 800);



@Override
doctorDB.this.dispose();
}
@Override
122 | P a g e
}
@Override
});
JPanel panel_session = new JPanel();

panel_session.addMouseListener(new
PanelButtonMouseAdapter(panel_session) {
@Override
menuClicked(session);
}
});
panel_session.setLayout(null);
panel_session.setBorder(new BevelBorder(BevelBorder.LOWERED, null,
null, new Color(0, 0, 0), null));
panel_session.setBackground(new Color(0, 160, 152));
panel_session.setBounds(35, 172, 193, 44);
panel.add(panel_session);
JLabel lbl_Doctor = new JLabel("SESSIONS");

lbl_Doctor.setHorizontalAlignment(SwingConstants.CENTER);
lbl_Doctor.setForeground(Color.WHITE);
lbl_Doctor.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_Doctor.setBounds(10, 5, 173, 39);
panel_session.add(lbl_Doctor);
panel_medhist = new JPanel();

panel_medhist.addMouseListener(new
PanelButtonMouseAdapter(panel_medhist) {
123 | P a g e
@Override
menuClicked(medhist);
}
});
panel_medhist.setBounds(35, 227, 193, 44);

panel.add(panel_medhist);
panel_medhist.setLayout(null);
panel_medhist.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_medhist.setBackground(new Color(0, 160, 152));
lbl_medhist = new
JLabel("<html><center>MEDICAL<br>RECORD/HISTORY</html>");
lbl_medhist.setHorizontalAlignment(SwingConstants.CENTER);
lbl_medhist.setForeground(Color.WHITE);
lbl_medhist.setFont(new Font("Segoe UI Black", Font.PLAIN, 16));
lbl_medhist.setBounds(0, 0, 193, 41);
panel_medhist.add(lbl_medhist);

@Override
doctorDB.this.dispose();
}
}
});
124 | P a g e


JLabel lblNewLabel_1_1 = new JLabel("Total Session :");

JLabel ttlSession = new JLabel("0");

ttlSession.setHorizontalAlignment(SwingConstants.CENTER);
ttlSession.setForeground(Color.WHITE);
ttlSession.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
ttlSession.setBackground(new Color(232, 252, 255));
ttlSession.setBounds(150, 515, 75, 42);
panel.add(ttlSession);
JLabel todaySession = new JLabel("0");

todaySession.setHorizontalAlignment(SwingConstants.CENTER);
todaySession.setForeground(Color.WHITE);
todaySession.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
todaySession.setBackground(new Color(232, 252, 255));
todaySession.setBounds(150, 554, 75, 42);
panel.add(todaySession);
125 | P a g e
JLabel lblNewLabel_1_1_1 = new JLabel("Session Today :");

17));

@Override
try {
Connection conn=
String sql = "SELECT COUNT(*) from session";
while (rs.next()) {
ttlSession.setText(Integer.toString(count));
}conn.close();
};
try {
Date date = new Date();
DateFormat df = new SimpleDateFormat("YYYY-
MM-dd");
today = df.format(date);
Connection conn=
String sql = "SELECT COUNT(*) from session
where date = '"+today+"'";
while (rs.next()) {
todaySession.setText(Integer.toString(count));
126 | P a g e
}conn.close();
};
try {
Connection conn=
String sql = "SELECT COUNT(*) from medhist";
while (rs.next()) {
records.setText(Integer.toString(count));
}conn.close();
};
}
});
panel_prescription = new JPanel();

panel_prescription.setLayout(null);
panel_prescription.addMouseListener(new
PanelButtonMouseAdapter(panel_prescription) {
@Override
menuClicked(pres);
}
});
panel_prescription.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_prescription.setBackground(new Color(0, 160, 152));
panel_prescription.setBounds(35, 281, 193, 44);
panel.add(panel_prescription);
JLabel lbl_Doctor_1 = new JLabel("PRESCRIPTION");

lbl_Doctor_1.setHorizontalAlignment(SwingConstants.CENTER);
127 | P a g e
lbl_Doctor_1.setForeground(Color.WHITE);
lbl_Doctor_1.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_Doctor_1.setBounds(10, 5, 173, 39);
panel_prescription.add(lbl_Doctor_1);
JLabel lblNewLabel_1_1_1_1 = new JLabel("Total Records :");

lblNewLabel_1_1_1_1.setForeground(Color.WHITE);
lblNewLabel_1_1_1_1.setFont(new Font("Segoe UI Black", Font.PLAIN,
17));
lblNewLabel_1_1_1_1.setBackground(new Color(232, 252, 255));
lblNewLabel_1_1_1_1.setBounds(17, 592, 133, 42);
panel.add(lblNewLabel_1_1_1_1);
records = new JLabel("0");

records.setHorizontalAlignment(SwingConstants.CENTER);
records.setForeground(Color.WHITE);
records.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
records.setBackground(new Color(232, 252, 255));
records.setBounds(150, 592, 75, 42);
panel.add(records);
//get total of session

try {
Connection conn=
while (rs.next()) {
}conn.close();
};
//get total of session for the day
try {
DateFormat df = new SimpleDateFormat("YYYY-MM-dd");
128 | P a g e
Connection conn=
String sql = "SELECT COUNT(*) from session where date =
'"+today+"'";
while (rs.next()) {
}conn.close();
};
try {
Connection conn=
String sql = "SELECT COUNT(*) from medhist";
while (rs.next()) {
records.setText(Integer.toString(count));
}conn.close();
};

panel_main.add(session);
panel_main.add(medhist);
panel_main.add(pres);
menuClicked(session);
}
129 | P a g e
//for navigation
session.setVisible(false);
medhist.setVisible(false);
pres.setVisible(false);
}

JPanel panel;
this.panel=panel;
}
@Override
@Override
}
@Override
}
@Override
}
}
}
1.3. Staff Dashboard

130 | P a g e
import java.text.DateFormat;
import java.text.SimpleDateFormat;
import java.util.Date;
public class staffDB extends JFrame {

private addSession addsession;
private sessionlist sessionList;
private JLabel lbl_sessionlist;
private patInfo patInfo;
private String today;
/**
*/
131 | P a g e
public void run() {
try {
staffDB frame = new staffDB();
}
}
});
}
/**
* Create the frame.
*/
public staffDB() {
setBounds(100, 100, 1244, 935);


132 | P a g e
addsession = new addSession();

addsession.setBounds(0, 0, 1300, 800);
sessionList = new sessionlist();
sessionList.setBounds(0, 0, 1300, 800);
patInfo = new patInfo();
patInfo.setBounds(0, 0, 1300, 800);

@Override
staffDB.this.dispose();
}
@Override
}
@Override
});
JPanel panel_Session = new JPanel();

panel_Session.addMouseListener(new
PanelButtonMouseAdapter(panel_Session) {
133 | P a g e
@Override
menuClicked(addsession);
}
});
panel_Session.setLayout(null);
panel_Session.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_Session.setBackground(new Color(0, 160, 152));
panel_Session.setBounds(35, 172, 193, 44);
panel.add(panel_Session);
JLabel lbl_session = new JLabel("ADD SESSION");

lbl_session.setHorizontalAlignment(SwingConstants.CENTER);
lbl_session.setForeground(Color.WHITE);
lbl_session.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_session.setBounds(10, 5, 173, 39);
panel_Session.add(lbl_session);
JPanel panel_sessionlist = new JPanel();

panel_sessionlist.addMouseListener(new
PanelButtonMouseAdapter(panel_sessionlist) {
@Override
menuClicked(sessionList);
}
});
panel_sessionlist.setBounds(35, 227, 193, 44);

panel.add(panel_sessionlist);
panel_sessionlist.setLayout(null);
panel_sessionlist.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_sessionlist.setBackground(new Color(0, 160, 152));
lbl_sessionlist = new JLabel("SESSIONS");
134 | P a g e
lbl_sessionlist.setHorizontalAlignment(SwingConstants.CENTER);
lbl_sessionlist.setForeground(Color.WHITE);
lbl_sessionlist.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_sessionlist.setBounds(10, 0, 173, 41);
panel_sessionlist.add(lbl_sessionlist);

@Override
staffDB.this.dispose();
}
}
});


135 | P a g e

JLabel lblNewLabel_1_1 = new JLabel("Total Session :");

JLabel ttlSession = new JLabel("0");

ttlSession.setHorizontalAlignment(SwingConstants.CENTER);
ttlSession.setForeground(Color.WHITE);
ttlSession.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
ttlSession.setBackground(new Color(232, 252, 255));
ttlSession.setBounds(150, 515, 75, 42);
panel.add(ttlSession);
JLabel todaySession = new JLabel("0");

todaySession.setHorizontalAlignment(SwingConstants.CENTER);
todaySession.setForeground(Color.WHITE);
todaySession.setFont(new Font("Segoe UI Black", Font.PLAIN, 17));
todaySession.setBackground(new Color(232, 252, 255));
todaySession.setBounds(150, 554, 75, 42);
panel.add(todaySession);

@Override
136 | P a g e
try {
Connection conn=
while (rs.next()) {
}conn.close();
};
try {
DateFormat df = new SimpleDateFormat("YYYY-
MM-dd");
Connection conn=
String sql = "SELECT COUNT(*) from session
where date = '"+today+"'";
while (rs.next()) {
}conn.close();
};
}
});
137 | P a g e

JLabel lblNewLabel_1_1_1 = new JLabel("Session Today :");

17));
JPanel panel_patientInfo = new JPanel();

panel_patientInfo.addMouseListener(new
PanelButtonMouseAdapter(panel_patientInfo) {
@Override
menuClicked(patInfo);
}
});
panel_patientInfo.setLayout(null);
panel_patientInfo.setBorder(new BevelBorder(BevelBorder.LOWERED,
panel_patientInfo.setBackground(new Color(0, 160, 152));
panel_patientInfo.setBounds(35, 281, 193, 44);
panel.add(panel_patientInfo);
JLabel lbl_sessionlist_1 = new JLabel("PATIENT INFO");

lbl_sessionlist_1.setHorizontalAlignment(SwingConstants.CENTER);
lbl_sessionlist_1.setForeground(Color.WHITE);
lbl_sessionlist_1.setFont(new Font("Segoe UI Black", Font.PLAIN, 20));
lbl_sessionlist_1.setBounds(10, 0, 173, 41);
panel_patientInfo.add(lbl_sessionlist_1);
//get total of sessions for the day

try {
138 | P a g e
Connection conn=
while (rs.next()) {
}conn.close();
};
try {
DateFormat df = new SimpleDateFormat("YY-MM-dd");
Connection conn=
String sql = "SELECT COUNT(*) from session where date =
'"+today+"'";
while (rs.next()) {
}conn.close();
};

139 | P a g e
panel_main.add(addsession);
panel_main.add(sessionList);
panel_main.add(patInfo);
menuClicked(sessionList);
}
//for navigation
sessionList.setVisible(false);
addsession.setVisible(false);
patInfo.setVisible(false);

JPanel panel;
this.panel=panel;
}
@Override
@Override
140 | P a g e
@Override
}
@Override
}
}
}
141 | P a g e
Other Relevant Documents
CHAPTER 1
142 | P a g e
CHAPTER 2
ELECTRONIC HEALTH RECORDS
CONVERTING FROM PAPER-BASED TO ELECTRONIC RECORD KEEPING
143 | P a g e
IMPACT OF ELECTRONIC HEALTH RECORDS ON INFORMATION
PRACTICES
144 | P a g e
UTILISATION OF ELECTRONIC HEALTH RECORDS FOR PUBLIC HEALTH
145 | P a g e
HEALTH INFORMATION SYSTEM
BARRIERS AFFECTING THE ADOPTION OF ELECTRONIC MEDICAL
RECORDS IN THE PHILIPPINES
146 | P a g e
ELECTRONIC MEDICAL RECORDS IN THE PHILIPPINES
CHAPTER 3
147 | P a g e
TURN IT IN RESULT
COPYRIGHT CERTIFICATE
148 | P a g e
User’s Guide
Log in as admin if you are admin if not

log in as a doctor or clinic staff if you
already create an account by the admin
Admin can Add an account Admin can Add an account for

for doctor by adding the info staff by adding the info of the
of the doctor clinic staff
149 | P a g e
Admin can Edit Account of Admin can Edit Account

Doctor if want to change the of Staff if want to
details of doctor change the details of
Staff
Only clinic staff can Only clinic staff can

add session edit session
150 | P a g e
Only clinic staff can edit Only the doctor can add
Patient info laboratory results ,diagnoses and
presicription
Lists
Only the admin can view Only the admin can view
the list of doctors the list of staff
151 | P a g e
Staff can view the patient list

Both doctor and staff can view
and edit basic information
session list however their
interaction to the list differs
from each other
Only doctor can view the list of

Only doctor can view the list of
medical records
medical records
152 | P a g e
Documentation
153 | P a g e
154 | P a g e
155 | P a g e
Approval Form
156 | P a g e
Curriculum Vitae of the Researchers
157 | P a g e
158 | P a g e
159 | P a g e
160 | P a g e

Digitizing Patient Record For Mary Angels Diagnostic Clinic Document

Uploaded by

Document Information

Original Description:

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

Digitizing Patient Record For Mary Angels Diagnostic Clinic Document

Uploaded by

Copyright:

Available Formats

Republic of the Philippines

RIZAL TECHNOLOGICAL UNIVERSITY

COLLEGE OF ENGINEERING AND ARCHITECHTURE

Digitizing Patient’s Record for Mary Angels Diagnostic Clinic

Presented to the Faculty of Engineering and Architecture

RIZAL TECHNOLOGICAL UNIVERSITY

Brgy. Malamig, Boni Avenue

In Partial Fulfillment of the Requirements for the Degree of

Bachelor of Science in Information Technology

Department of Information Technology

Adornado, Raymond Anthony L.

Quintans, Alfred Jhunnell A.

Barbon, Daniel Louis O.

Salamante, Christoper Phillip D.

COLLEGE OF ENGINEERING AND ARCHITECHTURE

Prof. Kenneth Martinez

Dr. Jaevier A. Villanueva

Program Chair, BSIT

Ms. Marthea Andrea O. Daluyon, DIT(CAR) Engr.Ramil N. Madriaga, MSIT

Technical / IT Expert Local Panelist

Engr. Greta A. Rosario, MSIT

DR. CORLETO R. BRAVO

Dean, College of Engineering, Architecture Technology

COLLEGE OF ENGINEERING AND ARCHITECHTURE

and pushed me to surpass my limit.

Raymond Anthony Adornado

people who served as my motivations and inspirations.

Christoper Phillip Salamante

This capstone project is dedicated to my family, who supported me in everything I

through. And lastly, to my mother.

Alfred Jhunnell Quintans

project in spite of the challenges we encountered.

Daniel Louis Barbon

COLLEGE OF ENGINEERING AND ARCHITECHTURE

finish the research.

knowledge we required, always reminded us to be keen in helping us grow as people, and

gave us advice on how to accomplish this research more efficiently.

right track and reliable.

COLLEGE OF ENGINEERING AND ARCHITECHTURE

understanding their health status, causing misinterpretation of prescriptions and doctors’

instructions due to poor handwriting. As a result, there is also a difference in creating

patient's medical care. Patient information is stored in a centralized system. It includes

information about the patient's demographics and medical condition. It is intended to

from a single database.

COLLEGE OF ENGINEERING AND ARCHITECHTURE

COLLEGE OF ENGINEERING AND ARCHITECHTURE

RELEVANCE OF THE TECHNOLOGIES.......................................................................... 27

COLLEGE OF ENGINEERING AND ARCHITECHTURE

System Testing ....................................................................................................................... 84

COLLEGE OF ENGINEERING AND ARCHITECHTURE

COLLEGE OF ENGINEERING AND ARCHITECHTURE

COLLEGE OF ENGINEERING AND ARCHITECHTURE

COLLEGE OF ENGINEERING AND ARCHITECHTURE

BACKGROUND OF THE STUDY

A medical record contains a person's health-related details, such as age, gender,

confidential health data from unauthorized disclosure. In clinics, organizing patient

replace paper-based medical charts by adhering to clinic standards. In this application,

COLLEGE OF ENGINEERING AND ARCHITECHTURE

interface to access specific records.

PURPOSE AND DESCRIPTION OF THE PROJECT

as medical knowledge grows, advancements in other fields, like computer programming,

COLLEGE OF ENGINEERING AND ARCHITECHTURE