“If each discipline acted independently, the care of the

patient would be fragmented, causing duplication of

efforts and delays of treatment.” (Selker et al, 1989).
 PLANNING
SYSTEMS
ANALYSIS
SYSTEMS
DESIGN
DEVELOPMENT
CLINICAL
INFORMATION
TESTING
SYSTEMS
TRAINING
IMPLEMENTATIO
N
EVALUATION
 PLANNING

 Identification of the composition of the

CIS management team
 Definition of the Problem
 Feasibility Study
 Environmental Assessment
 Development of a Project Timeline
 Giving of Recommendations
 Documentation and Negotiation of a
Project Scope Agreement
 Allocation of Resources
1

CIS Steering Committee

Project Team
Departmental Team
MAIN MANAGERS OF CIS
 composted of representatives from the
different areas (hospital administration,
nursing administration, medical staff,
information systems, major ancillary
departments, health information
management, legal affairs, consultants, and
appointed members)
 in charge of providing oversight GUIDANCE
to the selection and integration of a new
CIS into the organization
DESIGN AND UPGRADING MANAGERS OF CIS
 composed by the project manager and team
leaders from each of the major departments;
 Objectives:
▪ To understand the technology, including restrictions of a
proposed system
▪ To understand the impact of intradepartmental decisions
▪ To make decisions at the interdepartmental level for the overall
good of the CIS within the organization
▪ To become key resource for application
*Project Manager - has significant
implementation experience, is
responsible for managing the
software application development,
hardware and networks and all
aspects of the healthcare project
implementation.
KEY IMPLEMENTORS OF CIS
 has the task of understanding the
department’s information needs and
the software features and functions,
merging system’s capabilities with
department’s operations, participating
in developing and conducting end-user
education, and providing high level of
support in utilization of the system
 STEERING PROJECT
COMMITTEE TEAM

DEPARTMENT
AL
TEAM

PROBLEM
DEFINITION
2

 includes statements of the problem identified

in the institution requiring CIS development
or utilization, key goals after the project
implementation, and evaluation techniques
 if upgrading a system, it may also include
identification of equipment available, age,
degree of amortization, and need for
upgrades
 I.Feasibility Study

BENEFITS and PRODUCTS vs. RISKS

and ISSUES; TO BE OR NOT TO BE
 a preliminary analysis to determine if
the proposed problem can be solved by
the implementation of CIS; with
identified objectives
*Issues may be legal, operational, or
technical in nature
4

“Is the proposed project in line

with organizational mission-
vision and plans?”
 determine the information needs of
the intended or existing users, as
well as specifying the scope of the
project (limitations)
5

to show the key

milestone events of the
project; somewhat
similar to an action plan
6
7

A project scope agreement

is drafted by the project
team and submitted to the
project’s steering
committee for acceptance
8

 Considerations: - staffing workload

- human resources
- present cost of operation - relationship of
implementation events with nonproject
events - training costs
- space availability
- current and anticipated equipment
requirements
 SYSTEMS
ANALYSIS

FACT-FINDING PHASE
 During this phase, all data
requirements related to the problem
defined in the project scope
agreement are collected and
analyzed to gain a sound
understanding of the current system
 SYSTEMS
ANALYSIS

 Data collection
 Data analysis
 Data review
 Benefits identification
 System proposal development
 1

HARDWARE, PROCEDURES, SOFTWARE, PROCESSING,

OUTPUT, INTENDED REPORTS
 creation of workflow documents and functional design document
*Workflow document – assimilates the data collected into logical
sequencing of tasks and subtasks performed by the end users
for the goal or problem area
*Functional design document – overview statement of how the
new system will work; uses the workflow document as its basis in
creating a new system, or upgrading a previously existing
system
2

provides overview of the

nursing problem and/or
stated goal; use tools to
analyze data (data flowchart,
grid chart, decision table,
organizational chart, model)
3

review data gathered thru

feasibility study, workflow
document, and functional
documents, and provide
recommendations
4

basis for measuring the

success of the project
5

 proposal is submitted to the

project’s steering committee for
review and approval, identifying
the problems and/or goals and
requirements for the new
system’s overall design
 SYSTEMS
DESIGN

Functional specification
Technical specifications
Implementation planning
1

 formulation of a detailed description

of ALL system inputs, outputs and
processing logic required to
complete the scope of the project
 includes also data manipulation and
output review
 starting point for developing testing
plans for verification of the software
2

 done to make sure that technical

components of the proposed system
work in concert with technology and
end-user needs and to assist in the
development of the implementation
plan
 4 Elements:
HARDWARE INTERFACES
SOFTWARECONVERSIONS
3

 development of a detailed implementation

plan
 Contents of the Plan:
▪ Personnel
▪ Timeframes
▪ Costs and budgets
▪ Facilities and equipment required
▪ Development or implementation tasks
▪ Operational considerations
▪ Human-computer interactions (interfaces)
▪ System test plan
 DEVELOPME
NT

 development of the software

 iterative process of programming
sections of the design
 determination of product packaging and
marketing materials, establishment of
product pricing, development of
system/application documentation, and
establishment of a marketing plan
 TESTING

alpha test vs. beta test

 verifies that computer programs
are written correctly and ensures
that when implemented, the
system will function as planned
 **Document system – Refer to
Book (p.305)
 TRAINING

 includes the databases, processing

logic, and outputs of the system’s
features and functions
Levels:
1. project team and selected members
of the departmental team receive
training from the developers or vendor
2. end-user training
 -done no more than 6 weeks prior to
activation of the new system
 TRAINING

Important Notes:
▪ Training should take place before
and during activation of a new
system
▪ Training is most effective when it
is interactive and hands-on.
 IMPLEMENTAT
ION

IMPLEMENTATION +
COLLABORATION
 materialization of the implementation
plan
4 Approaches:
▪ Parallel
▪ Pilot
▪ Phased-in
▪ Big Bang
 EVALUATION

“Were the identified objectives met?

Were the plans identified are carried
out as expected?”
 describes and assesses in detail the new
system’s performance
 Includes cost-benefit analysis – IS THE
SYSTEM WORTH ITS PRICE?; relates system
cost and benefits to system design, level of
use, timeframe, and equipment costs