Hospital Information System Development: A Comprehensive Analysis

Desklib provides past papers and solved assignments for students. This report analyzes a Hospital Information System.

COIT 20248: Information Systems Analysis and Design
Term 1, 2019
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name

Student Number

Table of Contents
1. Introduction......................................................................................................................... 1
2. Approach to Systems Development.....................................................................................2
3. Systems Requirements.........................................................................................................4
Functional Requirements......................................................................................................4
Non-Functional Requirements..............................................................................................4
4. Project Cost-Benefit Analysis................................................................................................6
5. Project Schedule...................................................................................................................8
6. System Information Requirement Investigation Techniques..............................................11
Stakeholders Analysis......................................................................................................... 11
Investigation Techniques....................................................................................................11
7. Reflections and Conclusions...............................................................................................13
8. References..........................................................................................................................14
List of Figures
Figure 1: Waterfall Model Diagram..........................................................................................2
Figure 2: Cost-Benefit Analysis.................................................................................................7
Figure 3: Work Breakdown Structure.......................................................................................8
Figure 4: Gantt chart................................................................................................................ 9

1. Introduction
In this report, an analysis of the Hospital Information System is conducted. Every year
hospitals generate a large amount of data which has to be managed precisely to make sure
that the overall functioning is efficient enough. The overall system analysis includes the
gathering of requirements, system requirements, cost analysis and project scheduling. The
Hospital Information System must be secure and safe as the data which is stored in the
database is highly sensitive. The Hospital Information System provides various facilities like
unique patient ID, fast registration at the emergency times with breaking the glass feature,
data security, privacy & confidentiality of patients. To compare the archived images with
the images the Electronic Medical Record is integrated with the Laboratory Information
System, Radiology Information System, Picture Archiving and Communication System. Cost-
benefit analysis is also conducted in this report. An overall budget of $750,000 is available
for the development of the Hospital Information System. Overall development cost and
other costs related to the project implementation are included in this budget. There is also
a maintenance cost included and is estimated to be approximately $7500/ month. This
information system is developed and designed to be used for various department in the
hospital which will cover a good range of the hospital management and the administration
process. This is a project will improve the overall quality and the management of the
hospital related information in the crucial areas like analysis of the clinical process and costs
related to each activity.
Page 1

2. Approach to Systems Development
For the hospital information system where each and every requirement is already given, the
waterfall methodology will be the best. Though the waterfall model might be an old
methodology still traditional ways are required in some projects. There are various other
methodologies like agile, RAD, spiral etc. which are also good but in this particular case
where requirements are known and are to be developed then the waterfall model is the
best. Waterfall model is required for the development of large software products which
have requirements pre-defined. Waterfall model is structured and a risk-free methodology.
In other methodologies like agile, the whole project is divided into small time boxes which
implements the project in a cycle which is good but not the best as it is really time-
consuming and the project sometimes never ends in these cases. So, we are having
requirements defined already then, we will go for the waterfall methodology.
Figure 1: Waterfall Model Diagram
There are various phases in which the hospital information system will be implemented. The
phases are as follows – System analysis & planning, designing, development, testing and
maintenance. This model is really easy to understand and is simple to use. It is rigid in
Page 2

nature which makes it easier to be managed. Each and every phase in the model has a
specific task and deliverables with the review process. The overlapping of the phases
doesn’t occur in the waterfall model and all the phases are completed with full processing at
a particular time. This type of model is really useful in those projects where the
requirements are visibly defined and are understood well. Thorough planning and analysis
of the system are done before starting with the design and development of the project.
Page 3

3. Systems Requirements
Functional Requirements
 The patient must be able to register on the system. For every patient, there will be a unique
health ID i.e. UHID.
 In the case of an emergency, registrations should be quick with not the full record including
the cause of emergency and all.
 Patient’s information confidentiality & privacy should be maintained with full security.
 The facility of E-prescription for the outpatients and Computerized Physician Order Entry for
other people.
 There should be secure remote access for viewing all the information.
 Tracking of the items in the medical stores and alerting of any situation to the stakeholders.
 Patients, services, material and medication should be tracked with the help of a bar code.
 Generation of patient’s report should be done by the system itself.
 Updating patient data and other information
Non-Functional Requirements
 Performance – The overall performance of the system should be good as there are a
lot of emergency cases which might occur. The overall response time should be less
so that every patient can access the system with ease and fast.
 Capacity – The capacity of the system to hold a large amount of data should be there
as a number of patients keeps on increasing and there must be a smooth way to
solve this issue.
 Availability – This is the most important requirement as availability of the system
should be there as patients access the system at any time, or at times of emergency.
So, the system should be available to enter data or any other crucial information.
Page 4

 Data Integrity – The data of the patients is very crucial for the hospital so the
integrity of data is one of the most important requirements. This requirement must
be taken care of as data is important for everything.
 Data Security - Patient’s information is very useful and should be secure. It should
not go into the hands of a wrong person who can misuse it against the patient. This
is also an important requirement as it deals with the security of the patient’s data.
Page 5

4. Project Cost-Benefit Analysis
CBA is a process used by companies for analysis of decisions. The analyst sums up the
advantages of a situation and then reduces the related costs.
ROI is an instrument for determining an investment's interest rate. The value of the
advantages achieved and application of the formula is calculated by determining the
amount spent. ROI = ((Benefits - Costs)/Costs) X 100
NPV is the difference between the current value of cash inflows and cash outflows reduced
to a particular rate.
Tangible benefits are monetized and intangible benefits cannot be measured monetarily,
but have a major business effect.
 Tangible Benefits – improves overall process productivity, lowers the cost and
