Dependable Nursing Information Systems

studied byStudied by 3 people
0.0(0)
Get a hint
Hint

System Reliability

1 / 61

flashcard set

Earn XP

Description and Tags

At the end of this unit, the students are expected to: Cognitive: 1. Identify the need for dependable systems in healthcare 2. Enumerate guidelines for dependable systems 3. Review clinical information systems (CIS) 4. Understand the process of designing, implementing and upgrading clinical information Systems Affective: 1. Listen attentively during class discussions 2. Demonstrate tact and respect when challenging other people’s opinions and ideas 3. Accept comments and reactions of classmates on one’s opinions openly and graciously. Psychomotor: 1. Participate actively during class discussions and group activities 2. Express opinion and thoughts in front of the class

62 Terms

1

System Reliability

the system consistently behaves the same way

New cards
2

Service Availability

required services are present and usable when they are needed.

New cards
3

Confidentiality

sensitive information is disclosed only to those who authorized to see it.

New cards
4

Data Integrity

data are not corrupted or destroyed.

New cards
5

Responsiveness

the system responds to user input within an expected and acceptable time period.

New cards
6

Safety

the system does not cause harm.

New cards
7

five (5) Fundamental Guidelines that can help increase the dependability of healthcare systems

Architect for Dependability

Anticipate Failures

Anticipate Success

Hire Meticulous Managers

Don’t be Adventurous

New cards
8

Architect for Dependability

an enterprise system architecture should be developed from the bottom up so that no critical component is dependent on a component less trustworthy that itself.

New cards
9

Anticipate Failures

features that are transparent to software applications should be implemented to detect faults, to fail over to redundant components when faults are detected, and to recover from failures before they become catastrophic.

New cards
10

Anticipate Success

the systems planning process should anticipate business success and the consequential need for larger networks, more systems, new applications and additional integration

New cards
11

Hire Meticulous Managers

good system administrators should meticulously monitor and manage system and network performance

New cards
12

Don’t be Adventurous

an organization must use only proven methods, tools, technologies and products that have been in production, under conditions, at a scale similar to the intended environment

New cards
13

eight (8) phases of designing

The Planning Phase

The System Analysis Phase

The System Design Phase

The Development Phase

The Testing Phase

The Training Phase

The Implementation Phase

The Evaluation Phase

New cards
14

Architect for Dependability

should be developed from the bottom up so that no critical component is dependent on a component less trustworthy that itself.

New cards
15

Anticipate Failures

applications should be implemented to detect faults, to fail over to redundant components when faults are detected, and to recover from failures before they become catastrophic.

New cards
16

Anticipate Success

the systems planning process should anticipate business success and the consequential need for larger networks, more systems, new applications and additional integration

New cards
17

Hire Meticulous Managers

good system administrators should meticulously monitor and manage system and network performance

New cards
18

Don’t be Adventurous

an organization must use only proven methods, tools, technologies and products that have been in production, under conditions, at a scale similar to the intended environment.

New cards
19

The Planning Phase

t begins once an organization has determined that an existing need or problem may be filled or solved by the development or implementation of a CIS or application.

New cards
20

Definition of the Problem

description of the how the system will be evaluated

New cards
21

Feasibility Study

s a preliminary analysis to determine if the proposed problem can be solved by the implementation of a CIS or component application

New cards
22

Feasibility Study project areas:

Statement of Objectives

Environmental Assessment

Determination of Information Needs

Determination of Scope

New cards
23

Documentation and Negotiation of Project Scope Agreement

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

New cards
24

Allocation of Resources

A firm commitment of resources for development of the entire CIS project scope agreement is needed before the system can fulfill its stated objectives.

New cards
25

The System Analysis Phase

provides the data for development of an overview of the nursing problem and/or stated goal defined in the project scope agreement.

New cards
26

Data Collection

the first step in the system analysis phase.

New cards
27

Workflow document

assimilates the data collected into logical sequencing of tasks and subtasks perform by the end users for each goal or problem area.

