At a glance
- A remote monitoring platform should cover the vital signs your service lines actually use, not a fixed shortlist of sensors.
- Core signs include blood pressure, heart rate, pulse, oxygen saturation, temperature, respiration, weight, glucose and activity or sleep.
- Vital signs alone are incomplete; patient-reported outcome and experience measures give clinical context that raw biometric readings cannot.
- Device-agnostic architecture matters more than any single device brand, because service lines change faster than procurement cycles.
- Check EHR integration, alert logic and pathway configurability alongside the sensor list before you commit.
Datos Health
Published:
A remote patient monitoring platform — meaning software that collects patient data outside the clinic for clinical review — should support the vital signs your active and planned care pathways actually require, plus the patient-reported data that makes those readings interpretable. In practice that means a core set of blood pressure, heart rate and pulse, oxygen saturation, temperature, respiration rate, weight, blood glucose (including continuous glucose), and activity measures such as steps, workouts and sleep. Those cover the bulk of Hospital in the Home, cardiac rehabilitation, chronic heart failure, COPD, diabetes, oncology, perioperative and high-risk pregnancy programs. The more useful question for a hospital or health organisation evaluating platforms in 2026 is whether the system is device-agnostic — able to ingest data from whatever approved device a patient already owns or is issued — and whether new measurement types can be added to a pathway without a vendor project.
That distinction has commercial weight. One Datos Health platform replaces multiple point solutions — device-agnostic across 8+ vital-sign types with EHR/EMR integration — and, as published on the Datos Health hospital-at-home page, typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. Datos Health also publishes an integrations list spanning connected devices and platforms across glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep, which gives a concrete picture of what a broad coverage list looks like in practice rather than in a datasheet. The sections that follow set out which signs map to which programs, where PROMs and PREMs — patient-reported outcome and experience measures — belong alongside biometrics, how ingestion and alerting actually work, and which evaluation criteria separate a sensor catalogue from a care platform.
Which vital signs should a remote patient monitoring platform support?
The vital signs a remote monitoring programme needs to support depend on the pathway, but a core set covers most chronic and post-acute use cases. Remote patient monitoring (RPM) — collecting patient data outside the clinic for clinical review — only works when the measurements captured actually change what the care team does next. The list below narrows to that core set: what each measurement is, and what it signals.
| Vital sign | What is captured | What it tells the care team |
|---|---|---|
| Blood pressure | Systolic and diastolic readings, usually at home with a cuff | Whether hypertension is controlled and how a patient is responding to medication titration |
| Heart rate / pulse | Beats per minute at rest and during activity | Prompts review for rate or rhythm concerns; tracks tolerance in cardiac rehab |
| Oxygen saturation (SpO2) | The proportion of haemoglobin carrying oxygen, via pulse oximeter | Respiratory deterioration in COPD, post-COVID and Hospital in the Home cohorts |
| Respiration rate | Breaths per minute | An early deterioration signal; a standard input to Early Warning Scores (EWS), the composite scoring used to flag patients at risk |
| Temperature | Body temperature | Post-operative and infection surveillance in virtual wards |
| Weight | Day-to-day trend, ideally same-time measurement | Fluid retention in congestive heart failure, often the earliest sign of decompensation |
| Blood glucose and continuous glucose | Spot readings or continuous glucose monitoring traces | Glycaemic control and variability across diabetes pathways |
| Activity and sleep | Steps, workout data, sleep patterns | Functional recovery, rehab participation and adherence to an activity plan |
Two attributes matter as much as the list itself. The first is cadence: a Hospital in the Home patient may submit several readings a day, while a stable chronic patient submits weekly, and the platform should let the pathway set that rather than applying one rule to everyone. The second is context — biometric readings paired with patient-reported outcome measures (PROMs), the structured questionnaires patients complete about symptoms and function, tell a far more useful story than numbers alone.
How the readings arrive matters too. Home devices commonly pair over Bluetooth and push data automatically, some measurements are entered by hand in a patient app, and wearables stream continuously. A platform that accepts all three paths and writes the result back into the EHR spares nurses from re-keying numbers into the record.
What counts as a vital sign in remote monitoring, and how is it different from a patient-reported measure?
This depends on what you mean by the term: "vital sign" carries a narrow clinical sense and a broader procurement sense, and what counts under each one changes how you read a platform's device list.
The clinical sense. In bedside practice, vital signs are the core physiological measurements of body function — temperature, pulse, respiration rate, blood pressure and oxygen saturation. They are captured by an instrument, expressed as a number, and feed scoring tools such as Early Warning Scores (EWS), which convert a set of readings into a single escalation trigger. A pulse oximeter reading of a COPD patient at home is a vital sign in this sense.
The procurement sense. When hospitals write remote monitoring requirements, "vital signs supported" usually means the full set of device-sourced biometric streams a platform can ingest — the clinical five plus weight, blood glucose and continuous glucose, activity and steps, and sleep. A connected scale transmitting daily weight in a heart-failure pathway sits in this wider category, even though weight is not a bedside vital sign.
Patient-reported measures. PROMs and PREMs — patient-reported outcome measures and patient-reported experience measures — are structured responses supplied by the patient rather than by a device: a breathlessness score, a pain rating, a wound photograph, a medication-adherence confirmation, a survey of how the care felt. They are clinical data, validated and trended like any other, but their source is the person, not the sensor.
This article uses the procurement sense throughout, because that is the sense a remote monitoring requirements document is written in. Device-sourced readings tell you what the body is doing; patient-reported measures tell you what the patient is experiencing, and most chronic-care and hospital-in-the-home pathways run both streams through the same care plan.
Why do the vital signs you need change from one care pathway to another?
When you map out which vital signs a programme actually needs, the answer shifts with the clinical question each pathway is asking. A cardiac rehab cohort and a virtual ward cohort can sit on the same platform and still rely on almost entirely different measurement sets, capture modes and patient-reported inputs.
Two definitions help here. Patient-reported outcome measures, or PROMs, are structured questionnaires in which patients score their own symptoms, function and recovery. Early Warning Scores (EWS) are the standard bedside method of combining several observations — respiration, oxygen saturation, pulse, blood pressure, temperature, consciousness — into a single deterioration score, and they are widely used in Hospital in the Home and virtual ward settings, where hospital-level care is delivered in the patient's home.
| Pathway | Measurements usually relied on | What those readings are there to answer |
|---|---|---|
| Cardiac rehab and CHF | Weight, blood pressure, heart rate, activity and steps, symptom check-ins | Fluid status and exercise tolerance between visits |
| Respiratory / COPD | Oxygen saturation, respiration rate, pulse, breathlessness reports | Early signs of an exacerbation |
| Diabetes | Glucose and continuous glucose, weight, activity | Glycaemic patterns in the gaps between appointments |
| Oncology | Temperature, weight, PROMs on treatment side-effects | Treatment tolerance and febrile escalation triggers |
| Post-acute and perioperative | Temperature, pulse, blood pressure, wound and pain reports | Recovery trajectory and complication risk |
| Hospital in the Home / virtual wards | Full observation set feeding an EWS | Deterioration detection at ward-equivalent intensity |
Each attribute also carries its own capture mode, and that matters as much as the signal itself. Some readings arrive continuously from a wearable or sensor. Some are spot measurements the patient takes on a schedule the clinical team sets. Some are answers to questions rather than device data at all, which is why patient engagement design sits alongside device selection in any serious pathway build. A respiratory programme configured in Datos Health leans on scheduled saturation and breathlessness checks, while an oncology programme may run mostly on patient-reported side-effect scoring with temperature acting as the escalation trigger.
How should you evaluate an RPM platform's vital-sign coverage?
To evaluate an RPM platform's vital-sign coverage, set your criteria before you look at any vendor's signal list. Remote patient monitoring (RPM) means collecting patient data outside the clinic for clinical review, and a long list of supported readings tells you what a system can receive — the criteria below tell you what it can do once the reading arrives.
The criteria worth defining up front
- Signal breadth and device agnosticism. Whether the platform accepts readings from the devices your cohorts already own, across cardiac, respiratory, metabolic and activity signals. This becomes decisive when one service line's kit differs from another's.
- Where the data lands. EHR/EMR integration determines whether readings reach the record clinicians actually work in, or sit in a separate portal someone has to check.
- Patient-reported data alongside biometrics. PROMs and PREMs — patient-reported outcome and experience measures — carry symptom and function detail no sensor captures, and they matter most in value-based care and hospital-in-the-home work.
- What happens after a reading arrives. Automated assisted self-care means the pathway guides the patient through education, prompts and escalation rules, surfacing only the patients who need clinical attention. Alert-only handling passes every threshold breach to a human.
- Who can change the pathway. Whether clinical teams can edit thresholds and protocols themselves, or whether each change becomes an IT ticket.
| Criterion | Narrow feed | Workflow-ready coverage |
|---|---|---|
| Signal range | Fixed device list | Device-agnostic across vital-sign families |
| Destination | Standalone dashboard | Integrated with the EHR/EMR |
| Data types | Biometrics only | Biometrics plus PROMs/PREMs |
| After a reading | Threshold alert to staff | Automated pathway steps, escalation by exception |
| Pathway changes | Vendor change request | Clinical team edits directly |
Datos Health is built to meet these criteria in one place: it takes readings from a wide set of connected devices spanning cardiac, respiratory, metabolic and activity signals, carries them into the EHR/EMR, and runs them through automated pathway steps instead of a bare alert queue. Its no-code Design Studio lets clinical teams build and modify those pathways themselves, without IT dependency.
What happens to a reading after a connected device sends it?
What happens to a reading after a connected device sends it is where a remote care program either scales or stalls. The raw value — a blood pressure, a weight, a pulse oximetry figure — arrives from the device, is matched to the patient's active care plan, and is then evaluated against rules: personalised thresholds (the upper and lower bounds set for that individual), trend logic across recent readings, and in acute pathways an Early Warning Score, the composite risk score calculated from several vitals at once. That evaluation decides the next step, not a person.
From there the pathway branches. Most readings resolve without clinician involvement: the patient receives a guided instruction, an educational prompt, or a short symptom questionnaire through multi-channel communication — app, SMS, email or a scheduled virtual visit. This is the working definition of automated assisted self-care: the patient handles the routine step, and only the cases that genuinely need review surface in a clinician queue. Structured results and patient-reported outcome measures then write back to the EHR/EMR so the record stays single-source. Datos Health states that its no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs — which is how the branching logic above gets changed by clinicians rather than queued with IT.
Reading across pathways, the constraint on capacity is rarely how many vitals a system can capture; it is how many times a human has to re-make the same decision about an identical reading.
| Do this | But watch out for — and how to handle it |
|---|---|
| Set thresholds per patient, per pathway | Population-wide bounds generate noise on stable patients; tune bands inside the care plan at enrolment |
| Automate the first response to an out-of-range value | Automation can absorb real deterioration; pair every automated reply with a time-bound escalation rule |
| Deliver instructions across several channels | Messages go unread; configure fallback to a second channel before escalation |
| Write results back to the EHR/EMR | Duplicate or orphaned records; map to existing patient identifiers and fields at integration |
Frequently Asked Questions
What vital signs should an RPM platform support as a baseline?
Remote patient monitoring (RPM) — collecting patient data outside the clinic for clinical review — needs to cover the measurements your pathways actually act on. For most acute and chronic programs that means blood pressure, heart rate and pulse, oxygen saturation, respiration, temperature, weight, and glucose, including continuous glucose. Activity signals such as steps, workouts and sleep matter for rehabilitation and lifestyle pathways. Build the list backwards from your escalation rules: a vital sign you cannot escalate on is data you will not use.
How wide does device coverage need to be in practice?
Wide enough that a single pathway does not force patients onto two apps. Datos Health's published integrations list covers connected devices and platforms spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep — so coverage is device-agnostic rather than tied to one manufacturer's kit. That matters when a hospital already owns stock, or when patients bring their own consumer devices.
Why isn't vital-sign coverage on its own enough for a virtual ward?
Hospital in the Home, also called a virtual ward, delivers hospital-level care in the patient's home, and it needs workflow as much as data. One Datos Health platform replaces multiple point solutions — device-agnostic across 8+ vital-sign types with EHR/EMR integration — and typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, according to Datos Health's published hospital-in-the-home material. Coverage supplies the readings; automation decides which readings reach a clinician.
How do readings reach clinicians without adding alert noise?
Through automated assisted self-care: patients self-manage parts of their care via guided, automated pathways, so routine readings, education and check-ins are handled without a human in the loop, and only patients needing clinical attention are surfaced. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, as stated on the company's clinicians page — so thresholds, escalation logic and follow-up questions are tuned by the clinicians who own the pathway.
Which patient-reported measures belong alongside vital signs?
PROMs and PREMs — patient-reported outcome measures and patient-reported experience measures — carry the symptom, function and experience context that a number from a cuff cannot. In hospital-in-the-home programs, which generally begin after hospital discharge and run for a defined recovery window, patient-reported outcome measures sit alongside biometric data collection to give the care team clinical oversight. The same pairing does the work in cardiac rehab and heart-failure follow-up, where interactive care plans are used to lift adherence and keep contact with patients between visits.
What should teams check on governance and credibility in 2026?
Ask for two things. First, the data posture: have the vendor set out in writing how its privacy and information-security controls map to your jurisdiction's obligations, and confirm how each one applies to your specific deployment rather than to the product in general. Second, evidence the platform has already carried pathways like yours — reference programs in comparable service lines tell you more than a feature list does. Then confirm the practical detail: how vital signs, alerts and patient-reported measures write back into your EHR or EMR so clinicians work in one record.
About this article
Datos Health publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Datos Health before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-09-24