Development of Electronic Health Record in Australian Pharmaceutical Industries

The report is based on development of Electronic Health Record in Australian Pharmaceutical Industries. The existing EHR system of Australian Pharmaceutical Industries fails to deliver of accurately billing data for proper claim submittal. Therefore, a new system with new features are developed for the company. The scope of this project study is to design, develop, code, and host the electronic health record system for Australian Pharmaceutical Industries. The healthcare solutions should be complaint and it is up-to-date with enhance of processes which lead to quality patient care. The solution will integrate with the existing applications by utilization of HL7 interface and there is also solution which is packaged with 7days/24hours/365days support.

Running head: PROJECT PROPOSAL AND PLAN
Project Proposal and Plan: Development of Electronic Health Record in Australian
Pharmaceutical Industries
Name of the Student:
Name of the University:

1PROJECT PROPOSAL AND PLAN
Executive Summary
The report is based on development of Electronic Health Record in Australian
Pharmaceutical Industries. The existing EHR system of Australian Pharmaceutical Industries
fails to deliver of accurately billing data for proper claim submittal. Therefore, a new system
with new features are developed for the company. The scope of this project study is to design,
develop, code, and host the electronic health record system for Australian Pharmaceutical
Industries. The healthcare solutions should be complaint and it is up-to-date with enhance of
processes which lead to quality patient care. The solution will integrate with the existing
applications by utilization of HL7 interface and there is also solution which is packaged with
7days/24hours/365days support.

2PROJECT PROPOSAL AND PLAN
Table of Contents
1.0 Introduction to project..........................................................................................................3
2.0 Description of proposed project...........................................................................................3
2.1 Problems and solutions of EHR system in Australian Pharmaceutical Industries...........4
2.2 Recommended option impact...........................................................................................4
2.3 Implementation plan.........................................................................................................5
2.4 Future scope of proposed system.....................................................................................5
3.0 Project management overview.............................................................................................6
3.1 Scope of project................................................................................................................6
3.2 Objectives and constraints................................................................................................7
3.3 Statement of work............................................................................................................8
3.4 Project team members and responsibilities matrix...........................................................9
3.5 Work breakdown structure.............................................................................................11
3.6 Project schedule.............................................................................................................13
4.0 Risk assessment and plan...................................................................................................16
5.0 Quality plan........................................................................................................................18
6.0 Summary............................................................................................................................19
Bibliography.............................................................................................................................21

3PROJECT PROPOSAL AND PLAN
1.0 Introduction to project
The project plan is based on development of Electronic Health Record in Australian
Pharmaceutical Industries. The Electronic Health Record (EHR) is an electronic record of the
patient health evidence which is being produced by happenstances into daily care delivering
setting. The information system is being generated of patient data such as demographics of
patients, development notes, medications, historical medical history as well as workshop
data. The system is automated and streamlined of clinician workflows and has capability to
create of comprehensive record of the medical patient meeting and supported of healthcare
activities. The government, industry and medical centres are used of EHR to view as well as
manage into one place. It is simplified that this system is known as clinical information
systems.
The plan is analyzed from project management perspective where a plan is prepared
to determine the start in addition end date to the plan work with scope of project, objectives,
constraints and statement of work. There is also determination of project team members as
well as responsibilities of stakeholders those are involved into the project work. Work
breakdown structure and project schedule is analyzed to determine the required time for
completion of this work plan. Risks are also analyzed so that further prevention are to be
taken to mitigate any delays into the project work. Quality plan is also prepared to check for
quality of the proposed system into the company.
2.0 Description of proposed project
Australian Pharmaceutical Industries seeks to remove of its existing record heath
record system from use and implement a new solution which maintain of diverse features into
it. The benefits of the proposed system is enhanced of patient access to care and greater

