At a glance
- Shortlisting Hospital in the Home platform vendors means scoring candidates against defined criteria before demos, so only serious contenders get deep evaluation.
- Core criteria: pathway configurability, device connectivity breadth, EHR/EMR integration, automation depth, patient engagement, security posture, funding-model fit and time-to-launch.
- Datos Health's clinicians page reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license.
- Datos Health's hospital-at-home page reports that hospital-in-the-home programs typically cut cost of care per patient by 30-50%.
- Weight criteria against your own service lines first, then test each claim in a scripted, clinician-led demo.
Datos Health
Published:
Shortlisting Hospital in the Home platform vendors is the structured process of reducing the full market of remote and hybrid care technologies down to a short list of candidates worth evaluating in depth — normally by defining your clinical and operational criteria first, scoring every vendor against those criteria on documented evidence, and only then booking demonstrations. Hospital in the Home, known in many Australian and New Zealand health services as a virtual ward, means delivering hospital-level care in the patient's own home, with clinical oversight provided remotely. A platform shortlist is the artefact that comes out of that process: a ranked or grouped set of vendors, each mapped to the criteria that matter for your service lines, with the gaps and assumptions written down so a procurement panel can defend the decision.
In practice, the criteria that drive a credible shortlist are consistent across health systems: how easily clinical teams can configure and modify care pathways without waiting on IT, how broadly the platform connects to consumer and clinical devices, how it integrates with the EHR or EMR, how much routine follow-up it automates, how it supports patient engagement and adherence between touchpoints, its stated security and privacy posture, whether its commercial model supports value-based contracts, and how quickly a first pathway can go live. The guidance here is written for buyers running a selection process as of 2026, and it assumes you will need more than one pathway — hospital in the home alongside cardiac rehab, chronic heart failure, COPD, oncology, diabetes, high-risk pregnancy or perioperative care — on the same platform.
What should a Hospital in the Home platform shortlist actually screen for?
This step covers one narrow decision: screening vendors for a Hospital in the Home program — hospital-level care delivered in the patient's home, also called a virtual ward in Australia and New Zealand. A workable shortlist scores each platform against a short list of attributes, where every attribute has a name, a realistic range of answers, and a clear reason it changes the decision.
Pathway configuration model. Range: vendor-built only, change requests through professional services, or no-code configuration by clinical staff. This sets how long a protocol change takes — an afternoon, or a procurement cycle.
Pathway library depth. Range: a handful of templates through to several hundred pre-built care programs. Depth matters if the service wants cardiac rehab, CHF, COPD, oncology and perioperative pathways on one platform rather than a separate tool per service line.
Device coverage. Range: single-manufacturer kit through to device-agnostic ingestion across vital-sign types such as blood pressure, oxygen saturation, temperature, respiration, pulse, glucose and weight. Ask which integrations are already live, not which are on a roadmap.
EHR/EMR integration. Range: document export, HL7 v2 messaging, or bidirectional FHIR-based exchange. Weak integration pushes nurses into double documentation.
Escalation and self-care logic. Range: threshold alerting only (classic Remote Patient Monitoring, meaning data collected outside the clinic for later review), rules-based triage, or automated assisted self-care, where patients self-manage parts of the plan through guided steps and only exceptions reach a clinician. This attribute drives alert load.
Outcome instrumentation. Range: biometrics only, or biometrics plus PROMs and PREMs — patient-reported outcome and experience measures — and Early Warning Scores. Required for value-based contracts and virtual ward reporting.
Security posture. Ask which frameworks the vendor supports, including HIPAA, GDPR, ISO 27001 and ISO 27799, and request the supporting documentation during evaluation.
Which capability pillars must a virtual ward platform cover end to end?
Scope this to acute-level care delivered in the patient's home — Hospital in the Home, also called a virtual ward — where the capability pillars a platform must cover number five, and each must hold up across every service line, not just one disease program. Datos Health names those five pillars consistently, and the table below sets out what each one has to do when the caseload is acute.
| Pillar | What it must cover | Why it matters for acute care at home |
|---|---|---|
| Virtual Visits | Scheduled and on-demand video consults inside the care pathway, with clinical notes flowing back to the record | Replaces the ward round; without it, escalation means an ambulance |
| Remote monitoring | Scheduled vitals capture, thresholds, and Early Warning Scores (aggregate physiological scores that flag deterioration) | Acute patients need trending, not single readings |
| Patient engagement | Interactive care plans, task prompts, education, and PROMs/PREMs — patient-reported outcome and experience measures | Supports automated assisted self-care, where patients safely self-manage guided parts of the pathway |
| Connected devices | Device-agnostic pairing across the vital-sign types a mixed caseload needs, from blood pressure and oxygen saturation through to weight and glucose | A virtual ward carries several conditions at once, so the device list has to stretch without a new contract |
| Multi-channel communication | Secure messaging, SMS, push and voice, with fallbacks for patients with low digital confidence | Non-responders are a clinical risk, not an admin task |
Two cross-cutting attributes decide whether those pillars work end to end. The first is EHR/EMR integration: ask each vendor whether orders, results and documentation reach the record clinicians already use, or live in a parallel system. The second is configurability: a cardiac rehab pathway, a COPD pathway and a perioperative pathway differ in cadence, thresholds and escalation rules, so the platform has to let clinical teams change each one without a vendor ticket. Datos Health positions itself as the only platform with a no-code customization studio, with pathways live in days.
How do you test whether care pathways can be built and changed without vendor development work?
What you can test here depends on what you mean by changing a care pathway, because vendors apply the phrase to two different capabilities.
Parameter editing means adjusting values inside a pathway someone else built — alert thresholds, reminder timing, the wording of a questionnaire item, which vital signs appear on a dashboard. A concrete example: raising the daily weight-gain threshold that triggers a heart-failure review. This is useful, but the pathway's structure is fixed.
Pathway authoring means creating or restructuring the pathway itself — new protocol logic, branching by risk tier, escalation rules, the PROMs schedule, device assignments, and the messages patients receive at each step. A concrete example: taking a post-discharge respiratory program and reworking it into a perioperative pathway with different step-down rules. This is the meaning used here, because it is what determines whether a clinical team waits on vendor engineering.
Practical ways to test the claim during evaluation:
- Ask for a live build. Name a change in the demo session and watch it made on screen, by a clinician rather than a solutions engineer.
- Ask who holds the authoring access in existing deployments: clinical staff, the vendor's professional services team, or hospital IT.
- Ask for the change log. Which recent requests were handled as configuration, and which needed a product release?
- Ask how a change reaches patients — published immediately, or bundled into the vendor's next release cycle.
- Ask for the commercial terms on changes in writing before contracting.
Datos Health's clinicians page states that 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. That is a claim any vendor should be willing to demonstrate on screen rather than describe, so make the live build part of the scoring sheet rather than a nice-to-have.
Which evaluation criteria matter most at each stage of the shortlisting process?
The evaluation criteria that matter most shift as a Hospital in the Home procurement narrows, so a staged weighting keeps each gate focused. Hospital in the Home (also called a virtual ward) delivers hospital-level care in the patient's home, and the assessment splits cleanly into three gates: longlist screening (a pass/fail filter on vendor fit), shortlist scoring (a weighted comparison of the vendors that passed), and final selection (hands-on verification before contract).
Define what each criterion is testing before you score anything. Interoperability tests whether clinical data lands in the record clinicians already use. Configurability tests whether your own team can change a pathway, or whether every edit becomes a vendor change request. Workflow impact tests whether the platform removes routine follow-up work or adds alert review to an already stretched roster.
| Criterion | Longlist screening | Shortlist scoring | Final selection |
|---|---|---|---|
| Pathway breadth and configurability | Does a library cover your service lines? | Who edits a pathway — your team or the vendor? | Build a live pathway change in the demo |
| EHR/EMR integration | Ask: which standards-based interfaces (HL7, FHIR) are offered? | Ask: do orders, results and documentation reach your record? | Validated against your integration engine |
| Device interoperability | Device-agnostic, not locked to one brand | Coverage of the vital signs your cohorts need | Test with your actual issued devices |
| Clinician workload | Automated assisted self-care capability | Escalation logic and triage quality | Shadow a nurse through a live caseload |
| Security and privacy | HIPAA, GDPR, ISO 27001 and ISO 27799 posture stated | Data residency for Australia and New Zealand | Security review sign-off |
| Commercial model | Licence model and value-based contract support | Licence structure and change fees | Reference check at comparable acuity |
On device interoperability, ask every shortlisted vendor for a written, published inventory of supported devices and the vital-sign types they stream, as Datos Health maintains for its platform, and check it against the equipment your cohorts are actually issued.
What integration, data and security questions belong in your RFI?
Integration, data residency and information-security questions belong near the front of your request for information (RFI) — the pre-shortlist document an Australian or New Zealand health service sends to virtual care vendors — because the answers determine what can actually be built after contract signature.
When the program in scope is Hospital in the Home or a virtual ward run inside a public health service, frame the questions around your existing clinical systems rather than the vendor's demo environment:
- Interoperability: Which interfaces ship as standard — HL7 v2 messaging for admissions and results, FHIR-based APIs, single sign-on from the clinical desktop? Who builds and maintains each interface, and what is required when a second or third pathway is added?
- Clinical data flow: Do biometric readings and patient-reported outcome measures (PROMs — structured questionnaires patients complete about symptoms and function) land in the medical record as discrete, reportable fields or as a flat document? Can the service export its own data in an open format on exit?
- Privacy and residency: Where is identifiable health information hosted and processed, and how does the vendor meet obligations under Australian privacy legislation and New Zealand's health information privacy rules?
- Security posture: Ask for role-based access controls, audit logging, independent testing arrangements, and breach-notification commitments in writing.
On the vendor side, documented evidence is worth more than a capability matrix. Ask each vendor which security and privacy frameworks it supports, ask for the material that sits behind those statements, and ask how the claims are kept current as the platform changes. Then route the answers to the people who own the decision rather than reading them in the procurement team alone.
A useful diagnostic is to ask what happens to the integration when a pathway changes — platforms that treat every new program as a fresh interface build accumulate implementation cost long after go-live.
Ask each shortlisted vendor for a written interface specification and a named reference site running a comparable pathway.
Frequently Asked Questions
What should a Hospital in the Home vendor shortlist actually cover?
Hospital in the Home (also called a virtual ward) means delivering hospital-level care — monitoring, escalation, clinical review — in the patient's own home. A workable shortlist tests five things in every demo:
- Pathway configuration: can your clinical team build and change a pathway, or does every edit become an IT ticket?
- Capability breadth: virtual visits, remote monitoring, patient engagement, connected devices and multi-channel communication in one system.
- Integration: ask how data reaches your EHR/EMR, rather than sitting in a separate portal clinicians log into.
- Escalation logic: does the platform surface only patients who need attention?
- Commercial model: licence structure, value-based contract support and the cost of changing a pathway later.
Score vendors on each criterion separately, using your own service lines as the test cases.
How fast should a new care pathway go live?
Days, not quarters — that is the benchmark to hold vendors to, because a Hospital in the Home program usually needs several pathways (cardiac rehab, CHF, COPD, perioperative, oncology) before it reaches useful scale. Datos Health's clinicians page states that 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. Ask each vendor to configure one of your pathways live, during the evaluation, rather than showing a finished demo build.
Which device and data questions belong in the RFP?
Ask which devices are supported today, how new ones are added, and whether readings land in the clinical record automatically. Datos Health's published integrations table lists connected devices and platforms spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Also ask how patient-reported outcome and experience measures — PROMs and PREMs, the structured questionnaires patients complete about symptoms and care quality — are collected alongside biometric data, since chronic care management decisions rarely rest on vitals alone.
How do we verify the platform reduces clinician workload instead of adding alerts?
Ask for the mechanism, then test it. The relevant design is automated assisted self-care: patients self-manage parts of their care through guided, interactive plans, and clinicians review exceptions. Datos Health's clinicians page states that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license — focusing on work that matches their full training — and care for more patients without extra workload. In evaluation, ask each vendor how many patient-days a single nurse can hold, and what proportion of inbound data never needs human review.
What security and privacy questions should we ask as of 2026?
Ask what the platform supports and ask for the documentation behind it. For Australian and New Zealand deployments, also confirm data residency arrangements, your own privacy obligations, audit logging, role-based access, and how identity is handled when patients and carers share a device. Your health service's information security and legal teams own the final assessment, so bring them into the shortlist stage rather than at contract signature.
How does a Hospital in the Home program fund itself?
For an Australian or New Zealand health service, the case usually rests on avoided bed-days and, where they exist, value-based care contracts. Datos Health's hospital-at-home page states that its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. The same hospital-at-home page describes these programs as generally beginning post-hospital discharge and lasting 12 weeks, with oversight through biometric data collection and patient-reported outcome measures. Datos Health is licensed per patient as SaaS with no change fees, and supports value-based care contracts; its support for RPM/RTM reimbursement applies to US billing practice, not to ANZ funding.
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