Pathology Turnaround Time the Ordering Practice Sees

Every pathology group reports a pathology turnaround time it is proud of, and most of them are measuring a clock their clients never see. The lab clock starts at accession and stops at signout. The client clock starts when the specimen left their office and stops when a usable report is in front of the person who ordered it. Those two numbers can differ by days, and only one of them decides whether the account renews.

The gap is made of the parts nobody owns.

On the front end there is transit, then intake, then the pause while a requisition with a missing field waits for somebody to chase it. On the back end there is release, then transmission, then the silence between a report that was sent and a report that arrived somewhere a human will read.

Your internal number excludes both ends by construction. So a lab can hold a strong signout metric for a year while its accounts quietly conclude that results take too long, and there is no report on any dashboard that would have shown the disagreement.

Worse, the complaint arrives as a phone call rather than as data. One practice manager says results are slow. Nobody can tell whether that is true, whether it is true only for that account, or which stage caused it.

Measure the whole clock, then split it into stages you can act on

The fix is not a better signout metric. It is a longer one, cut into segments.

Four stages cover almost everything. Received to accessioned. Accessioned to signed out. Signed out to transmitted. Transmitted to confirmed. Each has a different owner and a different remedy, and an average that spans all four hides which one is broken.

Once it is split, the cause stops being an argument. A slow account is either a front-end problem, which is usually incomplete paperwork or courier timing, or a back-end problem, which is usually a delivery destination that has quietly stopped working. Both are fixable. Neither is visible in a signout number.

The stage that surprises most groups is the first one. Cases that arrive incomplete sit in a holding state that the lab does not think of as its clock, because the lab is waiting on somebody else. The client counts it anyway.

The data already exists as structured records, not as a report you buy

The reason this rarely gets measured is not that the data is missing. It is that the data lives in three systems and nobody joins them.

athenaOne holds more of it than most groups realize. Case documents carry state and close reasons, and there is a changed-document feed that reports what moved and when rather than what the current state happens to be. That distinction is the whole thing. A snapshot tells you where a case is. A change feed tells you how long it took to get there, which is the only version that produces a stage metric.

Close reasons matter as much as timestamps. A case that closed because it was delivered and confirmed and a case that closed because somebody gave up look identical in a count and opposite in a service level. Categorizing the closes is what stops a clean-looking metric from being an artifact of how the queue gets emptied.

Build the stage clocks on the change history, group them by account, and the conversation with a complaining client turns from an impression into a line.

Report it per account, because the average is the least useful number

A lab-wide median is the number most groups publish and the number least likely to change anyone’s behavior.

Accounts differ in ways that are structural rather than random. One sends complete paperwork and reads an interface. One sends handwritten forms and reads a fax that goes to a machine near the break room. One is a multi-site group whose several locations behave like different customers because they are configured differently underneath one parent.

Per-account stage reporting turns that into something you can sell against. It also turns a renewal conversation into a joint problem, because a client whose own intake gaps are adding two days to the clock will usually fix them once they can see it, and will not while the only number on the table is yours.

Revenue leakage tracks the same seams. Practices that find leaks in the revenue cycle find them at handoffs between steps rather than inside them, and the handoff points in a pathology case are exactly the four stage boundaries above.

A metric nobody works is a metric nobody trusts

Measurement only pays if something happens when a case crosses a threshold, and that is where automation earns its place.

A case that has been waiting on a missing requisition field for a day generates a call to the sending practice, not a row on a report. A case whose report has been released but never confirmed as delivered generates a redelivery call to the account. A case that has been in process past your own stated window becomes a flagged item for the lab rather than a surprise for the client.

Those three calls are administrative, repetitive, and almost never made, because they are nobody’s assigned work. Handing them to automation converts the metric from a scorecard into a control loop.

The monthly account review changes shape too. Instead of a single number, the client sees their own stage breakdown, the count of cases that stalled on intake, and what was done about each. That is a different meeting.

What the numbers are not allowed to do

Two boundaries keep this safe, and both are worth stating in the specification rather than assuming.

The first is scope. Everything here counts states and timestamps. Nothing reads the report, characterizes what a case shows, ranks cases by what is in them, or decides which one matters more. Case priority comes from your lab’s own rules and your pathologists, and the automation sorts by the flags they set rather than by content it inspected.

The second is release. The federal test report standard limits who a laboratory may release results to, and a stage metric that reports timing is a different object from a result. Keep the reporting layer built on states, accounts, and clocks, and the compliance question stops being interesting.

Where a threshold is crossed on a case your staff has flagged, the escalation goes to a person immediately and the automation stops. Faster escalation is the contribution. The call itself is not.

Key Takeaways

Measure received to confirmed, not accessioned to signout, because the client is already measuring the longer clock whether you report it or not.
Split the clock into four stages with different owners, since an average across all of them hides which one is actually failing.
Build the metric on the change history and close reasons rather than a current-state snapshot, which cannot produce a duration.
Report per account instead of lab-wide, because account differences are structural and a shared number gives the client something to fix too.
Attach an automated call to every threshold breach, or the metric becomes a scorecard nobody works.

The number your lab reports and the number your clients experience are different numbers, and the difference is made entirely of stages you do not currently time. Cut the clock into four, build it from the change history, report it per account, and put an automated call behind every breach. The pathology does not get faster. What changes is that the delay becomes visible while it is still cheap to fix, and the account review stops being a conversation about whose fault it is.

Sources