4PROJECT PROPOSAL AND PLAN
surgical volume. The scope of this system is implementation of user friendly electronic health
record which is being hosted by means of system service provider.
2.1 Problems and solutions of EHR system in Australian Pharmaceutical
Industries
The existing EHR system of Australian Pharmaceutical Industries fails to deliver of
accurately billing data for proper claim submittal. The proposed healthcare record system is
anticipated of solutions to providing of enhanced charge capture functionalities. The system
is not failing to meet with mandates acted by Department of Health and Human Services. The
proposed solution is certified to electronic health record technology. There is also
maintenance of functionality to collect as well as analyse of meaningful use. The system is
not interfaced with new billing systems and get of new system to find new way towards
interface. The project plan is aligned with mission as well as goals of practice to standardize
payment and health related operations. The healthcare solutions should be complaint and it is
up-to-date with enhance of processes which lead to quality patient care. The solution will
integrate with the existing applications by utilization of HL7 interface and there is also
solution which is packaged with 7days/24hours/365days support. There are also updates as
well as enhancements which is provided of no such addition cost to the business practices.
2.2 Recommended option impact
The proposed solution has some impacts on following areas such as:
Impact on existing clinical environment: Impact on the clinical workflow is being
insignificant then there is required for minimal training as well as education for preparation
of staffs.
Impact on existing financial environment: The financial impact is moderate because
of continual licensing as well as cost of maintenance is being associated with purchase of the

5PROJECT PROPOSAL AND PLAN
solutions. The financial constraints are being hinder the business practices which is needed
for acquire of new solutions. It is such a decision to avoid of any loan procurement.
Impact on existing administrative environment: The solution is being anticipated for
reduction of errors into clinical documents, maximization of revenue capture and also
enhance of administration reporting for entire practices. The proposed process will affect
daily duties for the staffs.
Impact on IT: There are support of services which is required to provide of 7/24/365
support to the patients. Downtime support structure is developed to meet with end user’s
requirements, and secondary support is failed to the super uses established at time of the
implementation processes.
2.3 Implementation plan
By the contractual agreement, the software vendor is going to provide of integration
testing for the software interfaces which will able to transmit of data among the systems.
Testing of proposed system is included but it is not limited to HL7 interfaces as well as
information exchanges. The software vendor is agreed to the load agency as the service. In
order for transferring of data, the software vendor is required to develop, transfer and load job
for the database. The vendor is provided of validation testing on customer completed with
figure necessities. After achievement of authentication testing, the client is required to grow
of testing scripts to authenticate that the software is being working as it is calculated. Post
implementation is also included into the study. The vendor is agreed all the support changes,
upgradation of codes and enhancements of customers prior to implement into production.
Testing is not revealed with the system issues and it should use for identification of errors
which affect payment as well as operations of proposed system.

6PROJECT PROPOSAL AND PLAN
2.4 Future scope of proposed system
In future, the system will become centred on story of the introduction of patient’s. It
will evaluate of stream of patient’s throughout clinic. The proposed information system is
advanced and get ability to accomplish of record occasions and expansion of findings. The
system will enable to take advantage of database of the patient’s data, encouragement of
accuracy prescriptions. EHR will upgrade to commitment as it ends up vital to the patient
experiences. The project plan is delivered on schedule, increased of adoption among the
patients as well as physicians, testing practices processes into the system and mitigation of
error into patient’s data. The system is being designed to provide of opportunities for advance
planning as well as allocation of resources and also timeline for deployment of project
activities. The system is provided and indicated of widespread concerns about the
recordkeeping effects on the public health. The clinicians and health care providers are used
of the system for meeting with the technological requirements of Australian Pharmaceutical
Industries.
3.0 Project management overview
3.1 Scope of project
The scope of this project work is implementation of EHR which will improve quality
care of patients, avert of medical errors, lessen of the health care costs, rise of administrative
effectiveness, lessening of paperwork as well as develop access to affordable care. As there is
progress of project work, capabilities of EHR impacts become easier. Throughout the time,
requests are to be modified and expanded scope for implementation. The proposed
information system is taking into account for the clinical requirement of the health
professionals to provide of health related services. EHR information are completed and it is
integral to maintain of quality of the system. The primary determination of this system is to

