-
Notifications
You must be signed in to change notification settings - Fork 134
LIMS Admin Analyzer Automation
Analyzer automation connects specific investigation items (parameters) to a laboratory analyzer so that results arrive in the LIMS automatically — without manual data entry by the MLT. This article explains how to map a report item to an analyzer and configure the test code that the analyzer uses to identify each test.
Before mapping automation:
- The analyzer must be registered in the system as a Machine. See Machine Setup.
- The investigation and its items must already be configured. See Managing Investigations and Investigation Items & Parameters.
- The middleware must be installed and connected to the analyzer. See Analyzer Middleware.
When a sample is accepted at the lab and placed on the analyzer:
- The middleware queries the LIMS for pending test orders for that sample barcode.
- The LIMS returns the list of test codes for that sample.
- The analyzer runs the tests and sends the results back to the middleware.
- The middleware matches each result to its investigation item using the test code mapping.
- The result is written into the patient's report automatically.
The accuracy of step 4 depends entirely on the test code configured in the LIMS matching the test code used by the analyzer.
- Go to Menu > Admin > LIMS > Investigations.
- Open the investigation, then open the specific item (parameter) you want to automate.
- In the Data Entry Method field, select Automated.
- In the Machine field, select the analyzer that produces this result (e.g., "Sysmex XS-500i — Haematology").
- Save the item.
Repeat for each parameter that the analyzer reports.
The test code is the identifier that the analyzer and middleware use to match a result to an investigation item. Every analyzer uses its own test code scheme.
- Open the investigation item (or the corresponding report item in the report format).
- Locate the Analyzer Test Code field (also called the Machine Code or Short Code).
- Enter the test code exactly as it appears in the analyzer's documentation (case-sensitive in most cases).
Examples of test codes by analyzer:
| Analyzer | Parameter | Typical test code |
|---|---|---|
| Sysmex XS Series | WBC | WBC |
| Sysmex XS Series | Haemoglobin | HGB |
| Dimension Clinical Chemistry | Glucose | GLU |
| Dimension Clinical Chemistry | Creatinine | CREA |
| Maglumi X3 HL7 | TSH | TSH |
| BioRad D10 | HbA1c | A1C |
Consult the analyzer's integration manual or the middleware vendor's documentation for the correct codes.
If an investigation can be run on more than one analyzer (e.g., a backup instrument), each item can only be linked to one primary machine. For backup scenarios, the middleware handles routing; consult the middleware configuration documentation.
After configuring:
- Run a test sample on the analyzer.
- Check the patient's report in the LIMS — automated results should appear in the value fields without manual entry.
- If results do not arrive, check:
- The middleware is running and connected (see Analyzer Middleware).
- The test code in the LIMS matches the code in the analyzer's output message.
- The sample barcode was scanned correctly by the analyzer.
Some investigations have a mix of automated and manual parameters. For example, a Full Blood Count may have WBC, RBC, HGB, HCT, MCV, MCH, MCHC, PLT automated via the Sysmex, but the differential morphology comment entered manually by the MLT.
Set Data Entry Method = Automated only for the parameters the analyzer reports. Leave the manual parameters set to Manual — the MLT will enter those after the automated results arrive.