HealthConnect Portal: Bridging Care through

Technology

Project Documentation

Gapay, Ma. Suzchen

Manucom, Reana Anika

Nilo, Daniella Kim

Soner, Kristian
TABLE OF CONTENTS

I. List of Tables……………………………………………………………………………………ii

II. List of Figures…………………………………………………………………………………..ii

III. List of Appendices……………………………………………………………………………...ii

IV. Introduction……………………………………………………………………………………...1

V. The Proposed System…………………………………………………………………………5

VI. System Coding………………………………………………………………………………..36

VII. Resource Requirements……………………………………………………………………..36

VIII. Appendices………………………………………………………………….…………………37

i
LIST OF TABLES

I. Functional Requirements
II. Non-functional Requirements
III. Use Case Narratives
A. Login as Patient
B. Login as a Healthcare Provider
C. Login as a System Administrator:
D. Log Out:
E. Patient Information Input as a Healthcare Provider:
F. Patient Portal Access as a Patient:
G. Appointment Scheduling as a Patient:
H. Search and Reporting as a Health Provider:
I. Emergency Access and Alerts as a Healthcare Provider:
J. Emergency Data Backup as a System Administrator:
K. Register a New User as a System Administrator:
IV. Reports/Form

LIST OF FIGURES

I. Use Case for HealthConnect Portal Version 0.3

II. Login GUI for HealthConnect Portal Version 0.3
III. Admin-Patient GUI for HealthConnect Portal Version 0.3
IV. Admin-Update Patient GUI for HealthConnect Portal Version 0.3
V. Admin-Update Healthcare Provider GUI for HealthConnect Portal Version 0.3
VI. Patient-Home GUI for HealthConnect Portal Version 0.3
VII. Patient-Diagnosis GUI for HealthConnect Portal Version 0.3
VIII. Healthcare Provider-Dashboard GUI for HealthConnect Portal Version 0.3
IX. Healthcare Provider-Patient Diagnosis GUI for HealthConnect Portal Version 0.3
X. HealthConnect Portal Screen Layout Version 0.3

LIST OF APPENDICES

Appendix A: GUI Mockups

Appendix B: Screen Layout

ii
1.0 INTRODUCTION

This chapter provides the background information of the project and gets into detail the
project’s aimed goals together with the problems to be solved.

1.1 Background of the Study

As we are in the era of rapid technological advancement, hospitals are presented

with limitless opportunities to enhance efficiency. One of these that can be enhanced
is the ability of hospitals to relay information about the patients' information by
developing a web-based comprehensive patient information system.

In our current healthcare system, there exists a significant challenge in providing

patients and their families with easy access to their medical information and facilitating
seamless communication with healthcare providers. Traditional methods often lead to
misunderstandings, delays, and difficulties in retrieving critical health data, affecting
the overall quality of patient care and satisfaction. Additionally, in situations such as
fire, flooding, or other mishaps, paper-based medical records are at risk of receiving
damage affecting patient services. Having an electronic-based data system remedies
this problem by offering an alternative backup for their data as well as higher security.

1.2 Statement of the Objectives

The main goal of this project is to provide Makati Medical Center and its patients, a
better tool for communication and information sharing. By introducing new
technologies in its service, it is expected that performance among doctors and
hospital staff will rise with the project allowing a more efficient approach in their work.

1.2.1 General Problem

The healthcare industry, including Makati Medical Center, currently

faces communication and information-sharing challenges. Traditional
methods may lead to inefficiencies, delays, and potential gaps in delivering
patient care. As technology advances, there is a growing need for

1
 healthcare institutions to adapt and incorporate modern solutions to
enhance overall operational efficiency.

1.2.2 Specific Problems

● Communication Barriers - Traditional communication channels may lead to

delays and misinterpretations among doctors, hospital staff, and other
stakeholders. A centralized communication platform can help quick
decision-making and coordination in critical situations.

● Information Fragmentation - Patient information is often dispersed across