7PROJECT PROPOSAL AND PLAN
provide benefit to the patient throughout support of current along with future healthcare
requirements.
The scope of this project study is to design, develop, code, and host the electronic
health record system for Australian Pharmaceutical Industries. The software vendor will host
as well as complete of training which is required to implement new system into the company.
Following are some of the criteria such as:
 To visualize agreeable and user friendly environment into the organization
 Mitigation of present application data over new and modified system
 Software as well as licensing are inclusive to the project work
 System is well-matched with existing technologies in addition coding systems
 Planning in addition performing comprehensive testing processes on the system to
make sure about the system functionality
 Hosting of system but it is not limited to generate of project reports such as
productivity, and HIPAA required reports
3.2 Objectives and constraints
Following are the project objectives for this project study such as:
 To develop of quantifiable goals for acceptance of EHR besides superiority
improvement
 To frame of strategies for supervise communiqué as well as change management
 To create of work plan for implementation of EHR
 To formulate of features and functionality that EHR is successful
There are some of the project constraints into the plan such as when required resources
are not available, then there is an increase of time to deliver the project on time. It results to
increase of project cost as alternative resources when available are expensive than it is

8PROJECT PROPOSAL AND PLAN
planned. When the quality analyst team finds that quality of project deliverable is not bad,
then more resources are to be required. There is an increase into cost for additional resources
and there is an effort to fix the project deliverables. It will also increase of time for delivering
the project plan. When project scope creep is happened on the project, then it is resulted into
increase of time, cost as well as resources along with reduction of quality. Therefore, there is
an increase of risk to deliver the project on scheduled time by the project manager.
3.3 Statement of work
The schedule of this project work is followed of steps such as plan for EHR
implementation, selection of the system, implementation of the proposed system and
optimization of the system for quality improvement. Development of EHR into the Australian
healthcare organization helps to make sure that the project plan is being performed as per
project specifications as well as expectations of project clients and team members. The total
duration of this project plan is 4 months and the clinical benefits of this project work is to
generate with increase of effectiveness to provide of medical care and facilitate of new
services which are not previously provided.

9PROJECT PROPOSAL AND PLAN
3.4 Project team members and responsibilities matrix
Resource Responsibility
Project Manager
Executive Project Sponsor
Project Sponsor
Administrative Manager
Administrative Staff Support
Financial Analyst
Project team
Project Scheduler
Quality Manager
Technical Manager
System Engineer
Implementation Manager
Application Support Manager
Test Manager
Configuration Manager
Operations Manager
Customer Support Manager
Risk Manager
Executive Steering Committee
Making of implementation plan R - C I R - - - - I C R C I R C R R C
Accountable for success of project work R A I R R - - - - I - R A - I C R C I
Executive sponsorship for project success C R R I - - - I I R C I R I C R A C I
Collection of fund for the project plan - C R - R R - - - C R C I C R C R R A
Resource availability and implementation
of proposed system
- - R C I R I C I C - - C R A - - - -
Time and effort of project roles for project
success
- - I R I R - - - C I I R A C - - - I
Responsible for day-to-day management of
the system
C - - - R R - I I - - R C I R I C I -
Support of operations by supervising the
plan and project staffs
I I I R R - C I I R A - R A - - - R A
Schedule the project plan - - - R C R R C I R A I R R - C I I -
Perform of required tasks for the company
systems
R I R - - - R - - R A I R R - - - - R

