📘
New Ebook: SharePoint alone, or SharePoint + Jint? Find out.
Learn more
📘
New Ebook: SharePoint alone, or SharePoint + Jint? Find out.
Learn more
📘
New Ebook:  SharePoint alone, or SharePoint + Jint?.
Learn more
📘
New Ebook: SharePoint alone, or SharePoint + Jint?
Learn more

A clinical staff app, without company phones

Florian Bouron
Florian Bouron
October 5, 2026
A clinical staff app, without company phones
A clinical staff app, without company phones
A clinical staff app, without company phones

Table of content

How do you give clinical staff mobile access without company phones or a second directory?

A news item published on Monday morning reaches support functions within the hour. It rarely reaches the night nurse, the care aide in a nursing home or the porter. Their only shared tool is the phone, and it raises three IT questions: identity, data and device.

The boundary between employee data and patient data sets the legal framework. France's data protection authority defines three categories of health data (CNIL, 2018), which this guide turns into a simple test for each content type. It then compares the possible architectures and sets a framework for personal phones.

What's inside this guide:

  • Why mobile access lands on IT's desk: the three questions on identity, data and device to write at the top of your requirements document.
  • What the app carries, and what it does not: the three-question health data test applied to six content types, and whether health data rules apply, set out as a working assumption to confirm with legal counsel.
  • Three architectures, one decision grid: Teams and Viva Connections, a standalone app and a Microsoft 365 extension compared on six criteria, with the five recurring burdens of a second directory.
  • A single identity for all clinical staff: the sign-in journey of a clinician without an email address in Microsoft Entra ID, and what Microsoft 365 F1 and F3 licenses contain.
  • Personal phones, without overreach: the four measures recommended by France's CNIL, the rules to check in Quebec and the shared device for those who have no smartphone.
  • Sixty days to roll out: three phases with one exit criterion each, the actions to take unit by unit and four indicators defined before launch.
  • Three tools: the 20 checkpoints to complete before launch and to revisit afterward, and twelve questions to send in writing to any vendor before the demo.

Why download it:

A neutral decision grid. All three architectures are treated as viable, 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 each content type: a single “yes” excludes it from the app.

A framework for personal phones. Data separation, remote wipe limited to work data, staff information and the shared device are brought together in 20 checkpoints.

Written answers before the demo. The twelve questions cover identity, licenses, hosting, security and reversibility, and the answers can be reviewed in committee.

3

mobile access architectures compared on one grid

20

checkpoints for personal phones

60 days

to roll out with a single identity