Netaji Subhash Engineering College

Subject: Software Engineering

Topic: Hospital Management System
Subject Code: ESC591
GROUP-13

Roll No. Group Member

61 Suman Ghosh

62 Atreyee Paul

63 Susanta Bag

198 Abhirup Samanta

199 Akash Majumder

HOSPITAL MANAGEMENT
SYSTEM
 CONTENTS
Topic Page No.

1. Overview of the project ............................................... 4-5

Introduction To The Project
Objective Of The Project
Need Of Hospital Management Website
Why Us?
2. Feasibility Report .......................................................... 6-9
Economic Feasibility
Technical Feasibility
Operational Feasibility
Legal Feasibility
Schedule Feasibility
3. Conclusion 10
4. SDLC Phases for an Online Hospital Management
System using Agile model ........................................... 12-19
5. SRS .............................................................................. 20-33
7. COCOMO ..................................................................... 34-42
8. DFD and Data Dictionary.......................................... 43-61
9. UML Diagrams ......................................................... 62-69
10. Conclusion ................................................................... 70
1. Overview Of The Project
❑ Introduction
A Hospital Management System (HMS) is an integrated software solution
designed to manage the operations of a hospital or medical facility. It aims to
streamline processes, improve patient care, and enhance the overall efficiency
of the hospital's administrative and clinical functions.

❑ Objectives:
Efficient Management: To streamline and automate hospital operations such
as patient registration, appointment scheduling, and billing.
Improved Patient Care: To enhance patient care by providing timely and
accurate medical information.
Data Management: To ensure secure and efficient management of patient
and hospital data
Resource Optimization: To optimize the utilization of hospital resources
including staff, equipment, and facilities.

❑ Need for Hospital Management Website

Patient and Doctor Management: Online registration, appointment booking,

secure patient portal for accessing medical records, and doctor profiles with
scheduling and availability information.

Telemedicine and Virtual Consultation: Integrated platform for virtual

consultations, online prescription management, and video conferencing
capabilities.

Data Security and Compliance: Secure data storage and transmission,

compliance with healthcare regulations and regular security audits to
protect patient information.
❑ Why Us?

1. Comprehensive and Customizable Solutions: Our platform is

designed to meet the specific needs of hospitals and healthcare

providers, offering a range of features from patient

management to telemedicine. We provide customizable

solutions that can be tailored to the unique requirements of

your institution.

2. User-Friendly and Accessible Design: We prioritize user

experience, ensuring an intuitive and responsive design that is

easy to navigate for patients, doctors, and staff. Our websites

are accessible across all devices, providing seamless interaction

for all users.

3. Advanced Security and Compliance: Data security is our top

priority. We implement robust encryption methods and adhere

to strict healthcare regulations, ensuring your data is protected

and compliant with standards like HIPAA. Regular security

audits and updates keep your website safe from vulnerabilities.

1. Technical Feasibility

Hardware and Software Requirements:

Servers: Robust servers to host the HMS.
Workstations: Computers for staff access.
Network Infrastructure: Reliable internet and intranet connectivity.
Software: Operating systems, database management systems, and application
software.
Technical Expertise:
Development Team: Skilled developers with experience in healthcare software.
IT Support: Ongoing technical support for maintenance and troubleshooting.
Scalability:
System Scalability: The system should handle increased loads as the hospital
grows.
Integration: Ability to integrate with existing systems (e.g., laboratory, pharmacy,
radiology).
2. Economical Feasibility
The economic feasibility will determine if it's financially viable. It
involves a cost-benefit analysis to assess the project's profitability.

Financial model:

ITEM AMOUNT

Initial Investment 25,00,000

Operational Cost per Month 1,50,000

Monthly Revenue 4,00,000

Profit (after 1 year) 18,00,000

Break-even Months 10

Licensing and Others 25,00,000

 Technological Cost:

CATEGORY SUBCATEGORY COST (RS)

Frontend Development UI/UX Design 5,00,000

Development 7,00,000

Testing 3,00,000

Backend Development Server-side Logic 7,00,000

Database Integration 4,00,000

API Development 4,00,000

.... .... ....

Total 30,00,000

Amounts are in approx...

Total cost required: Rs. 80,00,000 approx

3. Operational Feasibility

Integration
Compatibility: Ensure the website integrates with existing hospital
systems and data.
Data Migration: Plan for smooth transfer of existing data.
User Training and Support
Training: Provide comprehensive staff training.
Support: Offer ongoing technical support and resources.
System Maintenance
Technical Support: Ensure reliable support for troubleshooting.
Updates: Regular updates and maintenance to keep the system
secure and current.
Workflow Integration
Process Alignment: Ensure the system enhances existing workflows.
Efficiency: Evaluate improvements in administrative tasks.
Scalability
Adaptability: Ensure the system can scale and adapt to future needs.
Customization: Verify that it can be customized for specific
requirements.

4. Legal Feasibility

Data Protection Compliance

IT Act, 2000: Adhere to data privacy and protection provisions.
Personal Data Protection Bill: Follow upcoming regulations on data
collection and processing.
Patient Privacy and Consent
Informed Consent: Obtain clear consent for data use and ensure
transparency.
Data Anonymization: Protect patient identities through
anonymization techniques.
Healthcare Regulations
Clinical Establishments Act, 2010: Follow standards for medical
record maintenance.
National Digital Health Blueprint (NDHB): Align with digital health
standards.
Intellectual Property
IPR Protection: Safeguard the website’s content and technology.
Accessibility
Rights of Persons with Disabilities Act, 2016: Ensure website accessibility for
all users.

5. Schedule Feasibility

Planning and Analysis (2-4 Weeks)

Requirements Gathering: Define needs and project scope.
Timeline Creation: Develop a project schedule.

Design Phase (4-6 Weeks)

UI/UX Design: Create and refine design prototypes.

Development Phase (8-12 Weeks)

Build: Develop front-end and back-end functionalities.
Integration and Security: Connect with existing systems and ensure data
protection.

Testing Phase (4-6 Weeks)

Functional and Security Testing: Ensure all features work and meet security
standards.
User Acceptance Testing: Validate with end-users.

Training and Implementation (2-4 Weeks)

Staff Training: Train users on the new system.
Deployment: Launch the website.

Post-Launch Support (Ongoing)

Monitoring and Maintenance: Track performance and provide updates.

Total Estimated Timeline: 20-32 Weeks

Overall Feasibility Conclusion

By analyzing the technical, economic, operational, legal, and schedule

aspects, we can determine the overall feasibility of the Hospital
Management System project. Suppose all aspects indicate that the
project can be successfully developed and implemented within the
available resources, budget, and timeframe while meeting all
regulatory requirements and operational needs. In that case, the
project is considered feasible.

Summary :
Technically Feasible: If the hospital has or can acquire the
necessary technical resources.
Economically Feasible: If the financial benefits exceed the costs.
Operationally Feasible: If it can be integrated smoothly and
supported by users.
Legally Feasible: If it complies with all relevant regulations and
ensures data security.
Schedule Feasible: If it can be completed within the proposed
timeframe.
 SDLC Phases for an Online Hospital Management System
