Hospital Management System for

The Mayo Clinic

Project 2 (CBAP Certification

Submitted by
POOJA TAWARE
Table of content

1. Introduction
2. Business Analysis core concept model (BACCM)
3. Requirement classification schema (RCS)
4. Stakeholders
5. Proposed System Workflow
6. Project Scope
7. Context Diagram
8. Main Features to be developed
9. Entity Relationship Diagram
10. Dataflow Diagram
11. Functional Requirements and Nonfunctional Requirements
12. Flowcharts for patients’ admission process
13. Mock screens
 Introduction

The Mayo Clinic is an American nonprofit academic medical center currently

based in three major locations, Rochester, Minnesota; Jacksonville, Florida; and
Scottsdale, Arizona focused on integrated patient care, education, and research.
Mayo Clinic holds the number 1 rank among hospitals in the United States.
It was opened on the 30th of September 1889. Over the years it grew in size and
facilities. It increased the size of its premises and also the number of doctors it
employs. The vast number of patients it treated made management of such a
huge hospital an arduous task. The paperwork and storing of all patients’ records
was becoming unmanageable. It was then the management of the hospital
decided to invest money in a hospital management software. The Hospital
Management System is designed to manage all hospital operations.
The 1980s initiated transformative changes that set the course for the modern
Mayo Clinic. As an early adopter of the Internet, Mayo Clinic has been recognized
for its online communications to patients.
 hBusiness Analysis Core Concept Model (BACCM)
The conceptual framework of business analysis has been captured
as outlined in the BABOK guide.

Business Analysis Core Concept Model as per BABOK

The business analysis core concept model for the Mayo clinic hospital
management system is presented as under:

CORE CONCEPT DESCRIPTION

Change Provide a hospital management system for
 Mayo Clinic.
Need  As the clinic size and facilities were
increasing, managing such volume
with paperwork was a difficult task.
 The need is to have a hospital
management software that can help
the clinic to manage all the hospital
operations.

Solution  To develop a hospital management

system that can facilitate patient
registration, appointments and
reminders, bed occupancy details,
billing info, lab tests and reports, staff
management and insurance.
 The data will be stored on cloud and
thus eliminating the need of
paperwork and manual efforts.

Stakeholders External stakeholders:

 Supplier
 Project Manager
 Implementation SME
 Operational IT team
 Testers
Internal stakeholders:
 Hospital staff and managers
 Doctors and nurses
 Patients
 Medical team
 Lab attendants
Business Analyst

Value  Reduce Operating Costs.

 Securely saving patient’s data,
promoting paperless documentation.
 Save time for patients and staff.
 Easy tracking system for availability of
beds.
Context  The context leading to change is that
due to the increase in hospital size
and facilities, the patient’s data has
also increased.
 The current system is not efficient to
store and manage such huge data.

Requirements Classification Schema (RCS)

 Business requirements: To develop a Hospital Management System

(HMS) to manage all the hospital operations and that can help the users
(patients) to book online appointments and track their medical records.
Other requirements are:
 Reduce operating costs of the hospital.
 Provide reports to senior management for better decision-making.
 Save patients’ time.
 Keep patients’ medical records secure and stored in cloud.
 Keep track of empty and filled beds in the hospital.
 Easy access to patient data
 Reduce documentation in the hospital.

 Stakeholder requirements:

 Patients: The patient will register themselves on the system and the
system will record all their information and medical history.
 Registration Staff: The registration staff will give each registered
patient a unique patient ID, which will be used by the patient
throughout their stay in hospital.
 Doctors and nurses: They will use the system to access patient’s
medical records and history at the time of providing medical
diagnosis and care. They can prescribe any test from the HMS.
  Laboratories and Radiation department: The prescribed tests are
received by the laboratory or radiation department directly. Once
the tests are done, the reports will be uploaded by the labs
attendants into the HMS which can be again accessed by the doctors
and patients.

 Solution requirements:
 Functional requirements:
 Database: MySQL Database to be used since it is open source and
free.
 Operating System: Shall be Windows 2016
 Web-Based: The system shall be a web-based application.

 Non - functional requirements:

 Errors: The system shall keep a log of all the errors
 Availability: The system shall be available all the time 24/7
 Usability: The screens should be self-explanatory and very user
friendly. Management would not want employees not ordering from
the system as they cannot understand the screens and data fields on
screen

 Transition Requirement – Transition from manual system to online

system.
 Storage of all existing data securely.
 Training for all the employees for new online system.
 Stakeholders.
The different levels of stakeholder involvement for the creation and
implementation of the Hospital management System project as described using
an onion diagram:

 Stakeholder Onion Diagram

Solution Delivery Affected Organizational Enterprise Affected

Unit External
Stakeholders
 Project Manager  Project Manager  Domain  Patients
 Implementation  Implementation SME  Hospital staff
 SME SME  Sponsor  Hospital
 Business Analyst  Domain SME  Supplier  Management
 Operational IT  Regulator.
support
 Tester

Proposed System Workflow

Process workflow diagram has been used to explain the system workflow of the
proposed Hospital Management System. Workflow Process refers to a series of
activities or tasks that need to be completed sequentially or in parallel to achieve
a business outcome.
  Process Flow Diagram

In-scope and out-of-scope items for this software

In Scope Requirements Out Of Scope requirements

Appointment Scheduling Emergency department (ICU, Ventilators,
Oxygen tanks, Beds etc.)
Appointment reminders Hospital payroll management
Patient registration Visitor log
Add / delete / update/ maintain
Medical staff’s details
patient’s record
Order medical prescription
Order lab tests and lab test
results
Patient admission

Bed occupancy management

Staff (nurses and ward boys)
management
Report generation

Billing and Insurance

Scope of the HMS (Context Diagram).

The scope of the hospital management system has 5 components: Patient,
Registration staff, Doctors and Nurses, Lab and radiation department, Hospital
management and Billing.
 Main Features

Patient Patient Bed occupancy

appointment registration
management

Labs/Blood bank Billing and Reports

department invoice

 Main Features to be developed

 Entity Relationship (ER) Diagram
An entity relationship diagram (ERD) shows the relationships of entity sets stored
in a database.

 Entity Relationship Diagram

Flowchart
A flowchart is a visual representation of the sequence of steps and decisions
needed to perform a process. Each step in the sequence is noted within a diagram
shape. Steps are linked by connecting lines and directional arrows. The flowchart
for the patient’s admission process has been shown below:
Mock Screens: -