10PROJECT PROPOSAL AND PLAN
Managing and monitoring of installed
systems
R - R - - - - R - C R C I - - - I I I
Quality test of proposed system - - - I R A - I - C R - R R - - - -
Configure the proposed system R A R A R A R R - - - R C I R I C I -
Involve with oversee production of goods R R I I I R R - R A R A R A R A - - -
Lead and motivate the team of staffs R A I I I R R - R R - I - R R - A A -
Taking of project related decisions R - R R A R A R A C I I - - - R A I A
Facilitate of global collaboration among
the participants
R A I R R - - - - I I I R R - C I I -
Providing of strategic direction to project
work
C R C I - - - I I A R A - - - A - R R
Achieve of project benefits - C R - R R - - - R - C I R - A R - -
Here, R- responsible, A- Accountable, C- Consulted, and I-Informed

11PROJECT PROPOSAL AND PLAN
3.5 Work breakdown structure
WBS WBS activities
0 Development of electronic health information system in Australian
Pharmaceutical Industries
1 Initiation phase
1.1 Education to organization on EHR and project
1.2 Identification of project stakeholders
1.3 Understanding of skills set for clinical
1.4 Identification of skills set of clinical and IT staffs
1.5 Development of business case
1.6 Understanding of business cycle
1.7 Understanding of procurement process
2 Planning phase
2.1 On site assessment
2.2 Development of gap analysis of actual systems
2.3 Scope requirements
2.4 Preparation of budget and resources required
2.5 Selection of vendor and approval of start date
2.6 Updating of schedule and project plan
3 Execution plan
3.1 Building the test and development of system
3.2 Documentation of system
3.3 Testing the system prior to implement EHR
3.4 Verify the configuration and usability
3.5 Deployment of pilot site
3.6 Deploy of disaster recovery site
3.7 Obtain of site completion

12PROJECT PROPOSAL AND PLAN
3.8 Sign off the implementation
4 Control phase
4.1 Control validate through project
4.2 Risk monitoring and control
4.3 Development of risks
4.4 Cost control review
4.5 Providing financial reports on monthly basis
4.6 Performance reporting
5 Closing phase
5.1 Complete closeout of contracts
5.2 Sign off the customer acceptance
5.3 Closeout the financial matters
5.4 Document lessons learned
5.5 Completion and collection of project records
5.6 Preparation of final reports
5.7 Conduct a review of project report
5.8 Final sign off

13PROJECT PROPOSAL AND PLAN
Figure 1: Work breakdown structure
(Source: Created by author)
3.6 Project schedule
WBS Task Name Duration Start Finish
0
Development of electronic health
information system in Australian
Pharmaceutical Industries
120 days Tue 07-08-
18
Mon 21-01-
19
1 Initiation phase 33 days Tue 07-08-
18
Thu 20-09-
18
1.1 Education to organization on EHR and
project 4 days Tue 07-08-
18
Fri 10-08-
18
1.2 Identification of project stakeholders 9 days Mon 13-08-
18
Thu 23-08-
18
1.3 Understanding of skills set for clinical 6 days Fri 24-08-
18
Fri 31-08-
18
1.4 Identification of skills set of clinical and IT
staffs 10 days Mon 03-09-
18
Fri 14-09-
18
1.5 Development of business case 14 days Mon 13-08-
18
Thu 30-08-
18

