FACULTY OF ENGINEERING & TECHNOLOGY

Department of Computer Engineering

01CE0607 - Software Engineering – Lab Manual
Practical 5

System Analysis and Design for the Selected System

Aim: Perform system analysis on selected system. 1)Systems analysis (what the system should do)
2) Systems design (how to accomplish the objective of the system.)

5. System Analysis and Design

The Medical Record Management System (MRMS) is a software solution designed to manage
patient health records and streamline medical practice operations. This system automates the
management of patient information, diagnosis history, treatment plans, appointments, prescriptions,
and billing, allowing doctors to offer more efficient and error-free care. By centralizing all medical
records in a secure and accessible digital format, the system enhances the quality of care, ensures
patient privacy, and improves overall practice management.

5.1 System Analysis

The Medical Record Management System aims to meet the following key objectives:

 Efficient Patient Management: Maintain an up-to-date and organized record of patients,

including medical history, diagnoses, treatment plans, and prescription details.
 Automated Appointment and Scheduling: Allow patients to schedule appointments, track
availability, and automatically send reminders for upcoming visits or treatments.
 Medical Record Access and Update: Facilitate real-time access for doctors to patient
records and history for faster diagnoses and treatment planning.
 Prescription Management: Enable doctors to write, update, and track prescriptions, with
automatic alerts for drug interactions or allergies.
 Billing and Insurance Integration: Manage billing processes, insurance claim processing,
and patient payment tracking efficiently.
 Reporting and Analytics: Generate medical reports, treatment outcomes, and financial
reports to help doctors make informed clinical decisions and manage the practice effectively.
 Security and Data Privacy: Secure storage of sensitive patient data, ensuring compliance
with health regulations (e.g., HIPAA).

5.1.1Gather System Requirements

The system will consist of the following modules to ensure seamless operation for medical
professionals:

Functional Requirements:

1. User Management Module:

o Secure login and role-based access control for doctors, patients, administrative staff,
and insurance agents.
o Doctors can update and manage patient records, treatment history, and prescriptions.
2. Patient Management Module:

Hiren (92200103148) 1 TC5 - A Batch

FACULTY OF ENGINEERING & TECHNOLOGY
Department of Computer Engineering
o Provides a comprehensive patient database 01CE0607 - Software
including Engineering
personal details, –medical
Lab Manual
history, and visit history.
o Doctors can view previous treatments, diagnoses, and lab results for each patient.
3. Appointment Scheduling Module:
o Allows patients to request appointments and doctors to schedule visits.
o Sends reminders for upcoming appointments via email/SMS.
4. Medical Record Management Module:
o Doctors can update patient medical records with diagnoses, prescriptions, treatments,
and notes.
o Keeps a comprehensive log of all interactions with the patient’s health history.
5. Prescription Management Module:
o Doctors can write prescriptions, track previous medications, and monitor any
potential drug interactions.
o Automatically sends prescriptions to pharmacy systems for fulfillment.
6. Billing and Insurance Module:
o Automates the billing process for treatments, consultations, and medications.
o Integrates with insurance companies to process claims and reimbursements.
7. Reporting and Analytics Module:
o Generates reports on patient progress, financial health, treatment efficacy, and
practice performance.
o Helps doctors analyze treatment success and patient demographics for better
decision-making.

Non-Functional Requirements:

 Performance: The system must ensure quick access to patient records and appointment
scheduling, especially during peak usage times.
 Scalability: Should support growing patient data and user load, especially as the
practice expands.
 Security: Ensures encrypted storage and transmission of sensitive medical data, with
role-based access control.
 Maintainability: The system should be modular to allow for easy updates or new
feature additions.
 Reliability: The system should be available 24/7, ensuring minimal downtime for
doctors or patients accessing records or scheduling appointments.

5.1.2 Analyze the Current System

Existing Issues

 Manual Record-Keeping: Many practices still rely on paper records or outdated digital
systems, leading to inconsistent data, difficult access, and potential loss of records.
 Scheduling Conflicts: Manual appointment scheduling leads to missed appointments,
double bookings, and inefficient time management.
 Drug Interaction and Prescription Errors: Current systems may not flag dangerous drug
interactions, allergies, or incorrect prescriptions.

Hiren (92200103148) 2 TC5 - A Batch

FACULTY OF ENGINEERING & TECHNOLOGY
Department of Computer Engineering
 01CE0607
Billing Discrepancies: Manual billing processes can - Software
result in errors in Engineering – Lab Manual
payments, insurance
claims, and discrepancies in billing codes.
 Lack of Real-Time Updates: Doctors are unable to access up-to-date information from