reduces inventory and lead time.
 Intangible Benefits – Increases the overall transparency, makes data access faster
and more accurate and improves the overall client response.
Page 6

RMO Cost/Benefit Analysis for HIS
Year of Project
year 0 year1 year 2 year 3 year 4 year 5 TOTALS
Net economic benefit $0.00 $3,18,000.00 $3,18,000.00 $3,18,000.00 $3,18,000.00 $3,18,000.00
Discount Rate 8% 1 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Benefits $0.00 $2,94,444.44 $2,72,633.74 $2,52,438.65 $2,33,739.49 $2,16,425.46
NPV of all BENEFITS $0.00 $2,94,444.44 $5,67,078.19 $8,19,516.84 $10,53,256.34 $12,69,681.79 $46,46,234.68
One Time Costs $7,50,000.00
Recurring Costs $0.00 $90,000.00 $90,000.00 $90,000.00 $90,000.00 $90,000.00
Discount Rate 8% 1.0000 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Recurring Costs $0.00 $83,333.33 $77,160.49 $71,444.90 $66,152.69 $61,252.49
NPV Of All Costs $7,50,000.00 $8,33,333.33 $9,10,493.83 $9,81,938.73 $10,48,091.42 $11,09,343.90 $29,33,168.78
Overall NPV $17,13,065.90
Overall ROI = (Overall NPV / NPV Of All Costs 0.58
Break-Even Analysis
Yearly NPV Cash Flow $0.00 $2,11,111.11 $1,95,473.25 $1,80,993.75 $1,67,586.81 $1,55,172.97
Overall NPV Cash Flow $7,50,000.00 ($5,38,888.89) ($3,43,415.64) ($1,62,421.89) $5,164.92 $1,60,337.89
Project break-even occurs between years 2 and 3
Use 1st year of positive cash flow to calculate break-even fraction (180,993.75-162,421.89)/180,993.75 = 0.1026
3 years + 136 days (0.1026*365)
OR
3.273 years
Figure 2: Cost-Benefit Analysis
The NPV value for the project is $1713086.90 and the project become profitable after 3.273
years or 3 years and 136 days.
Page 7

5. Project Schedule
Figure 3: Work Breakdown Structure
WBS is a way to carry out a multi-stage, complex project. It is a way of dividing up and conquering
large projects to achieve things more efficiently and faster. It is a structure like a hierarchical tree
that sums up and breaks up the project in smaller and handier phases.
Page 8

ID Task
Mode
Task Name Duration Start Finish
0 HIS Project 44 days Mon 22-04-19Thu 20-06-19
1 Planning 11 days Mon 22-04-19Mon 06-05-19
2 Project defining3 days Mon 22-04-19Wed 24-04-19
3 Scheduling 2 days Thu 25-04-19Fri 26-04-19
4 Staff Allocation4 days Mon 29-04-19Thu 02-05-19
5 Meetings 2 days Fri 03-05-19 Mon 06-05-19
6 Analysis 8 days Tue 07-05-19Thu 16-05-19
7 Requirement
Gathering
2 days Tue
07-05-19
Wed
08-05-19
8 Defining
system
requirement
3 days Thu
09-05-19
Mon
13-05-19
9 investing
requirement
3 days Tue
14-05-19
Thu
16-05-19
10 Design 9 days Fri 17-05-19 Wed 29-05-19
11 Project Layout 3 days Fri 17-05-19 Tue 21-05-19
12 UI & Wireframes3 days Wed 22-05-19Fri 24-05-19
13 Database
designing
3 days Mon
27-05-19
Wed
29-05-19
14 Development &
Testing
10 days Thu
30-05-19
Wed
12-06-19
15 Software
Development
5 days Thu
30-05-19
Wed
05-06-19
16 Testing 5 days Thu 06-06-19Wed 12-06-19
17 Deployment 5 days Thu 13-06-19Wed 19-06-19
18 Final Meeting 1 day Thu 13-06-19Thu 13-06-19
19 Final Report
Submission
2 days Fri 14-06-19 Mon
17-06-19
20 Project
deployed &
installed
2 days Tue
18-06-19
Wed
19-06-19
21 Maintenance 1 day Thu 20-06-19Thu 20-06-19
22 User Support 1 day Thu 20-06-19Thu 20-06-19
23 Project
Maintenance
1 day Thu
20-06-19
Thu
20-06-19
24 Updating Project1 day Thu 20-06-19Thu 20-06-19
19 22 25 28 01 04 07 10 13 16 19 22 25 28 31 03 06 09 12 15 18 21 24 27 30 03 06 09 12 15 18 21 24 27 30 02 05
April 2019 May 2019 June 2019 July 2019 August 2019
Figure 4: Gantt chart
The above two diagrams represent a work breakdown structure and Gantt chart. Both of these
diagrams depict scheduling. WBS is a way to carry out a multi-stage, complex project. It is a way of
dividing up and conquering large projects to achieve things more efficiently and faster. It is a
structure like a hierarchical tree that sums up and breaks up the project in smaller and handier
phases. For time management planning, the task sequencing approach is important because it helps
to visually represent project information and data in the WBS. Gantt chart forms part of the
methodology for sequencing tasks.
There are various tasks in the Gantt chart. Planning which has subtasks named as project defining –
the project objectives are defined, scheduling – tasks are scheduled, staff allocation and meetings.
The analysis includes the gathering of requirements, defining the system requirements and investing
requirements. The design includes designing of the project layout and User interface designing and
wireframes and prototype designing with database designing. Development & testing includes the
development of the software and its testing. The deployment includes final meeting, final report
Page 9