> ## Content Index
> Fetch the complete content index at: https://www.healthdatacon.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# 10 keys to keeping text messages safe
- URL: https://www.healthdatacon.io/articles/10-keys-to-keeping-text-messages-safe/
- Published: 2016-07-26T10:34:06.000Z
- Updated: 2026-11-10T10:50:16.000Z
- Description: Organizations should use these policies and procedures to help protect sensitive patient data.
- Author: HDM Staff
- Tags: Health IT

## 10 keys to keeping text messages safe

Before implementing a secure text messaging approach, leaders from IT, clinical, security, legal and human resources must collaborate to develop policies and procedures ensuring that all processes and technology involved will be effective and secure. Here are 10 ways to get there, based on research by Spok, a vendor that specializes in messaging applications.

  
## Policy: Eligibility

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-98089185.jpeg)

Define which users are eligible to use secure text messaging based on the clinical workflows in which they are involved.

  
## Policy: Expense allocation

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-83863233.jpeg)

Define who pays for the device, the application, and mobile carrier voice and data services.

  
## Policy: User roles and responsibilities

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-59881166.jpeg)

Define user responsibility for the use and maintenance of the technology, such as battery management, availability while on call, and damaged or lost devices.

  
## Policy: Security and feature management

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-97031830.jpeg)

Define how data shared within secure text messages will be secured in transit and at rest. This will likely include using mobile device management for enforcing pass codes, device encryption and restrictions.

  
## Policy: IT support

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-96985103.jpeg)

Define what devices, networks, services and features IT will support, and what is out of its scope of coverage.

  
## Procedure: Consumer application usage

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-145290313.jpeg)

Define whether or not users are allowed to use consumer messaging apps, such as iMessage and WhatsApp, in any workflows, or whether they will be prohibited.

  
## Procedure: Texting orders

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-47702836.jpeg)

Define whether or not staff can use secure text messaging to text orders. However, certain secure text messaging solutions may not support everything needed to enable these workflows, such as order verification.

  
## Procedure: Screenshots

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-71745205.jpeg)

Create a procedure to prohibit screenshots of secure text messages. Most secure texting solutions natively prevent copy/paste, but they cannot prevent screenshots without a mobile device management solution.

  
## Procedure: Dictation

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-23308452.jpeg)

Create a procedure to prohibit the use of keyboard dictation for any messages containing protected health information. If your secure texting solution uses the native keyboard, this is not a HIPAA-compliant workflow.

  
## Procedure: Attachments

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2016/07/july-26-adobestock-72004085.jpeg)

Create a procedure to prevent the ability to attach images or video that contain PHI from the device’s camera roll. Instead, devise a procedure whereby users have to add attachments from the camera.