This 2014 review looked at 34 studies that looked at the effectiveness of safety checklists:
> The main findings were improved communication, reduced adverse events, better adherence to standard operating procedures, and reduced morbidity and mortality. None of the included studies reported decreased patient safety or quality after introducing safety checklists.
> Safety checklists appear to be effective tools for improving patient safety in various clinical settings by strengthening compliance with guidelines, improving human factors, reducing the incidence of adverse events, and decreasing mortality and morbidity. None of the included studies reported negative effects on safety.
So I'm going to ask for a citation on that claim.
The studies concerning long-term impact of surgical checklists I found all claim an improvement.
> Sustained use of the checklist was observed with continued improvements in process measures and reductions in 30-day surgical complications almost 2 years after a structured implementation effort that demonstrated marked, short-term reductions in harm. The sustained effect occurred despite the absence of continued oversight by the research team, indicating the important role that local leadership and local champions play in the success of quality improvement initiatives, especially in resource-limited settings.
>Only 3 of 22 operating stations (13.6%) had a functioning pulse oximeter prior to the intervention; accordingly, a pulse oximeter (model 7500; Nonin Medical Inc) was installed at each operating station as part of the implementation effort
The addition of essential medical equipment surely won't bias our results!
Interesting, that kind of surprises me. Without going to research it right now, I wonder how/if the efficacy is affected by things like going through them in tandem with a partner, or doing them out loud or with exaggerated physical acknowledgements (like the Japanese train drivers who point out signs/notices along their route as a way to maintain focus on those notices).
Over time people internalize the checklists because they unwittingly conclude the reason for the checklist is to learn a new procedure rather than foolproof their procedures and avoid errors. As a result, they start to skip the checklist or get sloppy with it.
There are a couple other points related to this that I believe Gawande does address in his book:
1. Doctors (more generally experts or egoists) will be resistant to checklists because they find them unnecessary (given their experience or expertise).
2. Checklists need to managed with regular review and updates.
You can boil Gawande's book down to: "Start using checklists because they're really effective." But his book goes deeper than that and addresses some of the underlying human factors involved in getting an organization to use checklists effectively.
At the end of Chapter 7 of Gawande's book (The Checklist Manifesto) is this revealing tale:
<quote>
Nonetheless, some skepticism persisted. After all, 20 percent did not find it easy to use, thought it took too long, and felt it had not improved the safety of care.
Then we asked the staff one more question. “If you were having an operation,” we asked, “would you want the checklist to be used?”
A full 93 percent said yes.
</quote>
But I agree with you wholeheartedly. I don't want my mind cluttered with stuff that can be handled by simple script.
It's been almost a year now since I read this but I'm fairly certain Atul touched on this, either in this book or in his book "Better", that after those implementing the changes left, the departments often fell back into old habits.
Could this be the case?
In order for the benefit to stick, you need to actually change the system. Otherwise, complacency or other things will return when the pressure and other early benefits wear off.
- [ ] not complete
- [x] completed
Other tools support additional per-task workflow states:
- [o] open
- [x (2019-04-17)] completed on date
I worked on a large hospital internal software project where the task was to build a system for reusable checklists editable through the web that prints them out in duplicate or triplicate at nearby printers. People really liked having the tangible paper copy.
"The Checklist Manifesto" by Atul Gawande was published while I worked there. TIL pilots have been using checklists for process control in order to reduce error for many years.
Evernote, RememberTheMilk, Google Tasks, and Google Keep all support checklists. Asana and Gitea and TaskWarrior support task dependencies.
A person could carry around a Hipster PDA with Bullet Journal style tasks lists with checkboxes; printed from a GTD service with an API and a @media print CSS stylesheet: https://en.wikipedia.org/wiki/Hipster_PDA
I'm not aware of very many tools that support authoring reusable checklists with structured data elements and data validation.
...
There are a number of configuration management systems like Puppet, Chef, Salt, and Ansible that build a graph of completable and verifiable tasks and then depth-first traverse said graph (either with hash randomization resulting in sometimes different traversals or with source order as an implicit ordering)
Resource scheduling systems like operating systems and conference room schedulers can take ~task priority into account when optimally ordering tasks given available resources; like triage.
Scheduling algorithms: https://news.ycombinator.com/item?id=15267146
TodoMVC catalogs Todo list implementations with very many MV* JS Frameworks: http://todomvc.com
GitHub and GitLab support (multiple) Issue and Pull Request templates:
Default: /.github/ISSUE_TEMPLATE.md || Configure in web interface
/.github/ISSUE_TEMPLATE/Name.md || /.gitlab/issue_templates/Name.md
Default: /.github/PULL_REQUEST_TEMPLATE.md || Configure in web interface
/.github/PULL_REQUEST_TEMPLATE/Name.md || /.gitlab/merge_request_templates/Name.md
There are template templates in awesome-github-templates [1] and checklist template templates in github-issue-templates [2].
I'll often be on call with customer and create a checklist on MacOS Notes on the fly. Then will copy paste that in slack or github for simple tracking.
You can post GitHub/GitLab project updates to a Slack/Mattermost channel with webhooks (and search for and display GH/GL issues with /slash commands); though issue edits and checkbox state changes aren't (yet?) included in the events that channels receive.
You'd need some system to mark when one list ends and the next begins, KanBan just treats them as individual tasks.
> even basic stuff like re-arranging your list.
All of them let you re-arrange your list. Is this a mobile specific issue?
That said, "the medical community" is not a homogeneous monolith, and you can absolutely find regional variation in what checklists are used for, how detailed they are, how closely they're followed, how people are accountable for keeping to them, etc.
"The Checklist Manifesto" chose to overlook the studies about how transient the benefit of checklists is.