Using Agile

Introduction to SDLC of an Online Hospital Management System

The Software Development Life Cycle (SDLC) for an online Hospital
Management System (HMS) involves a systematic approach to creating a user-
friendly and efficient platform that manages hospital operations. The HMS
integrates key functionalities like patient registration, appointment scheduling,
electronic medical records (EMR), billing, and administrative tasks, ensuring
smooth communication across departments.

The Agile development model is ideal for this project, enabling iterative
development, continuous feedback, and regular updates. This approach
ensures the system adapts to user needs and technological advancements.
The SDLC stages include thorough requirement analysis, meticulous design,
iterative development, rigorous testing, and continuous improvement,
ultimately delivering a high-quality system suited to the dynamic demands of
modern healthcare.
1. Requirements Gathering and Planning
Objective: The primary goal of this phase is to understand the project’s
scope and to prioritize the features that need to be developed. This sets
the foundation for the entire development process.
Activities:
Stakeholder Engagement: Collaborate closely with stakeholders,
including end-users, business analysts, and project managers, to
gather comprehensive requirements. This involves capturing user
stories that describe the desired functionality from the user’s
perspective.
Product Backlog Creation: Compile the gathered requirements into a
prioritized list known as the product backlog. This backlog is a
dynamic document that evolves as the project progresses.
Sprint Planning: Based on the product backlog, plan the first sprint by
selecting the most critical tasks. Could you define the sprint goals,
timelines, and resource allocation to make sure the team is aligned on
what needs to be accomplished in the upcoming iteration?

2. Design and Development

Objective: To design the system’s architecture and develop the
required features in iterative cycles, ensuring that each iteration results
in a potentially shippable product.
Activities:
System Design: Design the architecture and user interface of the
system based on the requirements gathered. This includes creating
wireframes, flowcharts, and database schemas that guide the
development process.
Iterative Development: Begin coding the features as outlined in the
sprint plan. Agile development focuses on building small, functional
parts of the system in each sprint, rather than trying to complete the
entire project in one go. This approach allows for early testing and
feedback.
Daily Stand-ups: Hold daily stand-up meetings where the
development team discusses progress, challenges, and plans for the
day. This ensures continuous communication and quick resolution of
any issues.
3. Testing and Deployment
Objective: To ensure that the developed product meets the required
quality standards and is ready for use in a live environment.
Activities:
Continuous Testing: Testing is integrated into each sprint, with
developers and testers working closely to identify and fix bugs as they
arise. Unit tests, integration tests, and user acceptance tests (UAT) are
conducted to verify that the product functions as intended.
Sprint Review: At the end of each sprint, the team demonstrates the
completed work to stakeholders during a sprint review meeting.
Feedback is collected, and any necessary adjustments are noted for the
next sprint.
Incremental Deployment: Deploy the functional product increment to a
staging or production environment. This deployment allows stakeholders
to interact with the new features and provides an opportunity to gather
real-world feedback.

4. Refinement and Enhancements

Objective: To continuously improve the product by refining existing
features and adding new functionalities based on feedback and evolving
requirements.
Activities:
Gathering Feedback: After each deployment, gather feedback from end-
users and stakeholders to identify areas for improvement. This feedback
is crucial for ensuring that the product remains aligned with user needs
and business goals.
Backlog Refinement: Update the product backlog with new requirements,
enhancements, and any adjustments needed based on user feedback.
This refined backlog will guide future sprints.
Ongoing Development: Continue the iterative cycle of development,
testing, and deployment. Each sprint builds on the previous one,
gradually enhancing the system’s functionality and usability. This
process continues until the product is fully refined and meets all the
project’s objectives.
Benefits of Using the Agile Model for the Hospital
Management System (HMS) Project

Flexibility : The Agile model supports quick adaptation to changing

healthcare regulations and evolving project requirements. This
flexibility is achieved through iterative development, allowing the
team to adjust the system in response to new information or
changes in the healthcare environment.
Continuous Feedback: Agile emphasizes regular collaboration with
stakeholders, including healthcare professionals, administrators,
and end-users. This ongoing feedback loop ensures the system is
aligned with real-world needs, leading to improved usability and
functionality tailored to the unique demands of a hospital
environment.
Faster Delivery : By breaking the project into smaller, manageable
increments, Agile enables the delivery of core features early in the
development process. These incremental releases provide
immediate value to the hospital while the development team
continues to enhance and expand the system. Additionally,
continuous testing ensures that each release maintains high
quality.
Risk Management: Agile’s iterative nature allows for early
identification and mitigation of risks. By delivering the essential
features first, the development team can address critical issues
and ensure that the project stays on track to meet deadlines and
objectives.
Enhanced Collaboration: Agile promotes a collaborative
environment where cross-functional teams work seamlessly.
Regular updates, transparency, and open communication ensure
that all team members are aligned and that the development
process remains comprehensive, covering all aspects of the
hospital’s needs.
Advantages of Agile over Other Models

Flexibility and Adaptability:

Unlike traditional models like Waterfall, Agile allows for changes at
any project stage. This flexibility is crucial for projects where
requirements can evolve, ensuring the final product meets current
user needs and industry standards.
Continuous Feedback and Improvement:
Agile promotes regular interaction with stakeholders, leading to
continuous feedback. This ongoing dialogue helps refine the product
throughout the development process, reducing the risk of delivering a
system that doesn't fully meet user expectations.
Faster Time-to-Market:
Agile’s iterative approach allows for incremental releases of
functional software. This means essential features can be delivered
quickly, providing immediate value to users while the development
continues, unlike models where the final product is only available at
the end of the development cycle.
Enhanced Collaboration and Communication:
Agile fosters a collaborative environment where cross-functional
teams work closely together. This improves communication and
ensures that all aspects of the project are aligned, leading to a more
cohesive and well-rounded final product.
Better Risk Management:
By delivering work in small, manageable increments, Agile allows for
the early identification and mitigation of risks. This proactive approach
helps prevent major issues from derailing the project, which is often a
challenge in more rigid models like Waterfall.
Higher Quality Through Continuous Testing:
Agile integrates testing into every iteration, allowing for continuous
quality assurance. This frequent testing helps catch and address
issues early, resulting in a more reliable and polished final product
than models that rely on end-phase testing.
Customer-Centric Development:
Agile places a strong emphasis on satisfying the customer through
early and continuous delivery of valuable software. This focus on
customer satisfaction ensures that the final product is more likely to
meet or exceed user expectations.
Iterative Process Overview and Implementation Plan

Iteration 1: Core Modules

