Faculty of Science

Department of Mathematics and Computer Science

Software Engineering (CMPS 344)

Medical File

Student Name: Student ID:

Mohamad Ezzo 202203099
Ali Ismail 202302947
Ahmad Nasser 202302528
Hamza Shamseddine 202205005
 May, 2024
Abstract
The medical file project is a digital database system and a web-application user

friendly interface using firebase as that stores and organizes patient information,

medical records, treatment plans, and other medical data in a secure and efficient

manner. The project aims to streamline the healthcare process by providing

healthcare providers with easy access to patient information, reducing errors and

improving patient care.

The system will allow healthcare providers to create and update patient profiles,

schedule appointments, input diagnosis and treatment details, track medication

usage, and store test results. It will also have the ability to generate reports, send

alerts and reminders to patients, and facilitate communication between different

healthcare providers.

The medical file project will prioritize patient privacy and data security by

implementing strict access controls, encryption measures, and regular data backups.

It will comply with all relevant healthcare regulations and standards to ensure patient

confidentiality and data integrity.

Overall, the medical file project seeks to enhance the efficiency and effectiveness of

healthcare delivery, improve patient outcomes, and provide a comprehensive and

user-friendly platform for healthcare providers to access and manage patient

information.

Project proposal:
Title: Medical File Management System

1. Introduction:
The Medical File Management System is a digital database and web application
project designed to streamline the healthcare process by organizing and storing
patient information, medical records, treatment plans, and other relevant medical
data. This proposal outlines the objectives, features, and benefits of the project.

2. Objectives:
- To create a user-friendly interface for healthcare providers to manage patient
information efficiently.
- To improve the accuracy and accessibility of medical records.
- To reduce errors in diagnosis and treatment through organized data management.
- To enhance patient care by providing healthcare professionals with real-time
access to critical information.
- To ensure data security and confidentiality through robust encryption measures.
3. Features:
- Secure login system for healthcare providers to access patient information.
- Digital storage of medical records, treatment plans, and test results.
- Ability to update and track changes in patient information in real-time.
- Search functionality for quick retrieval of patient data.
- Customizable user permissions to control access to sensitive information.
- Integration with Firebase for secure cloud storage and real-time data
management.
-Easily to contact between the patient and the doctors.

4. Benefits:
- Improved efficiency in healthcare processes by reducing paperwork and manual
data entry.
- Enhanced accuracy in diagnosis and treatment through up-to-date patient
information.
- Better coordination of care among healthcare providers through centralized data
storage.
- Increased patient satisfaction through streamlined and organized medical records.
- Cost-effective solution for healthcare facilities through digital data management.

5. Implementation Plan:
- Conduct a thorough analysis of existing systems and workflows in healthcare
facilities.
- Design a user-friendly interface based on feedback from healthcare providers and
administrators.
- Develop the database structure and integrate Firebase for secure data storage.
- Conduct user testing and feedback sessions to ensure the system meets the needs
of healthcare professionals.
- Implement the Medical File Management System in a pilot program at select
healthcare facilities.
- Evaluate the system's effectiveness and make necessary improvements based on
user feedback.

6. Conclusion:
The Medical File Management System aims to revolutionize healthcare data
management by providing a secure, efficient, and user-friendly solution for storing
and accessing patient information. By leveraging the power of digital technology
and cloud storage, healthcare providers can deliver better patient care and improve
healthcare outcomes.
Research for a Medical File Project may involve the following steps:
1. Literature Review:
- Review existing literature on electronic health record (EHR) systems, medical
file management systems, and healthcare data management.
- Identify key challenges and trends in healthcare data management.
- Explore case studies and best practices in implementing digital healthcare
solutions.

