Drivers and integration for your equipment.
A connected device is only useful once its data arrives, structured and on time, in the system that needs it. We build the driver that understands the device, the output systems can use and the route that gets it there.
Vendor neutral. One library of drivers to choose from.
Data Scripting is independent of any equipment manufacturer. The library covers the device classes found across critical care, theatres, laboratories and production. Every driver is developed and tested against the real equipment before release.
Drivers run on the gateway, so the device is understood at the point of capture.
Choose from the library, or ask us to add a device (how compatibility works).
- Ventilators and anaesthesia workstations
- Patient monitors and haemodynamic monitoring
- Dialysis, infusion and renal replacement equipment
- Laboratory analysers and point-of-care instruments
- Industrial PLCs, controllers and instruments over RS232, RS422 and RS485
From a raw stream to a record a system can use.
Drivers turn the device's own protocol into structured, time-stamped records, output in multiple formats to suit any receiving system your organisation approves.
Capture
The gateway reads the device over an isolated serial or USB interface, exactly as the equipment produces it.
Structure
The driver parses the protocol into clean fields, units and timestamps. Anything unexpected is marked as unparsed, never guessed.
Hold
If the onward connection drops, captured records stay on the gateway, up to 7 days on DSECURE with one connected device and less with more, and up to 48 hours on DS NANO, and are sent when it returns. Records held in memory are lost if power is removed. Readings from disconnected equipment cannot be captured.
Deliver
The gateway sends records onward to the EPR, integration engine or operational system in the format it expects.
Into the systems you already run.
Clinical deployments connect to the site's integration engine and EPR. DSECURE and DS NANO can output in multiple formats to any receiving system your organisation approves. Clinical integration is delivered through our partners.
Industrial and facilities deployments connect to historians, MES, LIMS and building systems.
Patient data goes directly to the approved receiving system and is kept away from DS Atlas and DS-Nexus by design. Those show gateway status, not patient data.
Records leave only for approved receiving systems.
Over an encrypted link, on a route agreed and documented before the first record moves.
Is your equipment already supported?
Send us the manufacturer, model, the interface it offers and where the data needs to go. We will tell you which of these applies.
Already in the library
A driver and cable exist for the device. We configure them for your site and receiving system, and the work is part of deployment.
New integration
We build and test a driver and cable against the real device, scoped and quoted as integration work. The new driver then joins the library and reaches existing customers through the normal update route.
How a project runs
Each integration is surveyed, built against the real device, proven on a first site and released through DS-Nexus as a signed update, with the delivery route agreed in writing.