Objective: Establish the foundational components of the HMS,
essential for the system's overall operation and future expansions.
Details:
1. User Authentication: Develop a secure authentication system that
includes user registration, login, password management, and user
roles. This will ensure that only authorized personnel have access
to specific areas of the system, maintaining security and
confidentiality.
2. Role-Based Access Control (RBAC): Implement role-based access
control, assigning different permissions to various user roles such
as doctors, nurses, administrators, and patients. This ensures that
each user can only access the information and functions relevant
to their role.
3. Dashboard Creation: Build a basic dashboard for users, providing a
centralized interface where they can access different
functionalities based on their roles. This dashboard will serve as
the main navigation hub, offering a clear overview of the system’s
capabilities.
4. Patient Management: Introduce a basic patient management
module that allows for patient registration, demographic data
entry, and appointment management. This module will form the
core of the patient-related operations within the system.

Iteration 2: Patient Interaction

Objective: Enhance patient engagement by integrating features
that facilitate direct interaction between patients and the
healthcare system.
Details:
1. Patient Portal Development: Create a patient portal that allows
patients to log in, view their medical records, book appointments,
and communicate with healthcare providers. This portal will be
accessible via web and mobile platforms, ensuring that patients
can interact with the system conveniently.
2. Advanced Appointment Scheduling: Implement a sophisticated
appointment scheduling system that supports online booking,
rescheduling, and cancellations. The system will also allow for setting
up reminders and managing the availability of healthcare providers.
3. Notification System: Integrate a notification system that sends
reminders and alerts to patients via email or SMS. This could include
appointment reminders, follow-up notifications, or alerts for new
messages from healthcare providers.

Iteration 3: Medical Information Management

Objective: Establish comprehensive modules for managing and
storing medical information securely and efficiently.
Details:
1. Electronic Medical Records (EMR) System: Develop an EMR
system where healthcare providers can securely store and access
patient medical histories, treatment records, clinical notes, and
other critical information. This system will support
interoperability, allowing seamless data exchange between
departments.
2. Lab Results Integration: Implement functionality to integrate lab
results directly into the EMR. This allows healthcare providers to
view lab results within the patient's medical records, facilitating
better decision-making and faster responses to test results.
3. Prescription Management: Create a module for managing patient
prescriptions, enabling doctors to issue, modify, and review
prescriptions electronically. This module will support e-
prescriptions, reducing the risk of errors and improving the
efficiency of the prescribing process.

Iteration 4: Financial Management

Objective: Develop a robust financial management system that
handles billing, payments, and insurance processing efficiently.
 Details:
1. Billing Module: Design and implement a billing system that
generates invoices for services rendered, tracks payments and
manages outstanding balances. This module will automate many
aspects of the billing process, reducing the administrative burden
on staff.
2. Insurance Claims Processing: Integrate a system for managing
insurance claims, including submission, tracking, and reconciliation
of claims with insurance companies. This feature will streamline
the processing of insurance payments and reduce delays.
3. Payment Gateway Integration: Integrate a secure payment
gateway that allows patients to make online payments for their
medical bills. This feature will support multiple payment methods,
ensuring convenience for patients.

Iteration 5: Expanded Access to Care

Objective: Extend the HMS’s capabilities to include telemedicine
and remote patient monitoring, expanding access to healthcare
services.
Details:
1. Telemedicine Functionality : Develop a telemedicine module that
enables virtual consultations between patients and healthcare
providers. This module will include video conferencing capabilities,
secure messaging, and the ability to share medical documents
during consultations.
2. Remote Patient Monitoring: Integrate IoT devices that allow for
real-time remote monitoring of patients' vital signs and other
health indicators. Data collected from these devices will be
automatically fed into the EMR, providing healthcare providers
with up-to-date information.
3. Virtual Consultation Platform: Enhance the telemedicine module
with additional features such as virtual waiting rooms,
appointment scheduling, and integration with the EMR for
documenting virtual visits.
Iteration 6: Data Analysis and Reporting
Objective: Implement tools and features that enable
comprehensive data analysis and reporting, supporting data-
driven decision-making.
Details:
1. Analytics Dashboard: Develop an analytics dashboard that
provides healthcare administrators with insights into key metrics
such as patient outcomes, resource utilization, and financial
performance. This dashboard will allow for real-time monitoring
and strategic decision-making.
2. Custom Reporting Tools: Create custom reporting tools that allow
users to generate reports based on specific parameters, such as
patient demographics, treatment effectiveness, and financial data.
These reports will support compliance with healthcare regulations
and provide valuable insights for improving patient care.
3. Regulatory Compliance Reporting: Ensure that the reporting tools
support the generation of reports required for compliance with
healthcare regulations, such as HIPAA. This includes reports on
patient privacy, data security, and clinical outcomes.

Iteration 7: System Cohesion and Interface Optimization

Objective: Refine the system to ensure all modules work
seamlessly together, and optimize the user interface for better
usability and performance.
Details:
1. System Integration: Conduct thorough testing to ensure that all
modules are fully integrated and that data flows seamlessly
between them. This ensures a unified user experience, where all
functionalities work together without issues.
2. User Interface (UI) Optimization: Refine the user interface based
on user feedback and usability testing. This involves improving the
layout, navigation, and accessibility of the system across different
devices and screen sizes.
3. Performance Tuning: Optimize the system’s performance to
handle increased user loads and large datasets. This includes
optimizing database queries, improving load times, and ensuring
the system remains responsive under heavy use.
Iteration 8: Final Review and Continuous Improvement
Objective: Finalize the system, ensuring it meets all requirements,
and establish a plan for ongoing maintenance and improvements.
Details:
1. Comprehensive Testing: Perform final testing of the entire system,
including performance testing, security audits, and user
acceptance testing (UAT). Address any remaining issues to ensure
the system is fully functional and ready for deployment.
2. Stakeholder Review: Conduct a final review session with all
stakeholders to gather feedback and confirm that the system
meets all requirements. This review may result in minor
adjustments before the final deployment.
3. Deployment and Rollout: Plan and execute the deployment of the
system to the live environment, ensuring a smooth transition for
all users. This includes training sessions for staff and providing
support during the initial rollout phase.
4. Continuous Improvement Plan: Develop a plan for ongoing
maintenance, updates, and enhancements based on user feedback
and emerging healthcare trends. This ensures the system remains
relevant and effective over time.
 SOFTWARE REQUIREMENT SPECIFICATION

1. Introduction
Purpose:
a) Streamline Hospital Operations
Centralize Processes: Integrate patient registration, appointment
scheduling, medical records, billing, and more into a single, unified
system.
Enhance Efficiency : Reduce paperwork and manual processes,
allowing hospital staff to focus more on patient care.

b) Improve Patient Care

Access to Information: Provide healthcare providers with quick
and easy access to comprehensive patient information, improving
decision-making and care quality.
Support Telemedicine: Enable virtual consultations and online
prescriptions to make healthcare more accessible to patients.

c) Ensure Data Security and Compliance

Protect Patient Data: Implement robust data protection measures
to secure sensitive patient information.
Compliance: Ensure the system adheres to legal and regulatory
standards, including data privacy laws and healthcare regulations.

d) Enhance User Experience

