Hospital Information System Development: A Comprehensive Report

Desklib provides past papers and solved assignments for students. This report details the development of 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
Introduction...........................................................................................................................................2
Approach to Systems Development......................................................................................................3
Systems Requirements..........................................................................................................................5
Project Cost-Benefit Analysis.................................................................................................................7
Project Schedule....................................................................................................................................8
System Information Requirement Investigation Techniques...............................................................10
Reflections and Conclusions................................................................................................................12
Page 1

Introduction
A hospital Information system is a type of information system which collects the
information regarding the hospitals. It stores the wealth of data generated by the
hospitals. This system includes various functions in order to manage the information
generated by the hospitals for better functioning. The system stores information like
information related to the patients who admitted for a short time as well as for a long
time (Moody et al., 2016). The system manages the data for the hospital to manage the
hospital workflow.
The main objective of this system is to manage the data of the hospital. The system is
introduced to form a functional architecture for the hospital in order to manage all
functioning of the hospital. The system is developed in order to be secure and safe in
point of view of data management. This system ensures the efficient flow of data into
the system. The system also ensures the semantic and syntactic interoperability in the
system.
Page 2

Approach to Systems Development
Features Waterfall model Prototyping
Model
Spiral model Iterative model
Requirements
specification at
the beginning of
the system
development
process.
The
requirements
specification is
required
(Alshamrani, A.
and Bahattab, A.,
2015).
The
requirements
frequently
change
Not all
requirements
specifications
are required
because some
of them are
changing.
Not all
requirements
specifications
are required
because some
of them are
changing.
Cost included in
the system
development
process.
Cost is almost
equal to the
estimated cost
in the waterfall
model.
Cost is generally
above from the
estimated cost.
Cost is very high
from the
estimated cost.
Cost is generally
above from the
estimated cost.
Success
Guarantee
The success
guarantee is low
in the waterfall
model.
A success
guarantee is
moderate in the
prototype
model,
A success
guarantee is
high in the spiral
model.
A success
guarantee is
high in the
iterative model.
Type of
framework
applied
The linear
framework is
required.
The iterative
framework is
required in
order to
develop the
system.
The
combination of
the iterative and
linear
framework is
required in
order to
develop the
The
combination of
the iterative and
linear
framework is
required in
order to
develop the
Page 3

system. system.
System testing The system
occurs after the
completion of
the coding
phase.
System testing
occurs after the
iterative
prototype
model.
System testing
occurs at the
end of the
engineering
phase of the
system.
System testing
occurs after
every iteration.
Customer
involvement in
the system
development
process.
Customer
involvement is
low in the
waterfall model.
Customer
involvement is
high after each
iteration.
Customer
involvement is
low after each
of the iterations.
Customer
involvement is
high after each
iteration.
We have used the spiral model in order to develop this system (Karagiannis, D., 2015). We
have preferred spiral model because it is the combination of the iterative and spiral model.
There are several advantages of the Spiral model:
 Each phase of the spiral model starts with a goal and in the end, the client can
also give a review after completing each phase.
 The additional changes can be done in this model at the later stage. Risk
management can be done with repeated development.
 In this model, there is space for feedback of the customer.
 In the spiral modelling cost estimation is easy.
 There is repeated or continuous development in this model.
There are some disadvantages to the Spiral model:
 For small projects, it cost a lot.
 In this model documentation is more.
 There are many protocols which have to follow strictly.
 There is a risk of not meeting the budget and cost.
Page 4

Systems Requirements
Functional requirements
Registration and Quick Registration: Registration is done in order to register a patient in the
system. Data related to any patient can be stored in the system after the registration only
(Nilashi et al., 2016). At the time of registration, the user has to enter the personal and
medical details. The quick Registration process is also available in the system which stores
the information like who did what, when and why for the reason for the action.
Biometric and Barcoding: Biometric and Barcode functional specification also added in the
system in order to track the patients, materials, medications and the services of the
hospital. These functionalities implemented to secure the data and track the information
fast and efficiently.
E-prescription: E-prescription functional specification also added in the system to generate
the prescription by the system. It makes the system more advanced. This specification helps
to make the work fast in the hospital.
Electronic Medical record: Electronic medical record specification is also introduced in the
system. This specification generates the medical record of the patient which include the
current and past medical history of a patient with their personal information.
Non-functional requirements
Data Security: Data security specification also implemented in the system in order to
maintain patient privacy and confidentiality. Data security is maintained by the passwords
generation and biometric scan facilities.
Management report: Management report also generated from the system which maintains
the rules of the hospital. This report contains the rules and regulation of the hospitals and
also includes the legal requirements which are necessary in order to enter in the system.
Add information and Notes: There is a secured remote access facility in order to view the
notes and information related to the patient and the services of the hospital. The system
Page 5

