Team structure and cooperation within the teams: Representation of the structures of the
multi-professional health care team, description of the cooperation between team members,
and teams.Weaknesses that may be found include a high effort for cooperation, insufficient
definition of team aims, and an unclear team structure for a particular patient.
In general, a system analysis yields an understanding of how a system
works and how different elements in a system interact.
This facilitates system design and system redesign, and aims to
improve the interface between components of a system in order to
enhance the functioning of each individual component in the overall
system.
System analysis has much to contribute to patient safety, specifically
through its study of organizational and work systems.
Although the definitions of fault are different for different systems and
in different situations, a fault is always an existing part in the system
and it can be removed by correcting the erroneous part of the
system.
System analysis can help manage and reduce risks by identifying
hazards so they can be controlled through good design. That is, in
order to improve safety, quality, performance, and comfort, a good
place to start is by analyzing the involved systems so they can be
improved.
The key to improving safety and reducing risk is through good system
design, which can only be achieved though a complete understanding
of the system.
Role dan
Responsibilities
Information
processing and tools
Communication
Bussiness processes
System element:
System attribute:
System boundary:
Spatial boundary:
Process boundary:
Hierarchical boundary:
Transformation:
Outputs:
Being Open Framework RCA Investigation Process Maps *RCA Report Writing Templates
Three Levels of RCA Getting Started Triggers for RCA Investigation
HC Risk Assessment Made Easy RCA Investigation Glossary
Barrier Analysis
Generating Solutions and Recommendations
*Types of Preventative Actions
THE PROBLEM
For some strange reason systems analysts frequently believe "they" are
expected to solve the problem.
This conception is far from the truth. They are expected to find a solution.
By asking users and those ultimately responsible for the process for their
thoughts and recommendations, we are able to compile a list of alternatives.
They have now been included in the solution process by having their ideas
solicited and considered. Therefore, if the users ideas are accepted, the
user has accountability.
DATA GATHERING TECHNIQUES
Interviews: Interviewing all persons associated with the system and asking the above
questions will assist in seeing the problem or need from a variety of
perspectives. It allows the opportunity to ask, "What do you recommend?"
Surveys: Surveys can reveal problems, needs and opportunities not discovered with
other techniques. A person completing a brief survey (less than five
minutes) may disclose problems, issues, processes, or solutions not seen
through other data gathering techniques.
Formal Many times formal reports and user documentation reveal needs or
problems.
Reports: This requires the writer to understand the problem - before they can write
about it.
Peer Groups: Attending professional peer group meetings can provide one-on-one
roundtable dialogue, and perspectives to a problem or need.
I. During Interviews 1. II. After Understanding III. With the User and Manager …
ask … 1. ask … ask
1. Why? 1. Eliminate?
2. What? 1. What do You Recommend?
3. Where? 2. Combine?
4. Who?
3. Simplify
5. When?
6. How? 4. Change?
to understand the process to seek alternatives for to have those closest and
solutions accountable take responsibility
(and often solve the problem)
Work System Analysis
Step 4
Step 5
The team should begin formal data collection to revise and update
the work system map, gauge the current performance of the system,
and determine baseline measures that will be used to evaluate the
effectiveness of the redesign. Data can be collected through time
studies, administrative databases, maintenance records,
structured observations of the process, and interviews of the
involved stakeholders. Interviews should be used to collect details
about the system elements and attributes, and to reconcile and/or
clarify data collected from observations.
Step 8
The team can begin analyzing the collected data. The purposes of the
analysis are to (a) identify weaknesses, variances, and any series of
events that could cause the system to fail; and (b) prioritize the
identified problems for redesign.
1/1/2014 :
Study will be Steering
Nobody is
initiated by the Committee
Sample analysis, responsible at this
Poorly designed Activate the lab director of approved the
Wrong test or possibly not time.Patient or Director of
Diagnostic test order form or ordering module laboratory quality change and study.
ordered by until results come physician is most None Laboratory
order wrong test chosen in the order entry to determine 1/22/2014 : Study
physician back or patient is likely to see the Quality Control
by physician system. change over time design approved.
notified mistake once
in rate of incorrect 2/27/2014 :
results come back
lab tests ordered. Baseline measures
being collected.
Step 10