COIT20248: System Analysis Responsibilities for HIS Implementation

This report, prepared by a student for Desklib, analyzes the system analysis responsibilities associated with implementing a Hospital Information System (HIS) in a healthcare organization. It begins by comparing different software development approaches, recommending Agile software development, and justifying this choice. The report then identifies and discusses both functional requirements (e.g., registration, reporting) and non-functional requirements (e.g., scalability, availability) of the HIS. A detailed cost-benefit analysis is presented, including a determination of investment decisions, comparison of costs and benefits, and break-even analysis. The project schedule is visualized using a Gantt chart. The report concludes by identifying stakeholders, discussing system investigation techniques, and reflecting on the overall project. All the information is presented in the form of tables and graphs for better understanding.

Running head: SYSTEM ANALYSIS RESPONSIBILITIES
System analysis responsibilities
Name of the Student
Name of the University
Author Note:

1SYSTEM ANALYSIS RESPONSIBILITIES
Table of Contents
Introduction......................................................................................................................................3
Task 1: Approaches to Systems Development................................................................................4
Developing of the Hospital Information System.........................................................................4
Comparison between different types of software development approaches...............................4
Best practise for the development of HIS....................................................................................5
Justification..................................................................................................................................5
Task 2: Systems Requirements........................................................................................................6
Functional requirements for HIS.................................................................................................6
List and discuss the requirements................................................................................................6
Non-functional requirements for HIS..........................................................................................6
List and discuss the requirements................................................................................................7
Justification of non-functional requirements...............................................................................7
Task 3: Project Cost Benefit Analysis.............................................................................................7
Determination of the investment decision...................................................................................8
Comparison of investments with total expected cost and total expected benefit........................9
Task 4: Project Schedule...............................................................................................................11
Significance of project scheduling.............................................................................................13
Task 5: System Information Requirement Investigation Techniques............................................13
Stakeholders involved................................................................................................................13
Useful investigation techniques.................................................................................................16
Justify of the usefulness of these 3 investigation techniques....................................................16
Reflection and Conclusion.............................................................................................................17
Reference.......................................................................................................................................18

2SYSTEM ANALYSIS RESPONSIBILITIES
Introduction
The notable determination of the paper is to focus on the system analysis responsibilities
of the incorporation of a Hospital Information System (HIS) in a healthcare organization as a
software consultant.
a. The paper will be having numerous segments and each of the segments needs to be understood
in the first place so that the complexities associated with the project can be minimized. The cost
associated with this project will be discussed in a detailed manner in this project along with the
stakeholders who will be involved in this project (Ahmadi, Nilashi and Ibrahim 2015). The
project scheduling of this paper will be presented in the form of a gnat chart diagram.
b. The prime objectives of this project are as followings:
o Comparison of different software development approaches and identifying the best
practice for the development of HIS. Justification of the choice of software development
approach.
o Identification of the functional and the non-functional requirements of HIS along with the
justification of the choice of the non-functional requirements.
o To determine if the investments decisions of the board of the organization is sound or not.
o Comparison of the total expected cost of each option with the total expected benefits.
o Providing the EBS structure and the project scheduling techniques along with the
justification of the project schedule.
o Identification of the stakeholders associated with the project.

3SYSTEM ANALYSIS RESPONSIBILITIES
o Identification of the useful investigation techniques along with the justification of the
usefulness of the investigation techniques.

4SYSTEM ANALYSIS RESPONSIBILITIES
Task 1: Approaches to Systems Development
Developing of the Hospital Information System
The development of the Hospital Information System (HIS), must be done in such as way
so that it can be helpful for both the consumers as well as the internal stakeholders of the
organization such as the administrative departments and the other essential employees such as
the doctors and the internal medical stores (Alam et al. 2015). The patient registration, billing of
the patients, electronic health records, patient data, finance records, records associated with the
use of the different types of technologies which are used in this organization can be managed in a
better way with the use of the HIS.
Comparison between different types of software development approaches
There are different categories of software development approaches which are discussed
below:
 Agile Software Development: Additional modifications can be done easily in this
software developmental approach.
 Crystal methods: Communication between the stakeholders are important in this
software developmental approach.
 Dynamic systems developmental model: This software developmental approach can be
useful to manage the difficulties of the organization (Angst et al. 2017). However the
existing process of the organizations may need to be altered regarding the use of the HIS.
 Extreme programming: This software development approach is mainly used in the
modifications of existing software.

5SYSTEM ANALYSIS RESPONSIBILITIES
 Feature driven developmental: This agile software development approach can be very
