5 min readTechnicians, reviewers, and lab managers.

Analyzer results

How analyzer results reach their samples by themselves, how to read the analyzer icon on the results sheet, and how to fix results that need attention.

Results go straight to their samples

When an analyzer sends a result through Kashef Connect or Kashef Local, Kashef finds the sample by its barcode and the test by the analyzer's code, and writes the value into that sample's results. Nobody has to accept it first.

The value arrives as an entered result, exactly like a value typed on the results sheet. Kashef checks it against the patient's reference range and sets the High or Low flag. It still goes through your normal review, approval and release; an analyzer never releases a result by itself.

Kashef keeps your work safe:

  • An approved or released result is never changed by an analyzer.
  • A value typed by staff is never overwritten. Kashef keeps it and notes the value the analyzer sent.
  • When the analyzer runs the sample again, its new value replaces its earlier one, and the earlier value stays visible in the result's analyzer details.
  • The same message sent twice is only used once.

The analyzer icon on the results sheet

Values that came from an analyzer have a small analyzer icon beside them on the results sheet and the review screen. Click it to see:

  • the analyzer, its model and the computer it is connected through;
  • when the result was measured and received;
  • the analyzer's code, the value and unit it sent, its flag and its own reference range;
  • the run number, operator and analyzer serial number when the analyzer sends them;
  • the earlier value if the sample was run again;
  • View in analyzer history to open the analyzer's page.

A teal icon means the value is the one the analyzer sent. An amber icon means staff changed the value after the analyzer sent it, or kept their own value instead of the analyzer's. The icon is not printed on the report.

When a result needs attention

Kashef cannot place a result by itself when:

What you see What to do
Match the code to a test The analyzer used a code Kashef does not know yet. Click Match to test and choose the test.
No sample with this barcode Check the barcode on the tube and the sample in Kashef, then click Try again.
Test not ordered for this sample Add the test to the order if it was requested, then click Try again, or dismiss the result.
The analyzer value could not be read Check the analyzer and enter the result by hand if needed.

Open Devices → Analyzers. Analyzers with waiting results show a Needs attention count, and the menu shows the total. Open the analyzer and its Needs attention tab.

Match to test is the fix you will use most. Choose the test (Kashef suggests one from the analyzer model when it can) and click Save and write results. Kashef saves the code for the analyzer, writes every waiting result with that code to its sample, and sends every future result with it straight to its sample.

Use Dismiss only for results that should never reach a sample, such as a test run on a control tube by mistake. Dismissed results stay in the analyzer's history.

Analyzer history

The analyzer's Activity tab lists everything on its line: results received, order requests the analyzer made, worklists Kashef sent, and connection changes. Click a line to see the sample, each result and where it went, and the message exactly as the analyzer sent it. Use Copy to send that message to Kashef support when something looks wrong.

CBC histograms

Some CBC analyzers send the WBC, RBC and PLT histograms with their results. When their codes are matched to the CBC's WBC, RBC or PLT rows, Kashef attaches each curve to that result without changing the measured count, and the curve appears on the worksheet and the printed CBC.

Daily habits

  • Look at Devices → Analyzers after each analyzer run. A Needs attention count usually means a new test was added on the analyzer and its code has not been matched yet.
  • Match codes from Needs attention rather than retyping results. The match is saved once and every later result with that code arrives on its own.
  • When a sample is run again on purpose, check the analyzer icon on the new value and the earlier value shown in its details before approving.
  • Managers: when the same reason keeps coming back, fix the cause, such as a barcode label that prints wrongly or a test missing from the order.

When expected results are missing

  • Open the analyzer's Activity tab. If nothing arrived, the problem is the connection: check that the analyzer shows Online on its page, and for Kashef Connect that the computer is Online on Devices → Kashef Connect. See Connect analyzers with Kashef Connect.
  • If the result arrived but is not on the sample, it is in Needs attention with the reason.
  • If the result is on the sample but with a different value, look at the analyzer icon: staff may have typed a value before the analyzer sent its own.