Normal results released by the lab’s own validated rules; criticals, delta failures and QC lockouts always wait for the pathologist.
Installs with LabBridge, whose screen it works onThe lab writes its release rules per test, with a lab default for the rest: release a value inside its reference range (or a narrower window per analyte), with no analyser or sample-quality flag, an accepted QC run on the analyte recently enough, and — if the lab says so — only for a patient who has had the test before. Four holds no rule can switch off: a critical value, a DeltaCheck failure, a QC lockout and a value with no reference range. Everything held waits in the pathologist’s queue with the reason in plain words, criticals first and then by turnaround time, for a one-tap verify and sign; routine holds can be signed together, the four hard holds only one by one. A new rule set starts in shadow mode, deciding without releasing, and the screen shows how often it agreed with the pathologist and how many results it would have released that the pathologist then changed — that number must be 0 before going live. Released results are signed in the duty pathologist’s name, and every release keeps the rule version and the inputs it was judged on. A version that has released anything is never edited: a change becomes the next version. Every critical value opens a call-back: who to call and their number, each attempt logged, closed only when someone reads the value back, and escalated when nobody is reached in time.
What it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.