Hospital Management System for Mayoclinic

Simplilearn Project for CBAP

Created and Submitted by – Anitha Veeramani

pg. 1
Created by Anitha Veeramani for Simplilearn
Solution

Stakeholders
Internal Stakeholders:
Project/Delivery Manager
Implementation SME
Operational IT support
Tester
Domain SME

pg. 5
Created by Anitha Veeramani for Simplilearn
External Stakeholders:

Sponsor – Hospital Management

Business Analyst who liaison the bridge between Internal and External stakeholders.

Value

pg. 6
Created by Anitha Veeramani for Simplilearn
Context
 The system will be developed using Java and MySQL database and will be compatible
with Windows 2016 operating system.
 The system will be highly scalable to support 500 users using it at the same time.
 The response time of the system will not exceed more than 1 sec.
 The system shall keep the log of all errors.
 The system will be available all times
 The screens will be user friendly.

Project Tasks

Supporting
No Project Tasks BA Knowledge Area Used Tasks/Techniques
. Used
1 Identifying stakeholders – BA Knowledge Area – Stakeholder
Create a list of stakeholders Business Analysis Planning & List,Map,Persona –
(as taught in Business Analysis Monitoring Onion Diagram
Planning and Monitoring Task - Plan Stakeholder
Knowledge Area) Engagement
2 Describe the proposed Knowledge Area: Strategy Process modeling
system’s workflow Analysis (Swimlane diagram)
Task - Define Future state for
future process/To-Be
3 Write the in-scope and out-of-
scope items for this software
4 As a Business Analyst working Knowledge Area: Strategy Scope Modeling –
on this project, find out the Analysis Context diagram
scope of the hospital Task: Define change strategy
management system. To find
the scope you can use Use
Case diagram (UML) or
Context diagram
5 Write down the main features
that need to be developed
6 Draw an ER diagram of the Knowledge Area: Elicitation Data Modelling -
system and Collaboration Crow Foot Diagram
Task: Conduct Elicitation
7 Draw a data flow diagram for Knowledge Area: Data Flow Diagram
HMS Requirement Analysis and
Design Definition
Task: Define design options

pg. 7
Created by Anitha Veeramani for Simplilearn
 Write out the Functional and
8 Nonfunctional Requirements
for this software
9 Draw a flowchart for the Knowledge Area – Process Modelling -
patients’ admission process Requirement Analysis and Flow Chart
(using flowcharts). You can Design Definition
use any of the popular tools in
the market like Microsoft Task – Specify and Model
Visio, Lucid Chart, Creately, Requirement
Pidoco, or Balsamiq
10 Draw wireframes or mock Knowledge Area: Prototyping
screens for any 2 of the Requirement Analysis and
features namely home page Design Definition
and patient registration Task: Define design options
screen. Students can draw
wireframes for any other
feature as deemed fit by
them. (Use the technique
prototyping or wire framing
that is taught in the training).
You can use any of the
wireframing tools like
Microsoft PowerPoint,
Microsoft Word, Balsamiq,
Sketch, Adobe XD, Adobe
Illustrator, Figma, UXPin,
InVision Studio, InVision
Freehand, or Moqups

BA Approach

Agile Methodology is used to develop online system for Library Management. Because,
 It is a rapid way of development of software, so client satisfaction is high.
 Client satisfaction is emphasized that means interaction with client is high so less chance
of product failure.
 There is a good communication between developers and clients.
 It is very flexible that even late changes in requirements are adopted without any
problems.

pg. 8
Created by Anitha Veeramani for Simplilearn
 1. Stakeholder List – Onion Diagram

2. Future System Work flow (Swim-Lane)

pg. 9
Created by Anitha Veeramani for Simplilearn
 3. Project Scope

4. Context Diagram

5. Main features
 Patient Account Setting/Login

pg. 10
Created by Anitha Veeramani for Simplilearn
  Schedule/Reschedule/Cancel Appointments
 Add/Update/Remove patient
 Maintain Insurance Details
 Mange/Maintain Doctor’s profile
 Maintain Patient Records
 Manage Tests details
 Manage prescriptions
 Billing
 Staf Allocation
 Reports
 Instructions for next staf

6. ER Diagram – Crow Foot Notation

7. Data Flow Diagram

pg. 11
Created by Anitha Veeramani for Simplilearn
 8. Non Functional Requirements
8.1 Availability Requirement:
The system is available 24 hours a day on all 365 days and is available for all users
accessing it. The system will be operational all time except during exigency conditions.

8.2 Scalability
The system will be able to handle all users interacting to it at the same time without
sacrificing performance.

8.3 Accuracy
The system will provide accurate information despite various concurrency issues. The
system shall provide 100% access reliability

8.4 Performance Requirement:

8.5 Maintainability and portability

pg. 12
Created by Anitha Veeramani for Simplilearn
 8.6 Efficiency
In case if the system goes down due to exigency, the system will be recovered and back
up in less than an hour of time.

8.7 Security:
● Logon ID: Any users who make use of the system need to hold a Logon ID and
password.
● Modifications: Any modifications like insert, delete, update, etc. for the database can
be synchronized quickly and executed only by the ward administrator.
● Front Desk Staf Rights: The staf in the front desk can view any data in the Hospital
Management system, add new patients record to the HMS.
● Administrator rights: The administrator can view as well as alter any information in the
Hospital Management System.

9. Flow Chart

10. Hospital Management System - Mockup Screen

pg. 13
Created by Anitha Veeramani for Simplilearn
 pg. 14
Created by Anitha Veeramani for Simplilearn