New cards
28

Data Analysis

provides the data for development of an overview of the nursing problem and/or stated goal defined in the project scope agreement.

New cards
29

tools used in the development of the workflow and functional design documents:

o Data flowchart

o Grid chart

o Decision table

o Organizational Chart

o Model

New cards
30

Data Review

focuses on resolving the problems and/or attaining the goals defined in the feasibility study based on the methods or pathways derived from the workflow documents and the functional design.

New cards
31

Benefits Identification

reflect the resolution of the identified problem, formulated and stated in quantifiable terms.

New cards
32

System Proposal Development

submission to the project’s steering committee for review and approval.

New cards
33

Functional design

overview of the statement of how the new system will work.

New cards
34

The System Design Phase

the design details of the system and the detailed plans for implementing the system are developed for both the functional and the technical components of the system.

New cards
35

Functional Specifications

builds on the design by formulating a detailed description of all system inputs, outputs and processing logic required to complete the scope of the project.

New cards
36

Technical Specifications

Dedicated technical manager is required

New cards
37

four major areas of detailed technical specification to be developed

o Hardware

o Application Software

o Interface Software

o Conversions

New cards
38

Implementation Planning

establishment of a detailed work plan.

New cards
39

The Development Phase

If the project steering committee decides to develop its own system programs, the project staff must proceed with this

includes hardware selection, software development, test system and document system.

New cards
40

The Testing Phase

The system, whether newly developed or commercially available, must be tested to ensure all data are processed correctly and the desired outputs are generated.

verifies that the computer programs are written correctly and ensures that when implemented in the production (live) environment, the system will function as planned.

New cards
41

The Training Phase

It is essential to train the end users on how to use the system properly. A CIS will function only as well as its users understand its operation and the operation streamline the work. All users of the new system or application must receive training.

New cards
42

The Implementation Phase

organizes all steps into a detailed plan describing the series of events required to begin using the system or application in the production or live environment

This phase ensures that once the system is installed in the live environment, the system and the delivery of healthcare in the organization will run smoothly.

New cards
43

The Evaluation Phase

describes and assesses, in detail, the new system’s performance. Using the criteria established in the planning and system design phases

summarizes the entire system, identifying both the strengths and weaknesses of the implementation process.

often leads to system revisions and, ultimately, a better system

New cards
44
New cards
45
New cards
46
New cards
47
New cards
48
New cards
49
New cards
50
New cards
51
New cards
52
New cards
53
New cards
54
New cards
55
New cards
56
New cards
57
New cards
58
New cards
59
New cards
60
New cards
61
New cards
62
New cards

Explore top notes

note Note
studied byStudied by 7 people
... ago
5.0(1)
note Note
studied byStudied by 12 people
... ago
5.0(1)
note Note
studied byStudied by 21 people
... ago
4.0(1)
note Note
studied byStudied by 32 people
... ago
5.0(1)
note Note
studied byStudied by 8 people
... ago
5.0(1)
note Note
studied byStudied by 9 people
... ago
5.0(1)
note Note
studied byStudied by 31 people
... ago
5.0(1)
note Note
studied byStudied by 357 people
... ago
5.0(5)

Explore top flashcards

flashcards Flashcard (24)
studied byStudied by 21 people
... ago
5.0(1)
flashcards Flashcard (51)
studied byStudied by 28 people
... ago
4.0(1)
flashcards Flashcard (198)
studied byStudied by 7 people
... ago
5.0(1)
flashcards Flashcard (34)
studied byStudied by 2 people
... ago
5.0(1)
flashcards Flashcard (39)
studied byStudied by 4 people
... ago
5.0(1)
flashcards Flashcard (61)
studied byStudied by 379 people
... ago
4.6(28)
flashcards Flashcard (116)
studied byStudied by 13 people
... ago
5.0(1)
flashcards Flashcard (65)
studied byStudied by 2352 people
... ago
4.6(14)
robot