User-Friendly Design: Create an intuitive interface that is easy for
patients, doctors, and administrative staff to use.
Continuous Improvement: Gather feedback from users to
continuously enhance the system’s functionality and usability.

e) Scalability and Future-Proofing

Accommodate Growth: Design the system to be scalable, allowing
it to grow and adapt as the hospital’s needs evolve.
Flexibility : Ensure the system can easily incorporate new features
and updates in the future.
Intended Audience:
a) Healthcare Providers
Doctors and Nurses: Access patient records, manage
appointments, update medical histories, and prescribe treatments
efficiently.

b) Administrative Staff
Receptionists and Schedulers: Manage patient registration,
appointments, and billing, reducing administrative workload and
improving accuracy.
Hospital Administrators: Oversee hospital operations, generate
reports, and ensure compliance with regulations through
centralized management tools.

c) Patients
General Patients: Book appointments, access medical records,
and consult doctors virtually, enhancing their healthcare
experience.
Chronic Care Patients: Regularly access their health information
and communicate with healthcare providers for ongoing care.

d) Hospital Management
Executives and Managers: Monitor hospital performance, manage
resources, and make data-driven decisions to optimize hospital
operations.

e) IT and Support Teams

Technical Staff: Maintain and support the HMS, ensuring it runs
smoothly, remains secure, and is updated with new features as
needed.

f) Regulatory Bodies
Compliance Officers: Ensure that the system meets legal and
regulatory standards, particularly concerning data privacy and
healthcare regulations.
g) External Stakeholders
Investors and Partners: Interested in the system’s efficiency and
scalability as it relates to the hospital’s financial performance and
growth potential.

Intended Use:
1. Centralize Hospital Operations: Integrate key functions like
patient registration, scheduling, and billing into one system.
2. Enhance Patient Care: Provide quick access to medical records
and support telemedicine services.
3. Ensure Data Security: Protect patient data and comply with legal
standards.
4. Improve User Experience: Offer an intuitive interface for
patients, doctors, and staff.
5. Support Scalability: Adapt to future growth and evolving needs
of the hospital.

Product Scope:

1. Core Functionalities
Patient Management: Includes registration, appointment
scheduling, and medical records management.
Billing and Invoicing: Automates billing processes, including
insurance claims and payments.
Telemedicine: Facilitates virtual consultations and online
prescriptions.

2. User Experience
Intuitive Interface: Easy-to-use design for patients, healthcare
providers, and administrative staff.
Multi-Device Support: Accessible via desktops, tablets, and
mobile devices.
3. Data Security and Compliance
Secure Data Handling: Ensures patient data protection through
encryption and secure access controls.
Regulatory Compliance: Adheres to healthcare laws and data
protection regulations.
4. Integration and Scalability
System Integration: Seamless integration with existing hospital
systems like EHRs and lab management systems.
Scalability: Designed to accommodate future expansion and new
feature additions.
5. Support and Maintenance
Ongoing Support: Includes regular updates, security patches, and
user support.

2. Overall Description

User Needs:
1. Efficient Operations
Streamlined processes for patient registration, appointment
scheduling, and billing.

2. Easy Access to Information

Quick and secure access to medical records for healthcare
providers.

3. Enhanced Patient Care

Support for telemedicine, virtual consultations, and online
prescriptions.

4. Data Security
Protection of sensitive patient information and compliance with
data privacy regulations.
5. User-Friendly Interface
Intuitive design for easy use by doctors, nurses, administrative
staff, and patients.

6. Scalability
Ability to accommodate hospital growth and future technological
advancements.

Assumptions:

1. Stable Internet Connectivity : Assumes that the hospital has

reliable internet access for the system to function smoothly,
especially for cloud-based features and telemedicine.
2. User Proficiency : Assumes that hospital staff will be provided with
the necessary training to use the system effectively.
3. Compliance with Regulations: Assumes that the hospital will
adhere to data protection and healthcare regulations, and the
system will be designed to comply with these requirements.
4. Availability of Resources: Assumes that the necessary hardware,
software, and technical support will be available throughout the
project.
5. Stakeholder Engagement: Assumes active participation from
stakeholders (doctors, nurses, administrators) for feedback and
testing during development.

Dependencies:

Third-Party Integrations: Depends on successful integration with

existing hospital systems (e.g., electronic health records, billing
systems).
Legal Compliance: Depends on adherence to healthcare
regulations and data protection laws, which may affect system
design and implementation.
 Technology Stack: Depends on the chosen front-end and back-
end technologies (React.js, Node.js, Django, MySQL) being suitable
for the project’s requirements.
Vendor Support: Depends on timely and effective support from
technology vendors for tools, platforms, and services used in the
project.
User Feedback: Depends on continuous feedback from users to
refine and improve the system during development.

3. System Features and Requirements

Functional Requirements:
1. Patient Management
Registration

Input: Patient details such as name, contact information, date of

birth, medical history, and insurance information.
Processing: The system validates the information, checks for
duplicate entries, and stores the data in the patient database.
Output: A confirmation message is displayed, and a new patient
record is created or an existing record is updated in the system.

Appointment Scheduling

Input: Patient ID, preferred appointment date and time, doctor

selection, and reason for visit.
Processing: The system checks the doctor's availability, confirms the
time slot, and schedules the appointment.
Output: An appointment confirmation is sent to the patient, and the
schedule is updated in the doctor's calendar.
2. Medical Records Management
Electronic Health Records (EHR)

Input: Patient medical history, diagnosis, treatment plans, medications,

and test results.
Processinoft: The system stores and organizes the data, allowing for easy
retrieval and updates as necessary.
Output: A comprehensive, up-to-date electronic health record that is
accessible to authorized healthcare providers.

Data Access

Input: User credentials (e.g., username and password) and patient ID

or search criteria.
Processing: The system verifies user permissions and retrieves the
relevant patient records.
Output: The requested medical records are displayed to the
authorized user.

3. Billing and Payment Processing

Invoice Generation

Input: Services provided (e.g., consultations, tests, treatments),

patient ID, and pricing information.
Processing: The system calculates the total bill, applies any discounts
or insurance claims, and generates the invoice.
Output: A detailed invoice is generated and sent to the patient, with a
copy stored in the system for records.

Payment Gateway Integration

Input: Payment details (e.g., credit/debit card information, digital

wallet details), invoice number, and patient ID.
Processing: The payment gateway processes the transaction, verifies
the payment, and updates the payment status in the system.
Output: A payment confirmation is sent to the patient, and the
payment status is updated in the billing records.
4. Telemedicine and Virtual Consultation
Video Conferencing

Input: Patient ID, appointment details, and video conferencing

platform login credentials.
Processing: The system sets up the video call, ensuring a secure
connection between the doctor and the patient.
Output: A virtual consultation session is conducted, with the
possibility of recording the session for future reference.

Online Prescriptions

Input: Doctor's notes, patient ID, and prescribed medications.

Processing: The system generates an electronic prescription, cross-
checks for drug interactions, and updates the patient’s medical
records.
Output: The prescription is sent to the patient and/or the pharmacy,
and a copy is stored in the patient's records.

