Hospital Information System Analysis and Design: COIT20248 Report

This report presents a comprehensive analysis of a Hospital Information System (HIS), detailing the approach to system development, system requirements, project cost-benefit analysis, project schedule, and system information requirement investigation techniques. The report emphasizes the use of agile methodology for HIS development, highlighting its iterative and incremental approach. It outlines both functional and non-functional requirements, adhering to the FURPS model, and provides a cost-benefit analysis demonstrating the financial implications over a five-year period. The project schedule is presented through a work breakdown structure and Gantt chart, illustrating the tasks and timelines. Furthermore, the report identifies key stakeholders and explores various investigation techniques employed in gathering system information, including interviews and document analysis. The ultimate goal of the project is to create an efficient and user-friendly information system for managing all hospital activities, including patient management, doctor-patient communication, and inventory control. The report concludes with reflections and conclusions, summarizing the findings and their implications for HIS implementation.

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 (TOC)
1. Introduction............................................................................................................................1
2. Approach to Systems Development.......................................................................................2
3. Systems Requirements...........................................................................................................3
4. Project Cost Benefit Analysis..................................................................................................5
5. Project Schedule.....................................................................................................................6
6. System Information Requirement Investigation Techniques................................................8
7. Reflections and Conclusions.................................................................................................11
8. Bibliography.........................................................................................................................12

1. Introduction
This report details the new information system of the Hospital Information System
that are mainly used in the hospitals. This report provided an approach to developing the
HIS system for the hospitals and the requirements of the system that are needed for
developing the system. The cost benefits analysis of the project is also defined in this project
along with the investigation techniques for gathering information system information.
a) The main aim of this project is to develop an information system for managing all
the activities of a hospital. The information system will able the users to handle their own
account from uploading their data and contacting their personal health doctors. This project
also aims to identify the stakeholders involved with the automated information system of
Hospital Management System.
b) The objective of the project is
 To create an approach of system development for developing the HIS system.
 To identify the functional as well as non-functional requirements that will be needed
for developing the HIS system.
 To create the cost benefit analysis for the project that is defined.
 To develop a project schedule for developing the information system.
 To find out the techniques used to investigate the information system.
Page 1

2. Approach to Systems Development
a) The approaches that are used for developing a software are waterfall model,
prototype model, spiral model, extreme programming model, agile model, RAD (Rapid
Application Development) and JAD (Joint Application Development).
The model that is used for developing the information system for HIS is agile
methodology of project management (Kerzner and Kerzner 2017). In agile methodology
iteration is used for developing the software application in life cycle of the system
development. In this particular approach of agile methodology, the development phase and
the testing phase are carried out concurrently which is not possible for any other type
approach used in system development (Kerzner and Kerzner 2017). Agile methodology of
system development includes team interaction for completing the processes as well as the
tools. The agile methodology also enhance working of the software along with the
documentation of the software. Customer collaboration is mainly focused over the contract
negotiation and this particular methodology focuses on the change that are included in a
plan.
b) The agile methodology is basically used in this project because this method
proposes iterative as well as incremental approach for designing the Information system
(Binder 2016). For completing the information system of HIS, the agile approach breaks
down the project in to small parts so that the team finds it easy to complete the project. As
agile methodology enhance customer involvement in the project, the agile methodology is
best for developing the HIS system. The information system of the project will be considered
Page 2

developed according the requirement of the customer. This particular methodology does
not have any structure for dealing the processes in the project. All the errors can be fixed
while the project is running as it runs the testing phase concurrently along with the
implementation phase. So, agile methodology is considered as the best approach that can
be used for conducting this HIS new information system.
3. Systems Requirements
a) The functional requirements that will be included in the HIS information system
are stated below:
 The user or the customer will have a signup process that will enable the patient to
register themselves for the system and have a unique id for each user.
 The user can avail quick registration when there is emergency.
 The user can input their personal details on the database of the information system
and upload their previous records.
 User can view the details of their doctors assigned and can have a talk with them
online.
 The user can also check their medical insurance eligibility with the information