much useful to maintain the cohesiveness of the organization (Xie, Yang and Yang
2018). Feature listing of the software can be done stepwise for this software
developmental approach.
 Joint application development: The development of the computer-based systems which
are based on the interactions are developed with the help of this software developmental
approach.
 Lean development: This software developmental approach can be very much useful for
the maintenance of existing software, the bugs and the vulnerabilities of the software can
be identified and removed using this software developmental approach.
 Rapid application development: This is an adaptive software developmental approach
which is entirely based on the RAD model (Cho et al. 2015). The prototype of the
systems can be managed very professionally in each phase of this software
developmental approach.
Best practise for the development of HIS
The development of the HIS can be done with the help of agile software development.
Justification
The agile software development procedure can be very much important to deal with the
complexities and the dynamism of the healthcare organization such as the increasing needs and
requirements of the consumers of this organization (English et al. 2018). The healthcare
organization have different categories of subsidiary organizations associated with them, the agile
software development approach can be very much useful for the development of the HIS as this

6SYSTEM ANALYSIS RESPONSIBILITIES
approach will be useful for the organization regarding the addition of additional features if
required after the completion of the project.
Task 2: Systems Requirements
Functional requirements for HIS
The functional requirements for the Hospital Information System includes the registration
page and the checkout options for the consumers of the organization as well as for the internal
stakeholders of the organization (Fredman et al. 2017). The generation of different types of
reports and maintaining of the organizational database for the HIS are the other functional
requirement of the HIS.
List and discuss the requirements
 Registration page and checkout options: The registration process is the primary
functional requirement regarding the use of the HIS by its different stakeholders (Zhang
et al. 2017). The checkout option is also important to maintain the security of the
accounts of the Information System.
 Report generation: The generation of the business reports, financial report and
electronic health records can be useful to maintain transparency in the business.
 Maintenance of database: All the data which are being accessed or used in8 this IS can
be stored and managed using the organizational database.

7SYSTEM ANALYSIS RESPONSIBILITIES
Non-functional requirements for HIS
The non-functional requirement of HIS includes the scalability issues of the organization,
availability of the system to all the stakeholders of the business, data recovery options, security
of the organizational assets, manageability and the usability of the system.
List and discuss the requirements
 Scalability: The medical workers of the organization can be positively impacted due to
the use of the HIS.
 Availability: The availability of this software is very much important for this
organization as it must be available for all the stakeholders associated with the business.
 Data recovery options: The data recovery plan must be compatible with the HIS.
 Manageability: The issues of this system must be identified during the testing phase of
this software.
 Usability: The new system must be compatible with different types of browsers as well
as in the mobile devices.
Justification of non-functional requirements
The non-functions requirements can be very much important for the healthcare
organization so that the business processes can be optimized using the HIS. The introduction or
the addition of the patient management system can be very much important to deal with the
patient data and the business data of this organization (Handayani et al. 2016). The increased
availability of the system will ensure the success of the software as well. The data recovery plan
can be important to deal with the data which may be lost in the network or difficult to retrieve
from the database.

