Professional Documents
Culture Documents
INTRODUCTION
General Objectives
Specific Objectives
To the Patient. It is beneficial to the Patient that they do not need to rush time
and easy to input the transaction of the clinic.
To the Researcher. This study gives more idea for the developing system
process and give some innovation of the system. This study would equip them
with knowledge about transaction process.
To the Future Researcher. The future researcher must give the new unique
technology about the transaction for the chosen study in the field of technology.
The patient must register, first the patient could input all their information
and the system can verify if that person is either student or personnel of SKSU
Isulan Campus and then they need to click the register button to register.
The system would manage the patient records, medical history and visit
details of a particular patient. The administrator would be log in first, then
manage the patient information after the log in the administrator would see all the
patient records, visit details and medical history. A medical history was provided
for patient information. All the transaction made by the administrator to the
patient information would be directly saved to the database.
Definition of Terms
In this chapter discussed the review of related literature and studies taken
from different sources such as books, internet, and electronic material like PDF.
Local Literature
The study of (Estinar et al., 2018) stated that with the system they
developed, the researchers were able to provide relevant health services as well
as a platform for the creation, storage, and consolidation of significant medical
data. This data backbone will be very useful for upcoming clinical applications.
Foreign Study
Process
They use manual
process of the
patient
information,
transaction.
Asses
Patient The system is
Information inefficient and
unproductive. HealthEase:
Identify Transaction
Transaction
The current Processing
system cannot System of
Medicine address the need
of the SKSU School Clinic
Isulan Campus
User Clinic.
Recommended
The study will
provide efficient
management of
data and services
in SKSU Isulan
Campus Clinic.
FEEDBACK
Figure 1. Conceptual Framework of the Study
Input
The input contains the basic manual knowledge requirements for the
system wherein the input consisting of the following: manual procedures of SKSU
Isulan Campus Clinic, patient information, patient transaction, medicine, and the
user. The researchers understand the basic information needed, analyzed, and
developed such strategies for the proposed study.
Process
Output
METHODOLOGY
HARDWARE
1pc. Laptop 25,999.00 25,999.00
SUPPLY AND MATERIALS
1Ream A4 bond paper 195.5 195.5
PRINT
The Agile development cycle will be used in constructing the study entitled
“HealthEase: Transaction Processing System of School Clinic”. This System is
consisting of five (5) Development as follows: Planning, Analysis, Design,
Coding, and Testing. It is a methodology construction to make sure that the
system follows a step-by-step approach.
Project Duration
Figure 2. The Gantt Chart of the Study
The researchers planned on how the admin can manage patient records.
The researchers gathered some information to the clinic on how they can
manage it manually after that we continue to plan how we can do it easily using
this system. The researchers used netbeans for the designing and different
function of the system and the researchers build it based on how to plan and
designed using MySQL. After we build, they tested the system if it is functioning
would or not and then they evaluated the system to the student and personnel.
After they tested, they reviewed the system if there was an error needed to repair
it on fix it and then it times to launch.
Context Diagram
Set Transaction
HealthEase:
Approve/Disapprove Transaction TRANSACTION
PROCESSING SYSTEM
OF SCHOOL CLINIC
Patient Inquiry
Logbook Record
Patient
Manual School
Detailed Information Clinic Management Patient Record
System
Nurse In-
Charge
This figure above shows the boundary of context diagram of the existing
manual system. It illustrates the user that interact with the system. The existing
manual system has two users such as patient and nurse in charge, but it is
manually operated works and the clinic.
Entity Relationship Diagram
transaction
transactionid
patienid
transactiondate
status
diagnosis
patient visit
visitid
patientid
This figure shows the entity relationship diagram of the study. It illustrates
the relationship process of the system. This diagram consists of four tables such
as transaction, patients, patient visit, and patient_medical_history.
The figure means that each patient has one or many transactions and
each transaction has one and only one patient, each patient has one or many
patients visit and each patient_visit has one and only one patient, each patient
has one or many patient_medical_history and each patient_medical_history has
one and only one patient.
DATABASE STRUCTURE
transaction_id Int 1 2
patient_id Int 1 2
The table shows the attribute for appointment such as Id, patient id,
appointment date, status, and diagnosis. The data type for id and patient id are
all integer with the 10 as its length. The data type for appointment date is date
time. The data type for transaction time is varchar with 15 as its length. The data
type for status is a varchar with 150 as its length. The diagnosis is text as to the
data type.
Table_patients
patient_id Int 1 2
status enum 1 1
The table shows the attribute for the patient registration such as Id, first
name, middle name, last name, gender, contact number and patient type. The
type for Id is integer with 10 as its length. The data type for first name, middle
name, and last name with 60 as its length. The data types for gender, contact
number are all varchar with 13 as its length.
Table_patient_visit
Patient_visit_id Int 1 2
Patient_id Int 1 2
notes Varchar
The table shows the attribute for patient visit such as id, patient id, date
visit, time visit, diagnosis, and notes. The data type for Id and patient Id are all
integer with 10 as its length. The data type for date visit, diagnosis, and notes are
all varchar with 200 as its length.
Table_medical_history
Medical_history_id Int 1 2
Patient_id Int 1 2
Nurse_name Varchar
The table shows the attribute for patient medical history such as Id, patient Id,
clinic name, diagnosis, diagnosis date, and nurse name. The data type for Id and
patient Id are all integer with 10 as its length. The data type for clinic name
diagnosis, diagnosis date and nurse name are all varchar with 200 as its length.
EVALUATION METHODOLOGY
Research Design
This study utilized a descriptive research design. This design helped
provide answer to the question which align to the objective. This design was
used to informing and concerning status of the study and describe the condition
in a situation.
Methods of Research
Descriptive methods were used to achieve of purpose of the study. This
method was concerned the condition of the study that exist and practices that
prevail or that held and process. The study sought to identify the things happen
at the present of flow of the system.
The survey questioners were answerable by the weighted means that focused on
the evaluation of the system's functionality, effectiveness, accuracy, and security.
HEALTHEASE: TRANSACTION PROCESSING SYSTEM OF SCHOOL
CLINIC
ALBENZAR K. SAGAD
OCTOBER 2023