various systems and documents, making it challenging for healthcare
professionals to access comprehensive and up-to-date records. Inefficient
data sharing may result in duplicated efforts and potential errors in patient
care.

● Workflow Inefficiencies - Current workflows might be manual and time-

consuming, affecting the overall efficiency of hospital staff. Streamlining
processes is important for maximizing the time and expertise of healthcare
professionals.

● Limited Patient Engagement - Patients may face difficulties accessing their

medical information and interacting with the healthcare system. Improving
patient engagement through enhanced communication tools is vital for a
more patient-centric approach.

● Technological Lag - The need for up-to-date technologies in the current

system may hinder the hospital's ability to adapt to modern healthcare
standards. A lack of integrated technology solutions can lead to suboptimal
performance and reduced competitiveness.

2
1.2.3 General Objectives

This project aims to improve the communication between patients and

Makati Medical Center by creating a web app that provides and secures
their respective data information. We are developing the HealthConnect
Portal to enhance communication channels between healthcare
professionals and patients, ensuring timely and accurate information
exchange. Also, implement features within the portal to empower patients,
enabling them to engage with their healthcare information actively and
have a comprehensive view of their medical cases.

1.2.4 Specific Objectives

● Create a User-Friendly Web Portal - develop an intuitive and user-friendly

web application, the HealthConnect Portal, accessible to healthcare
professionals and patients for seamless interaction.

● Implement Secure Patient-Professional Communication Tools - integrate

secure communication tools within the portal, facilitating direct and efficient
communication between healthcare providers and their patients.

● Enable On-the-Go Accessibility for Healthcare Professionals - provide

healthcare professionals, especially doctors, with a user-friendly platform
accessible from various devices, allowing them to review patient cases and
communicate efficiently, regardless of location.

● Enable Case Tracking and Updates - establish a system within the portal
that allows patients to track the progress of their medical cases and receive
real-time updates on appointments, test results, and treatment plans.

3
1.3 Scope and Delimitation

The scope of the HealthConnect Portal project is to establish a specialized web

application tailored to the unique communication and engagement needs within
Makati Medical Center. The primary focus is to develop a user-friendly platform that
enhances communication between healthcare professionals and patients, offering
features such as secure messaging, case tracking, and updates.

The portal will prioritize mobile accessibility for healthcare professionals,

acknowledging the dynamic nature of their work. While aligning with Electronic Health
Record (EHR) principles, the project is intentionally limited to specific functionalities
to simplify communication and patient engagement. The HealthConnect Portal
project deliberately excludes the comprehensive integration of Electronic Health
Records (EHR) in the traditional sense, emphasizing specific features related to
communication and case tracking. It does not extend to the development of a fully
automated system, standalone mobile applications, or a complete overhaul of the
existing IT infrastructure at Makati Medical Center. Unlike a traditional EHR system,
the HealthConnect Portal does not aim to encompass the entirety of patient health
records but focuses on real-time communication and engagement needs. It does not
replace the broader functionalities of conventional EHR systems but serves as a
targeted solution within the defined scope, optimizing communication efficiency and
patient involvement. This strategic delimitation ensures a more focused and
achievable project outcome while addressing specific challenges within the hospital's
operational framework.

4
 2.0 THE PROPOSED SYSTEM

This chapter includes all the details regarding how the system works, what it does, and
its possible interactions with the user.

2.1 System Overview

The HealthConnect Portal System is a healthcare management platform designed

to enhance the efficiency and accessibility of medical services. Developed for Makati
Medical Center, this system facilitates seamless interactions between healthcare
providers and patients by offering user registration and management features, secure
patient information input, appointment scheduling, search and reporting functionalities,
and emergency access and alerts. The system adheres to healthcare standards and
regulations. The user-friendly interface provides usability, with modules focusing on
user management, patient information, appointment scheduling, search and reporting,
emergency access and alerts, and data backup. The project aims to improve the
current healthcare management by providing an integrated solution prioritizing patient
care and data integrity.

2.2 Functional Requirements

