Lab analyzer integration, without a per-instrument bill
A blood count is twenty numbers. Read off the analyzer’s screen and typed into software, every day, by someone who is also doing three other things. Analyzer integration removes that step — and it is the single change that does most for a laboratory’s accuracy and its turnaround time.
- Network, serial cable or file export — if it has a data port, we connect it
- Scanners too, over DICOM: worklist out, images back
- Keeps collecting results when your internet is down
- No per-instrument fee, no interface licence from us
What analyzer integration actually is
Analyzer integration — LIS interfacing, as vendors usually call it — is the link between the machine that measures and the software that reports. Without it a technician reads a result off one screen and types it into another. With it, the measurement travels from the instrument to the patient’s record on its own. The argument for it is not speed. It is that a transcription step is a place where a decimal point can move, and a laboratory running two hundred samples a day is making thousands of small opportunities for that every week.
How it is set up
One program, installed once. Not a server, not a rack, nothing that needs an IT person on staff.
- 1
Download
A small Windows program from your Uyirly settings page. It installs on the computer that already sits next to your machines.
- 2
Pair
Read out one eight-character code from the screen. That is the entire configuration — the program now knows which hospital it belongs to.
- 3
Point the machine at it
Give your analyzer engineer the address the program shows. For a scanner, give them an AE title instead.
- 4
Nothing else
There is no per-instrument setup. A machine announces what it is when it first speaks, and Uyirly recognises it and lists it.
Why the program runs in your laboratory
It would be simpler for us to do this in the cloud. We do not, for one reason: an analyzer transmits a result once and then forgets it. If nothing is listening at that exact moment, the measurement is gone and the sample has to be run again. So every result is written to your own computer the instant it arrives — before any attempt to send it anywhere — and uploaded when the connection returns. A broadband cut costs you the delay and nothing else. For a hospital in a town where the line goes down for an afternoon, this is the difference between integration being a convenience and being a liability.
A machine can produce a result. It cannot release one.
Every analyzer result lands unverified and waits for a person in the laboratory to authorise it, and the report names who did. That is NABL 112’s requirement, and it is the line between automation and unattended reporting. Correct a value afterwards and the authorisation is withdrawn by itself — a result that has changed has not been checked by anybody yet. If a corrected value was critical and the clinician had not yet been telephoned, the entry in the critical value register is withdrawn too, with the reason kept.
Which machines can be connected
If the instrument has a data port — a network socket, a serial cable or a file export — we will connect it. That covers most of what Indian laboratories run, including Mindray and Transasia/Erba. Scanners connect over DICOM, so the console pulls the day’s worklist and sends studies back matched to the right patient. What we cannot connect is an analyzer whose only output is its own built-in printer, and we would rather say so before you buy than after. Send us the model and we will tell you.
| How the machine talks | Typical instruments | Supported |
|---|---|---|
| ASTM over network | Mindray BC-5130 and similar haematology | Yes |
| ASTM over serial (RS-232) | Mindray BC-20s, Transasia/Erba H360 | Yes |
| File export to a folder | Many semi-automatic biochemistry analyzers | Yes |
| DICOM | Ultrasound, X-ray, CT consoles | Yes — worklist and images |
| Built-in printer only | Some entry-level semi-auto analyzers | No — cannot be connected by anyone |
| Orders sent back to the machine | Two-way / bidirectional interfacing | Not yet — on our roadmap |
What it costs
Nothing beyond the Growth plan. There is no per-instrument fee, no interface licence and no commissioning charge from us, however many machines you connect. One caution that has nothing to do with us: some analyzer manufacturers charge separately for the data-output module on their own instrument, and it is easier to negotiate that while you are still buying the machine than afterwards. Ask the vendor before you sign.
Frequently asked questions
Do you charge per analyzer?
No. Connection is included in the Growth plan with no per-instrument fee and no interface licence, however many machines you connect.
Will it work if our internet goes down?
Yes. The program runs on a computer in your laboratory and writes every result to that computer before trying to send it, so results keep being collected through an outage and upload when the line returns.
Does Uyirly support HL7?
Not today. The connector speaks ASTM for analyzers and DICOM for imaging. If your instrument only speaks HL7, tell us the model and we will say honestly whether we can connect it.
Can Uyirly send orders to the analyzer as well?
Not yet. Results travel from the machine to Uyirly; sending the test list back down to the instrument is on our roadmap and we will not claim it until it is built.
Do we need a server in the hospital?
No. It is one small program on an ordinary Windows PC — the one already sitting next to your machines is fine. It runs as a service, so it starts before anyone logs in and survives a power cut.
What about our scanner?
The same program handles DICOM. Your ultrasound or X-ray console pulls the day’s worklist from Uyirly, so the radiographer picks the patient instead of typing the name, and studies come back attached to the right person.
See it in your own hospital
Uyirly runs OPD, IPD, pharmacy, lab, billing and staff scheduling in one platform. 30-day free trial, no credit card.
Start free trial