Book a Demo

Every device, connected and talking

Analysers on the bench, monitors and ventilators at the bedside, the fridge and the generator that keep them running. Whatever the machine already speaks, its readings reach the record without anyone retyping them, and keep arriving when the network does not.

5,000+
devices connected
50+
models supported
0
readings retyped
Automation
Mulago Hospital · WS-LAB-01
Devices
Sysmex XN-550
sysmex-xn-series v2.1
Connected2 today
Cobas C311
cobas-c311-serial v1.4
Connected8 today
GeneXpert IV
genexpert v3.0
Disconnected1h ago
Mindray DC-70 Pro
mindray-dicom v2.0
Connected5 studies today
Applications
Mulago LIMS
MedX LIMS
14 pushed
National DHIS2
DHIS2
12h ago
Abbott
Roche
Siemens Healthineers
Sysmex
Beckman Coulter
bioMérieux
Cepheid
BD
Bio-Rad
Mindray
Nihon Kohden
Erba
Abbott
Roche
Siemens Healthineers
Sysmex
Beckman Coulter
bioMérieux
Cepheid
BD
Bio-Rad
Mindray
Nihon Kohden
Erba
Human
Dymind
77 Elektronika
Snibe
Vital Scientific
icubio
Infopia
Immucor
Miralab
Zonci
Audicom
Bifour
Human
Dymind
77 Elektronika
Snibe
Vital Scientific
icubio
Infopia
Immucor
Miralab
Zonci
Audicom
Bifour

The problem

The numbers are already there. Someone types them again.

Almost every machine in a hospital produces a perfectly good reading and then hands it to a person with a pen. The analyser prints it and a technologist retypes it into the lab system. The monitor at the bedside shows it and a nurse copies it onto an observation chart every hour. That is where the day goes, and where the errors come from, a transposed digit on a viral load, a reading filed against the wrong patient, a machine that has been down since Tuesday and nobody upstream knows.

Results retyped by hand, once per system that needs them
ICU monitor, ventilator and pump readings charted on paper hourly
Transcription errors that only surface when a clinician queries them
No single view of which devices are actually running

Both directions

Results out, orders in.

The connection runs both ways. Finished results leave the analyser for wherever they are needed, and the next test order arrives at the bench without anyone retyping it.

  • Serial, HL7 v2, ASTM, file drop, or a modern API: whatever the analyser already speaks
  • Orders arrive from the lab system and clear themselves when the run completes
  • No middleware box to buy, license, or maintain
Leaving the bench
142 today
Released results
Run records
Quality control checks
Arriving at the bench
38 today
New test orders
Repeat requests
Patient details
No transcription, in either direction
The bench and the patient record stay in step on their own.

One result, many destinations

Enter it once. It arrives everywhere.

A finished result is usually needed by the lab system, the patient's record, and the national programme at the same time. Each destination is tracked on its own, so one system being down never holds up the others, and never quietly loses a result.

  • Every delivery tracked separately, with its own retries
  • A failed hand-off is visible rather than silently missing
  • Nothing is marked done until the receiving system confirms it
Released 09:14 · Central Laboratory3 destinations
Lab system
result filed against the order
Delivered
Patient record
visible to the treating clinician
Delivered
National programme
counted in this month's return
Sending
Enter a result once. It arrives everywhere it is needed.

When the network goes

The bench keeps working.

Connectivity in a district hospital is not a given. Results are held on site through an outage and sent the moment the line returns, so an unreliable link never becomes an unreliable record.

  • Work carries on while the connection is down
  • Everything held on site goes out automatically on reconnect
  • Reconciled and accounted for, not just resent
  • No usable line at all? The kit brings a managed connection of its own
Bench kept running throughout Nothing lost
09:13connection dropped · results held on site
09:14connection back
09:14sending the 12 results that were waiting
09:15all 12 accounted for
Beside the analyserIn your server roomOr in the cloud

When there is no line

Some sites have nothing to reconnect to.

Holding results through an outage assumes the outage ends. Where a facility has no usable connection at all, the Hardware Kit brings a managed one of its own, with the data included, so the reporting never waited on the facility's internet in the first place.

See the Hardware Kit

Works with what you own

Devices in, systems out.

A wide range of manufacturers and models, with new integrations added regularly. If a device is not on the list, it is usually a matter of days.

Diagnostics

Analysers and point of care

Haematology, chemistry, molecular, immunoassay and rapid tests. Results are verified in the lab system and released signed, the way a result is meant to leave a laboratory.

Clinical devices

Monitoring and imaging

Patient monitors, ventilators, infusion and syringe pumps, fetal monitors, incubators and ultrasound, writing to the patient's record directly. Nothing charted by hand on the hour.

Environment and power

Cold chain, oxygen, supply

Fridges, oxygen concentrators, autoclaves, the generator and the UPS, reporting through low-cost sensors so a failure is an alert rather than a discovery.

Analysers in the field todayCepheid GeneXpertRoche COBAS c311Abbott ArchitectAbbott Afinion 2bioMérieux VITEK 2Sysmex XN SeriesBeckman Coulter DxHMindray BC-10Mindray BC-30sMindray BC-3000 PlusNihon Kohden CelltacWerfen Echo LumenaHuman HumaCountHuman HumaStarSeamaty SD1Hemax Series
Routes results toALISOpenMRSDHIS2MedX LIMSFHIR serversSQL databases

How it works

Three steps, and nobody retypes anything.

STEP 1

Connect the device

It finds the machines already on the network and speaks whatever each one speaks. No rewiring, and nothing to replace.

STEP 2

Check the reading

Every reading is validated and put in a common shape as it arrives, so a bad run is caught where it happened rather than downstream.

STEP 3

Send it onward

It goes to the lab system, the patient record and the national programme, each tracked separately until the receiving system confirms it.

Deploy it anywhere

It goes where the instrument is.

On a desktop

Beside the analyser on the bench, on the workstation that is already there. The usual choice for a single lab.

On your server

One deployment covering every instrument in the building, run by your own IT alongside everything else.

At the edge, or in the cloud

A tablet at a field site, or a hosted instance for a network of facilities. Same software, same behaviour.

Free to use

Download it and connect your first device.

MedX Automation is free to download and run, on Windows or Ubuntu. There is no licence to buy and no middleware box to rent.

DownloadView documentation