Patient Safety Lives in the Gaps Between Teams

Many patient safety failures do not belong to one person or one department.

They happen in the space between them.

Between the emergency department and the inpatient unit.

Between nursing and pharmacy.

Between the hospital and the next place a patient receives care.

Each team may complete its own part correctly while the patient still experiences a gap.

That is why patient safety depends on more than strong departments. It depends on the connections between them.

🧭 Today, We Go Off the Clinical Path…

Healthcare is organized into teams for good reasons. Different disciplines bring different expertise, responsibilities and ways of seeing risk.

Patients, however, do not experience care as an organizational chart.

They experience one journey.

A medication changes during hospitalization. A follow-up appointment needs to be scheduled. A test result returns after discharge. A new symptom appears while the patient is moving from one setting to another.

In each moment, safety depends on whether the right information reaches the right person and whether someone clearly owns the next step.

Handoffs are often discussed as communication events, but they are also transfers of responsibility. A good handoff answers more than what happened. It makes clear what remains unresolved, what could go wrong, who is watching and what should happen next.

When that ownership is vague, risk settles into the gap.

🥾 Where the Path Gets Rough

The most difficult gaps are often hidden by processes that appear complete.

A referral was placed, but no one confirmed that the receiving team accepted it. A critical result was routed correctly, but the person responsible was away. Discharge instructions were documented, but the patient did not understand which medication to stop. A concern was mentioned during report, but it was not clear who would follow up.

Everyone touched the process. No one fully owned the outcome.

Technology can make this more complicated. One team documents in the electronic record. Another relies on an inbox, work queue or separate platform. Alerts may be sent without confirming that they were seen. A completed task may mean the message left one system, not that the next action occurred.

Organizational boundaries add another layer. Departments may use different definitions, escalation paths and operating hours. Each process can work within its own area while failing at the point of connection.

When an event occurs, reviews sometimes focus on the last person who touched the patient. That may identify an individual action, but it can miss the conditions that made the gap predictable.

The more useful question is not only, ‘Who missed this?’ It is, ‘Where did shared responsibility become unclear?’

🧭 Check Your Compass

Leaders can learn a great deal by mapping the moments when work changes hands.

Where does information move from one team, role or system to another?

What must the receiving team know immediately?

How does the sender know the handoff was received and understood?

Who owns unresolved items during the transition?

What happens after hours, during high volume or when the usual person is unavailable?

How does the patient know whom to contact?

These questions should be tested against real work, not only the written policy.

A process map may show a clean arrow between departments. The lived workflow may include phone calls, sticky notes, copied messages, personal relationships and repeated checking. Those adaptations often reveal where the formal process is not carrying the full load.

Frontline teams know which handoffs make them uneasy. Their near misses, workarounds and repeated follow-up calls are valuable safety data.

💡 A Different Direction

What if organizations managed the spaces between teams as deliberately as they manage the teams themselves?

That could mean creating shared measures for transitions instead of separate departmental measures. It could mean reviewing delayed referrals, missed follow-up and incomplete escalation across the entire pathway rather than assigning each piece to a different committee.

It could also mean designing handoffs around closed-loop communication. The sender communicates the concern. The receiver acknowledges it. Responsibility is named. Completion is visible. If the expected action does not occur, the process escalates without relying on one person’s memory.

Patients and families belong in that loop. They often become the only people who see the whole journey, yet we may give them fragments of information from each department and expect them to assemble the plan.

Clear language, one point of contact and visible next steps can reduce that burden while strengthening safety.

Closing gaps does not require every team to work the same way. It requires them to agree on how responsibility crosses the boundary.

⭐ Finding True North

Healthcare will always involve transitions.

Patients will move between shifts, departments, clinicians, organizations and settings. Expertise will remain distributed across teams.

The goal is not to eliminate every boundary. It is to make the boundary safe to cross.

That requires leaders to look beyond whether each department completed its own task. We have to ask whether the patient’s need made it all the way through the system.

Many safety failures live in the gaps between teams.

So do many of our best opportunities to improve care.

Think about one transition in your organization that depends too heavily on memory, persistence or knowing the right person. That may be a gap worth closing.

Until next time, keep asking questions, challenging what has always been done and finding your true north. 🧭

Off the Clinical Path—Navigating the challenges, changes and innovations shaping healthcare.