Table 3. Framework of core secure messaging functionalities, secure messaging advanced functionalities, and technical needs.
| Application features | Essential requirements | Secondary requirements |
|---|---|---|
| Basic security and administrative functionality | ||
| Displays message status (sent, delivered, and read) | X | |
| Secure communication platform | X | |
| Log sender and recipient of message | X | |
| Messages can be saved/discoverable for set periods of time | X | |
| Time stamps on messages | X | |
| Usage analytics and administrative controls available | X | |
| Mobile device management (MDM) features | X | |
| Integrations and advanced functionality | ||
| Can acknowledge receipt of alerts/alarms | X | |
| Can deliver critical laboratory results to application | X | |
| Can deliver radiology reports to application | X | |
| Can escalate alerts/alarms to other users if needed | X | |
| Can extract roles and schedules from third party scheduling applications (e.g., AMiON Physician Scheduling) | X | |
| Can integrate with active directory to populate user database and login information | X | |
| Can integrate with and deliver monitor alerts (e.g., telemetry monitors) to application | X | |
| Can integrate with and deliver nurse call alarms to application | X | |
| Can integrate with EHR | X | |
| Can provide an integrated scheduling platform | X | |
| Communication and workflow functionality | ||
| Able to differentiate resident/fellow/attending clinical roles | X | |
| Able to invite individual to ongoing group conversation | X | |
| Able to message groups of individuals on the same application | X | |
| Able to search and message individual by clinical role on the same application | X | |
| Able to search and message individual by name on the same application | X | |
| Able to send secure messages to users who do not have the application | X | |
| Available for nurses | X | |
| Available for other clinical staff (e.g., social workers, physical therapists, occupational therapist, unit clerk, transport, etc.) | X | |
| Available for physicians | X | |
| Can create and save quick reply messages | X | |
| Can define clinical roles (e.g., on-call for cardiology) | X | |
| Can easily call the same individual that you are messaging | X | |
| Can forward messages to another individual | X | |
| Can identify entire care team for each patient (physician, nurse, ancillary services, etc.) | X | |
| Can send broadcast messages (e.g., hospital emergency, cardiac arrest) to correct individuals | X | |
| Can securely send photos through application | X | |
| Can securely send videos through application | X | |
| Can use patient admission, discharge, transfer (ADT) information for patient lists | X | |
| Has desktop application that is fully integrated and synced with mobile application | X | |
| Phone call occurs through Wi-Fi (voice over internet protocol, or VoIP) | X | |
| Phone number can be blocked/edited | X | |
| Signal status to others (e.g., available, busy, offline) | X | |
| Signal urgency of message | X | |
| Users can be organized by hospital, department, unit, etc., instead of just a single directory | X | |
| Technological needs | ||
| Application can be downloaded on portable devices and supports IOS and Android | X | |
| Application comes preinstalled on vendor phone if not BYOD | X | |
| Can receive pager messages | X | |
| Can use cellular signal | X | |
| Wi-Fi-enabled | X | |
Abbreviations: BYOD, bring your own device; EHR, electronic health records.