Four Surgical Patients Received the Wrong Medication. The Lesson Isn't “Be More Careful.”

Sep 17

6 min read

On August 14, 2026, four patients arrived at Ascension Saint Thomas Hospital Midtown in Nashville for joint-replacement procedures.

They were supposed to receive the anesthetic medication mepivacaine.

Instead, they received potassium phosphate.

All four experienced serious adverse reactions.

When a story like this reaches the news, the immediate reaction is understandable:

How could someone make that mistake?

But after reviewing what investigators found, there is a more important question for those of us who work in high-risk healthcare environments:

How did one error make it through multiple layers of a healthcare system and reach four patients?

Because this wasn't one mistake.

First, Let's Get the Facts Right

Early reporting created confusion about the medications involved. Subsequent information released by Ascension clarified that the four affected patients received potassium phosphate instead of the intended anesthetic medication, mepivacaine.

Ascension reported that seven joint-replacement patients were on the surgical schedule that day and four received the incorrect medication.

The hospital identified the error on August 14, self-reported the event to regulators, and began implementing corrective measures.

The subsequent Tennessee investigation provided a much more troubling picture.

Investigators identified failures involving pharmacy processes and broader hospital systems. The state cited three immediate-jeopardy conditions involving pharmacy services, surgical services, and hospital governance.

Five syringes containing the incorrect medication had reportedly been prepared.

Four reached patients.

That distinction matters.

The question isn't only how the wrong medication got into a syringe.

It's why the system didn't reliably catch it before it reached multiple patients.

Patient Safety Cannot Depend on Perfect People

Healthcare professionals are human.

We can become distracted.

We can misread something.

We can become fatigued.

We can trust that someone before us already verified something.

We can develop workarounds when technology repeatedly interferes with workflow.

None of that makes an error acceptable.

It explains why healthcare cannot build patient safety around one instruction:

“Be more careful.”

High-risk systems are supposed to anticipate human error.

That's why we have layers.

Medication storage.

Product selection.

Barcode verification.

Labeling.

Independent checks.

Final verification.

Communication.

Each layer is another opportunity to prevent an error from reaching a patient.

When several of those layers fail at the same time, the result can be catastrophic.

A Warning Isn't a Safety Barrier If We Routinely Work Around It

One of the most important issues raised in reporting on the investigation involves medication scanning and verification.

The process reportedly allowed barcode problems to be bypassed as the medication moved through preparation.

Think about what that means beyond this individual case.

Technology can give us warnings.

But a warning only protects someone if the system requires us to meaningfully respond to it.

Anyone who works in healthcare knows how workarounds develop.

The scanner won't read.

The computer isn't cooperating.

Something isn't where it's supposed to be.

Everyone is busy.

So somebody figures out another way to keep the workflow moving.

Sometimes workarounds solve legitimate operational problems.

But there is a danger when bypassing a safeguard becomes so routine that nobody experiences it as bypassing a safeguard anymore.

After this event, Ascension announced a mandatory stop-and-resolution process requiring independent verification for spinal-medication scan alerts.

That raises a question every healthcare department should consider:

When our technology tells us something doesn't match, does our system make it easier to investigate the problem—or easier to bypass the warning?

Multiple Checks Aren't Enough

We frequently talk about double-checks in healthcare.

But two people participating in a process doesn't automatically mean there were two independent checks.

Imagine this:

Person A assumes Person B will catch a problem.

Person B assumes Person A already checked it.

Person C sees that two people have already handled it and assumes the verification must have occurred.

Technically, multiple people interacted with the process.

Functionally, nobody performed a truly independent verification.

That's why safety isn't measured by how many signatures appear on a document.

The question is whether each checkpoint actually functions as another opportunity to identify a problem.

Following the Nashville incident, Ascension announced that spinal-medication workflows now require a second trained pharmacist to conduct final visual and physical checks.

Training Is Part of the Safety System

There's another lesson here that matters tremendously to FTLOS.

Healthcare has to train new people.

Students need experience.

New graduates need experience.

Professionals changing specialties need experience.

People learning new technologies need experience.

There is nothing wrong with learning.

The question is:

What system surrounds the learner?

Strong training requires appropriate supervision, demonstrated competency, clear expectations, and an environment where asking for help is encouraged.

That applies whether we're talking about pharmacy, nursing, surgical technology, anesthesia, sterile processing, or another high-risk healthcare role.

Being new should never mean being unsupported.

And being experienced should never mean assuming somebody else already checked.

What Happens When the Unexpected Starts Repeating?

Perhaps one of the most difficult questions raised by this event is that four patients received the incorrect medication before the problem was stopped.

That should make every surgical professional think.

Unexpected events happen in healthcare.

One unexpected event may have many possible explanations.

But what happens when something unusual begins repeating?

At what point does a team stop asking:

“What's happening with this patient?”

and begin asking:

“Is there something these patients have in common?”

This isn't about second-guessing the clinical decisions made in Nashville. We weren't there, and FTLOS is not here to diagnose these patients or tell clinicians how they should have treated them.

It's about something broader:

Does our culture empower someone to stop the process when the pattern no longer makes sense?

“Stop the Line” Has to Mean Something

Healthcare organizations frequently tell employees to speak up.

But speaking up isn't created by a poster.

It isn't created by an annual training module.

It becomes part of culture when people know they can actually say:

Wait.

Something doesn't look right.

I want to check this again.

I'm not comfortable moving forward yet.

And they can do that regardless of seniority, title, or how much pressure exists to keep the schedule moving.

A high-reliability environment doesn't simply give people permission to speak up.

It expects them to.

Accountability Without Blame

Accountability absolutely matters.

Professional standards matter.

Investigations matter.

Organizations have an obligation to understand what happened and address failures.

But if our only question after a serious event is:

“Whose fault was this?”

we may identify a person without fixing the conditions that allowed the error to travel through the system.

A stronger safety investigation asks:

What happened?

Why wasn't it caught?

Which safeguards failed?

Which warnings were bypassed?

Where did independent verification stop being independent?

What changes would make this error harder to repeat?

That's not accountability without consequences.

It's accountability without blame.

The purpose is not to excuse mistakes.

The purpose is to learn enough from them to protect the next patient.

What Changed Afterward?

Ascension says it implemented several additional safeguards following the event.

Those include:

separating and distinctly marking high-alert medications;
implementing a mandatory stop-and-resolution process with independent verification for spinal-medication scan alerts; and
requiring a second trained pharmacist to perform final visual and physical checks for spinal-medication workflows.

The hospital also said it engaged independent third-party quality experts to review its mitigation plans and continues to cooperate with state and federal regulators.

Those changes are important.

But the larger lesson shouldn't belong only to Ascension.

Every healthcare organization can ask:

Do we already have the safeguards we would implement after something goes wrong?

The Question Every Surgical Department Should Ask

The easiest response to an event like this is:

“That would never happen here.”

But that's probably the least useful response.

Healthcare professionals make mistakes because healthcare professionals are human.

The more productive question is:

If one of us makes a mistake tomorrow, how many truly independent opportunities does our system have to catch it before it reaches the patient?

That conversation can happen today.

Before an incident.

Before an investigation.

Before someone's life changes.

That's what a culture of safety should be about.

Not expecting perfection from people.

Building systems that help good professionals catch one another's mistakes before those mistakes reach the patient.

Join the Conversation

For healthcare and surgical professionals—without identifying patients, coworkers, or facilities:

What is one safety process you understand differently now than you did when you first entered healthcare?

FTLOS discusses this case for professional education around healthcare operations, safety culture, and systems improvement. This article does not provide medical advice or determine individual professional, legal, or organizational liability.