14PROJECT PROPOSAL AND PLAN
1.6 Understanding of business cycle 4 days Mon 17-09-
18
Thu 20-09-
18
1.7 Understanding of procurement process 10 days Fri 31-08-
18
Thu 13-09-
18
2 Planning phase 39 days Fri 24-08-
18
Wed 17-10-
18
2.1 On site assessment 12 days Fri 21-09-
18
Mon 08-10-
18
2.2 Development of gap analysis of actual
systems 14 days Mon 03-09-
18
Thu 20-09-
18
2.3 Scope requirements 5 days Fri 24-08-
18
Thu 30-08-
18
2.4 Preparation of budget and resources
required 17 days Fri 31-08-
18
Mon 24-09-
18
2.5 Selection of vendor and approval of start
date 17 days Tue 25-09-
18
Wed 17-10-
18
2.6 Updating of schedule and project plan 15 days Fri 21-09-
18
Thu 11-10-
18
3 Execution plan 59 days Tue 09-10-
18
Fri 28-12-
18
3.1 Building the test and development of
system 12 days Fri 12-10-
18
Mon 29-10-
18
3.2 Documentation of system 14 days Tue 30-10-
18
Fri 16-11-
18
3.3 Testing the system prior to implement EHR 19 days Mon 19-11-
18
Thu 13-12-
18
3.4 Verify the configuration and usability 11 days Fri 14-12-
18
Fri 28-12-
18
3.5 Deployment of pilot site 12 days Tue 09-10-
18
Wed 24-10-
18
3.6 Deploy of disaster recovery site 14 days Thu 25-10-
18
Tue 13-11-
18
3.7 Obtain of site completion 12 days Wed 14-11- Thu 29-11-

15PROJECT PROPOSAL AND PLAN
18 18
3.8 Sign off the implementation 12 days Fri 30-11-
18
Mon 17-12-
18
4 Control phase 102 days Fri 31-08-
18
Mon 21-01-
19
4.1 Control validate through project 13 days Tue 18-12-
18
Thu 03-01-
19
4.2 Risk monitoring and control 12 days Fri 04-01-
19
Mon 21-01-
19
4.3 Development of risks 15 days Fri 31-08-
18
Thu 20-09-
18
4.4 Cost control review 3 days Fri 12-10-
18
Tue 16-10-
18
4.5 Providing financial reports on monthly
basis 12 days Wed 17-10-
18
Thu 01-11-
18
4.6 Performance reporting 13 days Fri 02-11-
18
Tue 20-11-
18
5 Closing phase 34 days Wed 21-
11-18
Mon 07-01-
19
5.1 Complete closeout of contracts 4 days Wed 21-11-
18
Mon 26-11-
18
5.2 Sign off the customer acceptance 2 days Tue 27-11-
18
Wed 28-11-
18
5.3 Closeout the financial matters 13 days Thu 29-11-
18
Mon 17-12-
18
5.4 Document lessons learned 6 days Tue 18-12-
18
Tue 25-12-
18
5.5 Completion and collection of project
records 2 days Wed 26-12-
18
Thu 27-12-
18
5.6 Preparation of final reports 3 days Fri 28-12-
18
Tue 01-01-
19
5.7 Conduct a review of project report 2 days Wed 02-01-
19
Thu 03-01-
19

16PROJECT PROPOSAL AND PLAN
5.8 Final sign off 2 days Fri 04-01-
19
Mon 07-01-
19
4.0 Risk assessment and plan
While implementation of EHR solutions are critical to enable of effective
collaboration along with enhance of patient care delivery, there are significant risks such as
technical risk, resource risk, budget risk, privacy and security risks as well as schedule risk.
Risk
factor
Risk description Impact Likeliho
od
Risk
level
Preventive measures
Technica
l risk
There is failure of
software
implementation.
When proper
maintenance is not
done for the
software, then there
is failure of the
system.
Moderate Possible Mediu
m
Before starting to work
into the project plan, there
is required of proper
maintenance of the
proposed system.
Resource
risk
When there is lack
of resources and
team members are
involved into the
project work, then
there is delay into
the project.
Significant Possible High There is required to hire of
more resources for the
project plan, so that there
are not possibility of
reduction of team
members to work into the
project.
Budget
risk
There is financial
exposure as well as
delay into ROI.
Investing into EHR
solution is not
allowed of
customization which
resulted that the
money is spent on
the solution are not
accomplished of
project outcomes.
Moderate Unlikely Mediu
m
The system should
improve of patient care,
eliminate the data entry
duplication and also
enhance the
documentation with
framework for
customization of daily
operations. The project
manager should account
for proper budget plan
before starting to work

