New OCR Guidance: HIPAA Compliant Apps and Health Information

Daniel Lebovic
Published: May 1, 2019•Last Updated: August 18, 2025•Read Time: 3 min

Summary

Complying with patient requests to send PHI to third party apps generally shields providers from HIPAA liability for subsequent app disclosures, provided the app was not developed for, or provided by or on behalf of, the provider and thus does not act on its behalf. Providers should honor requests even if concerned about an app, and should warn patients about risks of nonsecure transmissions.

Track and Manage Your Compliance
The Guard compliance dashboard
Unlock the Secrets to Effective Risk Assessments
Understanding and Applying Risk Assessment Procedures in Healthcare Compliance guide cover

In April of 2019, the Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has issued a new series of guidance in the form of FAQs about HIPAA compliant apps, health information, and the disclosure of PHI.

HIPAA guidance is routinely issued by OCR to clarify changes to enforcement or regulatory activity as a result of changes and trends in the healthcare industry. Oftentimes, this HIPAA guidance will be issued in response to changes or updates in technology.

HIPAA compliant apps

This most recent OCR HIPAA media guidance about compliant apps that process health information is just such a response.

In this HIPAA compliant apps guidance FAQ, OCR states that:

  • HIPAA gives individuals the right to access their protected health information (PHI, any demographic information that can be used to identify a patient). That means that if a patient requests for their PHI to be sent to a designated app, the provider should follow their request. That even includes scenarios when a provider may be concerned about the app’s privacy or security, or about how the app will go about using that PHI.
  • Providers who transmit PHI to a third party app at a patient’s request will not be held liable under HIPAA regulation for subsequent unlawful disclosures that the app may make. It should be stressed that this exception only applies so long as the app was not “developed for, or provided by or on behalf of the [provider] – and, thus, creates, receives, maintains, or transmits ePHI on behalf of the [provider].”
  • Providers who transmit PHI to a third party app at a patient’s request via an unsecured channel will not be held liable for a data breach that may occur in transit. However, the HIPAA compliant app HHS guidance stresses that providers should make patients aware of the risks involved with non-secure data transmissions.

To read the full guidance, click here to access the HHS/OCR release.

With newly unfolding healthcare tech, including apps and mHealth devices, HIPAA regulation must adapt to account for new data protection requirements. With increasing requests from patients to share PHI with third-party health information apps, providers must be aware of their responsibilities and liability when it comes to data privacy and security. Understanding HIPAA compliant app data sharing is critical to keeping up with patients’ increasing desire for data accessibility and provider engagement.

To find out more about HIPAA privacy and security requirements, click here to register for one of our upcoming educational HIPAA webinars!

Complete Compliance Solution

Make sure your business and the tools you use to run it are compliant.

Global CTAs Image

About the Author

Daniel Lebovic is the Corporate Legal Counsel and Content Editor at Compliancy Group. His extensive experience as a regulatory attorney, combined with his background as a legal writer, editor, and copy editor, uniquely qualifies him to translate healthcare regulations into easily digestible content that those with or without a legal background can understand.