2. Stakeholder Interviews:
- Conduct interviews with healthcare providers, administrators, and IT
professionals to understand their current systems, challenges, and needs.
- Gather feedback on desired features, usability requirements, and security
concerns for a medical file management system.
- Identify key stakeholders and decision-makers involved in the implementation of
the project.
3. Market Analysis:
- Research existing medical file management systems and electronic health record
(EHR) solutions in the market.
- Assess the strengths and weaknesses of competing products.
- Identify gaps or opportunities for innovation in the healthcare data management
sector.

4. Regulatory Compliance:
- Understand the regulatory requirements and standards for healthcare data
management (e.g., HIPAA compliance).
- Ensure that the proposed medical file management system adheres to data
security and privacy regulations.
- Consider the implications of data protection laws and guidelines on the
implementation of the project.

5. Technology Assessment:
- Evaluate different database systems, web application development platforms, and
cloud storage solutions for the project.
- Consider the scalability, interoperability, and security features of the technology
stack.
- Identify potential risks and challenges in implementing the chosen technology
solutions.

6. User Experience Design:

- Conduct user surveys or focus groups to gather insights on user preferences,
workflow requirements, and usability expectations.
- Work with UX/UI designers to create wireframes and prototypes of the medical
file management system.
- Incorporate user feedback and iterate on the design to ensure a user-friendly and
intuitive interface.

7. Data Security Analysis:

- Assess data security risks and vulnerabilities in healthcare data management
systems.
- Implement encryption protocols, access control mechanisms, and audit trails to
protect sensitive patient information.
- Develop a data security plan and contingency measures to mitigate potential
security threats.

By conducting comprehensive research across these areas, the Medical File Project
team can gather valuable insights, identify key requirements, and make informed
decisions to develop a successful and impactful healthcare data management
solution.
Project plan:
Task / Name Hamza Ali Al Hadi Mohammad Ahmad
Shamsdin Ismail Ezzo Nasser
Task 1: X X X X
Distribute
yourselves into
groups
Task 2 : X _____ X _____
Project Idea
and Goals
Task 3 : X X ______ _____
Feasibility
Study
 Task 4 : ______ X X X
Functional and
Non-functional
Requirements
Task 5: Design X ______ X X
Task 6: _______ X X ________
Implementation
Task 7 : X X _______ X
Testing

Task 8 : ______ _______ X X

Maintenance

This table outlines the tasks to be completed by the 4 students working on the
Medical File Project, along with their assigned deadlines and current status. It
provides a clear overview of the project plan and helps track progress throughout
the duration of the project.
Description Amount/Rate

Fixed costs 85.000$

Initial Development Cost 85,000$

Variable Costs 22,000$

Hardware Setup 15,000$

Revenue Streams (per year) 30,000$

Subscription Fee (per year) 15,000$

 Ongoing Costs(per year) 23,000$

Breakeven Points 3.86

Contribution Margin per Sale 22,000$

TOTAL : $315,860
 Table of Contents
Chapter 1. Introduction ...................................................................................................................... 10
Chapter 2. Project Plan ....................................................................................................................... 12
A. SDLC Model............................................................................................................................ 12
B. Ethical standards and guidelines ............................................................................................ 13
F. Schedule/Timeline ................................................................................................................... 14
G. Feasibility Study...................................................................................................................... 14
Chapter 3. Software Requirement Specification ................................................................................ 16
A. Non-functional Requirements................................................................................................. 16
B. Domain Requirements ............................................................................................................ 17
C. Functional Requirements........................................................................................................ 17
Chapter 4. Project Design: .................................................................................................................. 18
A.Use Case Diagram: ....................................................................................................................... 18
B.Use Case Description:................................................................................................................... 19
Technology Stack For Medical File Management System (Lab 11) :............................................. 22
Chapter 5. Methodology ...................................................................................................................... 24
Chapter 6. Conclusion and Future Work ........................................................................................... 26
Chapter 7. References ......................................................................................................................... 27
Appendices ........................................................................................................................................... 28

Chapter 1. Introduction

A. Main Project Description