17PROJECT PROPOSAL AND PLAN
into the project study.
Privacy
and
security
breach
There are posing of
data protection
which is a high risk
for the healthcare
providers. There are
possibility of stolen
of healthcare data
and access to the
patient data without
prior access
permission to it.
Significant Unlikely High Proper security and
authentication measures
are to be taken so that no
unauthorized person can
able to access to the
patient’s data.
Schedule
risk
There are possibility
that there is delay
into the project
schedule due to lack
of project resources
and lack of project
related budget.
Minor Possible Mediu
m
There should be proper
planning of schedule by
the project manager. The
manager should get an
idea of possible phases
which are undertaken to
conduct work into the
study by use of project
management tools and
techniques.
The risk matrix is as follows:
Impact
Negligible Minor Moderate Significant Severe
Likelihood
Very
likely
Likely
Possible Schedule
risk
Technical
risk
Resource
risk
Unlikely Budget
risk
Privacy
and
security
risk
Very
unlikely
Red- Extreme risk
Orange- High risk
Yellow- Medium risk

18PROJECT PROPOSAL AND PLAN
Green- Low risk
5.0 Quality plan
Quality assurance helps to identify potential areas of risks and help to make sure that
EHR project is being designed accurately. It is included to evaluate the implementation of
provider along with change management plans, schedule of training. Collection of data as
well as monitoring are also conducted to observe that there is proper implementation which is
on track to deliver of benefits highlighted into the project plan. The healthcare providers
along with professionals are requested to use of specialized EHR technology for exchanging
of electronic health related data for improvement of excellence care, submission of clinical
quality measures.
Issue Project
stage
product is
produced
End stage
assessment
Theory Observed in
the case
Procurement Initiation
phase
End of
initiation
phase
There is required to
prepare of preliminary
engineering plan.
The
procurement is
started
promptly for the
critical
technical
equipment’s.
Pre-
commissioning
Initiation
phase
End of
initiation
phase
It is done to save of
cost as well as
resources.
Commissioning is to be
done offshore.
The key
milestone for
defined
packages are
approved on
time.
Quality
schedule,
safety plan and
progress
reporting
Planning
phase
End of
planning
phase
The plan procedures are
related to the project
requirements for the
project is to be
submitted to client for
their approval.
Good schedule
for the
unforeseen bad
weather
conditions are
done among the
activities which
are long.

19PROJECT PROPOSAL AND PLAN
Close out of
the plan
Closure
phase
End of close
out phase
The vendor data and
check sheets are
available. All
completion tests are to
be done prior to handle
over to client.
There are
proper
requirement to
be applied into
the project plan
for successful
implementation
of proposed
information
system.
Payment
method
Planning
phase
End of
planning
phase
The payment method is
to be made related to
the milestones achieved
and progress of work
per month.
The payment is
made based on
the key project
milestones.
6.0 Summary
It is summarized that the proposed system is included of initiation phase, planning
phase, execution phase, control phase and closure phase. The total time required to develop
of EHR system into Australian Pharmaceutical Industries is 4 months. The scope of this study
is to implement of new system which is user friendly for the end users. The proposed solution
is mitigated current application data over the new system. All the software as well as
licensing are comprehensive to the project work. The proposed system should well-matched
with the present terminologies in addition to coding systems. There are proper testing
processes on the system ensures that best functionality should be meet to develop a new
solution for the company to record of health related information. The clinical benefits of
proposed system is enhanced provider and patient access to care documentation. The benefits
of this particular system is to generate of increased effectiveness to provide of medical care
along with facilitate of new services which is not provided previously. The new business
solution increases ability to provide of medical care, increase of business value, increase of

