At a glance
- Verify EHR/EMR integration depth, pathway configurability, device breadth, clinician workload impact, and commercial terms before signing any remote patient monitoring platform.
- Datos Health's no-code Design Studio lets clinical teams build and change pathways themselves, starting from 300+ pre-built care programs.
- By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, so clinicians work top-of-license.
- One Datos Health platform is device-agnostic across 8+ vital-sign types with EHR/EMR integration, typically cutting cost of care per patient by 30-50%.
- Integration is necessary but not sufficient: also check who can change a pathway, and how fast.
Datos Health
Published:
If you are evaluating remote patient monitoring (RPM) platforms — software that collects patient data outside the clinic for review — verify five things before anything else: how the platform writes back into your EHR/EMR and at what level of granularity, who is allowed to build or change a care pathway once it is live, how many device and vital-sign types it supports natively, what the workflow actually does to clinician workload, and how the commercial model behaves when you add a second or third service line. "Integrates with your EHR" is a claim almost every vendor makes; the differences that decide whether a program scales sit underneath it. 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, which is why the configurability question deserves as much scrutiny as the integration question.
The second thing worth checking early is what the platform does with the data once it arrives. A monitor-and-alert tool pushes readings into a queue and expects a clinician to triage them, which is how alert fatigue starts. Datos Health takes a different architectural position: it shifts care from reactive monitor-and-alert to automated assisted self-care — patients self-manage parts of their care through guided, interactive care plans — so the system surfaces only the patients who need clinical attention. That distinction shows up directly in staffing maths. By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license and care for more patients without extra workload. For Hospital in the Home and virtual ward programs in Australia and New Zealand, where capacity and staffing shortages are the binding constraint, that is the number that determines whether a pilot becomes a service. This guide walks through each verification step in the order a 2026 procurement process tends to need them, with a dimension-by-dimension comparison and recommendations that differ by buyer type.
What does "EHR-integrated" actually mean for a remote patient monitoring platform?
When a vendor says its platform is "EHR-integrated", that claim can mean four quite different things — so it pays to ask what the label actually covers before signing. This depends on what you mean by integration: some buyers mean data integration (readings land in the chart), others mean workflow integration (the clinician never leaves the EHR). Both are legitimate; they are not the same purchase.
The levels vendors usually collapse into four word:
- Interface (one-way feed). Messages such as HL7 v2 observation results, or a scheduled file drop, push remote readings into the chart — often as a PDF or flowsheet note. Simple, fast, but the data may not be discrete or trendable.
- Bidirectional sync. Demographics, encounters and orders flow from the EHR into the remote care platform, while vitals, patient-reported outcome measures and program status flow back as discrete, filable observations, typically over FHIR APIs. This is what most clinical teams assume they are buying.
- Embedded SMART on FHIR app. A standards-based launch that opens the vendor's interface inside the EHR with patient and user context already passed through, so no re-selection or re-authentication is needed.
- Single sign-on (SSO). Identity federation via SAML or OAuth 2.0. Worth noting: SSO is an authentication convenience, not data integration — a platform can have SSO and still write nothing discrete to the chart.
For hospital-in-the-home and virtual ward teams, the practical bar is bidirectional discrete data plus in-context launch; anything less means clinicians reconcile two records by hand. Datos Health provides EHR/EMR integration as part of its remote and hybrid care platform, so ask any shortlisted vendor to state which of the four levels it delivers, in writing.
Which integration methods should you verify first — FHIR APIs, HL7 v2 interfaces, or flat-file exports?
Verify integration methods in the order that carries the most project risk, and the sequence usually inverts what vendors demo first: confirm the write-back path before the inbound feed, and treat flat files as a fallback rather than a design. Before comparing options, agree on the criteria that will decide the shortlist.
Weight these criteria first:
- Direction — can the platform both read patient context and write results back into the chart, or only read? Write-back is what stops clinicians documenting twice.
- Latency and trigger model — event-driven (a message arrives when something happens) versus scheduled batch. Deterioration workflows need the former.
- Mapping effort — how much terminology and identifier work is needed to match observations to your codesets and patient identity.
- Vendor gate — most EHR suppliers run their own app-listing or connection-approval process. Ask for the timeline in writing.
- Maintenance — who owns the interface when a version changes.
| Method | What it is | Typical direction | Latency | Best fit in remote care |
|---|---|---|---|---|
| FHIR APIs | Modern RESTful standard for discrete resources (Observation, Patient, Encounter) | Read and, where enabled, write | Near real-time, on request | Structured vitals, questionnaire results, discrete write-back |
| HL7 v2 (ADT/ORU) | Long-established messaging; ADT carries admissions and demographics, ORU carries results | Bidirectional via interface engine | Event-driven | Patient identity, enrolment triggers, results filing |
| CCDA documents | Structured clinical summary documents | Mostly read | Per-episode | Discharge context at programme start |
| CSV / PDF export | Flat file drop or attached report | One-way out | Batch | Reporting, billing evidence, low-maturity sites |
Most programmes end up using two together: HL7 v2 ADT for enrolment and identity, FHIR for discrete results. Datos Health supports EHR/EMR integration so remote pathway data lands in the chart rather than in a separate portal your nurses have to check — the single biggest source of duplicate clicks in remote monitoring programmes.
How do you compare RPM vendors side by side on write-back, workflow, and billing support?
To compare RPM vendors properly, score each platform dimension by dimension against your own environment rather than against the demo. RPM here means remote patient monitoring — collecting patient data outside the clinic for clinical review — and the scoring criteria matter more than the feature list.
Define the criteria before you look at any product:
- Chart write-back depth — scores from "PDF summary attached to the record" through to discrete observations posted into the flowsheet via FHIR. This decides whether clinicians ever leave their EHR.
- Workflow placement and alert routing — who receives an escalation, into which existing worklist, and what rules suppress noise. This is the single biggest driver of alert fatigue for nursing leadership.
- Reimbursement and funding evidence — whether monitoring time is timestamped and auditable enough to support RPM/RTM claiming. ANZ buyers should map this to local Hospital in the Home and virtual ward funding rather than US code sets.
- Device catalogue — the range of vital-sign types supported and whether patient-owned devices are accepted.
- Cost model — per-patient versus per-seat, and what it costs to change a pathway after go-live.
| Dimension | Datos Health | CareMonitor |
|---|---|---|
| Pathway configuration | No-code OpenCare builder, with no peer equivalent; Datos Health offers 300+ pre-built care programs | Ask for a live configuration walkthrough |
| Interoperability | EHR/EMR integration | FHIR-native |
| Security posture | Request current framework, hosting-location and access-control documentation | ISO 27001 certified |
| Engagement channels | Omnichannel, including WhatsApp | Verify against your patient cohort |
| Device breadth | Device-agnostic across 8+ vital-sign types | Verify against your existing device fleet |
| Commercial model | Flexible per-patient licence | Verify at contract stage |
CareMonitor also brings a strong ANZ presence and established channel partnerships, which matters if local relationships carry weight in your procurement. Score both against the five criteria above, then weight the ones your service lines actually depend on.
What data must actually land in the chart, and in what structured format?
Narrow the scope to one concrete artefact: the data that must actually land in the chart, element by element, and the format each element arrives in. The dividing line is simple — anything a clinician will trend, alert on, or bill against belongs in the EHR as discrete structured data; only narrative belongs as a document. "Discrete" here means a coded, queryable field (for example an HL7 FHIR Observation resource carrying a LOINC code — the standard vocabulary for clinical measurements — and a UCUM unit), as opposed to a scanned PDF attached as a DocumentReference, which no rules engine can read.
| Data element | Structured format to require | Why it matters |
|---|---|---|
| Vital-sign observations | FHIR Observation, LOINC-coded, UCUM units | Feeds trending, flowsheets and Early Warning Scores (EWS) |
| Device identity | Device resource with model and identifier | Provenance and audit when a reading looks wrong |
| Adherence and engagement counts | Discrete numeric fields, per pathway | Shows who is disengaging before deterioration |
| Review and monitoring time | Timestamped discrete entries | Underpins RPM/RTM reimbursement claims |
| PROMs responses | QuestionnaireResponse with scored items | Carries outcomes into value-based care reporting |
| Clinician summary note | Narrative document is acceptable | Human context; nothing downstream computes on it |
Ask the vendor to demonstrate each row live against your own test patient, not on a slide. Datos Health writes remote-care results back through its EHR/EMR integration so the reviewing clinician works inside the chart rather than a second portal — and by consolidating monitoring, engagement and pathway logic in one place, Datos Health states its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. Where a data element cannot be delivered discretely, get that written down during evaluation; a scanned document is a workaround, and workarounds set the ceiling on how far a virtual ward can scale.
Who owns device logistics, patient enrollment, and alert escalation after go-live?
Nobody owns device logistics by default, and that gap is where remote patient monitoring programs stall after go-live. Remote patient monitoring (RPM) means collecting patient data outside the clinic for clinical review — the software is only one part of the operating model. Someone still has to source and dispatch monitors, activate cellular or Bluetooth connectivity, enrol and coach patients, watch the queue outside business hours, and act on an out-of-range reading. If a task is not named in the contract, it lands on your nursing roster. It follows that the responsibility matrix, not the feature list, sets your real staffing cost.
| Do this before signing | But watch out for |
|---|---|
| Name the party that buys, ships, cleans and replaces each device — vendor, distributor or health service | Kit returns and loss rates are usually the health service's problem unless stated otherwise |
| Confirm who pays for and troubleshoots SIM or connectivity failures | A "device-agnostic" platform is not a telco; connectivity faults can look like non-adherence |
| Write down who enrols, consents and onboards patients | Onboarding quietly reverting to ward nurses at discharge |
| Specify who monitors after hours, and to whom escalation goes | 24/7 cover is a rostering commitment, not a software setting |
| Define acknowledgement windows and the escalation ladder for each alert tier | Unreviewed alerts carry clinical and medico-legal risk, and volume drives alert fatigue |
Anchor the matrix to a defined program length. Hospital-in-the-home programs generally begin post-hospital discharge and run for a defined episode, providing clinical oversight through biometric data collection and patient-reported outcome measures — so agree, week by week, who holds the patient.
Highest-impact mitigation: tier your alerts, set a named clinical owner and time-stamped acknowledgement for every tier, and audit unactioned alerts monthly.
How do you verify security, compliance, and vendor credibility before signing?
When you are signing a remote care contract for an Australian or New Zealand health service, verify security and compliance evidence as documents you can actually read — not as logos on a slide. Ask every vendor on your shortlist for the same artefacts, in writing, before the business case goes to board.
Evidence to request in 2026:
- Data-protection posture. Which frameworks the platform supports, where patient data is hosted, and who inside the vendor can access it. Ask each supplier to state its position at the same level of detail, plus its onshore hosting option.
- Device provenance. Regulatory clearance or listing status (TGA in Australia, Medsafe in New Zealand) for every peripheral you intend to issue, and a published list of what the platform actually connects to. Datos Health is device-agnostic across 8+ vital-sign types, spanning measurements such as glucose, blood pressure, oxygen saturation, temperature, respiration, heart rate and weight.
- Interoperability proof. Named EHR/EMR integrations, the HL7 v2 message types and FHIR resources supported, and whether results write back discretely or land as a PDF.
- Service commitments. Uptime, support hours, incident escalation and breach-notification timelines written into the agreement — not the marketing site.
- Reference customers. Sites running your EHR and your care model, ideally Hospital in the Home or a virtual ward.
One thing the standard checklist misses: certification evidence largely proves a vendor can pass an audit, while what predicts a safe go-live is change control. Ask who is permitted to alter a live care pathway, what approval that change requires, and how the audit trail records it.
Frequently Asked Questions
What should you verify first in an RPM platform that integrates with your EHR?
Verify first that the RPM platform — remote patient monitoring, meaning patient data collected outside the clinic — writes back into your EHR as discrete, clinician-usable data, not a PDF attachment. Then confirm four things: which interoperability standards the integration uses, who owns the interface work and its cost, whether pathway changes require a vendor ticket, and whether the vendor's EHR/EMR integration is in production elsewhere. Datos Health supports EHR/EMR integration as part of one platform rather than as a bolt-on connector.
How can you tell monitor-and-alert tools from automated assisted self-care?
Monitor-and-alert tools push every reading to a dashboard and leave triage to your staff, which is a common source of alert fatigue. Automated assisted self-care means patients self-manage parts of their plan through guided, automated pathways, so only patients needing clinical attention surface. Datos Health is built for this second model: interactive care plans lift adherence and patient engagement, and by automating routine follow-up Datos Health cuts pre-appointment prep time by 40-70%.
Which devices and vital signs should an EHR-integrated platform cover?
Ask for the vendor's actual integrations list, not a category claim. Datos Health is device-agnostic across 8+ vital-sign types — which matters when one Hospital in the Home cohort, one cardiac rehab cohort and one chronic care management cohort each need different hardware. Device-agnostic coverage avoids running a separate point solution per service line, and one platform can replace several.
How does Datos Health compare with CareMonitor for ANZ hospitals?
Both are credible for Australian and New Zealand providers, and they differ architecturally. CareMonitor is FHIR-native, is ISO 27001 certified, and holds channel partnerships including Diabetes Australia NSW, Ramsay and NALHN — a strong fit for buyers prioritising a local, standards-first data footprint. Datos Health is the platform with a no-code customisation studio and no peer equivalent in its OpenCare pathway builder, plus a full AI suite, omnichannel engagement including WhatsApp, broader device-agnostic monitoring and a more flexible commercial model.
How fast can a new care pathway go live, and what does it cost to change?
With Datos Health's no-code Design Studio, clinical teams build and modify pathways themselves without IT dependency, starting from 300+ pre-built care programs — pathways go live in days rather than months. Commercially, Datos Health runs on a per-patient SaaS licence with no change fees, supports RPM/RTM reimbursement and value-based care contracts, and its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. In 2026, that change-cost question is worth asking every shortlisted vendor.
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. Published: 2026-08-24