The Medical File project aims to develop a digital database system and web
application interface that will streamline the healthcare process by efficiently
storing and organizing patient information, medical records, treatment plans, and
other medical data. This project will investigate research areas related to data
management, information security, and user experience in the healthcare industry.
The main problem that the project addresses is the need for a secure and user-
friendly system that provides healthcare providers easy access to accurate patient
information, thereby reducing errors and enhancing patient care.

B. Problem Statement
The primary problem that the Medical File project seeks to solve is the inefficiency
and potential errors in traditional paper-based medical record systems. Sub-
problems include issues with data accessibility, security, and organization. By
transitioning to a digital database system, the project aims to mitigate these
problems and improve overall healthcare processes.

C. Project Goal
The goal of the Medical File project is to create a user-friendly and secure platform
that allows healthcare providers to easily access and manage patient information.
By completing the project, we aim to improve the accuracy of medical records,
reduce errors in diagnosis and treatment, and enhance overall patient care. The
target audience for this project includes healthcare professionals, medical
administrators, and other staff involved in patient care.

D. System and Domain Review/Background

Existing systems in the healthcare industry often rely on outdated paper-based
record-keeping methods, which can lead to inefficiencies, errors, and security
risks. Alternative systems include electronic health record (EHR) systems, which
offer digital storage of patient data but may have complex interfaces and limited
accessibility. The Medical File project differentiates itself by providing a user-
friendly interface, real-time access to information, robust security features, and
efficient data management. From the user's point of view, the system will stand out
for its ease of use, accessibility, and enhanced organization of patient records.
Chapter 2. Project Plan

A. SDLC Model
For the Medical File Project, we will be using the Extreme Programming (XP)
software development lifecycle process model. Extreme Programming is an agile
methodology that emphasizes flexibility, continuous feedback, collaboration, and
customer involvement throughout the development process.

We chose Extreme Programming for the Medical File Project for the following
reasons:

1. Emphasis on Customer Involvement: XP places a strong focus on customer

involvement and feedback. In the context of the Medical File Project, involving
healthcare providers, administrators, and other stakeholders in the development
process will ensure that the medical file management system meets their specific
needs and requirements.

2. Flexibility and Adaptability: XP is known for its flexibility and ability to adapt
to changing requirements. In the healthcare industry, where regulations and
technology trends constantly evolve, having a flexible methodology like XP allows
us to respond quickly to changes and incorporate feedback in a timely manner.

3. Continuous Testing and Integration: XP promotes continuous testing and

integration, which is crucial for ensuring the reliability and security of a medical
file management system. By incorporating automated testing and frequent
integration, we can detect and address issues early in the development process.

4. Collaborative Team Environment: XP encourages close collaboration among

team members, which is essential for a project involving multiple stakeholders and
complex requirements. By fostering a collaborative team environment, we can
ensure effective communication, knowledge sharing, and problem-solving
throughout the project.

5. Iterative Development: XP follows an iterative development approach, where

features are developed incrementally and delivered in short iterations. This
iterative approach allows us to quickly deliver functional components of the
medical file management system, gather feedback from stakeholders, and make
adjustments as needed.

Overall, the Extreme Programming model aligns well with the goals and
requirements of the Medical File Project, as it promotes customer involvement,
flexibility, continuous testing, collaboration, and iterative development. These
characteristics make XP a suitable methodology for developing a reliable and user-
centric medical file management system.

B. Ethical standards and guidelines

For a medical file management system project, several ethical principles and
guidelines are crucial to ensure responsible and secure handling of sensitive patient
information. Here are key principles and corresponding strategies to address them:

