RPMConsole

What RPMConsole does

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.

How you actually use it

1. 1Write 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.
2. 2Enrol the patientEnrol a patient onto a live programme; a patient already on that programme is refused until the current enrolment is ended.
3. 3Record 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.
4. 4Work 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.
5. 5Pick 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.

What it does 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.

Questions clinics ask