HIPAA Compliant Secure Paging / Urgent Messaging

Physical pagers have been the staple in urgent communications for more than 50 years, so much so, the concept of paging is synonymous with urgent communications. This may explain why a 2017 study published in the Journal of Hospital Medicine found that nearly 80% of hospitals still use physical pagers, even though the pager's time has clearly passed.

Today, the ability of legacy paging technology to reliably deliver urgent messages is inadequate. The coverage of legacy paging networks is very limited, leaving many markets without any coverage and others with only spotty coverage by a single carrier.

Legacy pagers, for the most part, are insecure. Most paging devices have no authentication controls. These devices store and receive messages without any encryption. For entities that require HIPAA compliance, standard pagers simply aren't HIPAA compliant.

Acquiring and provisioning paging devices is a slow, expensive and labor intensive process. Additionally, a pager is yet another device that your users must carry.

In contrast, SecurePaging:

• Runs over cellular/WiFi networks
• Uses the smartphones your users already have
• Stores no data on users' phones
• Encrypts all data while at rest and in transit
• Allows the user to self register their own telephone
• Is HIPAA compliant

Developed by security engineers and born in the Cloud, SecurePaging was designed to do just one thing:

Secure, reliable, HIPAA compliant paging (urgent messaging)

SecurePaging easily co-exists in environments that have: EHR messaging, E-mail, VoiceMail, SharePoint collaborations, etc...

Other messaging apps attempt to be full "communication hubs". As such, their broad scope, more often then not:








Additionally, these messaging apps typically require management software to be installed on supported Windows desktops plus specific client software for desktops, tablets and telephones, all of which look and function differently. This further adds to user confusion as well as the complexity and burden of maintaining these apps.

In contrast, SecurePaging:

• Does not store data on user devices
• Does not require any software to be installed
• Works the same on any smartphone, tablet, or computer with a modern browser
• Does not overlap with organization's existing technology
• Easily integrates with existing technology
• Minimizes end user inefficiency and confusion
• Reduces organizational risks
• Minimizes complexity
• Reduces administrative burdens

As you have probably experienced, answering services are expensive, prone to human error, do not manage a page's lifecycle, and are often not even HIPAA compliant.

Here's the thing, answering services rely on a third person to construe, document and then route each message to its intended recipient. Each step in this process increases the likelihood that the message will arrive with error, if it arrives at all.

Once the answering service sends the page it is up to the recipient to manage it to closure. Often this is done with home-grown tools offering limited visability and even less checks and balances.

In contrast, SecurePaging:

• Costs a fraction of typical answering services
• Is far more accurate and reliable
• Provides clear statuses, notes, audit logs, shared oncall inbox views, and reports
• Is HIPAA compliant

Here's a real-time demonstration showing a patient calling a telephone number published on your website and the resulting page sent to your department's on-call personnel. SecurePaging hosts the telephone number/Voicemail box and therefore provides the necessary HIPAA controls around the data. Telephone greetings are fully customizable and allow for different "enabled" and "disabled" greetings

Highlighted is our device registration functionality which allows the user's telephone to be authenticated enabling quick and secure access. As you watch, please note: the link provided in the page notification will only work for this user, with this telephone and for the duration set by an administrator.