.webp)
How do you give clinical staff mobile access without creating a second identity?
A leadership message published on the intranet on Monday morning reaches administrative staff within the hour, but rarely the night nurse, the care aide in a long-term care home or the porter who changes floors every ten minutes. Across eight countries, 63% of frontline workers say messages from leadership do not reach them (Microsoft Work Trend Index, 2022). For a healthcare group, closing that gap is first an IT project.
This white paper treats the mobile app as an extension of your information system. It compares the options on neutral criteria, frames the boundary with patient health data as a working assumption to be confirmed by your legal counsel, and provides a framework for personal devices.
What's inside:
- Why mobile access lands on the CIO's desk: the three questions of identity, data and device to write at the top of your requirements document.
- What the app carries, and what it does not: a three-question health data test applied to ten content types, and a discussion of whether health data regulations would apply, presented as a working assumption to confirm with legal counsel.
- Three mobile access architectures: native Teams and Viva Connections, a dedicated app outside the tenant and a tenant extension, compared in a 3 × 10 decision grid, with the five recurring costs of a second identity and the place of Jint Mobile App, a native extension deployed in your Microsoft 365 tenant.
- A single identity for all clinical staff: the sign-in journey of a nurse without an email address in Microsoft Entra ID, and what Microsoft 365 F1 and F3 licenses contain.
- The 20-point personal device checklist: ten points to settle before launch and ten to review at every change and every year, with France and Quebec given as examples to map to your own framework.
- Twelve questions to ask any vendor: identity, licenses, hosting, subcontractors, remote wipe, access logs, accessibility, languages and reversibility, to send in writing before the demo.
- A 60-day rollout plan: three phases with one exit criterion each, five indicators defined before launch and three meetings to reach a decision.
Why download it:
A neutral decision grid. The ten criteria apply to all three architectures, and every point marked "to check" becomes a written question to the vendor.
A clear boundary for patient data. The health data test gives your DPO a simple rule for every content type: a single "yes" excludes it from the app.
A framework for personal devices. Voluntary participation, data separation, limited remote wipe and a shared device for those who decline are set out in a checklist ready for the DPO.
Three meetings to reach a decision. Scope, then architecture and identity, then personal devices and adoption: the white paper ends with the agenda of each meeting.