5. User Authentication and Authorization

Role-Based Access Control

Input: User credentials (e.g., username, password, role).

Processing: The system verifies the user's identity, determines their
role, and grants access to the appropriate system functions and data.
Output: The user is provided with a customized interface displaying
only the features and data they are authorized to access.

6. Reporting and Analytics

Generate Reports

Input: Report criteria (e.g., date range, patient demographics,

service types).
Processing: The system compiles the relevant data, applies any
filters, and formats it into a report.
Output: A detailed report is generated and can be viewed, printed,
or exported for further analysis.
Analytics Dashboard

Input: Data from various system modules (e.g., patient data,

appointment statistics, billing information).
Processing: The system aggregates and analyzes the data, identifying
trends and generating visualizations.
Output: A real-time dashboard displaying key performance metrics
and insights into hospital operations.

7. Notification and Alerts

Reminders

Input: Appointment details, patient contact information, and

reminder schedule.
Processing: The system schedules the reminders and sends them
according to the set timeframes (e.g., one day before the
appointment).
Output: Reminders are sent via SMS, email, or in-app notifications to
patients and staff.

Critical Alerts

Input: Patient vital signs, test results, or system flags (e.g., overdue
tasks).
Processing: The system monitors for critical conditions and triggers
alerts when thresholds are breached.
Output: Immediate alerts are sent to the relevant healthcare
providers via the chosen communication channels.

8. System Integration
Integration with Existing Systems

Input: Data from external systems (e.g., lab results, pharmacy

inventory, insurance claims).
Processing: The system translates and integrates the incoming data,
ensuring compatibility and consistency across platforms.
Output: A seamless flow of information between systems, with data
accessible across various hospital departments.
External Interface Requirements:
1. User Interface (UI)
Intuitive Design: Simple and easy-to-navigate interface for patients, doctors, and
staff.
Responsive Layout: Compatible with desktops, tablets, and smartphones.
2. Hardware Interface
Device Compatibility: Support for various devices like desktop computers,
tablets, and biometric devices (e.g., fingerprint scanners).
Peripheral Support: Integration with printers for reports and barcode scanners
for patient ID management.
3. Software Interface
Integration with Existing Systems: Seamless connectivity with existing hospital
software (e.g., Electronic Health Records (EHR), billing systems).
API Support: Use of APIs to connect with third-party applications like lab systems
and insurance platforms.
4. Communication Interface
Email/SMS Integration: Automated notifications for appointment reminders,
billing, and test results.
Telemedicine Integration: Support for video consultations and online chat with
healthcare providers.
System Features:
1. Centralized Patient Management
Registration and Records: Manage patient registration, medical histories, and
records in one place.
2. Appointment Scheduling
Online Booking: Patients can schedule, reschedule, or cancel appointments
easily.
3. Billing and Invoicing
Automated Billing: Streamline billing processes with automatic invoice
generation and payment tracking.
4. Telemedicine Support
Virtual Consultations: Enable online doctor-patient interactions and
consultations.
5. Secure Data Handling
Data Protection: Ensure patient data is encrypted and complies with privacy
regulations.
6. User-Friendly Interface
Easy Navigation: Intuitive design for seamless use by patients, doctors, and
hospital staff.
7. Reporting and Analytics
Insights: Generate detailed reports on patient data, hospital performance, and
financials.
8. Integration with Existing Systems
Seamless Operations: Integrate with existing hospital systems like EHRs and lab
systems.
9. Scalability
Future-Proofing: Easily add new features and expand as the hospital grows.
External Interface Requirements:
1. User Interface (UI)
Intuitive Design: Simple and easy-to-navigate interface for patients, doctors, and
staff.
Responsive Layout: Compatible with desktops, tablets, and smartphones.
2. Hardware Interface
Device Compatibility: Support for various devices like desktop computers, tablets,
and biometric devices (e.g., fingerprint scanners).
Peripheral Support: Integration with printers for reports and barcode scanners for
patient ID management.
3. Software Interface
Integration with Existing Systems: Seamless connectivity with existing hospital
software (e.g., Electronic Health Records (EHR), billing systems).
API Support: Use of APIs to connect with third-party applications like lab systems
and insurance platforms.
4. Communication Interface
Email/SMS Integration: Automated notifications for appointment reminders, billing,
and test results.
Telemedicine Integration: Support for video consultations and online chat with
healthcare providers.

System Features:
1. Centralized Patient Management
Registration and Records: Manage patient registration, medical histories, and
records in one place.
2. Appointment Scheduling
Online Booking: Patients can schedule, reschedule, or cancel appointments easily.
3. Billing and Invoicing
Automated Billing: Streamline billing processes with automatic invoice generation
and payment tracking.
4. Telemedicine Support
Virtual Consultations: Enable online doctor-patient interactions and consultations.
5. Secure Data Handling
Data Protection: Ensure patient data is encrypted and complies with privacy
regulations.
6. User-Friendly Interface
Easy Navigation: Intuitive design for seamless use by patients, doctors, and hospital
staff.
7. Reporting and Analytics
Insights: Generate detailed reports on patient data, hospital performance, and
financials.
8. Integration with Existing Systems
Seamless Operations: Integrate with existing hospital systems like EHRs and lab
systems.
9. Scalability
Future-Proofing: Easily add new features and expand as the hospital grows.
Nonfunctional Requirements:

1. Performance Requirements:
Response Time: The system should process user requests (e.g.,
accessing patient records, scheduling appointments) within 2 seconds
under normal load.
Throughput: The system should handle at least 200 concurrent users
without performance degradation.
Availability: The HMS should be operational 99.9% of the time, ensuring
minimal downtime.
Load Handling: The system should efficiently manage peak loads, such
as during patient check-in times, without slowing down.

2. Safety Requirements:
Data Integrity: Ensure that patient data, including medical records and
treatment history, is accurate and not corrupted during processing or
transmission.
Backup and Recovery: Implement regular data backups and a disaster
recovery plan to restore data in case of system failure or unforeseen
incidents.
Error Handling: The system should detect and handle errors gracefully,
ensuring that incorrect data entries or system glitches do not
compromise patient safety.

3. Security Requirements:
Data Encryption: All sensitive data, such as patient information and
medical records, should be encrypted both at rest and in transit to
prevent unauthorized access.
Access Control: Implement role-based access controls (RBAC) to ensure
that only authorized personnel can access specific data and system
functions.
Audit Trails: Maintain detailed logs of all system activities, including
data access and modifications, to monitor and detect any unauthorized
actions.
Authentication: Use multi-factor authentication (MFA) for users
accessing critical parts of the system, such as administrative or sensitive
patient data sections.
4. Usability Requirements:
User Interface: The system should have a clean, intuitive, and consistent
user interface that is easy for all users, including doctors, nurses, and
administrative staff, to navigate.
Accessibility: Ensure the system is accessible to users with disabilities,
adhering to standards like the WCAG (Web Content Accessibility
Guidelines).
Training and Support: Provide comprehensive training materials and
support to help users quickly become proficient with the system.
Language Support: Offer multi-language support to accommodate
diverse user populations within the hospital.

