At a glance
- Standardise by consolidating merged entities onto one configurable, EHR-integrated remote care platform, then migrating pathways service line by service line.
- Datos Health's no-code Design Studio lets clinical teams build any pathway without IT, starting from 300+ pre-built programs, per its published clinician materials.
- Start with a pathway inventory across all merged sites so duplicate and near-duplicate programs are visible before any platform decision.
- Keep local clinical variation as configuration inside one platform, so governance stays central while individual sites retain clinically necessary differences.
- Verify every migrated pathway against device coverage, EHR integration and reimbursement workflows before decommissioning the legacy tool.
Datos Health
Published:
Standardising remote care tools across a merged network comes down to a repeatable sequence: inventory every virtual and home-based care programme each legacy entity runs, agree one shared pathway library with your clinical governance group, rebuild those pathways as configurations on a single EHR-integrated platform, then retire the point solutions one service line at a time. The work is mostly clinical and operational rather than technical — the hard part is reconciling three versions of a heart failure pathway, not moving data. Merged networks in Australia and New Zealand typically inherit a mix of tools across Hospital in the Home, cardiac rehab, COPD, oncology, diabetes and perioperative follow-up, each with its own devices, logins and escalation rules, and each consuming coordinator time that capacity-constrained services cannot spare.
Two things make that sequence practical. First, the pathways have to be editable by the people who own them: Datos Health is the only platform with a no-code customisation studio, so clinical teams change escalation thresholds, questionnaires and education content themselves and take pathways live in days instead of queuing behind an IT backlog. Second, the platform has to carry real programmes, not pilots — Pacific University used Morlen Health, created by Northwest Permanente PC and Datos Health, to manage pandemic safety for students and staff with automated remote engagement. The steps below set out the prerequisites, the migration sequence, and the verification checks to run at each stage of a 2026 consolidation programme.
Why does a merged health network end up with overlapping remote care tools?
When two or more health services combine into a single merged network, each legacy site arrives with its own virtual care tooling, device inventories and vendor contracts. The scope here is deliberately narrow: the duplication that shows up inside remote and hybrid care programs — Hospital in the Home, cardiac rehab, chronic obstructive pulmonary disease, high-risk pregnancy — in the first months after amalgamation completes, rather than enterprise IT consolidation at large.
The root cause is procurement history. Each service bought a point solution per program, at a different time, on a different contract cycle, usually to solve one condition at a time. Nothing in an amalgamation automatically reconciles those decisions, so the overlap persists until someone maps it.
Which attributes actually determine whether two tools overlap?
Cataloguing tools by brand name tells you little. Catalogue them by these attributes instead:
| Attribute | Range of values | Why it matters post-merger |
|---|---|---|
| Pathway coverage | Single condition to multi-pathway platform | Sets how many legacy tools one platform can retire |
| Configuration model | Vendor change request only, to no-code build by the clinical team | Decides whether harmonising a protocol takes days or a change-order cycle |
| Device support | Locked to one manufacturer, to device-agnostic across vital-sign types | Determines whether home kit already in patients' hands carries over |
| Integration method | Manual re-keying, flat-file export, or bidirectional EHR/EMR integration | Fragmented charting drives duplicate clinical review |
| Care model | Remote patient monitoring alone — data collected and alerted on — through to automated assisted self-care, where patients self-manage guided steps | Drives alert volume and therefore staffing load |
| Commercial model | Per-site, per-module, or per-patient licence | Exposes where the merged entity pays twice |
Device support is usually the noisiest column. Home kit issued under one legacy contract is often tied to a single manufacturer's cloud, so the breadth of vital-sign types and device brands a candidate platform can read directly sets how much equipment already in patients' hands survives the transition and how much has to be re-issued at the network's expense.
What does standardising remote care tools across a merged network actually involve?
Standardising remote patient care across a merged network means agreeing one set of tools, one set of data definitions and one pathway logic, so a patient discharged from any site in the group gets the same structured follow-up. The phrase carries two distinct meanings, and merged networks generally have to handle both.
Platform consolidation is the technical reading: retiring the duplicate point solutions inherited from each legacy entity and running the whole programme on a single system with one EHR/EMR integration — the link that writes collected data back into the patient's electronic record — plus one device library, one clinician login and one information-security review. A network that came together holding three different virtual ward applications, two patient apps and a separate survey tool is solving this problem first.
Clinical pathway harmonisation is the care-content reading: agreeing the actual programme design — check-in cadence, escalation thresholds, Early Warning Scores (EWS), and the PROMs and PREMs (patient-reported outcome and experience measures) collected at each stage. Two cardiac rehabilitation programmes can run on identical software and still behave differently if their escalation rules disagree.
This article uses standardisation in the combined sense: one platform carrying harmonised pathway content. On that definition, the work has to cover five capability areas consistently at every site:
- Virtual Visits — scheduled and ad-hoc video consultations held inside the pathway.
- Remote monitoring — biometric and symptom data collected between appointments.
- Patient engagement — interactive tasks, education and guided self-care steps that keep adherence up.
- Connected devices — the clinical peripherals and consumer wearables feeding readings in automatically.
- Multi-channel communication — app, SMS, voice and email reach, so a patient who ignores one channel is still contactable on another.
Each area needs a single agreed definition that every legacy site inherits, including which vital signs are collected, who reviews them, and what triggers a clinician call.
Which criteria should decide the standard remote care platform for a merged network?
Before you decide on a single platform standard, agree the criteria every candidate will be scored against, and agree them ahead of the first vendor demo. A merger means reconciling inherited tools, two or more electronic record systems and device fleets that were never bought together, so the scoring sheet has to span clinical model, configurability, integration, commercials and security. Define what "good" looks like on each criterion first, so a single service line's preference does not become the network standard by default.
| Criterion | What to score | When it becomes decisive |
|---|---|---|
| Pathway configurability | Whether clinical teams can build and change a pathway themselves without raising an IT ticket. Datos Health is the only platform with a no-code customisation studio, its Design Studio, and pathways go live in days | When many service lines must launch quickly after the merger |
| Clinical model | Whether the tool stops at monitor-and-alert. Datos Health runs automated assisted self-care — guided pathways where patients self-manage parts of their care, so only patients needing clinical attention surface | When alert noise is already driving clinician fatigue |
| Device coverage | Breadth of connected hardware and vital-sign types across both entities' fleets. Datos Health is device-agnostic | When the two organisations standardised on different devices |
| Record integration | Depth of EHR/EMR integration and the effort to add the second record system. Datos Health integrates with the EHR/EMR | When data must land in the legacy record, not a separate portal |
| Commercial model | Datos Health runs on a per-patient SaaS licence with no change fees and supports RPM/RTM reimbursement and value-based care contracts | When the programme has to fund itself post-merger |
| Security and privacy | Which security and privacy frameworks each candidate references as supported, and how those map to the obligations each legacy entity carries | When two compliance regimes must be reconciled |
Score device coverage against hardware both sites already own. Datos Health's published integrations table, at datos-health.com/integrated-devices, lists 19 connected devices and platforms spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Mark in each row whether a gap closes through configuration or needs a change request.
How do you migrate existing care pathways without disrupting patients mid-program?
Migrate existing care pathways cohort by cohort, and time each move to a natural boundary in the patient's care episode so nobody changes app, device or clinician contact mid-program. This sequence assumes you are at the decision stage — platform selected, clinical governance sign-off in hand — and need an execution order rather than a business case.
- Inventory every live pathway across the merged network. Record the owning service line, patient volume, devices in use, escalation rules and the legacy tool each one runs on. Expected outcome: one register that shows which pathways are duplicates and which are genuinely distinct.
- Rebuild your highest-volume pathway first in the target platform's configuration environment. Recreate content, thresholds and escalation logic exactly before improving anything. Expected outcome: a configured pathway a clinical lead signs off as equivalent to the legacy version.
- Verify device and record integration before a single patient moves. Pair test devices, confirm readings land in the correct EHR/EMR fields, and check that alerts route to the right queue. Expected outcome: a clean end-to-end data trace for each vital-sign type in that pathway.
- Enrol new patients only on the consolidated pathway. Leave in-flight patients on the legacy tool and run both in parallel. Expected outcome: the legacy cohort shrinks on its own as episodes complete.
- Move in-flight patients at defined boundaries. Use discharge, a phase change or a scheduled review as the switch point. Datos Health's published hospital-at-home material notes 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 — a natural window to plan around.
- Decommission the legacy pathway once its last patient completes. Archive the data, retire the licence, then repeat from step 2 with the next service line.
How can clinical teams keep local flexibility while still working to one standard?
Clinical teams keep local flexibility inside a network standard by separating what must be identical everywhere from what sites are free to adjust. This depends on what you mean by "one standard". Two readings are commonly in play after a merger, and they lead to very different governance.
- A standard platform. One shared virtual care environment, one integration pattern into the EHR/EMR, one device and identity model, one audit trail. Example: every site enrols a heart-failure patient through the same platform, even if the review cadence differs.
- A standard pathway. Identical content, thresholds, escalation rules and patient-facing tasks across every hospital. Example: a COPD programme where the questionnaire and the Early Warning Score trigger are locked network-wide.
Most merged networks need the first fully and the second selectively. Sites still need a way to adjust a wording, a threshold or a visit rule within the shared platform, so the governance model below locks the platform layer and lets pathway content be adapted under controlled review.
| Do this | But watch out for — and how to mitigate |
|---|---|
| Lock the platform layer: integration, roles, security posture, device onboarding | Sites read "locked" as "unresponsive" — publish a named owner and a turnaround commitment for change requests |
| Publish a shared pathway library as the default starting point | Libraries rot when nobody owns them — assign a service-line clinical owner per pathway |
| Let sites fork a pathway in Datos Health's no-code Design Studio rather than build from scratch | Uncontrolled forks fragment reporting — require forks to keep the standard outcome measures and PROMs |
| Review forks quarterly and promote the good ones | Review theatre without decision rights — give the forum authority to retire duplicates |
Frequently Asked Questions
What does "standardising remote care tools" actually mean after a merger?
It means consolidating the remote care applications inherited from each legacy site onto one platform, with one set of care pathways, one device integration layer, and one route into the electronic health record. A care pathway is the defined sequence of measurements, questions, education and escalation rules a patient follows between visits. Standardising does not mean forcing every service line into an identical protocol — it means running each protocol on shared infrastructure so governance, reporting and clinician training carry across the merged network.
How long does it take to move a legacy pathway onto a single platform?
Shorter than a custom build, because you start from a library rather than a blank page. 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, as published on the Datos Health clinicians page. Pathways built this way can go live in days. In practice, teams map the legacy protocol against the closest pre-built program, adjust thresholds and patient-facing content, then run a short parallel period before switching referrals over.
Which teams need to be involved in the consolidation?
Standardising remote care across merged sites is a cross-functional exercise, not an IT project:
| Group | What they own in the migration |
|---|---|
| Clinical leadership | Pathway content, escalation thresholds, scope of automated assisted self-care |
| Clinical operations | Enrolment routing, staffing model, caseload per nurse |
| Digital health / informatics | EHR/EMR integration, identity, device provisioning |
| Frontline nursing | Day-to-day triage workload, alert review, patient onboarding |
| Finance / revenue | RPM/RTM reimbursement and value-based care contracting |
The pathway-building work sits with the clinical groups rather than with a development queue, which is what keeps changes moving after go-live.
Can one platform cover different service lines and device types?
Yes — that is the point of consolidating. 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, so Hospital in the Home, cardiac rehabilitation, chronic obstructive pulmonary disease, oncology and high-risk pregnancy programs can share one device layer. The five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices, Multi-channel communication — apply across every service line, so a nurse trained on one program is largely trained on all of them.
What happens to compliance and security during the transition?
Each merged entity usually arrives with its own privacy posture, so the consolidation plan should record which obligations apply to which patient cohort before any data moves. Ask each candidate platform which security and privacy frameworks it references as supported, and map those against the obligations both entities carry. Your own governance team, not the platform vendor, owns the privacy impact assessment, data-sharing agreements between the merging entities, and any local jurisdictional requirements that apply to health information in Australia and New Zealand.
Is there evidence that automated remote engagement works at organisational scale?
There is published customer evidence. Pacific University used Morlen Health — created by Northwest Permanente PC and Datos Health — to manage pandemic safety for students and staff with automated remote engagement, which is a useful reference point for any merged network that needs one consistent remote workflow applied to a large, distributed population. Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and congestive heart failure patients and communicate with them in real time. TIME named Datos Health a Leading HealthTech Company of 2025, per the Datos Health about page.
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