8SYSTEM ANALYSIS RESPONSIBILITIES
Task 3: Project Cost Benefit Analysis
Determination of the investment decision
The total estimated cost regarding the implementation of the Hospital Management
System is $78000 USD (Sharma et al. 2016). The cost regarding the development of this IS is
$70000 USD and the additional cost required for this project is $8000 USD.
Development of the HIS 70000
Additional cost 8000
Total Cost for the project 78000
Total Cost for the project
Figure1: Total Cost of the project
(Created by the author)
Year of Project
year 0 year1 year 2 year 3 year 4 year 5 TOTALS
Net economic benefit $0.00 $35,000.00 $35,000.00 $35,000.00 $35,000.00 $35,000.00
Discount Rate 8% 1 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Benefits $0.00 $32,407.41 $30,006.86 $27,784.13 $25,726.04 $23,820.41
NPV of all BENEFITS $0.00 $32,407.41 $62,414.27 $90,198.39 $1,15,924.44 $1,39,744.85 $4,40,689.36
One Time Costs $78,000.00
Recurring Costs $0.00 $100.00 $100.00 $100.00 $100.00 $100.00
Discount Rate 8% 1.0000 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Recurring Costs $0.00 $92.59 $85.73 $79.38 $73.50 $68.06
NPV Of All Costs $78,000.00 $78,092.59 $78,178.33 $78,257.71 $78,331.21 $78,399.27 $4,69,259.11
Overall NPV ($28,569.75)
Overall ROI = (Overall NPV / NPV Of All Costs -0.06
Figure 2: NPV of all cost in the next five years
(Source: Created by the author)

9SYSTEM ANALYSIS RESPONSIBILITIES
Based on the above diagram it can be concluded that the NPV of all the cost associated
with the implementation of the HIS for a period of 5 years is $469259 (Nilashi, et al. 2016).11
USD and the overall POI is found to be -0.06.
Overall NPV ($28,569.75)
Overall ROI = (Overall NPV / NPV Of All Costs -0.06
Break-Even Analysis
Yearly NPV Cash Flow $0.00 $32,314.81 $29,921.12 $27,704.75 $25,652.54 $23,752.35
Overall NPV Cash Flow $78,000.00 ($45,685.19) ($15,764.06) $11,940.68 $37,593.23 $61,345.58
Project break-even occurs between years 2 and 3
Use 1st year of positive cash flow to calculate break-even fraction 2.5690 years
Figure 3: Break –Even Analysis (Year wise NPV cash flow)
(Source: Created by the author)
Based on the above discussion it was found that that the investments of the board of the
organization of $78000 will be returned back within 2.5 years in the form of $440689.36
(Mignerat and Rivard 2015). Thus $362689.36 will is net profit if the board decides to invest
$78000 on the incorporation of the HIS.
Comparison of investments with total expected cost and total expected benefit
The total expected cost for the project is $78000. Out of the total cost $70000 is required
for the implementation of the Hospital Information System and an additional cost of $8000
words are required as the maintenance cost of the HIS.

10SYSTEM ANALYSIS RESPONSIBILITIES
The NPV of the two different types of cost ($70000+$8000) in the first year is $32401.4,
for the second year is $62414.27, for the third years is $90198.39, for the fourth year is
$115924.44 and for the final year is $139744.85.
Task 4: Project Schedule
ID Task
Mode
Task Name Duration Start Finish Predecessors
1 Implementation of
HIS
56 days Wed 01-05-19 Wed 17-07-19
2 Phase 1 10 days Wed 01-05-19 Tue 14-05-19
3 Information
gathering
2 days Wed 01-05-19 Thu 02-05-19
4 Evaluation of data 2 days Fri 03-05-19 Mon 06-05-19 3
5 Documentation 5 days Tue 07-05-19 Mon 13-05-19 4
6 Evaluation 1 day Tue 14-05-19 Tue 14-05-19 5
7 Phase 2 11 days Tue 07-05-19 Tue 21-05-19
8 Identification of
the risks of the
project
5 days Tue 07-05-19 Mon 13-05-19 4
9 Detailed analysis
of the impact of
the risks
1 day Tue 14-05-19 Tue 14-05-19 8
10 Formation of
mitigation strategy
for each of the
identified risks
5 days Wed 15-05-19 Tue 21-05-19 9
11 Phase 3 5 days Wed 22-05-19 Tue 28-05-19
12 Evaluation of the
cost required in
each phase of the
project
5 days Wed 22-05-19 Tue 28-05-19 6,10
13 Phase 4 36 days Wed 29-05-19 Wed 17-07-19
14 Installation of HIS 30 days Wed 29-05-19 Tue 09-07-19 12
15 Project closure 5 days Wed 10-07-19 Tue 16-07-19 14
16 Project
Evaluation phase
1 day Wed 17-07-19 Wed 17-07-19 15
28 02 06 10 14 18 22 26 30 03 07 11 15 19 23 27 01 05 09 13 17 21
22 Apr '19 06 May '19 20 May '19 03 Jun '19 17 Jun '19 01 Jul '19 15 Jul '19
Figure 4: Project schedule for each of the phases of HIS
(Created by the author)
The above diagram is very much important to understand the different phases of the
project such as the followings:

11SYSTEM ANALYSIS RESPONSIBILITIES
Phase 1: The phase 1 of this project will be done in 10 days. The information gathering
for the project will require 2 days, along with that the data generation of this project will also
require 2 days, the documentation of the project will be done in 5 days and the evaluation of the
project can be done in a day.
Phase 2: The phase 2 of this project will be conducted in 11 days. The identification of
the project can be done in 5 days, the analysis of the risks of the project can be done in a day
(Handayani et al. 2017). The risk strategy of the each of the identified risks can be done in 5
days.
Phase 3: The evaluation of the cost required in each phase of the project will require
around 5 days.
Phase 4: The phase 4 of this project is the most important phase of the project which will
require around 36days. The installation process of the Health Information System in the working
environment of this healthcare organization will require a month as there are numerous
complexities in each of the departments of the hospital (Henry et al. 2016). The closure phase of
this project is a 5 day affair and the project evaluation day of this project is also a one day affair
in this project.

12SYSTEM ANALYSIS RESPONSIBILITIES
HIS
Implementation of HIS
Phase 1
Information
gathering
Evaluation of data
Documentation
Evaluation
Phase 2
Identification of the
risks of the project
Detailed analysis of
the impact of the risks
Formation of
mitigation strategy
for each of the
identified risks
Phase 3
Evaluation of the
cost required in
each phase of the
project
Phase 4
Installation of HIS
Project closure
Project Evaluation
phase
Figure 5: Work Breakdown Structure of the project
(Created by the author)
Both the above two diagrams are related to each other as both of them helps in
understanding each of the phases in this project along with the sub-phases as well (Kochan et al.
2018). The Gnat chart, however, provides additional details such as the time required for each of
the sub phases of this project along with the predecessors for each of the sub-activities.
Significance of project scheduling
Considering the given set of systems, and the discussed scope of this project, it can be
said that the project scope is very much reasonable.
Considering all the discussed functional and the non-functional requirements of the HIS it
can be said that the project scheduling is very much reason. The cost required in each phase of
the project which is described in phase 2 of this project will depend entirely on the evaluation
sub-phase of phase 1 (Liang et al. 2017). The implementation of the IS will also consider the

13SYSTEM ANALYSIS RESPONSIBILITIES
existing systems which are used in the organization, thus the installation of the IS will require a
minimum of 30 days. The impact of the HIS has to be understood by the board of this
organization which may require 5-6 days, these aspects were highly considered while the project
scheduling plan was created for this project (MacMillan, Slessarev and Etchells 2016). Thus, it
can be said that the discussed scope of the project is reasonable.
Task 5: System Information Requirement Investigation Techniques 300 words
Stakeholders involved
The different types of stakeholders associated with this project along with their primary
activities will be mentioned in the below table.
Stakeholder Category of stakeholder Activity
IT experts External The IT experts are very much
important fir this project as
there will be numerous issue
during or after the
development of the new IS.
Designers and developers of
HIS
External The role of the developers
and the designers are very
much important regarding the
successful completion of the
project on time.
Software testers and
maintenance team
External The software tester will
ensure the quality of service
provided by the new IS.
Chief Financial Officer Internal The financial decision of this
project will be managed by
the CFO.
Project manager Internal Leadership skills of the
project manager are important
in each phase of this project.

14SYSTEM ANALYSIS RESPONSIBILITIES
Operational manager Internal The operational manager can
manage the efficiency of the
workers which will be
involved in this project.
Floor manager Internal The floor manager is very
much to deal with the
complexities in this project
such as the compatibility with
the existing legacy systems.
Ward manager Internal Complexities of each ward in
terms of the technologies will
be manage by the ward
managers
Table 1: Stakeholders involved
(Source: Created by the author)
Useful investigation techniques.
The three different types of investigation techniques which can be used in this project are
as following:
 Descriptive investigation: This investigative technique does not include any comparison
or variables.
 Comparative investigation: This investigation technique involves numeric calculations
and collection of data.
 Experimental investigation: This investigative technique involves the manipulation,
control and measurement of that effort which will be given by the designers and the
developers of the HIS.
Justify of the usefulness of these 3 investigation techniques

15SYSTEM ANALYSIS RESPONSIBILITIES
This unit of the paper will be justifying above discussed investigative techniques.
 Descriptive investigation: This type of investigation technique can be used by the floor
managers of this healthcare organization to understand the impact of using this IS for
each of the employees of the organization.
 Comparative investigation: This type of investigative technique can be used by the
project managers of this organization while conducting the external environmental
analysis of the new system.
 Experimental investigation: This investigative option can be chosen by the software
testers of the project to enhance the quality of the IS.
Reflection and Conclusion
Achievement: According to me, the incorporation of the HIS can be very much useful
for the healthcare organization as it could have improved the business process of the
organization. I believe that the complexities of the organization has to be identified in the first
phase, this aspect has been already described in the project scheduling of this paper. I also
believe that the project scheduling unit of the paper will be very much beneficial to understand
each phases and the sub-phases of this project along with the time required for each of the
phases.
Constraints: However, I also believe that the investments from the board have to be
professionally planned so that each of the phase of the project is completed on time. The other
risk associated with this project is the management of time required in each phase of the project.
The other constraint of this project is defining the role of each stakeholder of the project such as

16SYSTEM ANALYSIS RESPONSIBILITIES
the different categories of managers like the floor manager, operational manager and ward
managers.
Conclusion: The paper is very much useful to understand most of the issue and
parameters associated with the incorporation of a Hospital Information System. The paper helps
in identifying the software development approach which can be useful regarding the
development of this IS which is the agile software development. The non-functional and the
functional software requirements of the HIS was also identified from this paper. The details of
the CBA was provided in the paper with the help of pictorial diagrams. The stakeholders
involved in the project and the investigation technique used by the stakeholders was also stated
in the paper.

17SYSTEM ANALYSIS RESPONSIBILITIES
Reference
Ahmadi, H., Nilashi, M. and Ibrahim, O., 2015. Organizational decision to adopt hospital
information system: An empirical investigation in the case of Malaysian public hospitals.
International journal of medical informatics, 84(3), pp.166-188.
Alam, M.G.R., Masum, A.K.M., Beh, L.S. and Hong, C.S., 2016. Critical factors influencing
decision to adopt human resource information system (HRIS) in hospitals. PloS one, 11(8),
p.e0160366.
Angst, C.M., Wowak, K.D., Handley, S.M. and Kelley, K., 2017. Antecedents of Information
Systems Sourcing Strategies in US Hospitals: A Longitudinal Study. MIS Quarterly, 41(4).
Cho, K.W., Bae, S.K., Ryu, J.H., Kim, K.N., An, C.H. and Chae, Y.M., 2015. Performance
evaluation of public hospital information systems by the information system success model.
Healthcare informatics research, 21(1), pp.43-48.
English, M., Mwaniki, P., Julius, T., Chepkirui, M., Gathara, D., Ouma, P.O., Cherutich, P.,
Okiro, E.A. and Snow, R.W., 2018. Hospital mortality–a neglected but rich source of
information supporting the transition to higher quality health systems in low and middle income
countries. BMC medicine, 16(1), p.32.
Fredman, D., Haas, J., Ban, Y., Jonsson, M., Svensson, L., Djarv, T., Hollenberg, J., Nordberg,
P., Ringh, M. and Claesson, A., 2017. Use of a geographic information system to identify
differences in automated external defibrillator installation in urban areas with similar incidence
of public out-of-hospital cardiac arrest: a retrospective registry-based study. BMJ open, 7(5),
p.e014801.

18SYSTEM ANALYSIS RESPONSIBILITIES
Handayani, P.W., Hidayanto, A.N., Ayuningtyas, D. and Budi, I., 2016. Hospital information
system institutionalization processes in indonesian public, government-owned and privately
owned hospitals. International journal of medical informatics, 95, pp.17-34.
Handayani, P.W., Hidayanto, A.N., Pinem, A.A., Hapsari, I.C., Sandhyaduhita, P.I. and Budi, I.,
2017. Acceptance model of a hospital information system. International journal of medical
informatics, 99, pp.11-28.
Henry, J., Pylypchuk, Y., Searcy, T. and Patel, V., 2016. Adoption of electronic health record
systems among US non-federal acute care hospitals: 2008-2015. ONC data brief, 35, pp.1-9.
Kochan, C.G., Nowicki, D.R., Sauser, B. and Randall, W.S., 2018. Impact of cloud-based
information sharing on hospital supply chain performance: A system dynamics framework.
International Journal of Production Economics, 195, pp.168-185.
Liang, C., Gu, D., Tao, F., Jain, H.K., Zhao, Y. and Ding, B., 2017. Influence of mechanism of
patient-accessible hospital information system implementation on doctor–patient relationships: A
service fairness perspective. Information & Management, 54(1), pp.57-72.
MacMillan, T.E., Slessarev, M. and Etchells, E., 2016. eWasted time: Redundant work during
hospital admission and discharge. Health informatics journal, 22(1), pp.60-66.
Mignerat, M. and Rivard, S., 2015. Positioning the institutional perspective in information
systems research. In Formulating Research Methods for Information Systems (pp. 79-126).
Palgrave Macmillan, London.

19SYSTEM ANALYSIS RESPONSIBILITIES
Nilashi, M., Ahmadi, H., Ahani, A., Ravangard, R. and bin Ibrahim, O., 2016. Determining the
importance of hospital information system adoption factors using fuzzy analytic network process
(ANP). Technological Forecasting and Social Change, 111, pp.244-264.
Sharma, L., Chandrasekaran, A., Boyer, K.K. and McDermott, C.M., 2016. The impact of health
information technology bundles on hospital performance: An econometric study. Journal of
Operations Management, 41, pp.25-41.
Xie, C., Yang, P. and Yang, Y., 2018. Open knowledge accessing method in IoT-based hospital
information system for medical record enrichment. IEEE Access, 6, pp.15202-15211.
Zhang, Y., Qiu, M., Tsai, C.W., Hassan, M.M. and Alamri, A., 2017. Health-CPS: Healthcare
cyber-physical system assisted by cloud and big data. IEEE Systems Journal, 11(1), pp.88-95.