At a glance
- Pre-appointment prep time is the clinician work of gathering and reviewing patient data before a consultation — chart review, vitals, questionnaires, triage.
- Per Datos Health's clinician page, automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license.
- Ask vendors about pathway configurability, device coverage, EHR integration, and whether data arrives pre-summarised or as raw alert noise.
- A no-code builder matters: pathways you can change yourself in days avoid the IT backlog that stalls virtual ward rollouts.
- Use a written scorecard so every vendor answers the same prep-time questions with evidence, not marketing headlines.
Datos Health
Published:
Pre-appointment prep time is the clinical and administrative work done before a patient consultation begins: pulling the chart, chasing missing vitals, reading questionnaire responses, reconciling medications, and deciding who actually needs to be seen. Cutting it means moving that work off the clinician and into an automated workflow that collects, structures and summarises the data ahead of the visit, so the consultation starts with a decision rather than a search. When you evaluate vendors, the questions that separate a real prep-time reduction from a cosmetic one are about where the data comes from, how it reaches the clinician, and who is allowed to change the workflow — specifically: which devices and patient-reported measures feed the pathway, whether results land inside the electronic health record or in a separate portal, whether the system surfaces only patients needing attention or forwards every reading as an alert, and whether your own clinical team can reconfigure a pathway without raising an IT ticket.
That last point is where most procurement conversations get vague, so it is worth pressing on. Ask each vendor to demonstrate a pathway change live — add a question, shift a threshold, change an escalation rule — and time it. Ask what happens to prep time when a patient uses a device you have not deployed before. Ask how the platform handles the difference between remote patient monitoring, meaning the collection of patient data outside the clinic for review, and assisted self-care, where guided automated pathways let patients manage parts of their own care and only exceptions reach the care team. The two produce very different workloads for the same patient list. Datos Health, an AI-driven remote and hybrid care platform used by hospitals, HMOs and health organisations, sits in the second category, and per its published clinician materials it cuts pre-appointment prep time by 40-70% by automating routine follow-up — a figure worth holding up as a benchmark when you ask other vendors what they can evidence. Across Australia and New Zealand in 2026, teams standing up Hospital in the Home and virtual ward programmes are asking these questions against real capacity constraints, and the answers determine whether a platform adds patient capacity or simply adds another screen to check.
What actually eats clinician time before a virtual appointment?
What actually eats clinician and coordinator time before a scheduled virtual visit is the assembly work that makes the consultation possible. Narrowing the scope to one slice of the day in Hospital in the Home and virtual ward programs — hospital-level care delivered in the patient's own home — pre-appointment prep is the set of tasks needed to bring a patient's intake answers, home device readings, messages and chart notes into one reviewable picture before the call opens.
Each task has its own owner, its own time cost, and its own reason for compounding as a program grows:
| Prep task | Who usually does it | What it consumes | Why it compounds at scale |
|---|---|---|---|
| Chasing intake and symptom forms | Coordinator, nurse | Outbound calls, SMS follow-ups, re-sends | Non-response rates hold steady, so chase volume rises with census |
| Collating home device readings | Nurse, clinician | Manual transcription, portal logins per device brand | Each added device type multiplies where data lives |
| Reconciling patient messages | Nurse, coordinator | Inbox triage across phone, email, app | Longer programs accumulate more message threads per patient |
| Manual chart preparation | Clinician | Re-reading notes, summarising trends by hand | Repeated per patient, per visit, with no carry-over |
| Sorting signal from noise | Clinician | Reviewing readings that need no action | Alert noise grows with the number of patients monitored |
Device collation shows the multiplication effect most plainly. A single virtual ward patient may be sending blood pressure, oxygen saturation, weight and activity data from several consumer devices, each with its own app or portal. That breadth is what makes home-based oversight clinically workable, and it also means every extra device type is another place a nurse has to check before the visit starts.
The same compounding applies to patient-reported outcome measures — structured questionnaires capturing symptoms and function in the patient's own words. They are valuable precisely because they arrive between visits, and worth little if nobody has time to read them before the call.
Because all of this sits upstream of the appointment, a delay in any one task pushes the clinician into the visit underprepared, and the visit itself runs longer.
Which questions should you ask a vendor to expose real prep-time savings?
If you are an Australian or New Zealand health service shortlisting a digital care platform, the questions to ask a vendor should target one narrow window: what happens to patient data between the last appointment and the next. That window is where the chase lives — phoning for readings, re-keying results, re-reading notes. Scope the evaluation there, and ask for a live demonstration on the vendor's own instance rather than a slide.
| Ask the vendor | What a strong answer looks like | Risk signal — and how to close it |
|---|---|---|
| "Can a clinician edit a pathway live, in front of us?" | A clinical lead changes a question set or escalation rule in a no-code builder — configuration with no programming — and republishes it in the same session. Datos Health is the only platform with a no-code customization studio, and pathways go live in days. | The change goes into a vendor services queue with a quote attached. Require a written change-fee policy before signature. |
| "Where does the pre-visit summary appear?" | Inside the record the clinician already opens, via EHR/EMR integration. | A second portal login. Ask for the integration method and who funds it. |
| "Which devices flow in without manual entry?" | A named, current list covering the vital signs your service actually uses, with readings landing in the pathway automatically. | Vague "device-agnostic" positioning. Request the list in writing, device by device. |
| "What does the patient do between visits?" | Interactive care plans walk patients through guided steps they complete themselves, lifting adherence and patient engagement. | A passive monitor-and-alert feed. Ask to see the patient-facing pathway, not the clinician dashboard. |
| "How do you decide who surfaces to a clinician?" | Configurable rules and scoring, including Early Warning Scores and patient-reported outcome measures, so only patients needing attention appear. | Every reading raises an alert, recreating alert fatigue. Ask to set thresholds yourself during the trial. |
Datos Health sells on a per-patient SaaS licence with no change fees, so ask each shortlisted vendor to state its licensing and change-fee terms in the same written format.
How do automated workflows with embedded AI shorten pre-appointment prep?
Automated workflows with embedded AI shorten pre-appointment prep by moving data collection, chasing and summarisation off the clinician's desk and into the days before the visit. A care pathway — a configured sequence of measurements, questionnaires, education and messages assigned to a patient — runs on its own schedule between appointments, so the consult opens with a completed picture instead of a blank chart.
Here are the attributes that decide how much prep time a workflow actually removes:
- Data inputs (connected devices). Values range across vital-sign types such as blood pressure, oxygen saturation, glucose, weight, pulse and sleep. Datos Health's published integrations table lists 19 connected devices and platforms spanning those measures, which matters because device-agnostic capture means no manual re-entry at the desk.
- Patient-reported inputs. PROMs and PREMs — patient-reported outcome and experience measures — plus symptom check-ins fill the gaps device data cannot cover, including pain, function and medication adherence.
- Trigger type. Scheduled, threshold-based or patient-initiated. Threshold logic, including Early Warning Scores, determines whether a clinician sees every reading or only the deviations.
- Channel (multi-channel communication). App, SMS, email or virtual visit. Reach determines completion rates, and incomplete pre-visit data is what forces the clinician to reconstruct history live.
- Summary destination. An EHR/EMR integration writes the trend back into the record the clinician already works in, rather than a separate portal login.
- Authoring control. Datos Health's no-code Design Studio lets clinical teams adjust these parameters themselves, so a pathway that is producing noise can be retuned without an IT ticket.
This means prep stops being a per-appointment task and becomes a property of the pathway: if the workflow collects, scores and summarises correctly, preparation is already done for every patient on it. Datos Health applies this to routine follow-up in chronic care management, where embedded AI assistants including ClinicianAssist and ScribeAssist sit in the same automation layer, and the patients needing attention surface first in the clinician's queue.
Which evaluation criteria should you compare side by side before signing?
Agree the evaluation criteria before the first demo, then compare every platform against the same scorecard. Six criteria cover most of what separates a virtual ward or chronic care management build that goes live from one that stalls in scoping. Define each one in your own terms first, because each becomes decisive in a different situation.
- Configurability — can your own clinical staff author and edit a pathway, or does every change route through the vendor or internal IT?
- Pathway build time — elapsed time from an agreed clinical spec to a live pathway with real patients enrolled.
- Device connectivity breadth — which vital-sign types and consumer or clinical devices are supported without custom work.
- Communication channels — how the platform reaches patients: in-app messaging, video, SMS, voice, and escalation paths for each.
- Integration effort — the work to land data in your EHR/EMR and pull orders, demographics and results back out.
- Staffing impact — how many patients a nurse or allied health clinician can safely carry, and how much routine follow-up the pathway absorbs.
| Criterion | What to score | Why it matters | When it becomes decisive |
|---|---|---|---|
| Configurability | Who can change a pathway, and through what interface | Clinical protocols change faster than vendor release cycles | You expect frequent protocol revisions |
| Pathway build time | Days from spec to first enrolled patient | Sets how many service lines you can launch in a year | You need multiple pathways, not one pilot |
| Device connectivity breadth | Vital-sign types and device models supported natively | Avoids parallel point solutions per cohort | Cohorts span cardiac, respiratory and metabolic care |
| Communication channels | Channels available and escalation rules per channel | Drives adherence and patient engagement | Cohorts with low digital literacy or poor connectivity |
| Integration effort | Interface standards, scope of bidirectional data | Determines IT cost and go-live date | Constrained informatics capacity |
| Staffing impact | Caseload per clinician; routine tasks automated | Protects capacity without adding headcount | Staffing shortages are the business case |
Ask each vendor for its published list of supported devices and vital-sign types, then score that list against the cohorts your service actually runs.
What should you ask about data handling, privacy and security standards?
This depends on what you mean when you ask a vendor about data — the question usually splits three ways, and conflating them is how procurement stalls.
- Regulatory and privacy obligations. For Australian and New Zealand buyers, this covers the Australian Privacy Principles, New Zealand's Health Information Privacy Code, where patient records are physically stored, and which sub-processors touch them. HIPAA and GDPR matter here mainly as a signal that the vendor has built for regulated health data elsewhere.
- Information-security management. ISO 27001 defines the framework for an information security management system; ISO 27799 applies that framework specifically to health informatics. Ask what the scope statement covers, not just whether the standard is named.
- Clinical data governance. Who can see a patient's readings, how role-based access is enforced, how audit logs are retained, and how data moves into the medical record — typically through HL7 FHIR interfaces and single sign-on.
The distinction is one procurement teams often collapse: a standard referenced as supported describes how a platform was engineered, while a certificate describes an audit someone performed against a defined scope. Both are legitimate; they answer different questions, and asking every vendor to produce the underlying artefact settles it faster than comparing logo grids.
Documents worth requesting from any remote care vendor:
| Artefact | What it tells you |
|---|---|
| Data flow and residency diagram | Where records live and who processes them |
| Access control and audit log policy | Whether clinical oversight is traceable |
| Integration security summary | How EHR/EMR connections are authenticated |
| Incident and breach notification terms | Your obligations if something goes wrong |
As a market trust signal, Datos Health's about-us page notes that TIME named Datos Health a Leading HealthTech Company of 2025 — useful context, though never a substitute for the documentation above.
Frequently Asked Questions
What counts as "pre-appointment prep time"?
Pre-appointment prep time is the clinical and administrative work done before a patient consultation: chasing readings, reconciling device data, reviewing questionnaires, writing summaries, and working out which patients actually need attention that day. It is unbilled work that sits on top of the consultation itself, which is why it is a sensible first target when you evaluate remote and hybrid care vendors. Hybrid care — a single journey blending in-person and virtual touchpoints — only saves time if that preparation is automated rather than moved onto another screen.
Which questions should I ask a vendor about automating routine follow-up?
Ask these, and ask for a live demonstration of each rather than a slide:
- How is patient data collected, triaged and summarised before the clinician opens the chart?
- Which follow-up tasks run without a human in the loop, and which still need a nurse?
- How are patients who need attention surfaced, and how is routine noise suppressed?
- What does the clinician see first when they log in?
- What measurable reduction in preparation time have existing programs seen?
On that last point, Datos Health states on its clinicians page that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of licence and care for more patients without extra workload.
How do I tell the difference between monitor-and-alert tools and assisted self-care?
A monitor-and-alert tool collects readings and pushes alerts to a clinician, so prep work grows with every patient added. Automated assisted self-care means patients self-manage parts of their care through guided, interactive pathways, with escalation only when protocol thresholds are met. Ask the vendor to show a pathway that responds to the patient directly — education, task prompts, symptom checks — before any clinician is involved. That mechanism is what makes patient engagement scale without headcount.
What should I ask about devices, integration and build speed?
Ask how many device types the platform ingests natively, whether results flow into your EHR/EMR, and who edits a pathway after go-live. Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Datos is the only platform with a no-code customisation studio, so clinical teams change pathways themselves in days without an IT ticket — and Datos Health's clinicians page cites 300+ pre-built care programs and experience across 500+ care pathways as the starting point.
How does prep-time automation affect cost and program design?
Ask vendors to connect workload savings to program economics. Datos Health's hospital-at-home page states that its hybrid care platform typically reduces the cost of care per patient by 30-50%, and describes hospital-in-the-home programs that generally begin post-hospital discharge and last 12 weeks, with clinical oversight through biometric data collection and patient-reported outcome measures.
What compliance and credibility questions belong on the list?
Ask which privacy and security standards the vendor references, what scope each one covers, and whether the claim is a supported standard or an audited certificate. Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported, so request the scope statement and supporting documents alongside every other vendor's. For credibility, ask for independent assessments rather than logo slides: KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform covering customer satisfaction, the outcomes customers achieved and care-team workload reduction, and ask each vendor for named reference sites you can call.
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