Cloud Drive Mapper for healthcare

Healthcare IT is 24/7, life-critical, and unforgiving of friction. Files clinicians cannot reach at the right bedside cost time nobody has. Cloud Drive Mapper brings real-time Microsoft 365 file access to every hospital device, from EPIC workstations to shared nurse-station terminals to Citrix and Azure Virtual Desktop, without pulling gigabytes of PHI down to the local device.

1.5M+ active users worldwide

~5,000 organisations run CDM

ISO 27001 certified since 2016

01

Real-time file access anywhere on the ward

The OneDrive sync client is designed around eventual consistency. Changes made by one user propagate to others on the sync client's schedule, which can be minutes or hours late in a busy tenant. That is a poor fit for clinical environments where a nurse checking a patient's care plan at bedside needs the latest version, not the version that was current at breakfast.

Cloud Drive Mapper works in real time. It talks directly to Microsoft Graph on demand, so a file opened at the nurse's station shows the current version, edited by the consultant twelve seconds ago on their rounds tablet. No local mirror to reconcile, no propagation delay.

For the mobile end of the workforce (rounds tablets, portable ultrasound stations, mobile carts), that real-time behaviour makes files behave the way clinical staff already assume they do: always current, always available, always at the right bedside.

02

Full compatibility with EPIC and other healthcare applications

Many healthcare-specific applications, EPIC being the exemplar, are built to read and write files from real drive letters and UNC paths on the local Windows environment. They do not understand the OneDrive sync client's cloud-file semantics. They fail, or misbehave, or produce corrupted output when pointed at a sync-managed folder.

Cloud Drive Mapper presents Microsoft 365 storage as virtual network drives with real file paths. Every application that expects a Z: drive gets one. EPIC, MEDITECH, imaging workstations, laboratory information systems, clinical reporting tools, dictation software: anything that would work with a Windows file server works with CDM.

This matters because it means moving clinical file storage into Microsoft 365 does not require a parallel programme of application-compatibility remediation. The applications do not know they have moved.

03

Works properly in Citrix, Azure Virtual Desktop and Omnissa Horizon

Many hospitals run a VDI estate to centralise clinical desktop management. That estate is often the reason the OneDrive sync client is a persistent problem: profile-space consumption, non-persistent-session failures, and sign-in delays that hurt ward turnover.

Cloud Drive Mapper is built for the way VDI actually works. Non-persistent Windows sessions handled cleanly. No profile bloat. Small cache footprint keeps FSLogix container sizes manageable. Works across Citrix, Azure Virtual Desktop, Omnissa Horizon and RDS.

04

Imprivata single sign-on and shared-workstation environments

Shared clinical workstations, including nurse stations, ward PCs, workstations on wheels, often run Imprivata's tap-and-go single-sign-on to give clinicians fast access without repeated login friction. The OneDrive sync client is a poor fit for this pattern because it assumes long-lived user sessions and personal workstation profiles.

Cloud Drive Mapper's flexible local user identity model supports Imprivata's rapid-context-switching workflows. When one clinician taps in and another taps out, CDM cleanly hands off the Microsoft 365 session with the identity, without stale data hanging around from the previous user.

05

HIPAA-conscious by design: no persistent files on device

CDM does not create a persistent local cache of clinical files. Content is streamed from Microsoft 365 to the device at the moment a user opens it, and released when they close it. A lost or stolen device does not contain a residual copy of clinical data at rest.

Incident response is simpler: if a device is compromised, there is no local file inventory to enumerate; the compromise is scoped to what the user actively opened during the session. HIPAA's minimum-necessary principle is naturally supported.

None of this is a substitute for the wider HIPAA compliance programme, and Cloud Drive Mapper by itself does not make an environment HIPAA-compliant. It removes a specific class of risk that traditional sync-based file access creates.

06

Enterprise-scale SharePoint and Teams for care-team collaboration

Microsoft 365 has become the collaboration backbone in most healthcare environments: Teams for care coordination, SharePoint for departmental documentation, OneDrive for individual workspace. Where the OneDrive sync client breaks, at scale, in VDI, on shared devices, Cloud Drive Mapper keeps the collaboration model working.

A ward with 40,000 patient documents in a SharePoint site can still browse and update via CDM. A departmental Teams file library with 200,000 items across all teams still opens instantly. Scale that would defeat the sync client is unremarkable for CDM.

Implementation of Cloud Drive Mapper, and the associated transition to SharePoint that it enabled, has opened our staff up to a completely new world in collaboration and flexible work that they did not even know was possible.
President & CEO, Respiratory Health Association

Read the full Respiratory Health Association case study →

07

Cost savings from retiring on-site file servers

Many hospitals still run one or more on-site file servers as their primary clinical file store, often because previous attempts to migrate to SharePoint foundered on user-experience or application-compatibility issues. CDM removes both blockers. The move can happen without changing how clinicians open, save or search for files, because the drive letter stays the same.

The savings are direct: hardware refresh cycles avoided, on-site backup infrastructure retired, disaster-recovery scope reduced. And once the file server is decommissioned, the SharePoint content becomes usable by Microsoft 365 Copilot.

08

Copilot-ready SharePoint content

Microsoft 365 Copilot only sees content that lives in SharePoint, OneDrive and Teams. As long as clinical documentation lives on an on-premises file server, Copilot cannot use it, regardless of how well-organised the file server is.

Cloud Drive Mapper is what moves the content into a place Copilot can reach, without disrupting how clinical staff work. That converts a Copilot readiness project from a six-to-twelve-month change-management exercise into a matter of weeks. See the Copilot readiness solutions linked below for the wider work involved.

09

Familiar file experience for clinical staff

Adoption costs money and time. A programme that requires ward staff to learn new file workflows is a programme most healthcare CIOs will delay indefinitely rather than roll out during a busy quarter. Cloud Drive Mapper looks like a file server to the user. The Z: drive that was there for a decade is still there. Folders and files open the way they always have.

From the user's point of view, nothing changed.

Behind the scenes, storage has moved to SharePoint. That is the whole point.

Start a 30-day free trial Request a healthcare demo →

Frequently asked questions

Is Cloud Drive Mapper HIPAA-compliant?

HIPAA compliance is a property of your overall environment, not of any single tool. Cloud Drive Mapper is designed to support HIPAA-conscious IT: it does not persist clinical files on device, uses only delegated permissions inside your Microsoft 365 tenant, and holds no PHI on IAM Cloud's own systems. IAM Cloud can sign a HIPAA Business Associate Agreement where appropriate. Full detail is in the Security & Trust section and the Data Protection Agreement, both linked below.

Can Cloud Drive Mapper handle EPIC?

Yes. EPIC and comparable healthcare-specific applications generally expect files on a Windows drive letter or UNC path. Cloud Drive Mapper presents Microsoft 365 storage as exactly that, so EPIC treats CDM-mapped drives the same way it treats a traditional file server.

Do our clinicians need any new training?

No. Cloud Drive Mapper presents Microsoft 365 storage as network drives that work the same way as any other network drive in Windows. Existing workflows, shortcuts and application integrations continue to function without change.

Does Cloud Drive Mapper work with our existing Citrix VDI investment?

Yes, and CDM specifically addresses many of the reasons the OneDrive sync client is a problem in VDI. Non-persistent sessions, kiosk-style shared workstations, FSLogix container size, and sign-in latency are all handled cleanly. See the OneDrive in Citrix solution, linked below.