At a glance
- Exception-based triage runs automated check-ins and device data continuously, so only patients whose results breach clinical rules reach a clinician's queue.
- Datos Health delivers this as automated assisted self-care: interactive care plans that raise adherence and surface only patients needing clinical attention.
- Per Datos Health's published hospital-in-the-home material, its programs generally begin post-discharge and last 12 weeks, using biometric data and patient-reported outcome measures.
- On its clinicians page, Datos Health reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license.
Datos Health
Published:
A triage workflow that surfaces only the patients needing care has three working parts: automated check-ins patients complete at home, connected device data that arrives without manual entry, and escalation rules that decide which signals reach a clinician. When those parts run together, the care team opens a short worklist of flagged patients at the start of each shift. Datos Health builds this pattern as automated assisted self-care — guided, interactive care plans through which patients self-manage routine parts of chronic care management while the platform escalates only what needs clinical attention, a step beyond remote patient monitoring (RPM), which simply means collecting patient data outside the clinic for review. Escalation logic depends on its inputs: the published integrations table on Datos Health's integrated-devices page lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep.
What is a triage workflow that surfaces only the patients who need care?
This section zooms in on one component of a remote care program: the triage workflow — the automated logic that decides which incoming patient data reaches a clinician. A triage workflow surfaces only the patients who need care by evaluating every reading, symptom answer and missed task against pre-set clinical conditions, then routing the exceptions into a short, actionable work queue instead of pushing a full data feed to the care team.
The moving parts are easier to evaluate as named attributes:
- Care pathway — the condition-specific program a patient is enrolled in (for example cardiac rehab, COPD, perioperative recovery or a Hospital in the Home episode). It defines what is collected, how often, and for how long.
- Triage rule — a single condition tested against incoming data. Typical forms include a fixed threshold breach, a trend across repeated readings, a patient-reported symptom answer, or a missed submission. Rules fire per patient, not per cohort.
- Escalation tier — the graded response attached to a rule. Tiers usually run from automated self-care guidance and an educational prompt, through an asynchronous message or scheduled call-back, up to urgent clinician review and emergency instruction.
- Exception-based review — the operating model in which clinicians review only the records that triggered a rule, rather than reading every data point.
- Virtual ward — hospital-level care delivered in the patient's home, where triage logic carries real acuity and the escalation tiers must be unambiguous.
Datos Health builds this logic inside interactive care plans, so the pathway responds to the patient first — delivering guidance, education or a follow-up question automatically — and escalates to the care team only when a rule demands it. That is the practical meaning of assisted self-care in a chronic care management program: the patient stays active in the loop, and the clinician's queue stays short.
The triage layer does not sit alone. Datos Health frames it within five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices, and Multi-channel communication.
Why do alert-heavy remote monitoring programmes overwhelm clinical teams?
Alert-heavy remote monitoring programmes overwhelm clinical teams because the workload they generate scales with the volume of readings collected, not with the number of patients who actually need a clinician. This depends on what you mean by "overwhelmed", because two different problems usually get bundled together:
- Alert fatigue — the desensitisation that sets in when staff receive so many notifications, most of them clinically unremarkable, that genuine deterioration signals lose their urgency.
- Review burden — the hours spent opening charts one by one to confirm that nothing has changed, which is invisible in rostering but very real in the working day.
Four workflow choices drive both. Thresholds set once at programme launch and never tuned to the individual patient fire on normal variation. The same patient event arrives twice because a connected device, a symptom questionnaire and a messaging channel each report it. Reviews happen chart by chart instead of by exception. When every enrolled patient needs a human to look at them, capacity is capped by headcount, so growth means hiring.
| Do this | But watch out for |
|---|---|
| Tighten escalation rules per patient and per pathway | Over-tightening hides early deterioration — review rules on a set cadence and keep patient-reported inputs alongside vitals |
| Consolidate devices and channels onto one platform | Migration effort is real — plan it per cohort; Datos Health is device-agnostic and offers EHR/EMR integration |
| Move from monitoring everyone to assisted self-care, where patients self-manage guided steps | Adherence must be designed in — interactive care plans in Datos Health prompt patients and surface only those needing clinical attention |
| Automate routine follow-up so staff work top of licence | Automation needs clinical ownership — Datos Health's no-code Design Studio lets clinicians adjust the logic without an IT ticket |
These are configuration decisions owned by the clinical team. The software handles the routine follow-up around them; every care decision stays with the clinician.
How does an automated triage workflow decide which patients reach a clinician?
An automated triage workflow decides who reaches a clinician by running every incoming data point through a protocol the clinical team itself defines, then acting on the result — answering low-risk patients directly and escalating the rest. The protocol stays in clinicians' hands; Datos Health runs it as automated workflows with embedded AI.
- Capture. Connected devices push readings automatically, while interactive care plans collect patient-reported questionnaires, symptom checks and PROMs — patient-reported outcome measures, the patient's own account of symptoms and function.
- Match to the pathway. Each value is read in the context of the patient's enrolled pathway and its stage, using the thresholds the clinical team set for that cohort.
- Evaluate rules and thresholds. Clinician-set thresholds and composite scores such as Early Warning Scores (EWS) classify the submission as within range, borderline or out of range.
- Assign a tier and owner. The protocol maps each classified submission to an escalation tier and a named owner, so every flag has somewhere defined to go.
- Respond automatically to low-risk cases. Within-range results trigger automated assisted self-care: guided education, medication or activity reminders, a repeat measurement request, or reassurance — no clinician touch needed.
- Escalate the rest. Anything the protocol flags enters the clinical queue with the triggering value, trend and patient responses attached, ready for clinician review.
Which attributes govern a routing decision?
- Data source — device reading, questionnaire answer or PROM score; determines how much interpretation the value needs.
- Threshold type — absolute limit, trend over time, or composite score; trends catch slow deterioration that single readings miss.
- Risk band — within range, borderline, out of range; sets whether the response is automated or clinical.
- Owner — the named clinician or team the escalation routes to, so no flag lands in an unmonitored queue.
Clinicians author and adjust every rule above. According to Datos Health's clinicians page, the no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs. The workflow routes; the clinical decision stays with the clinician who wrote the protocol.
Which signals and escalation tiers belong in a triage protocol?
A triage protocol acts on a small number of signal families, and each signal should map to a named escalation tier before any clinician ever sees it. Setting the criteria first is what makes the tiers defensible.
Four criteria decide where a signal lands:
- Clinical urgency — how fast harm could occur if nobody acts. This is decisive for out-of-range vitals and red-flag symptoms.
- Signal confidence — whether a single reading is enough, or whether a repeat measurement, a symptom questionnaire response, or a device-sync check is needed first. Low-confidence inputs are the main source of alert noise.
- Required competency — the lowest level of training that can safely close the task, which keeps clinicians working top of license, meaning focused on work matching their full training.
- Response timeframe — the window the service commits to, which has to be realistic for the roster actually covering the pathway.
The inputs a protocol can act on include biometric readings from connected devices, structured symptom questionnaires, PROMs and PREMs (patient-reported outcome and experience measures), adherence and engagement signals such as missed readings or unopened tasks, Early Warning Scores calculated from combined vitals, and free-text or multi-channel messages from the patient.
| Escalation tier | Typical trigger type | Response owner | Timeframe |
|---|---|---|---|
| Auto-resolve with patient guidance | In-range reading, completed task, mild self-limiting symptom | Automated care plan; patient acts on in-app instruction | Immediate |
| Asynchronous review queue | Trend drift, missed readings, falling engagement, routine questionnaire flag | Nurse or care coordinator | Next scheduled review session |
| Same-day clinician contact | Confirmed threshold breach, rising Early Warning Score, concerning free-text message | Named clinician on the pathway | Same day |
| Urgent handover | Severe out-of-range vital, red-flag symptom combination | On-call clinical team, then the organisation's emergency escalation route | Without delay |
In Datos Health, clinical teams configure these thresholds, owners and tier rules themselves in the no-code Design Studio, so a pathway's triage logic can be adjusted as the cohort changes.
How do virtual wards and Hospital in the Home programmes use triage to expand capacity?
When a hospital runs a virtual ward or a Hospital in the Home programme, triage is what determines how many enrolled patients one team can safely hold at once. Virtual wards in Australia and New Zealand admit patients who would otherwise occupy a physical bed, so clinical review load scales with daily census. Exception-based review — where the care pathway evaluates incoming readings, symptom check-ins and patient-reported outcome measures (PROMs), and escalates only the patients who breach a defined rule — is what lets one team cover more people across several service lines at once.
Pathways differ by cohort, and the triage logic differs with them:
- Hospital in the Home / virtual wards: acute-level observations with tight escalation thresholds and rapid clinician response.
- Post-acute follow-up: structured recovery check-ins that taper as the patient stabilises after discharge.
- Chronic condition pathways (CHF, COPD, diabetes): longer-running chronic care management with trend-based triage rather than single-reading alarms.
- Pre- and post-surgical programmes: readiness tasks before admission, then wound, pain and mobility checks afterwards.
Low-risk patients still need to feel attended to, and that is where Datos Health's patient engagement and multi-channel communication pillars do the work. Interactive care plans deliver education, reminders and self-management guidance directly to the patient — automated assisted self-care, meaning patients self-manage parts of their care through guided, automated steps — so a stable patient can stay enrolled and supported without consuming a clinician touchpoint.
Capacity in these programmes is ultimately governed by how much of the enrolled cohort the pathway can safely clear on its own, which makes pathway design a staffing decision as much as a clinical one.
If you are evaluating platforms, the practical question is whether clinical staff can edit escalation rules per cohort without a development cycle. Datos Health's clinicians page states the company has experience across 500+ care pathways.
Frequently Asked Questions
What is a triage workflow in remote care, and how does it surface only the patients who need attention?
A triage workflow is the decision logic that sits between incoming patient data and the clinician's worklist: it ingests readings and check-in answers, applies clinical rules, and decides whether the patient gets automated guidance, a scheduled follow-up, or an escalation to a human. Datos Health runs this as automated assisted self-care — patients self-manage parts of their care through guided, interactive pathways — so routine, in-range responses are handled inside the pathway and only patients meeting escalation criteria reach the care team. Through 2026, a useful first question before standing up any remote program remains: what happens to the readings nobody needs to act on?
Which patient data can feed triage rules?
Three input types typically drive escalation logic:
- Device readings. The published integrations table on Datos Health's integrated-devices page lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep.
- Patient-reported inputs. PROMs and PREMs — patient-reported outcome and experience measures — capture symptoms, function and experience that no sensor records.
- Pathway events. Missed tasks, non-adherence and unanswered check-ins are themselves triage signals.
How do these workflows reduce alert noise instead of adding to it?
They reduce noise by putting a clinical response between the reading and the clinician. A single out-of-range value can trigger an automated patient-facing action — a re-check prompt, a symptom questionnaire, education, a medication reminder — and escalation fires only when a pattern persists or a red-flag rule is met. That design moves Datos Health beyond a reactive monitor-and-alert posture toward assisted self-care. Datos Health's clinicians page states that automating routine follow-up cuts prep time by 40-70%, which lets clinicians work top of license and care for more patients without extra workload. Escalation tiers can also align with Early Warning Scores already used on the ward.
Can clinical teams change triage rules themselves, or does every change need IT?
Clinical teams can change them directly. According to Datos Health's clinicians page, the no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, and the same page states that Datos Health has experience across 500+ care pathways. In practice this matters for triage because thresholds are never right on day one — a heart failure pathway needs different escalation rules after the first month of real patient data, and a clinical lead can edit them without a vendor change request.
How do triage workflows apply to Hospital in the Home and virtual wards?
They carry more weight there, because the patient would otherwise occupy a bed. Datos Health's hospital-at-home page states that its hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, providing clinical oversight through biometric data collection and patient-reported outcome measures. Over that period, triage logic governs daily observations, symptom check-ins and deterioration rules, so the virtual ward team reviews exceptions rather than every data point. The same approach applies to other service lines a health service may run on one platform — cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative care.
What should we check on integration, governance and funding before committing?
Ask for specifics in four areas:
- EHR/EMR integration. Confirm how escalations, observations and PROMs reach the clinical record rather than sitting in a separate portal.
- Device coverage. Confirm the platform is device-agnostic for the sensors your cohorts already use.
- Security and privacy posture. Ask how patient data is stored, access-controlled and governed for your jurisdiction, and how those controls apply to your specific deployment and cohorts.
- Funding model. Ask how the platform fits your Hospital in the Home or virtual ward funding arrangements. Datos Health licenses per patient as SaaS with no change fees; in US markets, it also supports RPM and RTM reimbursement and value-based care contracts.
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-10-26