Name Description Version

User The system should allow hospital staff to Version

Registration and register new users (healthcare providers, 0.1
Management administrators) and manage user roles
and permissions.

Required Information:

• Login Name
• Password (2x)
• Email Address
• First Name
• Last Name

5
 • Account Status (Patient,
Healthcare Provider, or System
Administrator)
• Mobile Number

Optimal Information:

• Second Name
• Date of Birth
• Sex
• Address
• Postal/Zip Code
• City
• Province/State
• Country
• Telephone Number
• Web Site

User The system should provide a secure user Version

Authentication authentication and login mechanism,
0.1
and Login allowing authorized users, including
system administrators, healthcare
providers, and administrators, to access
the HealthConnect Portal. Users should
have the flexibility to choose their role
during the login process.

6
 Patient Healthcare providers should have the Version
Information capability to thoroughly input and update
0.1
Input patient details within the HealthConnect
Portal.

This includes recording and managing

patient information such as:

▪ Medical history
▪ Diagnoses
▪ Treatment plans.

Patient Portal Patients and their families should have Version

Access secure access to their medical information 0.1
through a user-friendly portal

Prompting designated Healthcare Version

Providers and vice-versa, ensuring easy 0.2
communication with healthcare providers.

Appointment Patients should be able to request and Version

Scheduling
schedule appointments online. 0.2
(Optional or for
future updates)

Search and Healthcare providers now have a Version

Reporting calendar view to manage appointments.
0.2

Search functionality to quickly locate Version

specific patient records.
0.3

7
 Reporting tools for healthcare providers to Version
analyze patient data and trends.
0.3

Emergency System-generated alerts for critical health Version

Access and updates or emergencies. 0.3
Alerts

Emergency contacts are advised. Version

0.3

Emergency The system should automatically back up Version

Data Backup patient data to prevent loss during 0.3
emergencies (fire, flooding). This feature
serves as an alternative backup to
traditional paper-based records.

2.3 Non-functional Requirements

Security

● Compliance with healthcare data security standards.

● Encryption of sensitive patient information during transmission and
storage.

Reliability

8
 ● The system should have a high level of availability to ensure continuous
access.
● Regular data backups to prevent data loss in case of system failures.

Scalability

● The system should be designed to handle a growing number of users and

data.
● Scalable infrastructure to accommodate increasing demand.

Usability

● Intuitive and user-friendly interface for patients and healthcare providers.

● Accessibility features for users with disabilities.

Performance

● Fast response times for retrieving patient records and processing requests.
● System should be able to handle concurrent user interactions without
significant lag.

Compliance

● Adherence to relevant legal and regulatory requirements.

● Regular audits and updates to ensure compliance with changing
regulations.

Disaster Recovery

● A robust disaster recovery plan to ensure data integrity and availability in

case of unforeseen events.
● Regular testing of disaster recovery procedures.

Training and Support

● Comprehensive training programs for users to navigate the system

effectively.

9
 ● Responsive customer support to address user queries and issues
promptly.

2.4 Use-Case Diagram

Figure 1: Use Case Diagram for HealthConnect Portal Version 0.3

2.5 Use-Case Narratives

Login as a Patient:

Actor Actions System Responses

1. User chooses to login as a

patient

10
 2. User inputs their Patient ID

3. User inputs their password

4. User clicks “Login”

5. Checks if the provided Patient ID

corresponds to a registered patient

6. Checks if password matches the

Patient ID

7. Shows Welcome Page

8. Given the patient’s login information,

the system fetches and populates the
patient’s profile and medical records.
The data is fetched from the
HealthCare Portal Database.

Alternative Scenarios

5. Checks if the user is a registered

patient

6. Sends an error message stating that

the entered Patient ID is not
associated with a patient (if the
provided Patient ID does not
correspond to a registered patient)

6. Checks if password matches the

Patient ID

7. Sends an error message stating that

the password is incorrect (if the
entered password does not match the
Patient ID)

