Test turnaround
Test turnaround analytics in EDFlow: order-to-result and collection-to-result times per test, hour-by-weekday heatmaps, bucket coverage, the estimate level patients get, and the benchmark job.
The table
Each test type: volume, order-to-result p50, p75 and p90, collection-to-result p50, the share over the catalogue default, and n. Priority classes (stat, routine) are separate.
One test
Select a test to see:
- its hour × weekday heatmap of p50;
- bucket coverage: samples per weekday-hour bucket, with buckets under the minimum highlighted;
- the level patients get per bucket (same weekday and hour; hour ± 1; weekday or weekend; any day at that hour; any time; the catalogue default);
- the catalogue default next to the observed values;
- the benchmark job's last run, next run and duration.
What's excluded from samples
Cancelled and recollected orders, timed collections (kept separately), intervals spanning a closed service or recorded downtime, training and demo visits, dates inside "exclude from benchmarks" annotations, and values above the cap.
When the numbers look wrong
- A test far over its default may be mapped to the wrong code: check Unmapped codes and the catalogue.
- An imaging modality with long times at night may need service hours configured, so patients see when it opens instead of an estimate.
Related
Dernière mise à jour le
Cette page vous a-t-elle été utile?
Flow and bottlenecks
Find where ED time is lost with EDFlow: flow segments from arrival to departure, the per-visit bottleneck flag, the period bottleneck ranking by excess minutes, heatmaps, trends and capacity drivers.
Request analytics
Request analytics in EDFlow: volume by type, zone and hour, time to first response and to resolve, urgent in-person response, service-level compliance, escalations and alerts per nurse per hour.