Pagers create risk because they are one way devices, often lack encryption and authentication, and do not confirm whether a message was received, read, or acted on. That leaves clinicians guessing about delivery and creates exposure if a device is lost or messages contain protected health information. In practice, this slows care and weakens confidentiality at the same time.
Why pagers create a coordination problem as well as a privacy problem
Pagers are operationally fragile because they signal that “something was sent” without proving the message was actually received, understood, or acted on. That makes them poor for time-sensitive care coordination, where handoffs, callbacks, and closed-loop confirmation matter. The same weakness also increases the chance that protected health information is exposed in transit or on a lost device.
In practice, the risk is not just missed messages. It is the uncertainty created by one-way delivery, which forces clinicians to compensate with calls, duplicate paging, or manual follow-up. That adds delay, noise, and the possibility that the wrong person assumes the right person saw the page.
Why pager design weakens confidentiality
Traditional pagers were built for simple alerting, not for secure clinical messaging. If the content includes names, diagnoses, locations, callback details, or other patient identifiers, the device itself becomes a confidentiality exposure because many pager workflows were never designed around encryption, strong authentication, or robust access logging.
Loss, theft, shared use, and stale message retention make that exposure worse. If a pager can be read by anyone who picks it up, or if a message remains visible longer than intended, the device becomes part of the PHI attack surface rather than a neutral transport tool.
Clinically, that is why organizations often limit what they send by pager and reserve more sensitive details for systems that support encryption, identity verification, and message acknowledgement. A pager may still be useful for an initial alert, but it is a weak place to carry patient-specific detail.
What changes when care depends on a one-way message
When a workflow depends on a one-way channel, the team loses an important control point: confirmation. Without read receipts, identity binding, or reliable delivery status, staff cannot tell whether the right recipient saw the page, whether the message arrived late, or whether the recipient is even available. That uncertainty creates both patient safety risk and communication overhead.
The problem becomes more serious in escalation paths. If a critical result, consult request, or urgent bedside need is paged out and no one can verify receipt, the organization must rely on backup processes, duplicate contact methods, and human vigilance to close the loop. Those compensating steps help, but they also show that the pager itself is not providing the assurance the workflow requires.
Risk and Threat Considerations
Pagers create both operational exposure and privacy exposure because they are hard to authenticate, hard to audit, and easy to misroute in day-to-day clinical use. That combination makes them a weak fit for any workflow where delayed acknowledgement or exposed content could affect treatment decisions or confidentiality.
Failure mechanism: A one-way message path prevents the sender from proving delivery or action, while weak device protection increases the chance that PHI can be viewed by the wrong person if the pager is lost, shared, or left unattended.
Impact: The result can be delayed follow-up, missed escalation, duplicated work, and avoidable disclosure of patient information, all of which directly affect care coordination and privacy risk.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 and GDPR define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Pagers lack strong recipient assurance, so authenticated messaging matters. |
| IA-5 — Authenticator Management | Pager risk increases when shared or unmanaged credentials and access paths persist. | |
| Recommendation — Use authenticated channels when a message must be tied to a specific clinician. Manage and rotate any access credentials used for clinical messaging platforms. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Patient messages and device access need controlled, least-privilege handling. |
| Recommendation — Restrict who can access patient messaging content and the devices that carry it. | ||
| GDPR | Art.32 — Security of processing | Sensitive health data sent by pager needs appropriate security safeguards. |
| Recommendation — Apply appropriate technical and organisational measures before sending sensitive patient data. | ||
Practitioner Guidance
What to verify: Treat pagers as alerting tools, not as proof of communication. For any message that affects patient care, verify that the workflow includes an alternate acknowledgement path, a defined escalation timer, and a way to confirm who received the message.
Decision rule: If the content would be harmful or embarrassing if read by the wrong person, do not send it in full by pager. Use the pager for the alert, then move the substantive patient detail to a more controlled channel with authentication, encryption, and traceable receipt.
What good looks like: The pager triggers action quickly, but the clinical process does not depend on the pager alone to confirm receipt, interpret urgency, or carry sensitive detail. Closed-loop communication should exist somewhere else in the workflow.
Practitioner takeaway: The safest use of a pager is narrow, time-bound alerting; once the message must prove receipt or carry meaningful PHI, the workflow has outgrown the tool.
Related resources from NHI Mgmt Group
- Why does fragmented data create risk for patient care and operational decision-making?
- Why do exposed APIs and overlooked vulnerabilities create such high risk for patient care environments?
- Why does a siloed electronic patient record create problems for care coordination and service innovation?
- Why do fragmented application logins and non interoperable systems create risk for patient care and security?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 28, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