11
Login as a Healthcare Provider:

Actor Actions System Responses

1. User chooses to login as a

healthcare provider

2. User inputs their Healthcare

Provider ID

3. User inputs their password

4. User clicks “Login”

5. Checks if the provided Healthcare

Provider ID corresponds to a
registered healthcare provider

6. Checks if password matches the

Healthcare Provider ID

7. Shows Welcome Page

8. Given the patient’s login information,

the system fetches and populates
relevant information such as the
healthcare provider’s schedule,
patient appointments, and other
significant information regarding their
patients. The data is fetched from the
HealthConnect Portal Database.

Alternative Scenarios

5. Checks if the user is a registered

healthcare provider

6. Sends an error message stating that

the entered Healthcare Provider ID is
not associated with a healthcare
provider (if the provided Healthcare
Provider ID does not belong to a
registered healthcare provider)

12
 6. Checks if password matches the
Healthcare Provider ID

7. Sends an error message stating that

the password is incorrect (if the
entered password does not match the
Healthcare Provider ID)

Login as a System Administrator:

Actor Actions System Responses

1. User chooses to login as a

system administrator

2. User inputs their Admin ID

3. User inputs their password

4. User clicks “Login”

13
 5. Checks if the provided Admin ID
corresponds to a registered system
administrator

6. Checks if password matches the

Admin ID

7. Shows Welcome Page

8. Given the admin’s login information,

the system provides access to
administrative features such as user
management, data backups, and
system configuration. The data is
fetched from the HealthConnect
Portal Database.

Alternative Scenarios

5. Checks if the user is a registered

system administrator

6. Sends an error message stating that

the entered Admin ID is not
associated with a system
administrator (if the provided Admin
ID does not correspond to a
registered system administrator)

6. Checks if password matches the

Admin ID

7. Sends an error message stating that

the password is incorrect (if the
entered password does not match the
Admin ID)

14
Log Out:

Actor Actions System Responses

1. User clicks “Log Out” 2. Shows confirmation window (Are you

sure you want to log out?)

3. User clicks “Yes” 4. Logs out user from the system

Alternative Scenarios

2. Shows confirmation window (Are you

sure you want to log out?)

3. User clicks “No” 4. Retains current page the user is at

Patient Information Input as a Healthcare Provider:

Actor Actions System Responses

1. Healthcare Provider Login (See 2. Shows the Patient Profile panel

Login as a Healthcare Provider
use case)

3. Healthcare Provider navigates to 4. The application connects to the

the patient’s profile section
HealthConnect Portal Database and
fetches the data from the specified
patient profile. It also validates the
entered data for accuracy and
completeness.

5. Healthcare Provider selects the 6. System displays a comprehensive

option to input or update patient form for the healthcare provider to
details input or update patient details

15
 7. Healthcare Provider enters or
modifies detailed patient
information, which includes but
not limited to:
• Medical History
• Diagnoses
• Treatment Plans
10. Healthcare Provider submits the
updated patient information by
clicking “Update” or “Submit”
Alternative Scenarios
8. Checks if the healthcare provider
encounters an error during data entry
9. Checks if there are missing required
fields
11. Upon successful submission, the
system updates the patient’s medical
records with the new information. It
will also generate a confirmation
message indicating that the patient
information has been successfully
updated
8. Checks if the healthcare provider
encounters an error during data entry
9. System displays an error message
indicating the issue and prompts the
healthcare provider to correct it
9. Checks if there are missing required
fields.
10. System prompts the healthcare
provider to complete all mandatory
fields before submission.
16
Patient Portal Access as a Patient:

Actor Actions System Responses

1. Patient Login (See Login as a 2. Shows a user-friendly dashboard that

Patient use case) displays relevant options for the
patient

3. Patient navigates to the “Medical 4. The application connects to the

Information” section HealthConnect Portal Database and
fetches the data from the specified
patient medical information.

5. Patient has access to the 6. Checks if there are issues in

