Get started
OperationsListed · screen comingQueue & board

DeviceHub

Retired into VitalStream — the bedside half was built there.

Notify meJoin the early-access listHow pricing works →

What it is

Retired into VitalStream, which is already this product’s bedside-device app and now does the three things this page promised: the unit on a reading is the canonical one for its metric and a database CHECK says so, with only exactly-defined conversions applied and mmol/L for glucose refused rather than converted by a factor nobody checked; a device’s clock offset is measured and stored, the device’s own stamp is kept, and the corrected one is what everything sorts by; and the patient on a reading is re-read under the tenant policy with how they were identified recorded beside it. The laboratory bench was never part of this — analysers, their result codes and the barcode that matches a result to an order are BenchLink. Two tiles for the bedside would have been the duplicate this catalog is trying to stop.

Who uses it
Built for: Every specialty
Reads
Device feeds
Writes
Nothing — VitalStream holds the devices and their readings
Never
It does not exist as an app: opening the bedside device registry means opening VitalStream.
Access
Only people whose role includes it — the clinic owner decides who
Your data
Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

How it works

The usual shape of a queue & board app. DeviceHub’s own steps are written from its screen when it ships.

  1. It arrivesA new item lands on the board — from a booking, a referral or a colleague.
  2. Work itAssign it, move it along, see who is waiting and for how long.
  3. Close itDone items leave the board and stay in the record.

Rules it keeps

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

It does not exist as an app: opening the bedside device registry means opening VitalStream.
Nobody should be sold this and VitalStream for the same job, or this and BenchLink for the analysers.

AI in DeviceHub

AskQuestions about what is on screen — “What needs attention in DeviceHub 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.
Open the interactive design preview →

Questions clinics ask

What does DeviceHub do?
Retired into VitalStream — the bedside half was built there. Retired into VitalStream, which is already this product’s bedside-device app and now does the three things this page promised: the unit on a reading is the canonical one for its metric and a database CHECK says so, with only exactly-defined conversions applied and mmol/L for glucose refused rather than converted by a factor nobody checked; a device’s clock offset is measured and stored, the device’s own stamp is kept, and the corrected one is what everything sorts by; and the patient on a reading is re-read under the tenant policy with how they were identified recorded beside it. The laboratory bench was never part of this — analysers, their result codes and the barcode that matches a result to an order are BenchLink. Two tiles for the bedside would have been the duplicate this catalog is trying to stop.
What data does DeviceHub read and write?
DeviceHub reads device feeds and writes nothing — VitalStream holds the devices and their readings. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does DeviceHub deliberately not do?
It does not exist as an app: opening the bedside device registry means opening VitalStream. Nobody should be sold this and VitalStream for the same job, or this and BenchLink for the analysers.
What happens to our data if we uninstall DeviceHub?
All clinical data stays in the record.
Is DeviceHub available today?
DeviceHub is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.

Want to see DeviceHub 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.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Operations

All 145 →