5. Scalability Requirements:
Horizontal Scaling: The system should support the addition of more
servers to handle increased load without requiring significant changes
to the application architecture.
Modular Design: The system should be designed modularly, allowing
new features and functionalities to be added without affecting existing
operations.
Database Scalability: The database should be able to handle increasing
amounts of data as the hospital grows, without compromising
performance.
Geographic Expansion: The system should be able to support multiple
locations, allowing the hospital to expand its operations across different
regions seamlessly.
COCOMO MODEL(Cost Constructive Model)

COCOMO is defined in terms of three different models:

1. The Basic model,
2. The Intermediate model, and
3. The Detailed model.

The Development mode

The most important factors contributing to a project's duration and cost is the
Development Mode.
Organic Mode: The project is developed in a familiar, stable environment, and
the product is similar to previously developed products. The product is
relatively small and requires little innovation.
Semidetached Mode: The project's characteristics are intermediate between
Organic and Embedded.
Embedded Mode: The project is characterized by tight, inflexible constraints
and interface requirements. An embedded mode project will require a great
deal of innovation.

Basic COCOMO (Project type: Organic)

Development time is estimated with the formula,

Effort = 2.4 * (kLOC)^1.05 kLOC is the estimated size of the software
product indicate in Kilo Lines of Code
Tdev = 2.5 x (Effort)^0.38 Months E is effort in person-months.
Tdev is the development time in months

We are assuming for the project 26 kLOC of code is needed, so ,

Effort = 2.4 × (26)^1.05 = 73.44 person-months
Development time = 2.5 x (73.44)^0.38 = 12.79 Months
Cost = Effort * Monthly-Salary
Now assuming salary of resources is approx. 1,00,000/month
Total Cost approx.=73,44,000 INR
Intermediate COCOMO
For the Intermediate COCOMO model, there are 15 cost drivers, each representing an
attribute of the project that affects the development effort. Here's a detailed breakdown
of the cost driver attributes that are relevant to our Hospital Management System (HMS)
project:

COST DRIVERS RATING VALUE

RELY High 1.15

DATA High 1.08

CPLX Very High 1.30

TIME Nominal 1.00

STOR Nominal 1.00

VITR Low 0.87

TURN Nominal 1.00

ACAP High 0.86

AEXP Nominal 1.00

PCAP High 0.86

VEXP Nominal 1.00

LEXP Nominal 1.00

MODP High 0.91

TOOL Nominal 1.00

SCHED High 1.04

Calculation of Effort Adjustment Factor

The EAF is the product of all these cost driver multipliers.

EAF = 1.15 * 1.08 * 1.30 * 1.00 * 1.00 * 0.87 * 1.00 * 0.86 * 1.00 *
0.86 * 1.00 * 1.00 * 0.91 * 1.00 * 1.04
= 0.98

Final Effort Calculation

Now, using the intermediate COCOMO formula:

Effort=a × (kLOC)b× EAF

For an Organic project:

a = 2.4
b = 1.05
c = 2.5
d = 0.38

With kLOC = 26 and EAF = 0.98:

Effort = 2.4 × (26)^1.05 × 0.98 = 71.97 person-months

Duration = 2.5 × (71.97)^0.38 = 12.69 months
Now assuming salary of resources is approx. 1,00,000/month
Total Cost approx.=71,97,000 INR
Detailed COCOMO

Detailed COCOMO divides the project into its different phases such as:
Planning and Requirements
System Design
Detailed Design
Coding and Unit Testing
Integration and Testing

KLOC Distribution Calculation:

Planning and Requirements (5% of total KLOC):
5%×26=1.30 KLOC
System Design (10% of total KLOC):
10%×26=2.60 KLOC
Detailed Design (20% of total KLOC):
20%×26=5.20 KLOC
Coding and Unit Testing (50% of total KLOC):
50%×26=13.00 KLOC
Integration and Testing (15% of total KLOC):
15%×26=3.90 KLOC

Planning and Requirements

In this phase, we focus on understanding the problem, gathering requirements,

and ensuring reliability. The following cost drivers are most relevant here:

COST DRIVERS RATING VALUE

RELY High 1.15

DATA High 1.08

ACAP High 0.86

AEXP Nominal 1.00

EAF = RELY * DATA * ACAP * AXEP

= 1.15 * 1.08 * 0.86 * 1.00
= 1.068
System Design

During the system design phase, architects and designers create

the structure and define the system’s components. The following
cost drivers are key to this phase:

COST DRIVERS RATING VALUE

RELY High 1.15

DATA High 1.08

CPLX Very High 1.30

VITR Low 0.87

ACAP High 0.86

TOOL Nominal 1.00

EAF = RELY * DATA * CPLX * VITR * ACAP * TOOL

= 1.15 * 1.08 * 1.30 * 0.87 * 0.86 * 1.00
= 1.208
Detailed Design

This phase refines the system design into a more detailed design
specification. The following cost drivers will affect this phase:

COST DRIVERS RATING VALUE

DATA High 1.08

CPLX Very High 1.30

VITR Low 0.87

PCAP High 0.86

MODP High 0.91

EAF = DATA * CPLX * VITR * PCAP * MODP

= 1.08 * 1.30 * 0.87 * 0.86 * 0.91
= 0.956
Coding and Unit Testing

In this phase, the design is transformed into code, and unit tests
are conducted. The following cost drivers are particularly
important:

COST DRIVERS RATING VALUE

RELY High 1.15

CPLX Very High 1.30

TIME Nominal 1.00

STOR Nominal 1.00

SCHED High 1.04

EAF = RELY * CPLX * TIME * STOR * SCHED

= 1.15 * 1.30 * 1.00 * 1.00 * 1.04
= 1.554
Integration and Testing

In this phase, individual components are integrated, and the

system is tested for bugs and performance. The following cost
drivers are important here:

COST DRIVERS RATING VALUE

CPLX Very High 1.30

TIME Nominal 1.00

STOR Nominal 1.00

PCAP High 0.86

VEXP Nominal 1.00

LEXP Nominal 1.00

MODP High 0.91

TOOL Nominal 1.00

EAF = CPLX * TIME * STOR * PCAP * VEXP * LEXP * MODP * TOOL

= 1.30 * 1.00 * 1.00 * 0.86 * 1.00 * 1.00 * 0.91 * 1.00
= 1.017
Effort Calculation of each Phase:

Using the formula,

Effort (PM)=2.4 * (KLOC)^(1.05) * EAF(phase) and breaking the
effort into phases based on the distribution:

Requirement Analysis:
Effort = 2.4 * (1.30)^(1.05) * 1.068
= 3.376 person-months

System Design:
Effort = 2.4 * (2.60)^(1.05) * 1.13
= 7.396 person-months

Detailed Design:
Effort = 2.4 * (5.20)^(1.05) * 1.05
= 14.229 person-months