C. Patient Confidentiality:
a. Strategy: Implement robust data encryption, role-based access
controls, and audit trails to safeguard patient confidentiality. Ensure
that only authorized personnel have access to sensitive medical
information.
D. Informed Consent:
a. Strategy: Prioritize clear communication with patients about data
usage, storage, and access policies. Develop user-friendly interfaces
for obtaining and documenting informed consent within the system.
E. Data Security and Privacy:
a. Strategy: Adhere to industry-standard security protocols, regularly
update security measures, and conduct thorough security audits.
Establish strict access controls, ensuring that only necessary personnel
can access and modify patient records.
 F. Schedule/Timeline
Provide a rough schedule for each member or sub-group within your team.
For example, how long do you believe your developers will spend working
on each major feature listed in your product description? Who will work on
the design, and how much time do you expect it will take? For each feature,
when will it be complete (give a milestone, such as by the beta release)?

G. Feasibility Study

Risk Management:

Developing a medical portal involves handling potential issues, such as

ensuring data security and system functionality. We proactively plan for these
challenges, implementing measures similar to securing a digital fortress.
Additionally, having contingency plans in place allows us to respond quickly to
unexpected hurdles, ensuring the project's success and smooth operation.

Technical Feasibility

1. System Architecture: Assess the compatibility and scalability of the

proposed Health Portal software with existing healthcare infrastructure.
2. Data Security: Evaluate the technical measures implemented to ensure the
confidentiality and integrity of sensitive medical files within the portal.
3. Interoperability: Examine the portal's ability to integrate with other
healthcare systems, facilitating seamless data exchange and collaboration.
4. Performance Testing: Conduct rigorous tests to verify the portal's
efficiency, responsiveness, and overall performance under varying user
loads and conditions.

Economic Feasibility

1. Cost-Benefit Analysis: Evaluate the financial investment required for

developing and maintaining the Health Portal against the anticipated long-
 term benefits, including increased efficiency and reduced administrative
costs.
2. Return on Investment (ROI): Assess the potential return on investment by
considering factors such as improved healthcare operations, reduced
paperwork, and enhanced patient care.
3. Budget Considerations: Examine the project's economic viability by
ensuring that the development costs align with the available budget, taking
into account potential cost savings and revenue generation.

Delivery
Define the documentation that you plan to deliver with the system, e.g., user
guides, admin guides, man pages, help menus.
Chapter 3. Software Requirement Specification

A. Non-functional Requirements:
Non-Functional Requirements for Medical File Management System:
Requirement Description

Performance The system should be quick and responsive, allowing healthcare

providers to access information without delays.

Security Patient data must be kept safe, with measures in place to prevent
unauthorized access or breaches.

Usability The interface should be easy to use, ensuring healthcare providers

can navigate and manage files efficiently.

Scalability It needs to handle more users as the system grows, ensuring it doesn't
get slow or overloaded.
 B.Domain Requirements:

Requirement Description
Emergency Establish protocols for emergency access to critical patient
Access information, ensuring timely and secure access during urgent
Protocols situations.

Multilingual Provide support for multiple languages to accommodate diverse

Support: healthcare professionals and patients.

C.Functional Requirements
Functional Requirements for Medical File Management System:
Requirement Description
User Implement secure login mechanisms for healthcare providers
Authentication: with unique identifiers, ensuring authorized access to the
system.
Patient
Registration: Enable healthcare providers to register and manage patient
information, including demographics, medical history, and
contact details.

Document Provide a centralized repository for storing and managing

Management: medical documents, such as test results, medical images, and
scanned documents.
Appointment Enable healthcare providers to schedule and manage patient
Scheduling: appointments efficiently, with features like automated
reminders and calendar integration..
Communication Incorporate secure communication features, such as
Tools: messaging and notifications, to facilitate collaboration among
healthcare professionals and ensure timely information
exchange.
Chapter 4. Project Design:

A.Use Case Diagram:

B.Use Case Description:

1-Log In:

 Description: Allows registered users to log in to their accounts.

 Actors: Patient
 Preconditions: User has a registered account
 Related Use Cases Includes:Verify Account-Booking Appointment-Chat-