also provides the adding facility to the user so that the user can add the information and
notes remotely.
Page 6

Project Cost-Benefit Analysis
The cost benefits analysis is done in order to analyse the decisions made by hospital
management. This helps the hospital system to calculate the internal rate of return, return
on investment and net present value which help the system to take the decision on future
investment.
Table 1: cost benefit analysis
Page 7

Project Schedule
Work Breakdown Structure (WBS)
Work Breakdown Structure is used to represents the project in the manageable sections. It
defines the scope into the manageable section which a development team can understand.
In this system, WBS is created by identifying the hospital functional deliverables and then
further dividing them into the smaller sub-deliverables. These sub-deliverables can be
further divided. This helps the hospital system to distribute the cost investment into the
various sub deliverables and deliverables.
This is the Work Breakdown Structure for the Hospital Management System:
Figure 1 WBS
Page 8

Gantt chart
Gantt chart is created in order to scheduling and planning the Hospital Management System
activities. This can help the Hospital Management System to assess that for how long an
activity can be performed in the system. Gantt chart is also helpful in managing the
dependencies between the Hospital Management System tasks and sub-tasks.
The lifecycle of Hospital Information System development with the milestones are
represented by the given Gantt chart:
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names Cost
0 Hospital
Information
System
50 days Tue
23-04-19
Mon
01-07-19
$750,480.00
1 1 Project Planning9 days Tue 23-04-19Fri 03-05-19 $72,000.00
2 1.1 Define the
project
4 days Tue
23-04-19
Fri 26-04-19 Project
manager
$32,000.00
3 1.2
Scheduling
and planning
3 days Mon
29-04-19
Wed
01-05-19
2 Project
manager
$24,000.00
4 1.3 Project
staff meeting
2 days Thu
02-05-19
Fri 03-05-19 3 Project
manager
$16,000.00
5 2 RequirementAnalysis17 days Mon 06-05-19Tue 28-05-191 $272,000.00
6 2.1 Gathering
requirements
& information
4 days Mon
06-05-19
Thu
09-05-19
Developer,Project
manager
$64,000.00
7 2.2 Requirements5 days Fri 10-05-19 Thu 16-05-196 Developer,Project manager$80,000.00
8 2.3
Requirement
investigation
8 days Fri 17-05-19 Tue
28-05-19
7 Developer,Project
manager
$128,000.00
9 3 System
architecture
designing
3 days Wed
29-05-19
Fri 31-05-19 5 $46,880.00
10 3.1 Layout the
project
1 day Wed
29-05-19
Wed
29-05-19
Developer,Project
manager,System
designer
$23,440.00
11 3.2 User
Interface
Designing
1 day Thu
30-05-19
Thu
30-05-19
10 Developer $8,000.00
12 3.3
Implement
database
1 day Fri 31-05-19 Fri 31-05-19 11 Project
manager,System
designer
$15,440.00
13 4 System
development &
testing
6 days Mon
03-06-19
Mon
10-06-19
9 $92,640.00
14 4.1 System
software
development
2 days Mon
03-06-19
Tue
04-06-19
Developer,System
designer
$30,880.00
15 4.2 System
Testing
4 days Wed
05-06-19
Mon
10-06-19
14 Project
manager,System
designer
$61,760.00
16 5 Deployment
of the system
9 days Tue
11-06-19
Fri 21-06-19 13 $186,960.00
17 5.1 Staff final
meeting
3 days Tue
11-06-19
Thu
13-06-19
Project
manager,System
designer
$46,320.00
18 5.2
Submission of
final report
6 days Fri 14-06-19 Fri 21-06-19 17 Developer,Project
manager,System
designer
$140,640.00
19 6 System
maintenance
6 days Mon
24-06-19
Mon
01-07-19
16 $80,000.00
20 6.1 User support4 days Mon 24-06-19Thu 27-06-19 Developer,Project manager$64,000.00
21 6.2
Maintenance
of the system
2 days Fri 28-06-19 Mon
01-07-19
20 Developer $16,000.00
Project manager
Project manager
Project manager
Developer,Project manager
Developer,Project manager
Developer,Project manager
Developer,Project manager,System designer
Developer
Project manager,System designer
Developer,System designer
Project manager,System designer
Project manager,System designer
Developer,Project manager,System designer
Developer,Project manager
Developer
Apr May Jun Jul Aug
Qtr 2, 2019 Qtr 3, 2019
Figure 2 Gantt chart
Page 9

Gantt chart and WBS
WBS is a hierarchical decomposition of a system or project into the manageable sections
until they become manageable. The Gantt chart is generated from WBS. For WBS main
deliverables of the projects are required. For Gantt chart the WBS is required also the
branches should be updated to make them a task list.
Page 10