Exists
Lab has the result
Clear Range
The laboratory has the result. The investigator does not.
The investigator misses the receipt interval even though the result already exists.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
A laboratory has finished a result. The investigator who must act does not have it yet. The reporting hop between them is manual.
The result exists at the laboratory. It is absent from the investigator’s record.
The delay can mean the result is stuck on a slow path, the assay is still running, or an authorization is missing. Only one of those is fixed by changing how the result moves.
Speeding the assay, or chasing an authorization, should not count unless the result itself is what is late.
Lab has the result
Gap
Investigator does not
At risk. The interval closes
V8Y must distinguish a finished result on a slow reporting hop from an assay that is still running and from a missing authorization.
The investigator misses the receipt interval if the hop stays manual.
Not recovery
Success is not a faster assay.
Recovery
Success is that the investigator’s record holds the result inside the required time.
Observed results
No executed results are published for this thread.
These are the conditions the evaluation would test. They are not reported results.
Grounded in CDC reporting on Florida laboratory notifications, which showed multi-day delays when results moved by slow, non-electronic paths. This demonstration covers that reporting hop, not reagent shortages or courier time.
CDC. MMWR on Florida electronic laboratory reporting timeliness.
Same symptom. Different cause.
The field has not acted yet
The GateCompare with The Gate. Authority and a slow result are not the same wait.
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.