OperationsLive · in the productQueue & board

BenchLink

The analysers send their own results — matched to the order by barcode, or held for a person.

Get BenchLink Open the appAvailable nowHow pricing works →

What it is

A laboratory with its own bench runs five to twenty analysers, and every number they print is read off a screen and typed into a computer by somebody who is also doing three other things. BenchLink takes that job away. A small agent runs beside the instruments, speaks their own serial or network protocol, and posts what they say; the platform matches each result to an order by the barcode on the tube and files it through the ordinary lab path, so the reference range, the flag, the delta check and the acknowledgement queue all work exactly as they did. What it will not do is guess. A barcode nobody printed, a code nobody mapped, a test the order never asked for — each of those waits in a queue with the reason written on it until a person answers it. Quality-control runs go to Quality Control, and a stored result can never name both a patient’s order and a control material — the database itself refuses that row. The mapping between an instrument’s codes and your test master is the part that makes any of this mean something, and it is yours to fill in: nothing is pre-loaded, because a code that means glucose on one machine means something else on the next one along.

Who uses it: Built for: Hospitals
Reads: Lab orders, the test master, quality-control materials
Writes: Analyser registrations, code mappings, received messages, lab results, through LabBridge, quality-control runs
Never: It never attaches a result to a record it cannot prove the result belongs to: an unmatched barcode, an unmapped code, a test the order did not ask for, a value the order already carries and an order whose report has been signed are all held for a person, and the same rules apply again when that person attaches one by hand.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: The registrations, the mapping and the received messages stay with the tenant; the results themselves were LabBridge’s from the moment they were filed.

How it works

Register the analyserIts name, make and model, whether it speaks ASTM or HL7 v2, and whether it is on a serial cable or the network. That gives you the id the edge agent needs.
Map its codes to your testsOpen the instrument’s interface specification, find the code it prints beside each analyte, and pair it with the test in your master. Nothing is pre-filled — the codes differ between two machines from the same maker.
Label the tube at the drawMarking a specimen collected now prints its accession number. That number is the barcode the analyser quotes back, and it is how a result finds its order.
Work the queue, not the keyboardMatched results file themselves. What is left is the queue: each line says why it is waiting, and you attach it to an order or throw it away with a reason and your name on it.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It will finish a panel the analyser reported one test at a time — an analyte nobody has a value for yet has never been read — but it will not change a number that already stands: that is an amendment, and amendments are made by people.

It cannot put a control run on a patient — a stored line may name an order or a control material, never both.

The host query answers with the tests ordered on a barcode and nothing about the patient: no name, no MRN, no date of birth.

It ships with no analyser codes and no unit conversions pre-filled, and it does not talk to the instrument itself — that is the edge agent, which runs in your laboratory and holds no database connection and no keys of ours.

It is the laboratory bench only: bedside monitors, BP monitors, glucometers, scales and every other point-of-care device are VitalStream’s, which is where DeviceHub was folded.

AI in BenchLink

AskQuestions about what is on screen — “What needs attention in BenchLink today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

BenchLink — Analysers — Take results straight off the analysers instead of typing them — 01Analysers — Take results straight off the analysers instead of typing themCaptured from the running demo clinic

01Analysers — Take results straight off the analysers instead of typing themCaptured from the running demo clinic

1 of 1

Connected to

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.

Reads from · 3

LabBridge MachineLog QCBench

See the whole clinic →

Questions clinics ask

What does BenchLink do?

The analysers send their own results — matched to the order by barcode, or held for a person. A laboratory with its own bench runs five to twenty analysers, and every number they print is read off a screen and typed into a computer by somebody who is also doing three other things. BenchLink takes that job away. A small agent runs beside the instruments, speaks their own serial or network protocol, and posts what they say; the platform matches each result to an order by the barcode on the tube and files it through the ordinary lab path, so the reference range, the flag, the delta check and the acknowledgement queue all work exactly as they did. What it will not do is guess. A barcode nobody printed, a code nobody mapped, a test the order never asked for — each of those waits in a queue with the reason written on it until a person answers it. Quality-control runs go to Quality Control, and a stored result can never name both a patient’s order and a control material — the database itself refuses that row. The mapping between an instrument’s codes and your test master is the part that makes any of this mean something, and it is yours to fill in: nothing is pre-loaded, because a code that means glucose on one machine means something else on the next one along.

What data does BenchLink read and write?

BenchLink reads lab orders, the test master, quality-control materials and writes analyser registrations, code mappings, received messages, lab results, through LabBridge, quality-control runs. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does BenchLink deliberately not do?

It never attaches a result to a record it cannot prove the result belongs to: an unmatched barcode, an unmapped code, a test the order did not ask for, a value the order already carries and an order whose report has been signed are all held for a person, and the same rules apply again when that person attaches one by hand. It will finish a panel the analyser reported one test at a time — an analyte nobody has a value for yet has never been read — but it will not change a number that already stands: that is an amendment, and amendments are made by people. It cannot put a control run on a patient — a stored line may name an order or a control material, never both. The host query answers with the tests ordered on a barcode and nothing about the patient: no name, no MRN, no date of birth. It ships with no analyser codes and no unit conversions pre-filled, and it does not talk to the instrument itself — that is the edge agent, which runs in your laboratory and holds no database connection and no keys of ours. It is the laboratory bench only: bedside monitors, BP monitors, glucometers, scales and every other point-of-care device are VitalStream’s, which is where DeviceHub was folded.

What happens to our data if we uninstall BenchLink?

The registrations, the mapping and the received messages stay with the tenant; the results themselves were LabBridge’s from the moment they were filed.

Is BenchLink available today?

Yes — BenchLink is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see BenchLink running on your own patients?

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.

More in Operations

All 145 →

Featured inPathology & Laboratory