n=14
EUROCONTROL, European Organisation for the Safety of Air Navigation.
Analysis of GP-based pharmacist work system
A health board employed pharmacist had been working at a GP practice for 2 months. She worked in the practice in the mornings and at a neighbouring practice in the afternoons. One task she completed was reconciling medication changes after hospital discharge which was previously undertaken by GPs. Their introduction had not had the desired impact and a meeting was held between relevant parties who used the STEW principles to reach a shared understanding of the system and design system improvements. | |
Foundation concept | Purpose of system Agree boundaries |
Seek multiple perspectives | Practice-based pharmacist GPs GP administrative staff (including the practice manage) Patient representative Community pharmacists Local pharmacy clinical lead Secondary care representative (a pharmacist who was usually based on an acute medical ward) |
Consider work conditions | Demand/capacity Resources Constraints Leading indicators |
Analyse interactions and flow | Interactions and flow |
Understand why decisions make sense at the time | |
Explore performance variability | GPs and the pharmacist discussed the different ways they completed medication reconciliation and identified workarounds and trade-offs that would help achieve the goals of the system (reduced workload and increased quality). |
GP, general practitioner; STEW, Systems Thinking for Everyday Work.
The foundation concept acknowledges that ‘ most healthcare problems and solutions belong to the system ’. This emphasises that the aim of applying a systems approach is to improve overall system functioning and not the functioning of one individual component within a system. For example, improving clinical assessments will not improve overall system performance unless patients can access assessments appropriately.
All systems interact with other systems, but out of necessity those analysing the system need to agree boundaries for the analysis. This may mean the GP practice building, a single hospital ward, the emergency department, a pharmacy or nursing home. Despite this, it is important to remember that external factors will influence the system under study and changes may have effects in parts of the system outside the boundary.
Appreciate that people, at all organisational levels and regardless of responsibilities and hierarchical status, are the local experts in the work they do. Exploring the different perspectives held by these people, especially in relation to the other principles, is crucial when analysing incidents and designing and implementing change.
Obtaining multiple perspectives allows an exploration of variability in demand and capacity, availability of resources (such as information or physical resources) and constraints (such as guidance that directs work to be performed in a particular way). These considerations can help identify leading indicators of impending trouble by identifying where demand may exceed capacity or where resources may not be available. Multiple perspectives can also help explore how work conditions affect staff well-being (eg, health, safety, motivation, job satisfaction, comfort, joy at work) and performance (eg, care quality, safety, productivity, effectiveness, efficiency).
System outputs are dependent on the constantly changing interactions between people, tasks, equipment and the wider environment. Multiple perspectives on system functioning help explore interactions to better understand the effects of actions and proposed changes on other parts of the system. Examining flow of work can help identify how these interactions and the conditions of work contribute to bottlenecks and blockages.
This principle directs us that, when looking back on individual, team or organisational decision-making, we should appreciate that people do what makes sense to them based on the system conditions experienced at the time (demand, capacity, resources and constraints), interactions and flow of work. It is easy (and common) to look back with hindsight to blame or judge individual components (usually humans) and recommend change such as refresher training and punitive actions. This must consider why such decisions were made, or change is unlikely to be effective. The same conditions may occur again, and the same decision may need to be made to continue successful system functioning. By exploring why decisions were made, we move beyond blaming ‘human error’ which can help promote a ‘Just Culture’—where staff are not punished for actions that are in keeping with their experience and training and which were made to cope with the work conditions faced at the time. 35
As work conditions and interactions change rapidly and often in an unpredicted manner, people adapt what they do to achieve successful outcomes. They make trade-offs, such as efficiency thoroughness trade-offs, and use workarounds to cope with the conditions they face. In retrospect these could be seen as ‘errors’, but are often adaptations used to cope with unplanned or unexpected system conditions. They result in a difference between work-as-done and work-as-imagined and define everyday work from which outcomes, both good and bad, emerge.
The included case report describes the practical application of these principles to understand work within a system and the subsequent design of organisational change ( table 3 ). The presented details are a small part of a larger project in which the authors (DM, PB and SL) were involved. The new appointment of a health board employed pharmacist to a general practice had not had the anticipated impact and there had been unexpected effects. The GPs had hoped for a greater reduction in workload quantity, the health board had hoped for increased formulary compliance and there had been increased workload in secondary care.
Traditional ways of exploring this problem may include working backwards from the problem to identify an area for improvement. In this case, further training of the pharmacist may have been suggested and targets may have been introduced in relation to workload or formulary compliance. However, without understanding why the pharmacist worked this way, it is likely any retraining or change would be ineffective. The STEW principles provided a framework to analyse the problem from a systems perspective, understand what influenced the pharmacist’s decisions and explore the effects of these decisions elsewhere in the system. Obtaining multiple perspectives identified that the pharmacist had to trade off between competing goals (productivity vs thoroughness including safety and formulary compliance). The application of the principles identified how pharmacists varied their approach to increase productivity while remaining safe. Learning from this everyday work helped bring work-as-done and work-as-imagined closer and several changes to improve system performance were identified and implemented.
This ensured pharmacists had the information needed to complete the task ( System condition—resources ). It also reduced work in other sectors ( Interactions ) and increased the efficiency of task completion and so reduced delays for patients ( Flow ).
The timetable for the week was changed to prioritise other prescribing tasks at the start of the week and complete medication reconciliation later in the week ( System condition—capacity/demand ). Through discussion of system conditions, the pharmacist identified that certain discharges took longer to complete, resulted in further contact with the practice (with a resultant increased GP workload) or had an increased risk of patient harm. Discharges that included these factors were prioritised and completed early in the week in attempt to mitigate these problems.
Protocols were changed to have minimum specification to allow local adaptation by pharmacists ( System conditions—constraints ). This supported the pharmacists to employ a variety of responses dependent on the context ( Performance Variability ) which reduced pharmacists’ concerns of blame if they did not follow the protocol ( Understand why decision made sense ). For example, after a short admission where it was unlikely medication was changed, pharmacists did not need to contact secondary care regarding medication not recorded on the discharge letter ( Understand why decision made sense ). If they felt they did have to check, the option of contacting the patient was included. Similarly, the need to contact all patients after discharge was removed. Pharmacists could use other options such as contacting the community pharmacy if more appropriate ( Performance Variability ).
Regular GP mentoring sessions were included as pharmacists’ found discussing cases with GPs allowed them to consider the benefits and potential problems of their actions in other parts of the system (Interactions and Performance Variability ). For example, not limiting the number of times certain medication can be issued but instead ensuring practice systems for monitoring are used. This also allowed them to consider when they needed to be more thorough at the expense of efficiency ( Performance Variability ), for example, when there were leading indicators of problems such as high-risk medication.
This paper describes the adaptation and redesign of previously developed system principles for generic application in healthcare settings. The STEW principles underpin and are characteristic of a holistic systems approach. The case report demonstrates application of the principles to analyse a care system and to subsequently design change through understanding current work processes, predicting system behaviour and designing modifications to improve system performance.
We propose that the STEW principles can be used as a framework for teams to analyse, learn and improve from unintended outcomes, reports of excellent care and routine everyday work ‘hassles’. 36 37 The overall focus is on team and organisational learning by, for example, small group discussion to promote a deep understanding of ‘how everyday work is actually done’ (rather than just fixating on things that go wrong). This allows an exploration of the system conditions that result in the need for people to vary how they work; the identification and sharing of successful adaptations and an understanding of the effect of adaptations elsewhere in the system (mindful adaptation). From this, we can decide if variation is useful (and thus support staff in doing this effectively) or unwanted (and system conditions can then be considered to try to damp variation). These discussions can help reconcile work-as-done and work-as-imagined . Although, as conditions change unpredictably, new ways of working will continue to evolve and so we must continue to explore and share learning from everyday work, not just when something goes wrong.
The focus of safety efforts, in incident investigation and other QI activity, is often on identifying things that have gone wrong and implementing change to prevent ‘error’ recurring. 20 The focus is often on the ‘root causes’ of adverse events or categorising events most likely to cause systems to fail (eg, using Pareto charts). 20 38 This linear ‘cause and effect’ thinking can lead to single components, deemed to be the ‘cause’ of the unwanted event or care problem, being prioritised for improvement. Although this may improve the performance of that component it may not improve overall system functioning and, due to the complex interactions in healthcare systems, may generate unwanted unintended consequences. The principles promote examining and treating the relevant system as a whole which may strengthen the way we conduct incident investigation and how we design QI projects.
To successfully align corrective actions or improvement interventions with contributing factors, and therefore ensure actions have the desired effect, a deep understanding of everyday work is essential. 39 Methods such as process mapping are often promoted to explore how systems work which, when used properly, can be a useful method to aid healthcare improvers. To more closely model and understand work-as-done , the STEW principles could be considered to show the influences on components that affect performance such as feedback loops, coupling to other components and internal and external influences.
The STEW principles may also support another commonly used QI method: Plan, Do, Study, Act cycles. 40 It has been suggested that more in-depth work is often required in the planning and study stages of improvement activity, especially when dealing with complex problems. 40 The application of the principles may help explore factors that will influence change (such as resources, interactions with other parts of the systems and personal and organisational goals). Similarly, during the study phase, the principles can help explore how system properties prompted people to act the way they did. This level of understanding can then inform further iterative cycles.
Patient care is often delivered by teams across interfaces of care which further increases complexity. 41 It is estimated that only around half to three-quarters of actions recommended after incident analysis are implemented. 21 Although this is often due to a lack of shared learning and local action plans and involvement of key stakeholders, 21 those investigating such cases may feel unable to influence change in such a complex environment. This may result on a focus on what is perceived as manageable or feasible changes to single processes. Obtaining multiple perspective on work and improvement encourages a team-based approach to learning and change but systems are still required to ensure learning and action plans are shared. Although the principles have been used in incident investigation and to influence organisational change across care interfaces, simply introducing a set of principles alone will not improve the likelihood of the implementation of effective system-level change. 42 43 Training on, and evaluation of, the application of the principles is required.
Understanding how safety is created and maintained must involve more than examining when it fails. Improvement interventions often aim to standardise and simplify current processes. Although these approaches are important, in a resource-limited environment, it will never be possible to implement organisational change to fix all system problems. Even if this was possible, as systems evolve with new treatments and technology, conditions will emerge that have not been considered. To optimise success in complex systems, the contribution of humans to creating safety needs to be explored, understood and enhanced. 44 Human adaptation is always required to ensure safe working and needs to be understood, appreciated and supported. Studying systems using the principles may support workers who make such adaptations to be more mindful of wider system effects.
There is growing interest in healthcare in how we can learn more from how people create safety. The Learning from Excellence movement promotes learning and improvement from the analysis of peer-reported episodes of excellent care and positive deviancy aims to identify how some people excel despite facing the same constraints as others. 36 45 The Safety-II systems approach that influenced these principles is similar in that it focuses on how people help to create safety by adapting to unplanned system factors and interactions.
By understanding why decisions are made, the application of the principles supports the development of a ‘Just Culture’—indeed this was one of EUROCONTROL’s original principles and was incorporated into the principle, ‘Understand why decisions make sense at the time’. A ‘Just Culture’ has been described as ‘a culture of trust, learning and accountability’, where people are willing to report incidents where something has gone wrong, as they know it will inform learning to improve care and not be used to assign blame inappropriately. 35 Our approach aims to avoid unwarranted blame and increase healthcare staff support and learning when something has gone wrong. 46 47 Furthermore, application of the principles may empower staff and patients to not just report incidents but contribute to analysis and become integral parts of the improvement process through coproduction of safer systems. Obtaining the perspective of the patient when applying the principles is critical to understanding and improving systems as they are often the only constant when care crosses interfaces. This type of approach to improvement is strongly promoted and may avoid short-sighted responses to patient safety incidents (eg, refresher training or new protocols) and result in the design of better, and more cost-effective care systems. 48
Alternative methods exist for modelling and understanding complex systems, such as the Functional Resonance Analysis Method, 49 and a complex systems approach is used in accident models such as the Systems Theoretic Accident Modelling and Processes 50 and AcciMAPs. 51 These robust methods for system analysis are difficult for front-line teams to implement without specialised training. 29 The principles, on the other hand, were designed with front-line healthcare workers in order to allow non-experts to be able to adopt this type of thinking to understand and improve systems. The influence of conditions of work, including organisational and external factors, on safety has been appreciated for some time and is included in other models used in healthcare to explore safety in complex systems. 52–54 The Systems Engineering Initiative for Patient Safety (SEIPS) model is arguably one of the best known systems-based frameworks in healthcare. 53 While this model promotes seeking multiple perspectives to describe the interactions between components, the STEW principles focus on how these interactions influence the way work is done and thus may complement the use of the SEIPS model.
Any consensus method can produce an agreed outcome, but that does not mean these are wholly adequate in terms of validity, feasibility or transferability. Only 15 participants were involved in the initial development with 32 more in workshops; however, a wide range of professions with significant patient safety and QI experience were recruited. The appraiser workshop was attended by both primary and secondary care doctors, and other staff groups. Their comments were used to further refine the principles, but no attempt was made to assess their agreement on the importance and applicability of principles. The principles have not been shown in practice to improve performance, and further research and evaluation of their application in various sectors of healthcare is needed.
Systems thinking is essential for examining and improving healthcare safety and performance, but a shared understanding and application of the concept is not well developed among front-line staff, healthcare improvers, leaders, policymakers, the media and the general public. It is a complicated topic and requires an understandable framework for practical application by the care workforce. The developed principles may aid a deeper exploration of system safety in healthcare as part of learning from problematic situations, everyday work and excellent practices. They may also inform more effective design of local improvement interventions. Ultimately, the principles help define what a ‘systems approach’ actually entails in a practical sense within the healthcare context.
Under UK ‘Governance Arrangements for Research Ethics Committees’, ethical research committee review is not required for service evaluation or research which, for example, seeks to elicit the views, experiences and knowledge of healthcare professionals on a given subject area. 55 Similarly ‘service evaluation’ that involves NHS staff recruited as research participants by virtue of their professional roles also does not require ethical review from an established NHS research ethics committee.
The authors thank all those who contributed to the adaptation of the principles and Michael Cannon for his comments from a service user’s perspective.
Twitter: @duncansmcnab, @pbnes
Contributors: DM, JM and PB conceived the project. SS developed the original principles and led the consensus building workshop. DM and SL collected the data. DM, SL, SS, JM and PB analysed the feedback to adapt the principles. DM drafted the original report and SL, SS and JM revised and agreed on the final manuscript.
Funding: The authors have not declared a specific grant for this research from any funding agency in the public, commercial or not-for-profit sectors.
Competing interests: None declared.
Patient and public involvement: Patients and/or the public were involved in the design, or conduct, or reporting, or dissemination plans of this research.
Patient consent for publication: Not required.
Provenance and peer review: Not commissioned; externally peer reviewed.
Data availability statement: Data are available upon reasonable request. Data are available upon request relating to the stages of the consensus building process.
COMMENTS
Summary. This unit introduces systems and systems thinking. The unit is easily adaptable to any course and includes an introduction of terminology, motivation for using systems thinking, and practice reading, as well as interpreting and evaluating systems diagrams. Note that an Internet connection and speakers are required to play the audio ...
Systems Thinking Basics. Module 1 • 2 hours to complete. This course aims to help you understand the basic principles and concepts of systems thinking, identify and analyze the interrelationships in complex systems, apply systems thinking tools and methods to real-world problems and opportunities, and generate innovative ideas and solutions ...
Jake Spear. Mr. Gabriel Alaniz. IT-25 October 2020. 8-2 Project Three: Systems Thinking Lost Pines Outfitters is a small business that includes an online shop as well as a brick and mortar location that specializes in outdoor clothing for value-conscious customers.
Use systems thinking to gain insight into how others may see a system differently. Accept the limitations of being in-experienced; it may take you a while to become skilled at using the tools. The more practice, the quicker the process! Recognize that systems thinking is a lifelong practice. It's important to remember that the term "systems ...
Solving complex problems requires outside-the-box thinking. If you spend all your time looking at the finer details, you might miss the forest for the trees. Systems thinking empowers you to look at the totality of how an interlocking set of parts functions. Analyzing system behavior in this way helps you comprehend your business or organization on a much deeper level.
Purpose. This assignment gives you a chance to apply your systems thinking skills to a complex real life problem in corporate strategy: the rise and fall of People Express Airlines. People Express was the first airline formed in the wake of US airline deregulation in 1978. People Express was one of the most spectacular business success stories ...
2. Synthesis. In general, synthesis refers to the combining of two or more things to create something new. When it comes to systems thinking, the goal is synthesis, as opposed to analysis, which ...
1. Introduction. Systems thinking and design thinking are both approaches to problem solving and innovation. Systems thinking starts with understanding entire systems rather than individualized elements to spot opportunities for change, whereas design thinking is focused on understanding people's real needs to create human-centered products ...
Systems Thinking. Define the following systems-thinking concepts in your own words: Systems thinking: Away of looking at a system as a whole and seeing how each of the parts interact with each other as well as seeing the bigger picture. Collection: A set of similar data used as a single unit such as lists and sets to name a few.
6-1 Activity spear jake spear mr. gabriel alaniz 11 october 2020 systems thinking: systems thinking is essentially the act of stepping back from complex problem. Skip to document. University; High School. Books; Discovery. ... Assignments. 100% (56) 5. 3-2 Activity. Fundamentals of Information Technology. Assignments. 100% (25) 3.
Deidra Newton IT-200-Fundamentals Info Technology 1-3 Activity: Introduction to Systems Thinking A system is an organized collection of parts that are highly integrated to accomplish an overall goal. Systems have various inputs, which go through a certain process to produce outputs, together these outputs accomplish the overall desired goal.
Assignment: Systems Thinking Assessment Guidelines: Refer to the Student Handbook for a comprehensive set of assessment guidelines. Submission Due Date: 12 August 2019 at 10h00 Mark Scoring Guideline: Your mark for the assignment will contribute 40% towards your overall result for the Systemic Management Practice module.
As our world becomes ever more tightly interwoven globally and as the pace of change continues to increase, we will all need to become increasingly "system-wise.". This volume gives you the language and tools you need to start applying systems thinking principles and prac-tices in your own organization. IMS0013E.
1-4 intro to systems thinking. IT 200 Project Two. Module 3: Systems. Moduel 8 mtg 200 Case Study. 3-3 Activity Resource List. IT 200 Project 8. What to Submit To complete this project, you must submit the following: Systems Analysis Generate a report that analyzes the current systems in place at Lost.
Systems Thinking links theory and practice to better understand and improve the world around us. It examines the organization, activities, and interactions in nature, society, engineering, and everyday life. ... Key Dates milestones, assignments, briefs, and key events Date First Day of Class Sep 6 Individual, half-page Learning Summary due ...
10. Social and Economic Systems. Are highly complex systems: • Dynamic • Tightly coupled • Governed by feedback • Nonlinear • Limited Information • Ambiguity and delays in cause and effect. …and are typically more complex than human- made, physical systems. Systems Thinking and System Dynamics.
Human-Centered Systems Thinking Course. A holistic approach to problem solving starts with people. Preview Course. People are at the heart of every complex human system--but they're often the most overlooked. Effective problem solvers today know how to visualize the larger dynamics of the system while staying grounded in the needs of people.
In order to build the systems thinking diagram, we need to clearly identify the elements of the system and how it interacts with each other. Building the systems diagrams requires four steps; identify the events, identify the pattern of behaviour, build the system, and determine the mental models. The flow of creating a systems thinking diagram.
Take a helicopter view: Toggling between the details and the big picture is an important systems thinking skill and one of the habits of a systems thinker.When looking at a situation, event, or particular issue, encourage students to discuss systems as a whole. For example, in the classroom we may create a circle, where each student represents a system part and makes connections with a ball of ...
Systems thinking is a vantage point from which you see a whole, a web of relationships, rather than focusing only on the detail of any particular piece. Events are seen in the larger context of a pattern that is unfolding over time. ‐isee systems, inc. Systems thinking is a perspective of seeing and understanding systems as wholes rather than ...
Introduction. Adopting a 'systems thinking' approach to improvement in healthcare has been recommended as it may improve the ability to understand current work processes, predict system behaviour and design modifications to improve related functioning. 1-3 'Systems thinking' involves exploring the characteristics of components within a system (eg, work tasks and technology) and how ...