Every Reporting Requirement Is a Story We Don’t Tell Anymore

Patient Behind the Policy

Few healthcare tasks generate less enthusiasm than documentation.

Ask almost any clinician about reporting requirements, checklists, attestations, or reconciliation processes, and you'll hear a familiar question:

Why do we have to do all of this?

It's a reasonable question. Most requirements arrive without their history.

The processes are inherited long after the reasons are forgotten.

Medication reconciliation is one of those safeguards.

There is nothing particularly dramatic about the process itself.

A medication list is reviewed. Duplications are identified. Discrepancies are clarified. Changes are documented.

The consequences of getting it wrong are another story.

More accurately, thousands of stories.

Some visible. Some not.

Many of the requirements we follow today exist because healthcare chose to learn from those stories.

The requirements and processes were created after something revealed they were needed.

Every transition in care creates an opportunity for error. A patient is admitted. Transferred. Discharged. A specialist adjusts a medication. A primary care provider updates a treatment plan. A hospitalist discontinues a medication intended to continue after discharge. With every handoff comes the possibility that information will be lost, misunderstood, or assumed.

Medication reconciliation developed as a process to reduce those risks and clarify what medications a patient is actually supposed to be taking.

The need for safeguards like medication reconciliation did not arise in a vacuum.

In 1999, the Institute of Medicine published To Err Is Human, a landmark report estimating that between 44,000 and 98,000 Americans died each year as a result of preventable medical errors. More importantly, it challenged healthcare to think differently about patient safety. Rather than asking who made the mistake, it asked what conditions allowed the mistake to occur.

That shift changed the conversation.

Healthcare began looking beyond individual actions and examining the systems, processes, and communication failures that contribute to harm.

Efforts such as The Joint Commission's National Patient Safety Goals grew from that work. Medication reconciliation became a priority because transitions in care repeatedly revealed the same vulnerability: when information fails to follow the patient, the patient bears the risk.

Medication reconciliation is only one example.

Most requirements were not created because systems were working perfectly.

They were created because something exposed a gap, a risk, or a vulnerability that could no longer be ignored.

Somewhere, a communication failed.

Somewhere, an assumption went unchallenged.

Somewhere, a safeguard proved insufficient.

And somewhere, a patient experienced the consequences.

Over time, those stories fade.

The form remains.

The checklist remains.

The policy remains.

New employees inherit processes they did not create. Leaders inherit requirements they did not write. Teams follow procedures long after the circumstances that created them are forgotten.

Eventually, the process itself becomes the entire conversation.

People ask whether it is necessary.

Whether it creates value.

Whether it could be removed.

Sometimes those are the right questions.

But sometimes the better question is:

What lesson are we in danger of forgetting?

Compliance frustrations begin with the loss of context, not the requirement itself.

Most people are willing to do meaningful work.

What they struggle with is work that no longer seems connected to a meaningful outcome.

When people understand how their actions protect a patient, support a colleague, or reduce a known risk, the work carries a different kind of meaning. It becomes more than a task to complete or a box to check.

Over time, however, that connection can weaken. People inherit the process without hearing the story behind it. The step remains, but the lesson that gave it purpose becomes harder to see.

What was once a hard-learned lesson begins to look like bureaucracy.

That's why context matters.

The challenge for healthcare leaders is not simply maintaining policies.

It's preserving meaning.

Because when people understand the lesson, the process makes sense.

Not because every process is perfect, but because understanding why something exists is often what gives people the willingness to do it well.

We often describe compliance as a regulatory obligation.

I think of it differently.

Compliance is one of the ways organizations recall.

Not simply what happened, but what was learned.

Not simply the rule, but the reason it exists.

The policy is rarely the whole story.

Somewhere behind it is a lesson worth remembering.