Update Medical Records-Profile.
 Steps:

1. User navigates to the login page.

2. System presents the login form, prompting the user to enter their username
and password.
3. User enters their username and password into the respective fields.
4. System validates the entered credentials by checking against the database of
registered users.

2-Booking Appointment:

 Description: Allows registered patients to schedule appointments with

healthcare providers..
 Actors: Patient , Doctor
 Preconditions: User have loged in
 Related Use Cases Includes:Cancel appointment.
 Steps:

1. Patient navigates to the appointment booking section of the portal..

2. System presents the options for booking appointments, such as searching by
healthcare provider, specialty, or date.
3. Patient selects the preferred healthcare provider, specialty, or date for the
appointment.
3-Chat:

 Description: Enables patients to communicate with healthcare professionals

through a chat interface.
 Actors: Patient
 Preconditions: Patient is logged into the portal
 Related Use Cases Includes:Verify Account-Booking Appointment-Chat-
Update Medical Records-Profile.
 Steps:

1. Patient navigates to the chat section of the portal.

2. System displays the list of available healthcare professionals for chat.
3. Patient selects a healthcare professional they wish to chat with.

4-Profile:

 Description: Allows patients to view and manage their profile information,

including medical records and test results.
 Actors: Patient
 Preconditions: Patient is logged into the portal
 Related Use Cases Includes: View Billing Information / View Health
Tips/View Medical Records/View Test Results.
 Steps:

1. Patient navigates to the profile section of the portal.

2. System retrieves and displays the patient's profile information, including
personal details, medical history, and test results.
3. Patient views the displayed information, such as demographics,
allergies, medications, and past medical procedures.
4. If available, system provides the option to view test results and medical
records.
5. Patient selects the desired option to view test results or medical records.
6. System retrieves and displays the requested test results or medical
records.
7. Patient reviews the displayed test results or medical records.
8. Patient has the option to download, print, or share the test results or
medical records if needed.
5-Upload Medical Document:

 Description: Allows doctors to upload medical documents for patients.

 Actors: Doctor
 Preconditions: Patient is logged into the portal
 Related Use Cases:None.
 Steps:

1. Doctor navigates to the upload medical document section of the portal.

2. System presents the form for uploading medical documents, prompting
the doctor to provide necessary information.
3. Doctor fills in the required information, such as patient's details,
document type, and description.
4. Doctor selects the medical document file(s) to upload.
5. System validates the uploaded file format and size.
6. Doctor confirms the upload process.
7. System updates the patient's medical record with the uploaded
document(s) and logs the activity.

C. ER (Database)Diagram :
Technology Stack For Medical File Management System (Lab 11) :
Frontend: React.js
- React.js remains an ideal choice for the frontend, providing a powerful and
efficient way to create dynamic and responsive user interfaces for managing
medical data.

Backend: Node.js with Express.js

- Node.js with Express.js continues to be a suitable backend technology for
handling server-side logic, authentication, and integrating with the OracleDB.

Database: Oracle Database

- Oracle Database is a robust and reliable relational database management system
that is well-suited for managing structured healthcare data. It offers scalability,
high performance, security features, and advanced data management capabilities.

Security: HTTPS, OWASP security best practices, encryption algorithms

- The security measures, including HTTPS for data transfer, adherence to OWASP
security practices, and encryption algorithms for sensitive data storage, remain
crucial for protecting medical records.

Testing: Jest or Mocha for unit testing, Supertest for integration testing
- Jest or Mocha for unit tests and Supertest for integration testing can ensure the
reliability and functionality of the Medical File Management System while
utilizing OracleDB for data management.

Git version control:

https://github.com/JOKER3Z/Medical-File.git
Chapter 5. Methodology
A. Implementation:

- For this project, we will use a combination of off-the-shelf software

components and custom implementations. We plan to use a pre-built
database management system such as MySQL or PostgreSQL to store
all patient information securely. Additionally, we may utilize existing
libraries or frameworks for user authentication and access control.

