<?xml version="1.0"?>
<rss version="2.0"><channel><title>Learn: Learn</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/?d=1</link><description>Learn: Learn</description><language>en</language><item><title><![CDATA[Q&A: Patient safety derives from data-driven leadership (5 July 2024)]]></title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/qa-patient-safety-derives-from-data-driven-leadership-5-july-2024-r11747/</link><description/><guid isPermaLink="false">11747</guid><pubDate>Mon, 08 Jul 2024 08:23:00 +0000</pubDate></item><item><title>Near misses or great catches? A blog by Emma Walker</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/near-misses-or-great-catches-a-blog-by-emma-walker-r10057/</link><description><![CDATA[
<p><img src="https://www.pslhub-assets.org/monthly_2023_09/Singleimage10.png.add8458123c3cc9dbcfd2e0e2dcec1b7.png" /></p>
<p>
	I was on one of the great <a href="https://www.pslhub.org/learn/professionalising-patient-safety/the-voices-of-the-patient-safety-frontline-%E2%80%93-the-patient-safety-management-network-two-years-on-r9894/" rel="">Patient Safety Management Network</a> drop-ins the other week, where they were sharing the learning from a safety observation session. The Session had been in a busy A&amp;E department and at one point the observer flagged that a patient hadn’t been given a name tag for their wrist. The observer stepped in, identified the harm and it was rectified. I asked in the meeting chat if the organisation in question had flagged this as a near miss? "<em>No, I don’t think so</em>" was the response – "<em>there are just too many near misses, and we are just too busy to report every one.</em>" Many folk on the call agreed.
</p>

<p>
	I was surprised to hear this. Having spent nearly 20 years married to a chemical engineer and spending a lot of my free time with engineers from across industry, I know that this behaviour would be totally unacceptable across the organisational cultures they work in, and potentially a reportable/disciplinary issue. Interestingly, their ingrained behaviours and cultures are such that it doesn’t usually get to that stage as everyone just knows what the right thing to do is and there are systems and cultures to make it easy.
</p>

<p>
	However, not the NHS it seems. As my husband said when we discussed this later, "<em>this is free learning, and there are hundreds of firms across the country willing to show you tools and techniques to make reporting quick and easy"</em>.
</p>

<p>
	A colleague of mine, who was recently clinical, mentioned how ‘busy’ and ‘longwinded’ some reporting forms are... having to log into a computer (if one is available) while so busy: "<em>I used to do mine at the end of a shift, not getting home till after 10 at night despite finishing at 20:15</em>".
</p>

<p>
	Going back to the PSMN drop-in, what was really interesting was a nurse from the USA at the meeting was one of the few who agreed that not reporting near misses was really poor safety culture. She talked about how they are an aspiring high reliability organisation and how "<em>we love near misses – we call them great catches</em>". 
</p>

<p>
	What can you do today to start changing your safety culture? How can you make it easy for all staff to do the right thing? A culture that doesn’t blame with easy, quick processes to follow, and support for staff to do just that. 
</p>

<p>
	<span style="color:#1abc9c;"><strong>Go and make a great catch and prevent the next patient/member of staff suffering the same harm. As we know, a great catch missed today could become something far worse tomorrow.</strong></span>
</p>

<p>
	Do you have a 'good catch' reporting system? <span style="background-color:rgb(252,252,252);">Share your experiences and questions in our </span><a href="https://www.pslhub.org/forums/topic/341-do-you-have-a-good-catch-reporting-system/#comment-1490" rel="" style="background-color:rgb(252,252,252);">Community thread</a> or comment below <span style="background-color:rgb(252,252,252);">You'll need to</span> <a href="https://www.pslhub.org/register/" rel="" style="color:rgb(61,101,148);"><u>register for free first</u></a><span style="background-color:rgb(252,252,252);">. .</span>
</p>

<h3>
	<span style="font-size:18px;">Related reading:</span>
</h3>

<ul>
	<li>
		<a href="https://www.pslhub.org/learn/leadership-for-patient-safety/quality-and-safety-reports/near-miss-and-good-catch-reporting-r9917/" rel="" style="color:rgb(61,101,148);">Near-Miss and Good-Catch Reporting</a>
	</li>
	<li>
		<a href="https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/promote-a-culture-of-safety-with-good-catch-reports-r375/" rel="" style="color:rgb(61,101,148);">Promote a culture of safety with good catch reports</a>
	</li>
	<li>
		<a href="https://www.pslhub.org/learn/leadership-for-patient-safety/quality-and-safety-reports/using-good-catches-to-increase-worker-ownership-of-safety-r9919/" rel="" style="color:rgb(61,101,148);">Using good catches to increase worker ownership of safety</a>
	</li>
	<li>
		<a href="https://www.pslhub.org/learn/leadership-for-patient-safety/quality-and-safety-reports/5-examples-of-good-catches-in-healthcare-and-how-to-implement-a-near-miss-campaign-r9918/" rel="" style="color:rgb(61,101,148);">5 Examples of good catches in healthcare and how to implement a near miss campaign</a>
	</li>
</ul>
]]></description><guid isPermaLink="false">10057</guid><pubDate>Fri, 08 Sep 2023 14:43:00 +0000</pubDate></item><item><title>Health information technology&#x2013;related wrong-patient errors: Context is critical (December 2020)</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/health-information-technology%E2%80%93related-wrong-patient-errors-context-is-critical-december-2020-r3791/</link><description/><guid isPermaLink="false">3791</guid><pubDate>Tue, 22 Dec 2020 14:36:03 +0000</pubDate></item><item><title>Royal Cornwall Hospitals NHS Trust: Harms review standard operating procedure (October 2018)</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/royal-cornwall-hospitals-nhs-trust-harms-review-standard-operating-procedure-october-2018-r5585/</link><description/><guid isPermaLink="false">5585</guid><pubDate>Thu, 19 Nov 2020 16:44:00 +0000</pubDate></item><item><title>Promote a culture of safety with good catch reports</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/promote-a-culture-of-safety-with-good-catch-reports-r375/</link><description/><guid isPermaLink="false">375</guid><pubDate>Wed, 14 Aug 2019 12:06:00 +0000</pubDate></item><item><title>PSNet: Systems Approach</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/psnet-systems-approach-r372/</link><description><![CDATA[<p>
	In this article they use this case to highlight the importance of analysing errors using a systems approach. James Reasons 'Swiss cheese model of medical errors' is explained and put into context.
</p>]]></description><guid isPermaLink="false">372</guid><pubDate>Wed, 14 Aug 2019 11:43:00 +0000</pubDate></item><item><title>The Heinrich/Bird safety pyramid</title><link>https://www.pslhub.org/learn/improving-patient-safety/disasters-averted-near-misses/in-health-care/the-heinrichbird-safety-pyramid-r204/</link><description><![CDATA[
<p>
	The Heinrich/Bird safety pyramid is presented in an article in <em>Risk Engineering</em>. It includes an infographic with Heinrich's Accident Triangle. This triangle suggests that the ratio between fatal accidents, accidents, injuries and minor incidents are similar across all industries. It highlights the importance of investigating the minor incidents to present fatal incidents.
</p>

<p>
	<strong><span style="font-size:16px;">Challenge:</span></strong>
</p>

<p>
	In healthcare, are we investigating the wrong incidents?
</p>
]]></description><guid isPermaLink="false">204</guid><pubDate>Mon, 15 Jul 2019 07:14:00 +0000</pubDate></item></channel></rss>
