Tag Archives: Never Event

That’s not my baby!

By ThinkReliability Staff

New mothers and maternity centers alike live in fear that babies will be discharged to the wrong family. The Joint Commission considers discharge of an infant to the wrong person a never event, and it’s no surprise. Even if the mix-up is quickly rectified, huge problems can ensue.

Luckily, we don’t have to wait until an incident happens to us. We can instead perform a proactive root cause analysis, where we consider what COULD go wrong to result in an infant being discharged to the wrong person. A thorough root cause analysis built as a Cause Map can capture all of the causes in a simple, intuitive format that fits on one page.

For our very basic Cause Map, we can consider that two things have to happen in order for a infant to go home with the wrong family. First, the wrong baby has to be given to a family, and second, the matching system has to be ineffective. We’ll break each of these causes down into more detail.

The matching system may be ineffective because it isn’t being used. If a facility doesn’t have a matching system, it obviously won’t be effective. Additionally, if a computerized system is in use there is always the possibility that it won’t be working. Or the staff may not know how to use the system, possibly due to lack of training or insufficient staffing.

If the system is being used but not being checked, it won’t be effective. Again, this could be because the staff doesn’t know how to use the system, or it could just be that the discharge personnel forget.

The wrong baby could be given to a family if the matching system is on the wrong infant. (This is only likely to happen if the matching system is put on outside the delivery room.) Or, the wrong baby could be in a bassinet. This could happen if the baby is kept in an nursery and a nurse is transporting more than one baby..

It’s possible to add even more detail to this Cause Map as the analysis continues. As with any investigation the level of detail in the analysis is based on the impact of the incident on the organization’s overall goals. Once the Cause Map is complete, solutions can be brainstormed that match up with causes. The solutions are shown on the downloadable PDF.

Click on “Download PDF” above to download a PDF showing the Cause Map and Solutions.

The surgery went well . . . except it wasn’t supposed to be done on you.

By ThinkReliability Staff

A “never event” that should come as no surprise considering its profound implications on patient safety is performing a procedure on the wrong patient. Ordinarily there are many checks to ensure that a patient’s identity matches that on the procedure order.

However, sometimes a combination of oversights can result in these checks being ineffective. This is especially true when there are patients of similar names, as happened in this particular case.

A patient (patient 1) was scheduled for a procedure in the EP lab. The EP lab called up to Patient 1’s floor, and were directed (incorrectly) to another floor by a person on the telephone. Although Patient 1 was on that floor, another patient with a similar name (patient 2) had been moved to another floor. The EP lab then directed Patient 2’s nurse to bring Patient 2 to the lab. The nurse brought Patient 2 to the lab, over her objections, despite the lack of information in Patient 2’s chart, or a signed consent form.

The various staff members at the EP lab did not verify the identity of the patient, either. However, they did notice the lack of consent form, and convinced Patient 2 to sign a consent form, for a procedure she did not need, was not scheduled for, and had opposed throughout the process.

Although the procedure was stopped partway through, when the true identity was realized, and there was no lasting injury to Patient 2, any procedure performed on the wrong patient has huge risk for patient safety.

On the downloadable PDF page, a simplified version of the process for taking patients to procedures is shown. The individual causes of the incident are identified in the Cause Map, and, where applicable, the process map. This example shows how a process map can be used to identify the various causes that led to an event.

A thorough root cause analysis built as a Cause Map can capture all of the causes in a simple, intuitive format that fits on one page. Even more detail can be added to this Cause Map as the analysis continues. As with any investigation the level of detail in the analysis is based on the impact of the incident on the organization’s overall goals.

Click on “Download PDF” above to download a PDF showing the Cause Map and Process Map.

We Regret to Inform You We’ve Removed the Wrong Leg . . .

By ThinkReliability Staff

Performing surgery on the wrong body part or wrong-site surgery is a “never event” as defined by the National Qualify Forum (NQF), and can have serious health consequences for a patient.

We can use a Cause Map to determine some ways to prevent wrong-site surgery. Some of the common errors leading to wrong site surgeries are presented in the Cause Map found on the downloadable PDF. They include: time pressure, lack of paperwork, misreading radiography, not marking or incorrectly marking the surgical site, and marking the wrong site.

Once the root cause analysis is complete, solutions are brainstormed and placed with the cause they control. In this example, we use the solutions to create a basic Process Map for the surgical preparation procedure to prevent wrong site surgeries. The solutions are numbered based on the order they appear on the Process Map. It’s clear that consistent adherence to this Process Map would result in fewer wrong-site surgeries.

Click on “Download PDF” above to download a PDF showing the Cause Map and Process Map.

Go to Root Cause Analysis Healthcare Home Page