20PROJECT PROPOSAL AND PLAN
business revenue along with reduction of expenses. The project work is to be anticipated with
increasing in addition to providing of medical care to the end users and patients.
Into the project plan, there are also some project constraints such as there is delay into
the schedule when there is lack of project team members to conduct the plan. Therefore, it
also increases cost of the plan. The risks which are identified into the project study are
technical risk, schedule risk, budget risk and resource risks. It provides a higher effect into
the project work, therefore the risk manager takes of possible steps to mitigate those risks
before it impacts the project success. The data from existing system is not extracted,
transferred and loaded to the proposed system. There are risks which may be diverted the
resources and altered negotiation time for the implementation process. The proposed
information system is taking into account for the clinical requirement of the health
professionals to provide of health related services. EHR information are completed and it is
essential to uphold of quality of the system. EHR will upgrade to obligation as it ends up vital
to the patient experiences. The project plan is to be carried on schedule, augmented of
adoption among the patients as well as physicians, testing practices procedures into the
system in addition to justification of error into patient’s data.

21PROJECT PROPOSAL AND PLAN
Bibliography
Adler-Milstein, J., DesRoches, C.M., Kralovec, P., Foster, G., Worzala, C., Charles, D.,
Searcy, T. and Jha, A.K., 2015. Electronic health record adoption in US hospitals: progress
continues, but challenges persist. Health affairs, 34(12), pp.2174-2180.
Arvidsson, V., Holmström, J. and Lyytinen, K., 2014. Information systems use as strategy
practice: A multi-dimensional view of strategic information system implementation and
use. The Journal of Strategic Information Systems, 23(1), pp.45-61.
Ben-Assuli, O., 2015. Electronic health records, adoption, quality of care, legal and privacy
issues and their implementation in emergency departments. Health Policy, 119(3), pp.287-
297.
Birkhead, G.S., Klompas, M. and Shah, N.R., 2015. Uses of electronic health records for
public health surveillance to advance public health. Annual review of public health, 36,
pp.345-359.
Boonstra, A., Versluis, A. and Vos, J.F., 2014. Implementing electronic health records in
hospitals: a systematic literature review. BMC health services research, 14(1), p.370.
Carayon, P., Wetterneck, T.B., Alyousef, B., Brown, R.L., Cartmill, R.S., McGuire, K.,
Hoonakker, P.L., Slagle, J., Van Roy, K.S., Walker, J.M. and Weinger, M.B., 2015. Impact
of electronic health record technology on the work and workflow of physicians in the
intensive care unit. International journal of medical informatics, 84(8), pp.578-594.
Cassidy, A., 2016. A practical guide to information systems strategic planning. CRC press.
Galliers, R.D. and Leidner, D.E. eds., 2014. Strategic information management: challenges
and strategies in managing information systems. Routledge.

22PROJECT PROPOSAL AND PLAN
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.
Hicks, J.K., Stowe, D., Willner, M.A., Wai, M., Daly, T., Gordon, S.M., Lashner, B.A.,
Parikh, S., White, R., Teng, K. and Moss, T., 2016. Implementation of clinical
pharmacogenomics within a large health system: from electronic health record decision
support to consultation services. Pharmacotherapy: The Journal of Human Pharmacology
and Drug Therapy, 36(8), pp.940-948.
Hsiao, C.J., Hing, E. and Ashman, J., 2014. Trends in Electronic Health Record System Use
Among Office-based Physicians, United States, 2007-2012. US Department of Health and
Human Services, Centers for Disease Control and Prevention, National Center for Health
Statistics.
Jamoom, E., Yang, N. and Hing, E., 2016. Adoption of certified electronic health record
systems and electronic information sharing in physician offices: United States, 2013 and
2014. US Department of Health and Human Services, Centers for Disease Control and
Prevention, National Center for Health Statistics.
Johnson, P.F., 2014. Purchasing and supply management. McGraw-Hill Higher Education.
Kennell Jr, T.I., Willig, J.H. and Cimino, J.J., 2017. Clinical Informatics Researcher's
Desiderata for the Data Content of the Next Generation Electronic Health Record. Applied
clinical informatics, 8(04), pp.1159-1172.
Kim, Y.G., Jung, K., Park, Y.T., Shin, D., Cho, S.Y., Yoon, D. and Park, R.W., 2017. Rate of
electronic health record adoption in South Korea: A nation-wide survey. International
journal of medical informatics, 101, pp.100-107.

