Skip to main content
Nothing an instrument sends enters a report on its own. Results arrive in a review queue, a scientist accepts each one, and accepting runs exactly the same path as typing the result in by hand. The screen’s own subtitle says it: “Register each analyzer (or its bridge PC) with a private key. Incoming results queue below for review — nothing enters a report until a scientist accepts it.”

​
What you’re looking at

Two stacked sections, doing two different jobs. Each queued payload shows Received, Analyzer, Specimen / LAN, Matched, Values and a Review column holding the two actions. Matched means the payload has been tied to an order on your worklist; Unmatched means it has not, and Accept is disabled on that row. The heading always carries its count, so Results awaiting review (0) is the normal state of a lab that is on top of its queue. The empty state. Before you register anything the table reads No analyzers registered yet. With nothing queued, the review section reads Nothing waiting — new analyzer payloads appear here. Below Professional Lab the whole page is a locked card.

​
Register an analyser

1

Open the dialog

Select Register analyzer. It explains what is about to happen: “A private key is generated for the analyzer’s bridge — it authenticates every result it posts.”
2

Name the instrument

Enter a Name the bench will recognise (for example Chemistry bench analyzer) and, optionally, the Model (for example Mindray BS-240). Select Register.
3

Copy the key immediately

The Bridge key for {name} dialog appears with the key in a read-only field, and tells you where it goes: “Configure this key on the analyzer’s bridge PC as the X-Analyzer-Key header. For security it is shown once — generate a new key if it is lost (the old one stops working).” Select the copy button — the toast reads Key copied — then paste it into the bridge’s configuration before you close the dialog with Done.
The bridge key is shown once, at registration or rotation, and is never shown again. If you close the dialog without copying it, the only way forward is New key on that row — which issues a fresh key and stops the old one working, so the bridge goes silent until you reconfigure it.

​
Accept a result

The queue carries the rule underneath its heading: “Accept runs the same screen + finalize path as the manual form. Urine payloads without SVT values must be entered manually.”
1

Read the row

Check the Matched badge first. An Unmatched payload has no order to attach to, and Accept stays disabled on it.
2

Check the values against the specimen

This is the review, and it is the whole reason the queue exists. Compare the reported values and the specimen or accession number on the row with the order you expect them to belong to.
3

Accept or discard

Select Accept — the toast reads Result accepted into screening and the result travels the same screening and finalisation path as a manually entered one. Select Discard for a payload that should not be used at all; the toast reads Payload discarded.

​
Two things the instrument cannot finish for you

  • An unmatched result cannot be accepted. The specimen or accession identifier the instrument sent does not match any order. Correct it at the bench and let the analyser resend, or enter the result manually against the order — see Accession an incoming specimen.
  • A urine payload with no validity values must be typed in. Specimen validity testing is part of the screen, and an instrument that sends only the drug results has not completed it. Use the screening form instead — see Screening and confirmation.

​
Who can do this

Your plan decides whether Analyzers exists and role decides whether it appears at all. Only one act on the screen — accepting a result — is behind a permission. There is no permission for analyser setup. A toggle named Configure analysers and interfaces sat in the Diagnostics catalogue until August 2026 and nothing ever read it, so it was removed rather than left offering a control that did not exist. Registering, pausing, re-keying and discarding are governed by the plan and the route alone. Accepting is different, and it is the one act that is really gated: it writes the reading into the screening path and then signs it out, so it takes Enter results at the bench and Verify and authorise results. Someone on Own bench holds only the first and gets as far as the reading, never the sign-out — verification comes from the access tier, not from a job title, so a Lab Manager who was never given Whole lab or All sites can register an analyser and still not accept a single result from it. A Radiologist does not reach this page at all — their equivalent is Connect your imaging machines. Two behaviours surprise people:
  • Enforcement is opt-in, per person. Somebody never saved in the permissions sheet is unrestricted, and the sheet warns “Saving starts enforcing”.
  • A denied action is recorded; an allowed one is not. A figure you are not permitted to see renders hidden or as a dash, never as a zero.
See Permissions.
Analyser interfacing is still rolling out and what a given instrument needs varies with its make, age and bridge software. Talk to support about your specific bench before you plan a cutover date.

​
Check it worked

  • The analyser appears in the registry as Active, and Last seen changes from never to a timestamp once its first payload arrives.
  • New payloads raise the count in Results awaiting review ({n}).
  • An accepted result appears on the bench workflow exactly as a hand-entered one does — see Enter and verify results.

​
Common issues

You are on Starter Lab. The card reads Analyzer interfacing is a Professional feature — Register your analyzers, receive their results automatically, and accept them into the screening workflow with one click. Included from the Professional Lab plan. See Change your plan.
The bridge is not reaching you. Confirm it is configured with the key you copied at registration, that the analyser is Active rather than Paused, and that nobody has since issued a New key on that row.
Either the row is Unmatched — there is no order to attach it to — or you hold Enter results at the bench but not Verify and authorise results.
The payload has no specimen-validity values, so the screen is incomplete. Enter that result on the screening form instead.
Select New key on that analyser’s row, copy the replacement, and update the bridge. The old key stops working the moment the new one is issued.
Either your role does not reach Lab Station at all, or the interface is not yet enabled for your lab. Analyser integration needs Professional Lab or above, is still rolling out and is priced per interface — contact support.

​
FAQ

Almost always one of two reasons: the row is Unmatched, so there is no order for it to land on, or you do not hold Verify and authorise results. Accepting signs a result out, so it is deliberately not a data-entry permission.
No. Accept runs the same screening and finalisation path as the manual form, so a value that would be flagged if typed in is flagged when accepted. The instrument saves the typing, not the judgement.
They are not taken. Pausing does not queue them for later, so resume the instrument before it sends anything you need to keep.
Register each instrument separately. A key identifies a bridge, so sharing one makes Last seen meaningless and rotating that key silently stops a second instrument you had forgotten about.
The same idea and the same grant, on different hardware. Imaging has its own registry and review queue — see Connect your imaging machines.