system.
 The user can contact the doctors for outpatient service in case of emergency.
 The system can provide with e-prescription when there is an outpatient service.
Page 3

 The system will have the accessibility to provide Electronic Medical Record (EMR) for
all the lab test, radiology tests and PACS.
 The doctors also needs to login to the system and have access to the information of
the patients and add some specific notes if required.
 The system also keeps the record of the medical inventory and aware the
stakeholders if there is shortage of inventory.
 The system also has the bar coding mechanism which helps the system to track the
patients, the services that they provide, the medication and the materials that are
used in the system.
 The system also updates the rules, and regulations that are used in managing the
information system.
b) The non-functional requirements that are included in the new automatic
information system should follows the FURPS model (Schwalbe 2015). This model is mainly
categorized in to five different categories known as Functional, Usability, Reliability,
performance, as well as supportability.
The new information system is considered to have usability because the system will
all limitless user to access the system. No limits on the user expertise on the system (Turner
2016). The user interface of the new information system will have standard notations and
documentation will be provided for the system that is being developed.
Page 4

The system is reliable as all the security measures will be considered for developing
the system (Joslin and Müller 2015). The system will be able to handle its data in a safe and
secure method. The system will also have qualities like robustness, reliability, and
availability. It is capable of handling the exception and has error tolerance.
The system that is being developed also supports performance feature of FURPs as
the system supports unlimited number of users in the system (Heldman 2015). The response
time of the pages in the system are also less which increases the performance of the system.
The system support large amount of transactions per second.
Supportability is also included in this system as the system is developed with agile
methodology, it has the scope of changing the objective of the system and increasing t=its
functions as per usability.
4. Project Cost Benefit Analysis
a) The investment done for developing the HIS information system is not profitable
for the system up to 2.7 years. After developing the information system, the management
was able to make out the investment in 2.7 years. In the first year, the overall NPV (Net
profit Value) for developing the system was $462,500 and in the second year the value still
remained negative. So, for the first two years the company was running at loss. At the end
of third year, there was a profit of $50,188 and the profit amount started increasing
gradually. The cost benefit analysis shows the benefit of five years and by the end of five
years, the company was able to return $489,736 as a NPV value for the company. In total
the benefit of the project was increased to $278,415 from the cost.
Page 5

b) The investment that is done for each year is $318,000 and with recurring cost to
be $7,500 with a discount rate of 8% the total cost for 1st year should have been $750,000
and the profit for that particular year was $287,500 where there was a deficit of $462,500.
For the second year, there was a deficit of $196,296. From the third year, the company
started gaining profit from the investments that were made. There was a profit of $50,188
in the third year and $278,415 in the 4th year and in the fifth year, the profit was increased
to $489,736. The company was able to make out its investment by the end of 2.7 years.
5. Project Schedule
a) Work Breakdown structure
HIS Information system
Requirement gathering
Preparing the
Business case
Creating
specifications of
system requirement
Initiating Test
Planning for the
System
Performing the Risk
assessment
Developing the
project schedule
Developing the
management plan
Developing Quality
Plan
Checklist Phase
Design Phase
Creating conceptual
design
Creating logical
design
Creating physical
design
Creating
Implementation as
well as contigency
plan
Creating transition
plan
Checklist Phase
Developing Phase
Building a prototype
Executing the
management plan
Creating a database
Generating new data
Generating Modules
Developing the
media content
Reviewing the code
Preparing and
executing the Unit
test
Vefifying the
Application Build
Creating training
materials
Checklist Phase
Implementation Phase
Finalizing the
Implementation
Finalizing the
transition plan
Authorizing and
preparing the
deployment
Deploying the
solution
Acceptance of
deployed solution
Checklist Phase
Project Closure
Conducting Project
Review
Gathering
documents of
project
Conducting Project
Performance
Project Sign Off
Figure 1: Work Breakdown Structure
(Source: Created by Author)
Page 6

Project Gantt chart
Figure 2: Gantt chart
(Source: Created by Author)
Page 7