- In terms of the software toolset, we will primarily be using

languages such as HTML, CSS, and JavaScript for the front-end
development. The back-end will be developed using javascript
alongside frameworks like react.js. These languages and tools were
chosen for their versatility, ease of use, and suitability for web
application development.

B. Testing:

- The aspects we plan to test include functionality, data integrity,

security, performance, and usability. We will conduct unit tests to
ensure individual components work as intended, system integration
tests to verify the interactions between different modules, and
usability tests to gauge user satisfaction and efficiency. We will use
automated testing tools like Selenium for web interface testing and
JUnit for unit testing. Additionally, we will create test suites based on
the software requirements outlined in the SRS to validate the system's
adherence to these requirements.

C. Maintenance:
- For version control, we will use Git along with a remote repository
hosting service like GitHub or Bitbucket. This will allow us to track
changes, collaborate with team members, and easily revert to previous
versions if needed. In terms of bug tracking, we may utilize tools like
Jira or Bugzilla to accurately record and manage software defects. We
will also implement continuous integration and deployment pipelines
using tools like Jenkins or Travis CI to automate the build, test, and
deployment process, ensuring rapid updates and bug fixes.
Chapter 6. Conclusion and Future Work

In conclusion, the medical file management system project has been successfully
developed, allowing medical professionals to efficiently manage patient records
and streamline the healthcare process. The system provides a secure and organized
platform for storing and retrieving sensitive patient information, improving overall
patient care and administrative efficiency.

Future work on this project could focus on enhancing the system's user interface
and functionality, as well as integrating more advanced features such as data
analytics and automated communication tools. Additionally, collaboration with
healthcare institutions and IT professionals can help in further refining the system
to meet the evolving needs of the healthcare industry.

Overall, the medical file management system project has the potential to greatly
benefit healthcare providers and patients alike, and continued development and
improvement will only serve to enhance its effectiveness in the future.
Chapter 7. References

https://www.wikipedia.org/
https://deep.ai/
https://erdplus.com/
Appendices

Appendices for Medical File Management System Project:

Appendix A: System Requirements Specification (SRS)

- This document includes a detailed list of functional and non-functional
requirements for the medical file management system. It outlines the features,
capabilities, and constraints that the system must adhere to.

Appendix B: Database Schema

- This appendix contains the schema design for the database that will be used to
store patient information, medical records, and other relevant data. It includes
tables, relationships, attributes, and data types.

Appendix C: Wireframes and Mockups

- This section includes visual representations of the user interface design for the
medical file management system. It provides a glimpse of how the system will
look and function, helping stakeholders visualize the end product.

Appendix D: Test Plan

- The test plan outlines the testing approach, strategies, methods, and tools that will
be used to validate the functionality, performance, and usability of the system. It
includes test cases, scenarios, and acceptance criteria.

Appendix E: Project Timeline

- This appendix includes a detailed project timeline that outlines the key
milestones, deliverables, deadlines, and dependencies for the development and
implementation of the medical file management system.
Appendix F: Budget and Resource Allocation
- This section outlines the estimated budget, resources, and costs associated with
the development, testing, maintenance, and support of the medical file
management system. It includes a breakdown of expenses and allocation of
resources.

Appendix G: Risk Management Plan

- The risk management plan identifies potential risks, threats, and challenges that
may impact the successful completion of the project. It includes risk assessment,
mitigation strategies, and contingency plans to address any unforeseen issues.

Appendix H: User Manual

- This appendix includes a user manual or guide that provides instructions,
guidelines, and tips for users on how to effectively use the medical file
management system. It includes information on system navigation, data entry, and
troubleshooting.

Appendix I: Glossary
- This section contains a glossary of terms and acronyms used throughout the
project documentation. It provides definitions and explanations for technical terms,
jargon, and industry-specific terminology.