comprehensive view of their accessing the patient’s medical
medical information, which information
includes but not limited to:
7. System displays a comprehensive
• Medical History view of the patient’s medical
• Diagnoses information.
• Treatment Plans
• Prescriptions
• Other relevant information

17
 8. Patient can securely 9. Checks if there are communication
communicate with their errors between the patient and
designated healthcare providers. healthcare provider

· Patient can send 10. System ensures easy

messages or inquiries by communication channels between
filling up the message patients and healthcare providers,
box and clicking “Send” fostering seamless interactions

· Patient can receive

notifications for
appointment reminders,
test results, and other
relevant updates
regarding their health

Alternative Scenarios

6. Checks if there are issues in

accessing the patient’s medical
information

7. System provides assistance and

guidance, directing the patient to
support channels or by simply
refreshing the window.

9. Checks if there are communication

errors between the patient and
healthcare provider

10. System prompts the patient to check

their internet connection or provides
alternative means of support.

Appointment Scheduling as a Patient:

Actor Actions System Responses

18
 1. Patient Login (See Login as a 2. Shows a user-friendly dashboard
Patient use case) that displays relevant options for the
patient

3. Patient navigates to the 4. The application connects to the

“Appointment Scheduling” HealthConnect Portal Database and
section fetches the data from the available
dates for appointment

5. Patient selects the option to 6. System displays a calendar view

request a new appointment with available dates and time slots

7. Patient chooses a preferred date 8. Checks the availability of the

and time for the appointment. selected date and time
They can also provide any
specific details, request, or
preferences for the appointment

9. Patient submits the appointment 10. The system sends appointment

request through the “Submit” confirmation notifications to the
button patient

Alternative Scenarios

8. Checks the availability of the

selected date and time

9. System suggests alternative dates

and times or provides instructions
on contacting the healthcare
provider.

19
 11. Patient can cancel or reschedule 12. System displays a calendar view of
an existing appointment by the submitted appointment with
navigating to the “My selected date and time slots.
Appointments” section.

13. Patient selects the appointment 14. System guides the patient through
to cancel or reschedule. the cancellation or rescheduling
process.

Search and Reporting as a Health Provider:

Actor Actions System Responses

1. Healthcare Provider Login (See 2. Shows a user-friendly dashboard that

Login as a Healthcare Provider displays relevant options for the
use case) health provider

3. Healthcare Provider navigates to 4. The application connects to the

the “Search and Reporting” HealthConnect Portal Database and
section fetches the data from the patient’s
medical records and scheduled
appointments.

20
 5. Healthcare Provider can search
for patient records through
‘Patient Records Search’:
· Healthcare provider uses
the search functionality to
quickly locate specific
patient records
· Healthcare provider
enters search criteria and
initiates the search
8. Healthcare provider can view,
manage, and confirm upcoming
appointments.
Alternative Scenarios
6. Checks if the information provided in
the search function matches the
information from the database.
7. System provides a search interface
with filters such as patient name, ID,
or relevant keywords. Moreover, it
can show a list of matching patient
records based on the search criteria.
Reporting tools include various
parameters for customized data
analysis, such as date ranges,
specific conditions, or treatment
outcomes. The generated reports
can be exported or saved for future
reference
9. Checks if the date and time
appointments are confirmed and
present in the database
10. System displays a calendar view with
scheduled appointments. The
calendar view for appointment
management allows healthcare
providers to efficiently organize their
schedules.
6. Checks if the information provided in
the search function matches the
information from the database.
7. System informs the healthcare
provider that no matching records
were found based on the provided
criteria (if the search yields no
results)
21
 6. Checks if the information provided in
the search function matches the
information from the database.

7. System informs the healthcare

provider that no matching records
were found based on the provided
criteria (if the healthcare provider
encounters an error during the
search)

Emergency Access and Alerts as a Healthcare Provider:

Actor Actions System Responses

1. Healthcare Provider Login (See 2. Shows a user-friendly dashboard

Login as a Healthcare Provider that displays relevant options for the
use case) health provider

