SOFTWARE

ENGINEERING

Members:

Galvez, Richard S.

Tomelden, Diane

Ybanez, Justine
 PATIENT’S STORY FOR THE MANUAL TRANSACTION OF
BARANGAY LA PAZ HEALTH CLINIC

In Barangay La Paz Makati City the retrieval of the patient’s data was still manual and
paper-based. According to the people who interviewed with us, if one patient wished to have
their check-up they are just headed inside the clinic asking for someone’s assistance. Though
the problem was they did have need to wait until their names was called. (This is where the first
problem comes-in. This kinda always took the process to slow and resulting to have long-time
waiting processed and feels like become forever. Everyone have not exactly given a change to
get notice by the doctor immediately because too many patience where waiting inside the
clinic.) Then after waiting for so long, once the names are called this was the perfect time to get
and approach authorized personnel for the first phase of the process.

At this point, the person - let’s just the say the front-desk who was talking to the patient,
need to identify weather it was an old patient or a new one. (of course they did not do the same
process and so treated by the nurse and doctor would slightly different) If the front-desk identify
that they are newly patient, lot of papers form will be given directly to the patient and needs to
fill-in those forms honestly with accuracy because this will serve as the personal record of that
patient for the clinic prior for check-up. As for the old patient, they would directly ask for the
history of their check-ups written on the old brown envelope. Also front-desk would try to check
the old patients check-up history on their end. (This is where the second problem comes-in, it
was pain in ass and very time consuming for the front-desk to retrieved the patience’s
information stored over the paper hills inside the safe storage.)

Then, right after the nurses got the information that they need from the patient. They will
now subject them for the doctor’s diagnosis and treatment (if necessary) depends on the
situation and the level of health issues patient into. Because upon checking the patient might be
referred to hospitals for higher level of treatment once they knew that the condition of said
patient is too risky and couldn’t be handled by the clinic itself. However, if the condition is not
quite severe and serious enough the doctor’s prescription will be given to the patient but the
prescribe medicine would only be available at what so ever they called “PLANETS” must to
presents their YELLOW CARDS anyway.
USER REQUIREMENTS

 The system shall be able to store patients record using the system.

 The system shall be able to generate daily, weekly or monthly reports of the patient.

 The system shall be able to login in all the key players in the Clinic depending to their

roles.

 Administrator shall be able to view and modify all information system.

 Front desk staff shall be able to view all information in system, add new patients to

system but shall not be modify any information in it.

 The system shall be able to view all the patient data using the system.

SYSTEM REQUIREMENTS

 The system stores patient records by the assign Family ID.

 The system can view the list of registered patients

 The system can search and retrieve existing patient records by the assign Family ID.

 After each appointment/check-up, the patient’s record in the system will be updated.

 The system can send Push notification and/or notification via SMS depending on the

situation, to a specific patient/s with pending appointments/check-ups a day before the

scheduled appointment/check-up

 Before each appointment/check-up, the patient’s record in the system will be notify.

 The system will generate the total number of registered patient records in the system.

 If the patient’s scheduled appointment/check-up has been attended, the system will

remove the patient’s appointment/check-up on the list of current appointments/check-

ups. Or else If the patient’s scheduled appointment/check-up has NOT been attended, it

will transfer it on the list of missed appointments/check-ups.

FUNCTIONAL REQUIREMENTS

REGISTRATION

 Add patients – The system shall allow front-desk staff to add new patients to the

system.

 Assign Family ID – The system shall allow the front-desk staff to give each patient an

ID and add it to the patient’s record. This ID shall be used by the patient in getting the

medicine/s prescribes by the doctor.

MEDICAL MATTER

 Informs Doctor – The system shall inform doctors of new and/or old patients.

 Generate Report – The system shall generate the patient’s situation record.

 Record Procedure – The whole treatment procedure for the patient shall be recorded

by the system.

REPORT GENERATION

 Patient Information – Every end of the day, week, or month the system shall generate

reports of the patients depends on the clinic needs.

DATABASE

 Patient Mandatory Information – Each patient shall have the following mandatory

information: First name, Last Name, Phone number, Address, and so on.

 Update Patient Information – The system shall allow the user to update any patient’s

information.

 Search for Patient – The system shall allow the user to search for patient’s information

by first name, last name or just unique identification number or patient Family ID.
CONSULTATION

 Appointments/Check-ups – The staff shall use the system to receive the upcoming

appointment/check-ups and assign them according to date to be concerted.

 Assign to Waiting List – The staff shall use the system to assign Patient to a waiting

list if no doctor or vacant time is available.

NON- FUNCTIONAL REQUIREMENTS

SECURITY
 Patient Identification – The system requires the patient to identify himself/herself using
unique patient ID.
 Login ID – Any patient/user who uses the system shall have a login ID and password.

 Modification – Any modification (insert, delete, update) for the database shall be

synchronized and done only by the administrator.

 Front Desk Staff Rights – Front desk staff shall be able to view all information in

system, add new patients to system but shall not be modify any information in it.

 Administrator’s Rights – Administrator shall be able to view and modify all information

in system.

 Doctor’ Rights – Doctor’s shall only be able to search and view all information of the

patient, add consultation and prescription in system.

PERFORMANCE REQUIREMENTS

 Response Time – The system shall give responses in 1 second after checking the

patient’s information.

 Capacity – The system must support 1000 people at a time.

MAINTAINABILITY

 Back-up – The system shall provide the capability to back-up the Data

REALIABILITY

 Availability – The system shall be available all the time.

CONTEXT DIAGRAM OF THE PATIENT MANAGEMENT SYSTEM WITH PUSH NOTIFICATION

<System>
Patient Record System

<System> <System>
Appointment System Security System

<System>
Patient Management
System with Push Account Database
Notification

<System> <System>
Management Reporting Prescription System
System
<System>
Push Notification System
 THE ACTIVITY DIAGRAM OF
PATIENT MANAGEMENT SYSTEM WITH PUSH NOTIFICATION

Patient set an appointment

Patient visits the clinic

Front-desk will register the patient

Patient consultation with doctor

Test Performed

Prescribe Medicine

Follow up Check ups

Admit to Hospital

Discharged
CLASS DIAGRAM