Verity for diagnostic labs
Everything a lab is judged on happens between those two moments. Verity records each transition, so a delayed report has a traceable cause instead of an apology.
Verity runs lab operations. It is not an analyser interface or a reporting system.
Verity / Lab
LiveSamples today
1,240
Median turnaround
6h 20m
Pending beyond TAT
48
Reagents low
7
Needs attention
Illustrative figures. Verity shows your own lab in this shape.
How the business runs
A sample is collected, transported, received, accessioned, processed, verified and reported. Every one of those is a handoff, usually between different people at different locations, and the entire commercial and clinical value of the lab depends on that chain completing inside a time window. Turnaround time is the product.
When those transitions are not recorded, the lab can tell a patient that a report is delayed but cannot tell them why, and cannot tell itself where the delay repeatedly occurs. The delay is almost never in the analytical step everyone focuses on. It is in transport, in accessioning, in a sample that arrived without adequate identification, or in a verification queue waiting on one pathologist.
The second operational pressure is reagents. Tests cannot run without them, they have expiry dates and storage requirements, and consumption is proportional to a test volume that varies daily. A reagent shortage discovered on the morning of a heavy load stops revenue and breaks turnaround for every sample in the queue.
The third is that a lab’s demand comes from referring doctors and collection points rather than from patients directly. A referrer whose volume has halved is a commercial event, and it is usually noticed a quarter late because nobody counts referrals per referrer.
Verity records the sample lifecycle, the reagent position and the referrer relationship as connected records. It does not interface with analysers or generate clinical reports.
What Verity calls these things
What gets in the way
Lab problems are handoff problems, and handoffs are exactly what an analyser-focused view does not record.
Turnaround is reported as an average with no causes
The lab knows its median. It does not know that transport from one collection point adds ninety minutes on three days a week.
In Verity Every transition carries a timestamp and a location, so turnaround decomposes into stages that can each be addressed.
Samples are rejected after transport
A sample arrives haemolysed, insufficient or unlabelled, and the patient has to be recalled — which nobody attributes to the collection point that caused it.
In Verity Rejections are recorded with reason, collection point and phlebotomist, so recurring causes become addressable.
Reagent shortages stop a whole morning
Consumption is not compared with test volume, so a shortage is discovered when the run is due rather than when it could still be ordered.
In Verity Reagent stock is checked against forecast test load and supplier lead time, not against a shelf.
Verification is a single-person queue
Completed results wait on one pathologist, and the queue is invisible until reports are late.
In Verity Verification is a workflow step with an owner and an age, so the constraint is measurable.
Home collection routes break stability windows
A late route means samples arrive outside their stability window and must be recollected, at the lab’s cost and the patient’s inconvenience.
In Verity Routes are tracked against collection times and stability requirements, so a late route is flagged while it can be redirected.
Referrer decline is noticed a quarter late
A doctor who sent forty samples a month sends twelve, and nobody sees it because referrals are not counted per referrer.
In Verity Referrers are records with their volume and history, so a decline surfaces while it can still be discussed.
The complete system
One system across the sample lifecycle, reagents and referrers.
Records
Every sample is a record with its patient reference, tests requested, collection point, timestamps at each transition, state and result release.
Why it matters here The sample is the unit of work, and the lab’s entire performance is the history of its transitions.
In practice Forty-eight samples past turnaround, each showing the stage where the time was lost.
Work
Each stage is work with an owner, a location, a timestamp and a state, from draw through to report release.
Why it matters here Turnaround is made of stages, and only stage-level records tell you which one to fix.
In practice Nine urgent samples queued at the same step, visible before the reports are late rather than after.
Inventory
Stock is held with batch, expiry, storage location, supplier and cost, consumed by the tests that use it.
Why it matters here A reagent shortage is not an inconvenience; it stops revenue and breaks turnaround for everything queued behind it.
In practice Seven reagents short against tomorrow’s forecast load, flagged while a two-day lead time can still be met.
Relationships
Referrers are records with their referral volume, test mix, report delivery preferences, outstanding balances and contact history.
Why it matters here Referral volume is the lab’s demand, and it moves for reasons that are discussable if noticed in time.
In practice A referrer whose volume fell forty percent with no contact recorded since June.
People
The team is modelled once, and every collection, process step, verification and rejection carries who performed it.
Why it matters here Rejection rates and verification queues are both individual-level facts that only exist with attribution.
In practice Rejection rate by phlebotomist and collection point, from the rejections themselves.
Workflows
Sample rejection, repeat testing, critical value escalation and report amendment move through defined steps with recorded reasons.
Why it matters here These are the exceptions that determine both cost and clinical safety, and they are usually handled verbally.
In practice A rejection recorded with reason and collection point rather than a phone call asking for another sample.
Locations
Locations roll into the business, with samples, stock and reporting following the same structure, including routes as transit locations.
Why it matters here Most lost turnaround time is between locations, which is invisible unless transit is modelled.
In practice Transit time by route and collection point, which is where the delay usually is.
Reports and analytics
Turnaround by stage and test, rejection rates by cause and centre, reagent consumption against volume, referrer trends and verification queues come from the operational records.
Why it matters here Labs report turnaround averages to clients and rarely decompose them for themselves.
In practice Turnaround split into transit, accessioning, processing and verification, per centre.
Verity AI
Verity AI answers from your own sample, stock and referrer records, respects permissions, and can create assigned follow-ups.
Why it matters here The useful questions cross stage, location and time, which is exactly what a queue view cannot answer.
In practice "Where is turnaround time being lost this week?" returns the stage and the centre, with actions assigned.
Control
One permission model and one audit trail, with result release and amendment as recorded steps.
Why it matters here Diagnostic results carry access obligations and amendments carry clinical consequence.
In practice Every release and amendment carries the person, the time and the reason.
Communication
Notes, notifications and activity attach to the sample, route or referrer they concern.
Why it matters here A delayed report generates calls, and the person answering should be able to see the cause.
In practice A transport delay recorded against the route, visible to whoever answers the referrer’s call.
Work in motion
These already happen. Recorded as transitions, they turn a turnaround average into a fixable list.
The gap between collection and accessioning is where most unexplained turnaround time sits.
The verification queue is a single-person constraint in most labs and is rarely measured.
Attribution is what turns a recurring rejection cause into a training or process fix.
Ordering against forecast load rather than against a shelf check is what prevents a stopped morning.
A stability breach discovered at the lab is a recollection; discovered on the route it is a redirection.
A referrer usually leaves for a service reason the lab could have seen in its own records.
Verity AI
Verity AI reads the same sample, stock and referrer records the lab creates as it operates. It answers from your own lab, respects permissions, and can turn an answer into work assigned to a centre or a shift.
Verity / Ask
Verity AI only returns what the person asking has permission to see. It does not interpret results.
Without chasing
Each runs from the sample and stock records at the point the condition is met.
When
A sample approaches its turnaround target
When
A sample is rejected
When
Reagent stock falls below forecast requirement
When
Verification queue exceeds threshold
When
A collection route runs late
When
A referrer’s volume falls below their pattern
What you can understand
Turnaround decomposed and demand attributed, from the lab’s own transitions.
Verity records the operational lifecycle. Analysers, result generation and clinical interpretation remain with your existing systems and staff.
One system, different ways of seeing it
Everyone works from the same records, and each role opens on what they need.
Lab director
Where are we losing turnaround and demand?
Turnaround by stage and centre, rejection rates, referrer volume trends, reagent cost and expiry.
Lab manager
What is stuck right now?
Samples past target, verification queue, reagent shortfalls, routes running late.
Pathologist
What needs verification?
Results queued by urgency and age, critical values to escalate, amendments pending.
Collection supervisor
How are the centres and routes performing?
Rejection rates by centre and phlebotomist, route timing, collection volumes, recollections raised.
Accounts and relationships
Which referrers are we losing?
Referral volume trends, service experience by referrer, outstanding balances, contact history.
Where it is used
Timestamps at every transition, so an average becomes transit, accessioning, processing and verification — each separately fixable.
Rejections recorded with reason, centre and phlebotomist, turning recurring recollections into an addressable cause.
Stock checked against forecast test volume and supplier lead time rather than against a shelf, so a shortage does not stop a morning.
Verification as a workflow step with an owner and an age, exposing the single-person constraint most labs have.
Routes as transit locations tracked against collection times and stability windows, so a late route is redirected rather than recollected.
Referral volume and service experience per referring doctor, so a decline is discussed rather than discovered a quarter late.
Reagent batches with expiry and storage location, so expiring stock is used or replaced rather than discarded.
Plain-language questions across samples, stages, stock and referrers, with follow-ups assigned in the same step.
Getting there
Your analysers, result generation and reporting systems continue to run and are mapped during implementation. Collection centres, routes, referrers, reagent stock and open samples are brought across, and Verity is introduced as the operational layer around them.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
No. Analysers, result generation and clinical reporting continue in your existing systems and are mapped during implementation. Verity records the operational lifecycle around them — collection, transit, accessioning, queues, reagents, rejections, referrers and turnaround.
Verity AI answers questions from your own sample, stock and referrer records: where turnaround is being lost by stage and centre, which urgent samples are past target, which collection points have the highest rejection rates and why, which reagents fall short against tomorrow’s load. Each answer can become work assigned to a centre or shift.
Every transition carries a timestamp and a location, so a turnaround average decomposes into transit, accessioning, processing and verification. The delay is usually not in the analytical step, which is why an average alone never fixes it.
Rejections are recorded with their reason, collection point and phlebotomist, so recurring causes become attributable and addressable rather than absorbed as recollections.
Reagents are held with batch, expiry, storage location and supplier, and requirements are calculated against forecast test volume and supplier lead time — so a shortage is ordered against rather than discovered when the run is due.
Routes are treated as transit locations with collection times recorded, so a route running late against stability windows is flagged while samples can still be redirected rather than recollected.
Referrers are records with their referral volume, test mix and service experience, so a doctor whose volume has halved surfaces while the reason can still be discussed.
Verity has one permission model and one audit trail, and result release and amendment are recorded steps with the person, time and reason attached.
About four weeks: discovery and mapping of the sample lifecycle, configuration of stages and targets, migration of centres, referrers and stock, then an ongoing operations partnership.
In most labs it is transit and accessioning rather than processing, and almost nobody can prove it. Tell us how the lifecycle is tracked today.