Coding and Unit Testing:

Effort = 2.4 * (13.00)^(1.05) * 1.05
= 37.243 person-months

Integration and Testing:

Effort = 2.4 * (3.90)^(1.05) * 1.20
= 12.022 person-months

Total calculated Effort : 74.266 person-months

Duration = 2.5 × (74.266)^0.38 = 12.848 months
Now assuming salary of resources is approx. 1,00,000/month
Total Cost approx.=74,26,600 INR
 DFD for Hospital Management System

Introduction

The Data Flow Diagram (DFD) for the Hospital Management System
(HMS) visually represents how data flows through the system. The DFD
is composed of different levels that break down the system from a
high-level overview (Context Diagram) into more detailed processes
(Level 1 and Level 2). This documentation provides the necessary
information on the entities, processes, data stores, and data flows
within the HMS.

What is a Data Flow Diagram (DFD)?

A Data Flow Diagram (DFD) is a visual representation that depicts how

data moves through a system.
It shows the processes, data stores, and interactions with external
entities, providing a clear overview of the system’s data flow and
structure

Purpose of DFDs in System Design:

Visual Clarity: Provides a graphical view of the system to better

understand the flow of data.
System Analysis: Helps in identifying the major components and how
they interact.
Communication: Facilitates communication among stakeholders by
illustrating how the system operates.
 Level -0 DFD (Context Diagram)

The Context Diagram is correctly outlined with the HMS as the central
process interacting with external entities. Ensure that each interaction
and data flow is clearly represented in the diagram to visualize how the
HMS interfaces with these entities.

Entities and Data Flow

Patient:
Input: Provides personal info, requests appointments.
Output: Receives confirmations, bills, and medical records.
Doctor/Staff:
Input: Receives patient details, manages appointments.
Output: Updates records, provides prescriptions.
Admin:
Input: Manages patient data and billing.
Output: Updates patient and billing info.
Lab:
Input: Submits test results.
Output: Sends test reports to the system.
Pharmacy :
Input: Receives prescription data.
Output: Provides medications to patients.
Insurance Companies:
Input: Processes insurance claims.
Output: Returns processed claims for billing.
Level - 1 DFD (High-Level Processes)

In the Level 1 DFD, the HMS is broken down into major

functional areas. Each process interacts with data stores and
external entities.
External Entities:
Patient: Individuals seeking medical services, who interact with
various processes to register, log in, make appointments, and
manage their medical records.
Doctor: Healthcare professionals who provide medical services, add
prescriptions, and manage patient interactions.
Admin: Administrative personnel managing system data, including
doctor details and payment verifications.

Processes:
1.0 Registration: Captures patient details and updates the database.
2.0 Login: Authenticates patients using their credentials and
retrieves their information.
3.0 Make Appointment: Allows patients to schedule appointments
with doctors.
4.0 Add Prescription: Enables doctors to prescribe medications to
patients.
5.0 Doctor Details: Admins can manage doctor information and
update the database.
6.0 Payment: Handles patient payments, updating the database and
issuing receipts.
7.0 Cancel Appointment: Facilitates the cancellation of
appointments by patients.
8.0 Patient Module: Allows updates and management of patient
information within the system.

Data Store:
Hms.db: The central database that stores all patient, doctor, and
administrative data, ensuring data integrity and availability for various
processes.
Level - 2 DFD (Detailed Process Breakdown)

Detailed subprocesses provide clarity on how each high-level process

operates.

1. Registration (Process 1.0)

The Registration process enables patients to create a new profile in the
system by submitting personal details such as name, contact information,
and medical history. The registration process includes:

1.1 Input Patient Details: The patient submits their personal

information through a user interface.
1.2 Validate Data: The system validates the input data, checking for
mandatory fields and potential duplicate entries in the database.
1.3 Store Patient Data: Once the information is verified, the system
stores the data in the hospital management database (Hms.db),
creating a new patient record.
 Level-2 DFD for Registration (1.0)

2. Login (Process 2.0)

The Login process allows patients and administrators to access the
system using unique credentials. This process includes:

2.1 Validate Credentials: The system checks the patient’s or admin’s login
credentials, such as ID and password, for authentication.
2.2 Fetch Patient Data: Once validated, the system retrieves the relevant
patient’s or admin’s details from the database.
2.3 Update Login Status: The system updates the login status, indicating
the active session, and provides access to the patient’s or admin’s
dashboard.

Level-2 DFD for Login (2.0)

3. Make Appointment (Process 3.0)
The Make Appointment process enables patients to schedule an
appointment with a doctor. This includes:

3.1 Check Doctor Availability: The system checks the availability of the
selected doctor based on their schedule.
3.2 Schedule Appointment: If the doctor is available, the system allows
the patient to select a time slot.
3.3 Update Database: The system updates the hospital database with the
appointment details and confirms the booking to the patient.

Level-2 DFD for Make Appointment (3.0)

4. Add Prescription (Process 4.0)
Doctors can add and update prescriptions for patients through the Add
Prescription process. It includes:

4.1 Verify Patient: The system verifies the patient’s identity based on their
ID.
4.2 Add Prescription Details: The doctor enters the prescription details,
including medicine names, dosage, and advice.
4.3 Update Database: The prescription is saved in the hospital database, and
the patient's medical record is updated.

Level-2 DFD for Add Prescription (4.0)

5. Doctor Details Module (Process 5.0)
The Doctor Details Module process manages doctor profiles and information.
This includes:

5.1 Input Doctor Details: The admin inputs details about doctors, such as
name, age, and specialization.
5.2 Verify Details: The system verifies that the doctor’s details meet required
validation criteria.
5.3 Update Doctor Records: Once verified, the doctor’s profile is saved or
updated in the hospital database.

Level-2 DFD for Doctor Details Module (5.0)

6. Payment (Process 6.0)
The Payment process handles billing and payment for medical services
rendered. It includes:

6.1 Fetch Billing Info: The system retrieves the billing details for the
patient based on services provided (e.g., consultations, tests).
6.2 Verify Payment Details: The system checks the payment
information submitted by the patient, such as card or bank details.
6.3 Process Payment: The system processes the payment using a
payment gateway.
6.4 Update Payment Status: After successful payment, the system
updates the payment status in the database and sends a confirmation
to the patient.

Level-2 DFD for Payment (6.0)

7. Cancel Appointment (Process 7.0)
The Cancel Appointment process allows patients to cancel a
previously scheduled appointment. It includes:

7.1 Verify Appointment: The system verifies the patient’s appointment

details based on the appointment ID.
7.2 Update Status: If the appointment is valid, the system cancels it
and updates the status in the database.
7.3 Notify Patient: The system sends a notification to the patient
confirming the appointment cancellation.

Level-2 DFD for Cancel Appointment (7.0)

8. Patient Module (Process 8.0)

The Patient Module process manages the retrieval and updating of
patient records. It includes:

8.1 Fetch Patient Details: The system retrieves the patient’s data from
the database based on their ID.
8.2 Update Patient Details: The patient or admin can update details
such as contact information or medical history.
8.3 Store Updated Details: The updated information is saved in the
hospital management database.
 Level-2 DFD for Patient Module (8.0)

Data Dictionary

The Data Dictionary defines the data elements used in the Hospital
Management System (HMS). Each data item and its attributes (such
as format, description, and usage) are outlined below:
 Entities

Patient

Data
Attribute Description Example
Type

Unique identifier for

Patient ID Integer 101
each patient

Full name of the

Name String John Doe
patient

Age Integer Patient's age 30

Gender String Male/Female/Other Male

Residential address of
Address String 123 Street, NY
the patient

Contact Patient's phone

String 9876543210
No number

Medical Medical records and

Text Diabetic
History patient history

Insurance Patient’s insurance

String ABC Insurance
Info policy details
Doctor/Staff

Data
Attribute Description Example
Type

Unique identifier for

Doctor ID Integer 201
each doctor

Full name of the

Name String Dr. Smith
doctor/staff

Doctor's area of
Specialization String Cardiologist
expertise

Number of years of
Experience Integer 10
experience

Phone number of the

Contact No String 9876543210
doctor/staff
Admin

Data
Attribute Description Example
Type

Unique identifier for

Admin ID Integer 301
admin users

Username String Admin username admin123

Password String Admin password Admin@123

Defines the access

Role String role (e.g., super- Super-Admin
admin, manager)

Lab

was
 Pharmacy

Data
Attribute Description Example
Type

Unique identifier for

Pharmacy ID Integer 601
each pharmacy

Medications and
Prescription Paracetamol
Text prescriptions
Data 500mg
provided to patients

Insurance Company

ABC12345
Processes

Reoftistration

Input Data Output Data

Patient personal info (Name, Age, Patient ID, confirmation

Address, Contact No) message

Appointment Schedulinoft

Input Data Output Data

Patient ID, Doctor ID, Appointment Appointment confirmation,

Time/Date updated schedule

Billinoft and Payment

Patient ID, Service Details, Amount,

Invoice, Payment Status
Prescription Manaoftement

Input Data Output Data

Patient ID, Doctor ID, Prescription Updated prescription data,

Details (medications, dosage) sent to pharmacy

Lab Test Manaoftement

Input Data Output Data

Test ID, Patient ID, Test Details Test Report, Report Date

Insurance Claim Processinoft

Patient ID, Insurance Policy No, Claim Status (approved,

 Data Stores

Hms.db

Central database that stores all patient,

Description doctor, admin, lab, pharmacy, and insurance-
related data

Patient ID, Doctor ID, Appointment ID, Test

Fields
ID, Prescription ID, Insurance Claim ID, etc.

Storage Type Relational database (MySQL, PostgreSQL)

This Data Dictionary provides a structured overview of all entities,

processes, and data stores in the Hospital Management System
(HMS).

Conclusion

The Data Flow Diagram for the Hospital Management System (HMS)
provides a detailed view of how information flows through the system. It
highlights the external entities interacting with the system, the high-level
processes, and the detailed subprocesses involved in patient care,
appointment scheduling, medical records management, billing, and
telemedicine services. The DFD is a key component of the system’s
architecture, ensuring clarity in how the HMS handles data and
interactions with external entities.
Hospital Management System (UML Diagrams)

Use Case Diagram:

The use case diagram for the hospital management
system shows the actors:
Doctor
Patient
and their defined use cases:
Doctor
Visit the patient
Examine the patient
Add diagnoses
Prescribe drugs
Schedule the medical procedure
Discharge the patient
Report the patient condition
Patient
Register
Unregister
Apply for discharge
Confirm the medical procedure
Activity Diagram:

Hospital Management System Activity Diagram for the

Patient Users
Hospital Management System Activity Diagram for the
Admin Users
Hospital Management System Activity Diagram
Scenario for the Two Users
Class Diagram:

Classes of Hospital Management System Class Diagram:

Hospitals Class: Manage all the operations of Hospitals
Patient Class: Manage all the operations of Patient
Doctors Class: Manage all the operations of Doctors
Nurses Class: Manage all the operations of Nurses
Appointments Class: Manage all the operations of
Appointments
Medicines Class: Manage all the operations of Medicines
Classes and their attributes of Hospital Management System

Class Diagram:
Hospitals Attributes: hospital_id, hospital_doctor_id,
hospital_name, hospital_place, hospital_type,
hospital_description, hospital_address
Patient Attributes: patient_id, patient_name, patient_mobile,
patient_email, patient_username, patient_password,
patient_address, patient_blood_group
Doctors Attributes: doctor_id, doctor_name,
doctor_specialist, doctor_mobile, doctor_email,
doctor_username, doctor_password, doctor_address
Nurses Attributes: nurse_id, nurse_name, nurse_duty_hour,
nurse_mobile, nurse_email, nurse_username,
nurse_password, nurse_address
 Appointments Attributes: appointment_id,
appointment_doctor_id, appointment_number,
appointment_type, appointment_date,
appointment_description
Medicines Attributes: medicine_id, medicine_name,
medicine_company, medicine_composition, medicine_cost,
medicine_type, medicine_dose, medicine_description

Classes and their methods of Hospital Management System

Class Diagram:
Hospitals Methods: addHospitals(), editHospitals(),
deleteHospitals(), updateHospitals(), saveHospitals().
searchHospitals()
Patient Methods: addPatient(), editPatient(), deletePatient(),
updatePatient(), savePatient(), searchPatient()
Doctors Methods: addDoctors(), editDoctors(),
deleteDoctors(), updateDoctors(), saveDoctors(),
searchDoctors()
Nurses Methods: addNurses(), editNurses(), deleteNurses(),
updateNurses(), saveNurses(), searchNurses()
Appointments Methods: addAppointments(),
editAppointments(), deleteAppointments(),
updateAppointments(), saveAppointments(),
searchAppointments()
Medicines Methods: addMedicines(), editMedicines(),
deleteMedicines(), updateMedicines(),saveMedicines(),
searchMedicines()
Class Diagram for Hospital Management System
 Conclusion
The Hospital Management System (HMS) project successfully
demonstrates the application of software engineering principles to
streamline hospital operations and improve patient care. The
system provides efficient management of patient records,
appointments, billing, staff information, and inventory. Key
outcomes include:
1. Automation and Efficiency: The system automates routine
administrative tasks, reducing manual errors and saving time.
2. Enhanced Data Management: Centralized storage and easy
retrieval of data ensure secure and organized record-keeping.
3. Improved User Experience: The user-friendly interface simplifies
navigation for both staff and patients.
4. Scalability and Integration: The design supports future
enhancements and integration with other systems or
technologies.
5. Reliability and Security: The system incorporates robust
mechanisms to safeguard sensitive data against unauthorized
access.
This project showcases the practical application of concepts like
modular design, database management, and secure coding
practices, highlighting its value as a comprehensive solution for
modern hospital management needs.