OperationsLive · in the productQueue & board

DeviceLink

Bedside and point-of-care device readings onto the chart — unverified until a clinician confirms them.

Get DeviceLink Open the appAvailable nowHow pricing works →

What it is

A connector for the bedside and point-of-care devices a hospital already owns — monitors, pulse oximeters, glucometers, point-of-care analysers — that send HL7 v2 result messages (ORU^R01). The BenchLink edge agent on the hospital’s network carries each message, in device mode, under an integration key that can do nothing else; the platform keeps it once (by the device and its message control id) and reads it with that model’s own field map, written from the device’s interface specification. Every reading lands unverified and reaches the chart only when a clinician confirms it — or rejects it with the reason (probe off, patient moving); a reading in a unit the map does not expect, or not final, says so. The patient is the one the message names by MRN, or the one a nurse has put the device on; when neither can be told the reading is held, never attached to the nearest plausible record. No device is supported out of the box: a model is supported only once a message recorded from that model is kept as its fixture and parses into readings, and a device can be switched on only then.

Who uses it: Built for: Every specialty
Reads: Device HL7 v2 messages through the BenchLink agent
Writes: Device readings, confirmed observations on the chart, recorded device fixtures
Never: It does not claim any device works before a message recorded from that model has been kept and parsed, it does not put an unconfirmed reading on the chart, and it does not set alarms or replace the device’s own monitoring.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Readings, fixtures and the message log are kept; confirmed readings stay on the chart.

In the product

Who uses it: Operations manager — the demo profile it is best tried as
Where it opens: Clinical › Device readings /device-readings
Permission: devicelink.read

Every operations app in the handbook →

How it works

Register the modelWith the field map from its interface spec.
Keep a recorded messageIt must parse into readings before the model is supported.
Run the agentBenchLink in device mode, with a devicelink.post key.
Confirm at the bedsideEach reading reaches the chart only when a clinician confirms it.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not claim any device works before a message recorded from that model has been kept and parsed, it does not put an unconfirmed reading on the chart, and it does not set alarms or replace the device’s own monitoring.

AI in DeviceLink

AskQuestions about what is on screen — “What needs attention in DeviceLink today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

DeviceLink — Device readings — Bring bedside device readings to the chart, each confirmed by a clinician — 01Device readings — Bring bedside device readings to the chart, each confirmed by a clinicianCaptured from the running demo clinic

01Device readings — Bring bedside device readings to the chart, each confirmed by a clinicianCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 1

Patient Registry

See the whole clinic →

Questions clinics ask

What does DeviceLink do?

Bedside and point-of-care device readings onto the chart — unverified until a clinician confirms them. A connector for the bedside and point-of-care devices a hospital already owns — monitors, pulse oximeters, glucometers, point-of-care analysers — that send HL7 v2 result messages (ORU^R01). The BenchLink edge agent on the hospital’s network carries each message, in device mode, under an integration key that can do nothing else; the platform keeps it once (by the device and its message control id) and reads it with that model’s own field map, written from the device’s interface specification. Every reading lands unverified and reaches the chart only when a clinician confirms it — or rejects it with the reason (probe off, patient moving); a reading in a unit the map does not expect, or not final, says so. The patient is the one the message names by MRN, or the one a nurse has put the device on; when neither can be told the reading is held, never attached to the nearest plausible record. No device is supported out of the box: a model is supported only once a message recorded from that model is kept as its fixture and parses into readings, and a device can be switched on only then.

What data does DeviceLink read and write?

DeviceLink reads device HL7 v2 messages through the BenchLink agent and writes device readings, confirmed observations on the chart, recorded device fixtures. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does DeviceLink deliberately not do?

What happens to our data if we uninstall DeviceLink?

Readings, fixtures and the message log are kept; confirmed readings stay on the chart.

Is DeviceLink available today?

Yes — DeviceLink is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see DeviceLink running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 97 →