23PROJECT PROPOSAL AND PLAN
Kruse, C.S., Kristof, C., Jones, B., Mitchell, E. and Martinez, A., 2016. Barriers to electronic
health record adoption: a systematic literature review. Journal of medical systems, 40(12),
p.252.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education
India.
Lee, T., Ghapanchi, A.H., Talaei-Khoei, A. and Ray, P., 2015. Strategic information system
planning in healthcare organizations. Journal of Organizational and End User Computing
(JOEUC), 27(2), pp.1-31.
Mandel, J.C., Kreda, D.A., Mandl, K.D., Kohane, I.S. and Ramoni, R.B., 2016. SMART on
FHIR: a standards-based, interoperable apps platform for electronic health records. Journal
of the American Medical Informatics Association, 23(5), pp.899-908.
Manoharan, A., Melitski, J. and Bromberg, D., 2015. State strategic information system
plans: An assessment integrating strategy and operations through performance
measurement. International Journal of Public Sector Management, 28(3), pp.240-253.
Nguyen, L., Bellucci, E. and Nguyen, L.T., 2014. Electronic health records implementation:
an evaluation of information system impact and contingency factors. International journal of
medical informatics, 83(11), pp.779-796.
Osman, E., El Beltagi, I.M. and Hardaker, G., 2015. The impact of leadership orientation on
strategic information system planning processes, with an application to Libyan
organizations. Information Technology for Development, 21(4), pp.601-627.
Ozair, F.F., Jamshed, N., Sharma, A. and Aggarwal, P., 2015. Ethical issues in electronic
health records: a general overview. Perspectives in clinical research, 6(2), p.73.

24PROJECT PROPOSAL AND PLAN
Pearlson, K.E., Saunders, C.S. and Galletta, D.F., 2016. Managing and Using Information
Systems, Binder Ready Version: A Strategic Approach. John Wiley & Sons.
Peppard, J. and Ward, J., 2016. The strategic management of information systems: Building a
digital strategy. John Wiley & Sons.
Peppard, J., Galliers, R.D. and Thorogood, A., 2014. Information systems strategy as
practice: Micro strategy and strategizing for IS. J. Strategic Inf. Sys., 23(1), pp.1-10.
Prodinger, B., Maritz, R. and Aronsky, D., 2018. The Implementation of the International
Classification of Functioning, Disability and Health (ICF) in Electronic Health Records-A
Systematic Review.
Quinn, M. and Kristandl, G., 2014. Business information systems for accounting students.
Pearson Education Ltd..
Sauver, J.L.S., Carr, A.B., Yawn, B.P., Grossardt, B.R., Bock-Goodner, C.M., Klein, L.L.,
Pankratz, J.J., Rutten, L.J.F. and Rocca, W.A., 2017. Linking medical and dental health
record data: a partnership with the Rochester Epidemiology Project. BMJ open, 7(3),
p.e012528.
Schiff, A. and Szendi, J., 2014. Helping small business entrepreneurs avoid critical mistakes
in QuickBooks accounting software. The Entrepreneurial Executive, 19, p.169.
Tarhini, A., Ammar, H. and Tarhini, T., 2015. Analysis of the critical success factors for
enterprise resource planning implementation from stakeholders’ perspective: A systematic
review. International Business Research, 8(4), p.25.
Waterson, P., 2014. Health information technology and sociotechnical systems: A progress
report on recent developments within the UK National Health Service (NHS). Applied
ergonomics, 45(2), pp.150-161.

25PROJECT PROPOSAL AND PLAN