Platform · Deployment
Runs where you run.
Four topologies, one platform. The hospital chooses based on data residency, IT capacity and continuity requirements — and can mix patterns across units in the same hospital.
On-premises
Stays in the building
Data never leaves the hospital. Full control of the stack, the storage and the upgrade window. zMed provides the deployment package and the operations playbook; your IT team operates the infrastructure.
Sovereign cloud
In-country, managed for you
Hosted exclusively in-region — India-region data centres for Indian hospitals, US-region for US health systems. Subscription, automatically upgraded, capacity that scales, operated under a hospital-readable SLA.
Hybrid · Recommended
Best of both — recommended
Clinical chart and patient data on-premises; analytics, tele-ICU and reporting in the cloud. Automatic fall-back between layers: the bedside chart survives a cloud link drop without interruption.
Edge appliance
24h+ of offline operation
A per-unit appliance keeps the bedside chart available through network and data-centre incidents. Device traffic terminates at the LAN; data syncs and reconciles automatically when connectivity returns.
Continuity
When the network blips, the chart doesn't.
In the hybrid topology, zMed's edge appliance sits on the hospital LAN at the device boundary. Bedside devices feed the appliance; the appliance feeds the local chart; the chart syncs to the cloud when the link is available, holds local when it is not, and reconciles automatically when it returns.
Always-available chart
The bedside chart runs against the local appliance — cloud incidents, planned shutdowns and link drops do not stop clinical operations.
Device traffic stays local
Monitor, ventilator and infusion-pump traffic terminates at the LAN, not at the cloud — low latency, no dependence on the uplink.
Reconcile on reconnect
On reconnect the appliance reconciles with the cloud automatically — and the audit log is preserved across the incident.
For your IT team
The questions that matter — answered in the demo.
- Q Where does the bedside chart live during a planned data-centre shutdown?
- Q What are the recovery-point and recovery-time objectives for the clinical chart?
- Q Can a single ICU adopt a different deployment pattern from the rest of the hospital?
- Q Where is patient data stored — and does it stay in-country?