3. Healthcare Provider navigates to 4. System monitors critical health

the “Emergency Access and updates and emergencies in real-
Alerts” section time.

5. Healthcare provider receives 6. System generates an

immediate notification on the alert/notification indicating the nature
dashboard (if a critical health of the emergency or critical update.
update or emergency occurs for
a patient under the care of the
healthcare provider)

7. Healthcare provider 8. System provides detailed information

acknowledges and takes about the emergency, patient details,
necessary actions based on the and recommended actions. It also
alert allows customization of emergency
contact lists for each patient.

22
Alternative Scenarios

6. System generates an
alert/notification indicating the nature
of the emergency or critical update (if
there are multiple simultaneous
emergencies or critical health
updates)

7. The system prioritizes and displays

alerts based on severity. It will allow
the healthcare provider to navigate
through the list of alerts and respond
accordingly.

6. System generates an
alert/notification indicating the nature
of the emergency or critical update (if
the healthcare provider encounters
an error in receiving alerts)

7. The system displays an error

message and advises the healthcare
provider to contact technical support

Emergency Data Backup as a System Administrator:

Actor Actions System Responses

1. System Administrator Login (See 2. Shows a user-friendly dashboard that

Login as a System Administrator displays relevant options for the
use case) system administrator. It also alerts
and notifies the System Administrator
about any emergency situation.

23
 3. Healthcare Provider navigates to
the “Emergency Data Backup”
section
5. System Administrator confirms
the initiation of the emergency
data backup process
Alternative Scenarios
4. System provides options for initiating
the automatic backup process for all
patient data stored in the
HealthConnect Portal. Backup
includes comprehensive patient
information, medical records, and
related data.
6. System utilizes secure cloud storage
for immediate backup and recovery.
Backup process ensures redundancy
and data integrity.
7. System generates a confirmation
report indicating the success of the
emergency data backup.
4. System provides options for initiating
the automatic backup process for all
patient data stored in the
HealthConnect Portal (if the
automatic backup process
encounters an error)
5. System generates an error message
and logs the issue for review by
technical support. Emergency data
backup may be attempted again
once the issue is resolved.
24
 4. System provides options for initiating
the automatic backup process for all
patient data stored in the
HealthConnect Portal (if there are
limitations or delays in cloud storage
availability during the emergency)

5. System provides alternative backup

mechanisms, such as on-site backup
or secondary cloud storage. The
system administrator is notified of the
temporary backup solution and any
potential impact on data access.

Register a New User as a System Administrator:

Actor Actions System Responses

1. System Administrator Login (See 2. Shows a user-friendly dashboard

Login as a System Administrator that displays relevant options for the
use case) system administrator. Regular audits
are conducted to review user
accounts and ensure compliance
with security protocols

3. System Administrator navigates 4. System displays a form with required

to the “Add New User” section fields for entering new user
information, which includes:

• First Name
• Last Name
• Password
• Email Address
• Account Status (Patient,
Healthcare Provider, or
System Administrator)
• Mobile Number

25
 5. System Administrator fills up the
required fields for the new user
and clicks “Add” or “Create New
User” button to initiate the user
creation process
Alternative Scenarios
6. System validates the entered
information to ensure completeness
and correctness
7. System generates a confirmation
message indicating that the new user
has been successfully added (if
validation is successful, the system
adds the new user to the
HealthConnect Portal database)
8. The new user receives a notification
with login credentials and
instructions to access the
HealthConnect Portal
6. System validates the entered
information, ensuring completeness
and correctness (if the System
Administrator encounters an error
during the user creation process)
7. It will display an error message
indicating the issue (e.g., incomplete
information, duplicate ID). System
prompts the System Administrator to
correct the error and resubmit the
user creation form
26
6. System validates the entered
information to ensure completeness
and correctness (if the System
Administrator decides not to proceed
with adding the new user)

7. It will display a "Cancel" or "Go Back"

option to allow the System
Administrator to return to the main
dashboard without creating a new
user

