Immunoassay Analyzer Integration: What Makes It Different

Immunoassay instruments carry a weight routine chemistry usually does not. A thyroid panel, a cardiac marker, a fertility hormone or a tumour marker is frequently the result the clinical decision turns on. That raises the cost of every small reporting error, and immunoassay has more places for one to hide.

The reference range is the hard part

A sodium range is a sodium range. A TSH range depends on age. A beta-hCG range depends on gestational week. Several hormone ranges depend on sex and on phase of cycle. This is where immunoassay reporting most often goes wrong, and the failure is quiet: the number is right, the range beside it is not, and the flag is therefore wrong too.

It is worth being precise about where the fix lives. This is a catalogue problem, not an interface problem — the analyzer sends a number, and what it should be compared against is the laboratory’s decision. But it is where the two meet, because the range has to be selected against the patient in the header at the moment the result is filed.

Three more things that behave differently

Results outside the measuring range

Immunoassay results frequently arrive as "greater than" or "less than" a limit rather than as a number. A system that stores results as numbers only will either drop these or, worse, silently store the limit as though it were the measurement. They have to survive intact from the instrument to the printed report.

Dilutions and repeats

A sample above range comes back diluted, and the reported value is the measured value multiplied out. If the instrument sends both runs, the software has to know which is the reportable one. If the dilution factor is applied on the instrument, it must not be applied again.

Quality control that actually gets looked at

Internal quality control matters everywhere and matters more here, because immunoassay drift is gradual and easy to miss between calibrations. Control results arriving alongside patient results, plotted rather than filed, are what make a shift visible before a patient result is affected. SamLab captures IQC alongside results on the analyzer integration, and the analyzer add-on is available from the Pro plan upward.

What to check before you commit

• Does the system store reference ranges per parameter with age, sex and — where relevant — gestational bands, rather than one range per test?
• Do "greater than" and "less than" results survive to the printed report?
• Is the dilution factor applied once, and is it obvious where?
• Are control results captured and plotted, or only stored?
• Will the vendor confirm your exact analyzer model before you pay, rather than pointing at a brand?

That last point is worth insisting on with any vendor. An instrument can support a protocol on paper and expose it only with an optional interface board. SamLab’s analyzer list lists the families already connected in the field and states plainly that the exact make and model is verified at a demo rather than assumed.