other healthcare providers or systems, which may delay treatment decisions.

Gaps Identified
 Centralized Patient Database: A centralized database is essential to track patient data, medical
history, and appointments in one place.
 Automated Prescription Management: The system should have a mechanism to alert doctors about
potential medication interactions or allergies.
 Integrated Billing and Insurance: The system should have the ability to handle both patient billing
and integration with insurance companies.
 Real-Time Notifications: The system should alert patients and doctors about upcoming
appointments, prescription refills, and any changes to the schedule.

5.2 System Design

System design refers to translating the requirements into a blueprint that outlines how the various
system components work together to provide a seamless experience.

5.2.1 Architectural Design

The Medical Record Management System follows a three-tier architecture:

1. Presentation Layer:
o A web-based interface for doctors, patients, and administrative staff to interact with
the system. This layer also allows for mobile access.
2. Business Logic Layer:
o Handles patient data management, prescription processing, billing, and appointment
scheduling. This layer integrates logic for decision-making (e.g., sending alerts for
drug interactions).
3. Database Layer:
o Stores patient information, treatment history, prescriptions, appointment records,
billing details, and insurance claims. This layer uses a relational database model for
efficient data retrieval.

5.2.2 User Interface Design

The user interface is designed to be simple and user-friendly for all stakeholders:

1. Login Page:
o A secure login page with role-based authentication for doctors, patients, and
administrative staff.
2. Doctor Dashboard:
o Includes patient management, prescription writing, and appointment scheduling
options, with a quick view of upcoming consultations and treatment histories.
3. Patient Dashboard:

Hiren (92200103148) 3 TC5 - A Batch

FACULTY OF ENGINEERING & TECHNOLOGY
Department of Computer Engineering
o Allows patients to book appointments, check01CE0607 - Software
their medical Engineering
history, – Laband
prescriptions, Manual
bills.
4. Appointment Scheduling Interface:
o Simple calendar view with available time slots for easy booking and management of
patient visits.
5. Prescription Writing Interface:
o Doctors can write prescriptions, check for drug interactions, and send prescriptions
directly to pharmacies.
6. Billing and Insurance Interface:
o Displays patient charges, insurance coverage details, and payment options.

5.2.3 Module Description

 User Management Module:
o Manages user profiles, access control, and login credentials, ensuring role-based
access for doctors, patients, and staff.
 Patient Management Module:
o Tracks patient details, medical history, appointments, and health conditions, enabling
doctors to review past diagnoses and treatments quickly.
 Appointment Scheduling Module:
o Allows patients to schedule visits, manage doctor availability, and send reminders to
both patients and doctors.
 Prescription Management Module:
o Allows doctors to prescribe medications, check for drug interactions, and
automatically update patient medication records.
 Billing and Insurance Module:
o Manages billing records, insurance claims, payments, and reconciles accounts to
prevent errors.
 Reporting and Analytics Module:
o Provides comprehensive reporting on patient outcomes, treatment success rates,
billing, and practice performance.

5.2.4 Database Design and ER diagram

The database follows a relational model, organizing entities such as patients, doctors,
appointments, prescriptions, and payments.

Entities and Relationships:

1. User (User_ID, Name, Role, Email, Password, Contact_Info) – Defines system users
(Doctor, Patient, Admin).
2. Patient (Patient_ID, User_ID, Date_of_Birth, Medical_History, Allergies,
Contact_Info) – Stores detailed patient data and health history.
3. Appointment (Appointment_ID, Patient_ID, Doctor_ID, Appointment_Date, Status) –
Links patients to scheduled visits.
4. Prescription (Prescription_ID, Patient_ID, Doctor_ID, Medication, Dosage, Start_Date,
End_Date) – Tracks medications prescribed to patients.
5. Payment (Payment_ID, Patient_ID, Amount, Payment_Date, Insurance_Status, Status)
– Tracks billing, insurance claims, and payments made by patients.

Hiren (92200103148) 4 TC5 - A Batch

FACULTY OF ENGINEERING & TECHNOLOGY
Department of Computer Engineering
01CE0607 - Software Engineering – Lab Manual

Flow Chart

Schema diagram

Hiren (92200103148) 5 TC5 - A Batch

FACULTY OF ENGINEERING & TECHNOLOGY
Department of Computer Engineering
01CE0607 - Software Engineering – Lab Manual

System Architecture diagram

Sequence Diagram

Hiren (92200103148) 6 TC5 - A Batch

ER Diagram

Enroll no. Class-Batch