Reducing Patient Record Errors by 30% Through Better Process Documentation

Written By: Jordan King, Jordan B Consulting

Client: An anonymized healthcare provider

Location: US

Industry: Healthcare

Services: Process Documentation, SOP Development, Workflow Improvement, Knowledge Management

The situation

A 12-person call centre team at a healthcare provider was making errors on approximately 30% of patient records.

The team was working hard, but everyone was relying on a slightly different version of the process.

There was no central place to check what should happen during a live patient call. If someone wasn't sure, they asked a colleague. If that colleague wasn't sure, they asked someone else. Sometimes the answer depended on who happened to be available.

Management was already aware of the KPI problem and spending a lot of time trying to address it. But with managers tied up in meetings and staff still working from different versions of the process, the same questions and mistakes kept coming back.

The obvious answer might have been more training.

I wanted to understand the problem first.

So I tracked the errors and the workflow for two weeks. The issue wasn't simply that staff didn't know what to do. They didn't have accessible, consistent process documentation they could use while doing the job.

What I did

I built a central documentation system in Microsoft Teams so the entire team could work from the same information.

The system included:

• Clear documentation for each stage of the patient call process

• A shared location that representatives could access while speaking with patients

• Answers to common process questions

• A central place for staff to ask questions when something genuinely wasn't covered

• A system where an answer given to one person became available to the entire team

• A consistent reference point for the process rather than twelve individual versions of it

The aim wasn't to give the team another document to read. It was to make the correct information available at the point they needed it.

The results

Six weeks after the new documentation system was implemented:

• Patient record errors reduced by approximately 30%.

• Average call time dropped from more than six minutes to under five minutes.

• Staff stopped repeatedly asking the same questions because answers were documented and available to everyone.

• Representatives had one shared process rather than relying on individual knowledge.

• Management no longer had to be the answer desk for every small process question.

The improvement came from making the process clearer and easier to access, rather than starting the entire team over with another round of training.

Why this matters

When a team keeps making the same mistake, training is often the first thing people reach for. Sometimes training is the answer. Sometimes the problem is that the person already knows what to do, but can't find the answer when they need it.

That was the issue here.

Twelve people were doing the same job, but they were effectively working from twelve versions of the process.

The solution was to put the knowledge in one place, make it accessible in real time and make sure answers were shared across the team. That reduced errors, shortened calls and gave the team a process they could actually use.

Good process documentation shouldn't sit in a folder gathering dust. It should make someone's job easier five minutes after you create it.

That's the difference between documenting a process and actually improving one.

Same problem, different company? Let's talk about what the fix looks like for you.