ClinicalLive · in the productQueue & board

RPMConsole

Readings from home into a queue somebody works, labelled by how they were taken.

Get RPMConsole Open the appAvailable nowHow pricing works →

What it is

Patients on a monitoring programme send numbers from home — off a cuff, off a glucometer, typed into the Send a reading card on their portal link, or read off a watch — and those numbers are only useful if somebody looks at the ones that matter. A programme is a set of measurements and the numbers that make one worth a look; a reading that crosses one of those numbers becomes a line in a queue a nurse works, picks up, escalates to a named person, and closes with what was done. The thresholds are also the programme’s vocabulary: what it measures, spelled its way, in one unit each. A reading is recorded in that unit or refused — nothing is converted — and a measurement the programme has not asked for is refused rather than stored under a name no rule matches, so the flag cannot be defeated by a unit or a spelling. TWO THINGS THIS DOES NOT DO. It does not invent a threshold: the number that decides whether somebody is woken is the doctor’s decision, so none ship with the app, the field saying whose decision it is cannot be left blank, and a programme with no numbers takes no readings at all — which the screen tells you rather than showing an empty queue as safety. And it never lets a self-report look like a measurement: every reading carries how it was taken, the patient’s own link can only say “I measured this” or “my watch says”, and that label travels onto the alert, so a step count and a hospital vital can never be read as the same kind of fact.

Who uses it: Built for: Hospitals
Reads: Patients, your registered devices, the thresholds you wrote, the patient portal link
Writes: Programmes and their thresholds, enrolments, readings, the review queue
Never: It ships with no threshold in it and invents none: a number with no author is refused by the database, and a programme with none takes no readings.
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; operational history stays queryable.

How it works

Write the thresholds firstA programme with no thresholds takes no readings at all, and the screen says which programmes those are — the thresholds are the metrics a programme measures and the units it measures them in, and each one names the reference it was set from.
Enrol the patientEnrol a patient onto a live programme; a patient already on that programme is refused until the current enrolment is ended.
Record a reading with how it was takenEvery reading carries its measurement class — hospital device, home meter, patient reported or wearable — a hospital device reading needs a device this hospital registered, and a reading in a unit other than the threshold’s is refused rather than converted.
Work the review queueThe queue holds readings that crossed a threshold, each showing how it was taken, how long it has been open and whether that is past the programme’s review target.
Pick it up, escalate, then close itAcknowledge takes the alert, Escalate names the clinician it goes to, and closing asks what was done — a queue that empties into silence teaches nobody anything.

Rules it keeps

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

It ships with no threshold in it and invents none: a number with no author is refused by the database, and a programme with none takes no readings.

It converts nothing: a reading arrives in the threshold’s own unit or is refused, because a conversion factor typed into the code that decides whether a nurse is woken is a number this product will not carry.

It sets no review target either — an untimed queue is shown as untimed rather than measured against a figure nobody chose.

It does not write to the chart: these are monitoring readings, and the hospital’s own measured vitals stay in Vitals with the device that made them.

A reading recorded as clinically measured must name a device this hospital registered, proved against your own register rather than by the shape of the id; no other kind of reading may name a device at all, and one from the patient’s own link can only ever be marked patient-reported or from a wearable, which must say which watch or app.

An alert carries the class of the reading underneath it, copied rather than typed.

Escalating names somebody on your active staff list, and closing says what was done.

AI in RPMConsole

AskQuestions about what is on screen — “What needs attention in RPMConsole 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

RPMConsole — Remote Monitoring — Work readings from home, labelled by how each one was taken — 01Remote Monitoring — Work readings from home, labelled by how each one was takenCaptured from the running demo clinic

01Remote Monitoring — Work readings from home, labelled by how each one was takenCaptured 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 · 2

Patient Registry VitalStream

See the whole clinic →

Questions clinics ask

What does RPMConsole do?

Readings from home into a queue somebody works, labelled by how they were taken. Patients on a monitoring programme send numbers from home — off a cuff, off a glucometer, typed into the Send a reading card on their portal link, or read off a watch — and those numbers are only useful if somebody looks at the ones that matter. A programme is a set of measurements and the numbers that make one worth a look; a reading that crosses one of those numbers becomes a line in a queue a nurse works, picks up, escalates to a named person, and closes with what was done. The thresholds are also the programme’s vocabulary: what it measures, spelled its way, in one unit each. A reading is recorded in that unit or refused — nothing is converted — and a measurement the programme has not asked for is refused rather than stored under a name no rule matches, so the flag cannot be defeated by a unit or a spelling. TWO THINGS THIS DOES NOT DO. It does not invent a threshold: the number that decides whether somebody is woken is the doctor’s decision, so none ship with the app, the field saying whose decision it is cannot be left blank, and a programme with no numbers takes no readings at all — which the screen tells you rather than showing an empty queue as safety. And it never lets a self-report look like a measurement: every reading carries how it was taken, the patient’s own link can only say “I measured this” or “my watch says”, and that label travels onto the alert, so a step count and a hospital vital can never be read as the same kind of fact.

What data does RPMConsole read and write?

RPMConsole reads patients, your registered devices, the thresholds you wrote, the patient portal link and writes programmes and their thresholds, enrolments, readings, the review queue. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does RPMConsole deliberately not do?

It ships with no threshold in it and invents none: a number with no author is refused by the database, and a programme with none takes no readings. It converts nothing: a reading arrives in the threshold’s own unit or is refused, because a conversion factor typed into the code that decides whether a nurse is woken is a number this product will not carry. It sets no review target either — an untimed queue is shown as untimed rather than measured against a figure nobody chose. It does not write to the chart: these are monitoring readings, and the hospital’s own measured vitals stay in Vitals with the device that made them. A reading recorded as clinically measured must name a device this hospital registered, proved against your own register rather than by the shape of the id; no other kind of reading may name a device at all, and one from the patient’s own link can only ever be marked patient-reported or from a wearable, which must say which watch or app. An alert carries the class of the reading underneath it, copied rather than typed. Escalating names somebody on your active staff list, and closing says what was done.

What happens to our data if we uninstall RPMConsole?

All clinical data stays in the record; operational history stays queryable.

Is RPMConsole available today?

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

Want to see RPMConsole 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 Clinical

All 437 →

Featured inHome Care & Nursing Sleep Medicine