The project work breakdown structure is shown in figure 1 and figure 2 shows the
project Gantt chart that is designed for developing the HIS Information System. The WBS is
generally a project deliverable that is to be organized to the team’s work so that that it can
be managed easily (Larson and Gray 2017). The WBS is a structure that states the workflow
of the project. It is visual structure that defines the project scope in many different sections
so that the project is easily understandable. On the other hand, the project Gantt chart is a
bar representation chart of the tasks. The project schedule helps the team to get a graphical
representation of the project tasks that are to be carried out. This helps the team to get a
scheduled date of the project tasks, coordinate with the activities and track the tasks that
are already being completed.
b) The project schedule is reasonable as the project satisfies the project goal and the
objectives of the project that were assumed for the project (Hornstein 2015). The project
schedule shows the tasks or the activities that were assumed for developing the information
system of HIS. The goal of the system was to develop an information system that can be
used in HIS. All the requirements are fulfilled by the information system and satisfies the
scope of the project.
6. System Information Requirement Investigation Techniques
a. The stakeholders who are associated with this project are: Project manager, the
management of HIS, the users, doctors, and the system analyst.
Stakeholders Role of Stakeholders
1. Project Manager The project manager in this project has the
Page 8

role to complete the project as per the
schedule time and schedule budget. The
project manager has interest on the project
as because he needs to complete the project
on time with less budget to compete in the
market.
2. System Analyst The role of system analyst is to analyze the
system that is being built. The main role of
the system analyst is to check the testing of
the information system and check whether
the system is working well or not.
3. Patients or Users The patients or the user needs to login to the
information system to get the service of the
Hospital Information system. They can have
emergency call when needed and can book
short term bed or long term bed in the
hospital nearby.
4. Management Team of HIS This stakeholder maintains all the inventory
system and the status of the patients,
doctors and staffs associated with the
system. The management team also checks
Page 9

the payment status and insurance policy of
the patient.
5. Doctors The doctors associated with the information
provides service to the patients, checks
outpatients in case of emergency and
uploads prescription online or any additional
note for the patients.
b. Three techniques that are used for investigation techniques are planning,
collecting the data as well as analyzing the data that will be used for this project.
c. These three techniques are used in this project to collect the requirement of the
project that is needed by the users and the management team of HIS. Planning is needed for
developing the information system of HIS as because without planning, the project will not
be completed successfully (Svejvig and Andersen 2015). Collecting of data regarding the
requirement of project is required for developing the information system and analyzing the
data after the system is being built up to check whether all the requirement and objectives
are fulfilled or not.
7. Reflections and Conclusions
a. This particular project states the planning procedure of information system. This
project states the work breakdown structure of the project along with the approaches that
Page 10

are to be used in the project. This project teaches about how to complete a project
successfully within the scheduled time and scheduled budget. This project also helped in
achieving the ways to complete the project as per the requirement of the project and fulfills
the user specifications.
b. All procedures that are needed for developing the information system of the
project are stated in this project. This project clears the plan for developing the information
system. All the business requirements are used by the developer for developing this project.
The project finds all the possible functional as well as non-functional requirements that are
needed for completing the project. This project also includes project investigating
techniques that are explained in this project specifying which investigating technique is
useful for completing this particular project.
Page 11

8. Bibliography
Binder, J. 2016. Global project management: communication, collaboration and
management across borders. Routledge.
Harrison, F., and Lock, D. 2017. Advanced project management: a structured approach.
Routledge.
Heldman, K. 2018. PMP: project management professional exam study guide. John Wiley &
Sons.
Hornstein, H.A., 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
pp.291-298.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology
and project success in different project governance contexts. International Journal of Project
Management, 33(6), pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Larson, E.W. and Gray, C.F., 2017. Project management: The managerial process. McGraw-
Hill Education.
Muller, R., 2017. Project governance. Routledge.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Routledge.
Ramazani, J. and Jergeas, G., 2015. Project managers and the journey from good to great:
The benefits of investment in project management training and education. International
Journal of Project Management, 33(1), pp.41-52.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.
Svejvig, P., and Andersen, P. 2015. Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), 278-290.
Turner, R., 2016. Gower handbook of project management. Routledge.
Page 12