Solution

Medical IoT & integrations

Your analyzers and devices, talking to your system.

We connect laboratory analyzers, monitoring devices and third-party systems to Codon or to the software you already run, over the standards the devices actually speak.

Analyzers & IoT biochemistryhaematologymicrobiologymonitoring devices CODON INTEGRATION LAYER ASTM / HL7 parsercode mappingvalidation, referenceranges by age and sexaudit log · GDPR LIS sample registrationbiochemistrymicrobiologyverification bythe biochemist HIS · Clinic patient filedoctor seesthe resultappointmentswards, radiology Patient PDF reportSMS / e-mailinvoicefiscal receiptinsurer ASTM · HL7 v2MQTT · API results in 3 s verified result report · receipt orders worklist Green: data moving automatically, without retyping. Dashed: orders and worklists in the opposite direction.

What the studies show

The problem is not only paper. It is every step where a result is copied, identified or verified by hand.

≈70% of medical decisions are influenced by laboratory tests CDC, Laboratory Week
≈10% error rate in laboratory results entered by hand (8.8–10.2%) Black et al., Anaesthesia 2004; Mays et al., JAMIA 2019
60–70% of laboratory errors happen before the analysis itself Wilton & Pennisi 1994; Nordin et al. 2024
−54.5% laboratory turnaround time (TAT) after digitalising the workflow Mekhjian et al. 2002

Figures from international studies, not direct measurements of Codon. For Codon they translate into barcodes, patient identification, device integration and sample tracking.

The problem

Most laboratories still have someone reading a value from the analyzer screen and typing it into a form. Every retyped result is a delay and a possible error, and nobody can prove afterwards what the analyzer actually said.

How we work

  1. 1

    Inventory of every device: model, interface (serial, TCP/IP, USB), protocol version and the messages it emits.

  2. 2

    Integration layer that parses ASTM E1381/E1394 and HL7 v2.x, maps test codes to your catalogue and validates before anything is stored.

  3. 3

    Bidirectional where the device supports it: worklists and orders go to the analyzer, results come back with flags.

  4. 4

    Devices without a standard interface are bridged with MQTT or a small gateway service.

  5. 5

    Acceptance test on site with real samples, side by side with the old process, before switching over.

Request a demo

Talk to an engineer

A 30-minute demo with a Pyramid engineer: your workflow, your analyzers, your questions. No slides.

+383 44 830 909 · [email protected] · Prishtinë, Republic of Kosovo