DzIf each discipline acted

independently, the care of the

patient would be fragmented,
causing duplication of efforts and
delays of treatment.dz (Selker et al,
1989).
 —


 




 


 — 
 

 
 

 



 —  
 



 
 —


h 









h 


— !"
h !"#
$#
h % "


h %"


— &
"
h %



h $




— &



 
h
""

$ 
1

h ðIS Steering ðommittee

h Project Team
h Departmental Team







h 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)
h in charge of providing oversight GUIDANð to the
selection and integration of a new ðIS into the
organization



—






h composed by the project manager and team
leaders from each of the major departments;
h !&%'
^ 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 ðIS within the organization
^ To become key resource for application
£


 



 








 
  








 
    



 

m
 —   


h 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
 
— (

  

—
 



— ) 
 
2

h includes statements of the problem identified

in the institution requiring ðIS development
or utilization, key goals after the project
implementation, and evaluation techniques
h if upgrading a system, it may also include
identification of equipment available, age,
degree of amortization, and need for
upgrades
6



)

— 
%*
m


+

)

 

)
h a preliminary analysis to determine if the
proposed problem can be solved by the
implementation of ðIS; with identified
objectives
£  



 




4



 
 &

"
,

 -"
.%

"/0
h determine the information needs of the
intended or existing users, as well as
specifying the scope of the project
(limitations)
5

h to show the key milestone

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

h A project scope agreement is

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

h  '
. staffing workload
- human resources
- present cost of operation
- relationship of
implementation events
with nonproject events
- training costs
- space availability
- current and anticipated
equipment requirements
  





.
—1

h 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
  




h 
""
h 
"#
h 
%,
h )

h #
 "
%"
 1

1
2
3
— 3
 2
3
— 3

—3

— 
h 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

h 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

h review data gathered thru

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

h basis for measuring the

success of the project
5

h 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
  



h $" 
h "

h "
"
1

h formulation of a detailed description of ALL

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

h 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
h [
"'

ÎARDWAR INT RFAð S

SOFTWAR ðONV RSIONS
3

h development of a detailed implementation plan

h 


—"'
^ Personnel
^ Timeframes
^ ðosts and budgets
^ Facilities and equipment required
^ Development or implementation tasks
^ Operational considerations
^ Îuman-computer interactions (interfaces)
^ System test plan
  — 

h development of the software

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

"

%*
!

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


h includes the databases, processing logic, and

outputs of the systemǯs features and
functions
%"'
1. project team and selected members of the
departmental team receive training from the
developers or vendor
2. end-user training
h -done 
 

4
,5 prior to
activation of the new system
 


 
'
^ Training should take place before and
during activation of a new system
^ Training is most effective when it is
interactive and hands-on.
  —  
 

 —  
 
6

) 
 
h materialization of the implementation plan
h [

 '
^ Parallel
^ Pilot
^ Phased-in
^ Big Bang
 

 

2 


!&%
/
2 


"

 
 
$


7/0
h describes and assesses in detail the new
systemǯs performance
h Includes cost-benefit analysis Ȃ IS TÎ
SYST
WORTÎ ITS PRIð ; relates system
cost and benefits to system design, level of
use, timeframe, and equipment costs