6. System validates the entered

information to ensure completeness
and correctness (if there are
restrictions on the number of users
the system can accommodate)

7. It will notify the System Administrator

if adding a new user would exceed
the system's capacity

27
2.6 GUIs

Figure 2: Login GUI for HealthConnect Portal Version 0.3

Figure 3: Admin-Patient GUI for HealthConnect Portal Version 0.3

28
Figure 4: Admin-Update Patient GUI for HealthConnect Portal Version 0.3

Figure 5: Admin-Update Healthcare Provider GUI for HealthConnect Portal

Version 0.3

29
 Figure 6: Patient-Home GUI for HealthConnect Portal Version 0.3

Figure 7: Patient-Diagnosis GUI for HealthConnect Portal Version 0.3

30
 Figure 8: Healthcare Provider-Dashboard GUI for HealthConnect Portal Version 0.3

Figure 8: Healthcare Provider-Patient Diagnosis GUI for HealthConnect Portal Version 0.3

31
2.7 Screen Layout

Figure 9: HealthConnect Portal Screen Layout Version 0.3

2.8 Reports/Forms

The program to be made requires users to submit information regarding

themselves and their conditions that will be used for them to have access to the
project application and its functions. Below are the needed data information:

MAKATI MEDICAL CENTER STAFF

REQUIRED INFORMATION OPTIMAL INFORMATION

● Username ● Second Name

● Password ● Middle Name
● Email Address ● Sex
● First Name ● Telephone Number
● Last Name
● Department
● Account Status
● Mobile Number

32
 PATIENT

REQUIRED INFORMATION OPTIMAL INFORMATION

● Username ● Assigned Room Number

● Password ● Telephone Number
● Email Address ● Address
● First Name ● Postal/Zip Code
● Last Name ● Province/CIty
● Second Name
● Middle Name
● Sex
● Assigned Doctor
● Diagnosis
● Account Status
● Mobile Number

Additionally, the application will also provide diagnosis reports based on the data
submitted by the patient. For example, if patient A is diagnosed with hyperthyroidism,
the data from her most recent blood testing will be analyzed by their respective
assigned doctor who will produce a check-up result. The check-up result includes the
doctor’s comments about the patient’s results, instructions for them to follow, and
prescriptions.

2.9 Modules

I. User Management Module

This module is responsible for managing user-related operations, including

registration, login, and user roles and permissions.

Functionalities:

• User registration for healthcare providers, administrators, and system

administrators.

• User login with secure authentication.

• User role management and permission assignments.

33
 II. Patient Information Module

This module focuses on handling and updating patient-related data within the
HealthConnect Portal.

Functionalities:

• Input and update of comprehensive patient details by healthcare

providers.

• Storage and retrieval of medical history, diagnoses, and treatment

plans.

• Patient portal for secure access to personal medical information.

III. Appointment Scheduling Module

This module facilitates the scheduling of appointments, ensuring efficient

coordination between patients and healthcare providers.

Functionalities:

• Patients can request and schedule appointments online.

• Calendar view for healthcare providers to manage appointments.

• Confirmation notifications for scheduled appointments.

IV. Search and Reporting Module

This module provides healthcare providers with tools to quickly locate patient
records and analyze data trends.

Functionalities:

34
 • Search functionality to locate specific patient records based on
various criteria.

• Calendar view for managing appointments.

• Reporting tools for in-depth analysis of patient data and trends.

V. Emergency Access and Alerts Module

This module ensures prompt communication of critical health updates or

emergencies to healthcare providers.

Functionalities:

• System-generated alerts for critical health updates.

• Customizable emergency contact lists for each patient.

• Real-time notifications for healthcare providers.

VI. Data Backup Module

This module is responsible for automatically backing up patient data to

prevent loss during emergencies.

Functionalities:

• Automatic backup of patient data to secure cloud storage.

• Alternative backup mechanisms for data integrity.

• Regular testing of disaster recovery procedures.

