A system analysis of a suboptimal surgical experience
Notice bibliographique
Résumé
BACKGROUND: System analyses of incidents that occur in the process of health care delivery are rare. A case study of a series of incidents that one of the authors experienced after routine urologic surgery is presented. We interpret the sequence of events as a case of cascading incidents that resulted in outcomes that were suboptimal, although fortunately not fatal. METHODS: A system dynamics approach was employed to develop illustrative models (flow diagrams) of the dynamics of the patient's interaction with surgery and emergency departments. The flow diagrams were constructed based upon the experience of the patient, chart review, discussion with the involved physicians as well as several physician colleagues, comparison of our diagrams with those developed by the hospital of interest for internal planning purposes, and an iterative process with one of the co-authors who is a system dynamics expert. A dynamic hypothesis was developed using insights gained by building the flow diagrams. RESULTS: The incidents originated in design flaws and many small innocuous system changes that have occurred incrementally over time, which by themselves may have no consequence but in conjunction with some system randomness can have serious consequences. In the patient's case, the incidents that occurred in preoperative assessment and surgery originated in communication and procedural failures. System delays, communication failures, and capacity issues contributed largely to the subsequent incidents. Some of these issues were controllable by the physicians and staff of the institution, whereas others were less controllable. To the system's credit, some of the more controllable issues were addressed, but systemic problems like overcrowding are unlikely to be addressed in the near future. CONCLUSION: This is first instance that we are aware of in the literature where a system dynamics approach has been used to analyze a patient safety experience. The qualitative system dynamics analysis was useful in understanding the system, and contributed to learning on the part of some components of the system. We suggest that further data collection and quantitative analysis would be highly informative for identification of system changes to improve quality and safety.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,003 | 0,010 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,001 |
| Bibliométrie | 0,002 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,001 |
| Communication savante | 0,002 | 0,002 |
| Science ouverte | 0,001 | 0,002 |
| Intégrité de la recherche | 0,001 | 0,001 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,005 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».