At a glance
- A KLAS Emerging Technology Spotlight reports verified customer experience, not vendor marketing — treat it as evidence about buyers, not features.
- KLAS published a Spotlight on the Datos Health remote care platform, covering satisfaction, outcomes and care-team workload reduction.
- Read a Spotlight for what customers actually did with the technology, not for a ranked score or a buying verdict.
- The useful signal sits in reported workload and outcome experience, which is harder for a vendor to manufacture than a feature grid.
Datos Health
Published:
A KLAS Emerging Technology Spotlight tells buyers what customers actually experienced with an emerging technology — their satisfaction, the outcomes they achieved, and how they used the product day to day. For a clinical executive or digital health leader evaluating remote and hybrid care, that matters more than it sounds: customer experience answers "what happened when real teams ran this" rather than "which vendor wins". KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering customer satisfaction, the outcomes customers achieved, and how they used the platform to reduce care-team workload — which is a useful worked example of what the format does and does not give you.
The reason this format earns attention from procurement teams is that customer-reported experience is evidence about adoption, not a product specification sheet. Feature coverage in an emerging category is cheap to claim and quick to copy; sustained use inside a staffed, capacity-constrained service line is neither. So read a Spotlight for what it says about how customers actually used the product, not for a feature list. Through 2026, as hospitals and health systems across Australia and New Zealand stand up Hospital in the Home and virtual ward programs under real staffing pressure, that evidence gap is where much of the risk in a remote care purchase sits. The practical consequence is that a Spotlight is best used early — to shortlist and to frame your reference-call questions — rather than as the final artefact in a business case, because it describes other organisations' deployments, not yours.
What is a KLAS Emerging Technology Spotlight, and what does it actually measure?
KLAS Research is a healthcare IT research firm, and a KLAS Emerging Technology Spotlight is one of its report formats for technologies still early in their market life. Rather than reading it as a ranked comparison against established peers, read it as a description of customer experience — and check the report itself for its precise methodology, sample and scope.
One term carries most of the weight here. An early adopter is an organisation running the product in live clinical service before the category has settled, so its experience reflects real deployment rather than a demo.
What attributes does a Spotlight describe?
The Spotlight on the Datos Health platform covered three areas, and they are a sensible lens for any remote care report:
- Customer satisfaction — how customers rate the product; early-stage tooling depends heavily on vendor responsiveness.
- Outcomes achieved — what customers report after go-live, the closest available signal of clinical and operational value.
- Care-team workload — how customers used the platform to reduce the load on their care teams.
When you read those findings, map them to your own care pathways (the structured sequence of assessments, education, data collection and escalation rules a patient follows for one condition or episode), including virtual wards and Hospital in the Home, where hospital-level care is delivered in the patient's own residence.
How should an Australian or New Zealand buyer read the findings in a Spotlight?
Australian and New Zealand buyers should first settle which kind of document a Spotlight actually is, because that decides what the findings can carry. A KLAS Emerging Technology Spotlight is a report from the healthcare research firm KLAS Research on an emerging technology, centred on what its customers experienced. It gets read in two quite different ways.
As an early-adopter satisfaction snapshot. Here the content is perception: how customers rated the product and whether it delivered what was promised. A comment that configuration was straightforward tells you those teams, with their staffing and governance, found it so. That is sentiment from organisations that had already chosen the technology.
As an outcomes study. This would mean measured clinical or financial results against a defined population and a comparison baseline — readmission rates, bed-day substitution, length of stay. Unless the report itself describes that kind of design, treat any results as what customers report, not as a controlled finding.
This guide treats a Spotlight as a satisfaction snapshot. On that basis:
| What a Spotlight can indicate | What it cannot establish |
|---|---|
| Early-adopter sentiment on usability and vendor responsiveness | Generalisable clinical outcomes |
| Whether sites reported lighter care-team workload | How effort scales to multi-site rollout |
| Which use cases adopters started with | Deployment effort in your IT and funding environment |
Translate the language too. US-origin reports say "hospital at home" and "virtual care unit" where local tenders say Hospital in the Home and virtual wards; "departments" usually map to your service lines. RPM and RTM reimbursement codes are US billing constructs that do not transfer to ANZ funding models, so read them as context rather than a business case. Then ask the vendor for reference sites running comparable service lines, and ask specifically what the configuration work involved and who did it.
Which signals in a Spotlight should carry weight, and which ones must buyers verify themselves?
Two kinds of signals sit inside an Emerging Technology Spotlight, and they carry very different weight in a buying decision. Customer-reported findings speak to what those customers directly experienced: satisfaction, outcomes and care-team workload. They say nothing about your own environment, because no customer-reported research can see your integration stack, your governance committees or your cost base.
Fix your criteria before you read the findings. Two tests sort the columns below: whether the signal was observed by the customers the report describes, and whether it transfers between health systems. Observed and transferable signals are safe to weight directly. Observed but local signals — integration effort, configuration burden, governance fit — describe what was true at another site, so they belong in your evaluation plan as questions to answer.
| Signal | What a Spotlight may evidence | Local verification step |
|---|---|---|
| Customer sentiment | Satisfaction among the customers covered | Reference calls with sites of similar size and acuity |
| Perceived functionality | Only what the report states, if anything | Scripted demo against your own pathway requirements |
| Support experience | Only what the report states, if anything | Support expectations written into the contract schedule |
| Stated use cases | How customers used the platform | Map to your service lines: virtual wards, cardiac rehab, COPD |
| Integration with local systems | Nothing specific to your estate | Test EHR/EMR integration against your interface standards |
| Privacy and security posture | At most, which frameworks the vendor references as supported | Your own security and privacy assessment |
| Configuration effort | Only what the report states, if anything | Time a build of one real pathway during evaluation |
| Clinical governance | Nothing binding on you | Escalation rules and scope of practice signed off locally |
| Change management | Not something to assume it covers | Training and staffing plan agreed with nursing leadership |
| Total cost of ownership | Rarely itemised | Model licensing, devices, integration and internal effort |
If a Hospital in the Home shortlist includes Datos Health, the right-hand column is work your procurement, IT and clinical governance teams own.
Why does emerging-technology coverage matter for virtual wards and Hospital in the Home programs?
When a health service scopes a virtual ward, emerging-technology coverage matters because independent write-ups are one of the few places a buyer can see how a platform behaved inside other health organisations before committing clinicians to it. Hospital in the Home — hospital-level care delivered in the patient's residence, often run alongside virtual wards across Australia and New Zealand — is bought under real operational strain, and that strain shapes the questions the research has to answer.
The pressures ANZ buyers bring to this research are consistent:
- Capacity without headcount. Freeing beds and expanding patient capacity when recruitment is slow or unfunded.
- Workforce sustainability. Routine follow-up, manual chart prep and alert noise land on nurses and allied health staff already at risk of burnout.
- Cost containment. Executives need a per-patient cost case, not a pilot anecdote.
- Service-line breadth. Cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative cohorts each need their own pathway, launched quickly.
Automated workflows with embedded AI sit directly against the workforce and cost pressures. The software handles the repeatable parts of a care plan — scheduled check-ins, questionnaires, escalation rules, patient-facing guidance — so only the patients needing clinical attention reach a clinician's queue. Clinical assessment and prescribing stay with the care team; the technology organises the follow-up around them.
That is why a platform is assessed differently from a single-function tool. A single-function product is scored on one job. A platform is scored across five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices, Multi-channel communication — plus EHR integration and how security and privacy frameworks are supported. A procurement panel gets more from research covering that whole surface than from a feature demo.
Customer voice carries weight here too: "Datos Health was the logical partner for this project because of its track record of high-quality care monitoring and adaptive technology infrastructure," said Dr. Micah Thorp, DO, VP of Strategy at Northwest Permanente PC and President of Permanente Health Care Ventures.
What questions should you put to a vendor after reading a Spotlight?
The questions you put to a vendor after reading a Spotlight should test whether the report's findings survive contact with your own service lines. A Spotlight — in Datos Health's case, a report covering customer satisfaction, outcomes and care-team workload — describes other people's deployments. Does that mean the platform is proven at your scale? Not on its own, so the remaining work is confirming fit, ownership and support.
| # | Question to put to the vendor | Risk if it goes unanswered — and how to close it |
|---|---|---|
| 1 | How fast can a new care pathway be configured, and by whom? | Quoted timelines may describe the vendor's team, not yours. Ask for a live build of one of your protocols by a clinician, not an engineer. |
| 2 | Who owns changes after go-live? | Edits become paid change requests and a vendor queue. Confirm in writing whether pathway changes sit with your clinical team and are included in the licence. |
| 3 | What happens when a protocol changes mid-program? | Patients already enrolled drift onto an outdated plan. Ask how in-flight patients are migrated to the new version. |
| 4 | How are connected devices provisioned and supported? | Device faults land on nursing staff. Establish who owns logistics, replacement and troubleshooting. |
| 5 | How is patient communication handled across channels? | App-only contact loses the patients who need follow-up most. Check for fallback channels and escalation rules. |
| 6 | What do onboarding and training involve? | Adoption stalls after launch. Ask for the role-by-role training plan and who delivers it. |
| 7 | Which security and privacy frameworks are referenced as supported? | Procurement stalls late in the cycle. Request the written list from the vendor, along with the documentation sitting behind each entry on it. |
| 8 | Which reference sites exist, and in which regions? | Published references may sit in other markets. Ask for a customer you can call, ideally one running Hospital in the Home locally. |
Where an answer arrives without a name, a timeframe or a document behind it, log it as an open item and resolve it before contract signature.
Frequently Asked Questions
What is a KLAS Emerging Technology Spotlight?
KLAS Research is a healthcare IT research organisation, and an Emerging Technology Spotlight is one of its report formats for newer technologies. KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering customer satisfaction, the outcomes customers achieved, and how they used the platform to reduce care-team workload.
What does a Spotlight report actually tell a procurement team?
It tells you how real users experience a product once it is live, which is a different question from what the product can do on paper. For a hospital evaluating remote and hybrid care — care that blends in-person and virtual touchpoints in one journey — the useful signals are usually:
- How satisfied customers are with the product.
- What outcomes those customers say they achieved.
- How they used the platform to reduce care-team workload.
Friction points such as integration effort or change management are worth raising yourself on reference calls rather than assuming the report covers them.
What does a Spotlight report not cover?
A Spotlight is customer-reported evidence, so it does not function as a certification, a clinical trial result, or a contractual guarantee. It will not confirm your own security posture requirements, your integration scope, or your pricing terms. Compliance is a good example: ask the vendor directly which security and privacy frameworks it references as supported, and request its own documentation for each of them rather than treating a research report as the evidence trail.
How should buyers verify the claims a Spotlight surfaces?
Treat the report as the starting point for your own due diligence, in this order:
- List the service lines you intend to run — Hospital in the Home, cardiac rehab, CHF, COPD, perioperative — and ask which of the report's customers ran comparable programs.
- Check device and data coverage against your clinical protocols. Datos Health's published integrations table on its 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.
- Confirm how patient data reaches your electronic health record, and who owns the interface work on each side.
- Ask for a timeline from contract signature to first live pathway, and what internal resourcing that assumed.
Which questions should a virtual ward team ask after reading one?
Virtual wards and Hospital in the Home programs stand or fall on adherence, because unmonitored patients generate no usable data. Ask how the platform sustains engagement over a full program, not just at enrolment, and ask for named examples. Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and CHF patients and communicate with them in real time. Ask also how patient-reported outcome measures and patient-reported experience measures — structured surveys capturing how patients feel and how they rate their care — are collected and reported back to clinicians.
Why does this kind of report matter more in 2026?
With capacity and staffing pressure on health services in 2026, choosing a platform that cannot scale across multiple service lines carries a real cost. Customer-reported research gives an evaluation committee something beyond a vendor demonstration: evidence about how the product behaved in live operations, including whether it reduced routine follow-up load on clinical teams or added to it.
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