ClinicalLive · in the productClinical record

LabBridge

Lab and imaging orders with results into the chart.

Get LabBridge Open the appAvailable nowHow pricing works →

What it is

Orders move ordered → collected → resulted, or cancelled with a reason. Results are typed values flagged against their reference range, written into the chart as laboratory observations, and every resulted order waits for a named person to acknowledge it — worst flags first. The Send-outs tab keeps the referral labs a sample can go to and a register of what went where: sent with its due time fixed, closed when the report comes back, and its values filed as imported, carrying the referral lab’s own range. Each reference lab’s rate card (its price, its own test code and turnaround per test, from a date, loaded from the partner’s CSV) prices and times every send-out, and a test can be routed to its lab with a fallback for when that lab is retired. The day’s samples to one lab go under one manifest, downloaded as the CSV the partner keys from; the partner’s results CSV is read row by row, matched to the samples by accession number, and filed onto their orders only when a person files it — a row that matches nothing says so. The Add-ons tab adds one more test to a sample already in the lab: the bench says how the tube was kept and how much is left, and the server checks the specimen type, the sample’s age against the lab’s own stability window for that storage, and the volume, before the test becomes an order on the same sample. The windows are the lab’s own, set in the test master with their source; a test with none set is never added on. The Body fluids screen puts CSF, pleural, ascitic, synovial and pericardial taps on their own urgent path: logged as they land with how they look, the patient’s biochemistry, cytology and culture orders on the same tap linked so they are read beside the cell count, the count entered by the lab with a differential that adds up to 100, and the tap signed out by a verifier with what they concluded. The lab may set its own receipt-to-count target with its source; no cut-off ships. The Titres tab lines up a patient’s titres (dengue, TORCH, Widal and the rest the lab names) draw over draw from the results already reported, with the ratio between one draw and the one before, so a rising titre and a flat high one read differently. A rise is flagged only against the factor the lab sets with its source; none ships, and it does not run the assay or decide the diagnosis.

Who uses it: Built for: Diagnostics & Labs
Reads: Orders, the chart
Writes: Orders, results, observations, send-outs, reference lab rate cards and routes, manifests, partner results files, body fluid taps and cell counts, add-on requests and their outcome, sample stability windows, which analytes are titres, and the lab’s rise factor with its source
Never: A result never leaves the queue by silence — acknowledgement is a recorded user, not a boolean, and a resulted test cannot be cancelled or edited into a different fact.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Orders and results stay in the chart.

In the product

Who uses it: Lab technician — the demo profile it is best tried as
Where it opens: Clinical › Lab orders /labs
Permission: lab.read

Every clinical app in the handbook →

How it works

Describe your tests onceThe test master holds specimen, method, turnaround and reference ranges, each range with the source you took it from. It also lists the tests your own order history used that nobody has described yet.
Order against the masterPick the patient and the test. Free text still works for the one the master has not learned.
Collect, result, acknowledgeMove the order to collected, then type the values. Anything outside its range is flagged as you save and written into the chart. Every resulted order waits for a named person, worst flags first; silence does not clear it.
Sign the reportThe impression and the signature turn a set of values into a report you can print and send.
Line up titres draw over drawOn Titres, name which analytes are titres. A patient’s dengue, TORCH or Widal results then line up against their own earlier draws with the ratio between them. A rise is flagged only against the factor your lab sets, with its source; none ships.

Rules it keeps

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

A result never leaves the queue by silence — acknowledgement is a recorded user, not a boolean, and a resulted test cannot be cancelled or edited into a different fact.

AI in LabBridge

AskQuestions about what is on screen — “What needs attention in LabBridge 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

LabBridge — Labs — Order lab tests and get results into the chart — 01Labs — Order lab tests and get results into the chartCaptured from the running demo clinic

01Labs — Order lab tests and get results into the chartCaptured 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 · 10

AutoVerify BillDesk HomeDraw LabLink MicroBench OrderPad Patient Registry RadioReport ReflexLab TATLens

Hands to · 50

ABDMLink AnemiaTrack Automations AutoVerify BenchLink CarePlans ChargeGuard ClaimsLine CommandView ConsultScribe DeltaCheck DengueWatch DiabetesYear LabNetwork DietClinic DischargeLine EQASTrack FHIRBridge HemoLog HomeDraw HubRoute IHCTrack ImageVault Insightsand 26 more

See the whole clinic →

Questions clinics ask

What does LabBridge do?

Lab and imaging orders with results into the chart. Orders move ordered → collected → resulted, or cancelled with a reason. Results are typed values flagged against their reference range, written into the chart as laboratory observations, and every resulted order waits for a named person to acknowledge it — worst flags first. The Send-outs tab keeps the referral labs a sample can go to and a register of what went where: sent with its due time fixed, closed when the report comes back, and its values filed as imported, carrying the referral lab’s own range. Each reference lab’s rate card (its price, its own test code and turnaround per test, from a date, loaded from the partner’s CSV) prices and times every send-out, and a test can be routed to its lab with a fallback for when that lab is retired. The day’s samples to one lab go under one manifest, downloaded as the CSV the partner keys from; the partner’s results CSV is read row by row, matched to the samples by accession number, and filed onto their orders only when a person files it — a row that matches nothing says so. The Add-ons tab adds one more test to a sample already in the lab: the bench says how the tube was kept and how much is left, and the server checks the specimen type, the sample’s age against the lab’s own stability window for that storage, and the volume, before the test becomes an order on the same sample. The windows are the lab’s own, set in the test master with their source; a test with none set is never added on. The Body fluids screen puts CSF, pleural, ascitic, synovial and pericardial taps on their own urgent path: logged as they land with how they look, the patient’s biochemistry, cytology and culture orders on the same tap linked so they are read beside the cell count, the count entered by the lab with a differential that adds up to 100, and the tap signed out by a verifier with what they concluded. The lab may set its own receipt-to-count target with its source; no cut-off ships. The Titres tab lines up a patient’s titres (dengue, TORCH, Widal and the rest the lab names) draw over draw from the results already reported, with the ratio between one draw and the one before, so a rising titre and a flat high one read differently. A rise is flagged only against the factor the lab sets with its source; none ships, and it does not run the assay or decide the diagnosis.

What data does LabBridge read and write?

LabBridge reads orders, the chart and writes orders, results, observations, send-outs, reference lab rate cards and routes, manifests, partner results files, body fluid taps and cell counts, add-on requests and their outcome, sample stability windows, which analytes are titres, and the lab’s rise factor with its source. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does LabBridge deliberately not do?

A result never leaves the queue by silence — acknowledgement is a recorded user, not a boolean, and a resulted test cannot be cancelled or edited into a different fact.

What happens to our data if we uninstall LabBridge?

Orders and results stay in the chart.

Is LabBridge available today?

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

Want to see LabBridge 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 Clinical

All 225 →

Featured inDiagnostics Centre stack Diagnostics & Labs