35
 3.0 SYSTEM CODING

This chapter details the programming language and database to be used in creating the
program application.

3.1 Programming Language

HTML, CSS, JavaScript, and Node.js are the selected programming languages for
the system. HTML and CSS contribute to the front-end structure and styling, while
JavaScript, along with Node.js, is used for dynamic and server-side scripting.

3.2 Database

The project utilizes SQLite as the database system. SQLite is a lightweight,

embedded database that ensures efficient data management and retrieval.

4.0 RESOURCE REQUIREMENTS

This chapter details the identified hardware and software requirements needed
for the project to be implemented.

4.1 Hardware Requirements

The system demands a dedicated server with robust specifications to ensure optimal
performance. Recommended specifications include a multi-core processor (e.g., Intel
Xeon or AMD Ryzen), ample RAM (e.g., 16GB or higher), and sufficient storage
capacity with a solid-state drive (SSD) for enhanced data retrieval speed.
Additionally, a reliable internet connection is essential for real-time data access and
seamless user interactions.

4.2 Software Requirements

The software stack encompasses both Mac and Microsoft environments, providing
flexibility in deployment.

36
 • Operating System - For the server, a Unix-based system is recommended,
such as a Linux distribution like Ubuntu Server. Development environments
include compatibility with macOS for Apple users and Windows for Microsoft
users.

• Runtime Environment - Node.js is used as the runtime environment for

executing JavaScript code server-side, supporting both macOS and Windows
environments.

• Database Management System - SQLite, the chosen database management

system, is compatible with both macOS and Windows, ensuring seamless data
management.

Appendices

Appendix A: GUI Mockups

A.1 Login Interface

The login screen contains two text fields for the user to their username and corresponding
password. The login button is placed at the bottom right of the interface.

37
A.2 Admin-Patient List Interface

The Admin-Patient Interface contains the Patient List at the center panel, the number of
patients and search function on the right while the buttons for updating patient info are
placed on the left side.

A.3 Admin-Update Patient Interface

The Admin-Update Patient Interface is responsible for updating the patients’ records. The
text fields are used to fill up the required and optimal data about the patients. The admin
can also search, create, update, and delete patient information using the buttons on the
right side of the interface.

38
A.5 Admin-Update Healthcare Provider Interface

The Admin-Update Healthcare Provider Interface is responsible for updating the health
care providers’ records. The text fields are used to fill up the required and optimal data
about the healthcare providers. The admin can also search, create, update, and delete
healthcare provider information using the buttons on the bottom part of the interface.

A.6 Patient-Home Interface

The Patient-Home Interface is composed of the welcoming panel on the patient screen. It
also contains the basic information about a specific patient and the assigned healthcare
provider to them. The patient’s diagnosis tab is also located at the bottom left corner of the
interface.

39
A.7 Patient-Diagnosis Interface

The Patient-Diagnosis Interface is consisted of each patient’s diagnosis such as the

doctor’s note and their prescriptions. If the patient decides to return to the home (welcome)
panel, they can easily navigate back by pressing the home button at the left panel of the
interface.

A.8 Healthcare Provider-Dashboard Interface

The Healthcare Provider-Dashboard Interface contains the patient list at the center panel
so they can easily access each patient’s health record by typing their username at the
bottom right search function. They can also track the number of patients on the left panel
located above the search function.

40
 A.9 Healthcare Provider-Patient Diagnosis Interface

The Healthcare Provider-Patient Diagnosis Interface is composed of the patients’ name

information, doctor’s note, and their prescriptions which are accessible to the healthcare
provider in order to monitor their patient’s current diagnosis. They can also search and
update their patients’ diagnosis and prescriptions on the right side of the interface.

Appendix B: Screen Layout

B.1 General Screen Layout

The general screen layout provides a general view of where the elements of the GUIs are
located on the screen. The logo is located at the top right of the panel, the sidebar
navigation is at the leftmost section, the header occupies most of the top right panel, and
the main components container is located at the rightmost part of the screen.

41