HIPAA Compliance for Digital Therapeutics and App-Based Treatments
When does HIPAA apply to digital therapeutics apps?
HIPAA does not automatically apply just because an app collects health information or supports a treatment. It applies to covered entities—health plans, health care clearinghouses, and certain health care providers that conduct specified transactions electronically—and to business associates that handle protected health information (PHI) for them. An app company may itself be a covered entity if it meets one of those definitions, but developing a health app alone does not make it one. See HHS guidance on covered entities and business associates.
The relationship and purpose behind the data handling matter. An app offered by or on behalf of a covered provider to deliver treatment or manage patients may handle PHI under HIPAA. By contrast, information a person enters into an independent consumer app is generally outside HIPAA when that app is not provided by or on behalf of a regulated entity—even if the person originally obtained the information from a medical record. HHS explains how HIPAA applies to health information in apps.
When is an app developer a HIPAA business associate?
An app developer may be a business associate when it creates, receives, maintains, or transmits PHI on behalf of a covered entity to perform a covered function or provide a service. For example, a developer that contracts with a clinic to provide a treatment app for the clinic’s patients—and handles their information for patient messaging, monitoring, or care management—may be acting as a business associate. HHS lists app developers as potential business associates in these circumstances.
The distinction is not simply whether the app receives data from a health care organization. If a person independently chooses an app to receive information at their request, that transfer alone does not make the app developer a business associate. The relationship may differ if the covered entity or its contractor provides or uses the app to deliver services. HHS describes the difference between individual-directed app access and a business associate relationship.
When is a business associate agreement required?
When a covered entity engages an app developer to handle PHI on its behalf as a business associate, the covered entity generally must obtain written assurances through a business associate agreement (BAA) or another written arrangement that meets HIPAA requirements. A BAA sets out permitted uses and disclosures, requires appropriate safeguards, and addresses matters such as reporting incidents and handling PHI when the relationship ends. HHS summarizes the required BAA provisions.
Business associates must also obtain appropriate written assurances from subcontractors that create, receive, maintain, or transmit PHI on their behalf. If an app developer is not acting as a business associate—for example, an independent app merely receives information at a user’s direction—a BAA is not required solely because the app handles health data. 45 CFR § 164.502 and 45 CFR § 164.504 set out these contract requirements.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhat safeguards protect electronic protected health information in treatment apps?
For covered entities and business associates, the HIPAA Security Rule requires appropriate administrative, physical, and technical safeguards to protect the confidentiality, integrity, and availability of electronic protected health information (ePHI). A documented risk analysis helps an organization identify where ePHI is created, received, maintained, or transmitted, assess risks, and select safeguards suited to its environment. HHS guidance explains the risk-analysis requirement.
Depending on the organization’s risks and operations, safeguards may include workforce policies and training, facility and device protections, access controls, user authentication, audit controls, and protections for data in transit. The Security Rule does not prescribe one security product or technology for every app; organizations must choose measures that are reasonable and appropriate to meet the Rule’s standards. Addressable implementation specifications require a documented assessment and, where appropriate, an equivalent alternative measure—not simply ignoring the safeguard. HHS summarizes the Security Rule’s safeguards and flexibility.
How should teams assess app data flows and vendor access?
Start by mapping the app’s data flows: what information the app collects or receives, where it comes from, how it moves through the app and connected systems, where it is stored, and when it is deleted. Include identifiers and device or usage data that may be linked to a person’s health, not only clinical fields. Document which parties can access each data set and what each party does with it. HHS risk-analysis guidance calls for identifying ePHI and considering vendors or consultants that create, receive, maintain, or transmit it; the FTC also recommends understanding health-data flows.
Review the app’s contracts and technical connections alongside the data map. Determine whether each vendor acts on behalf of a covered entity or another business associate, whether a BAA or subcontractor agreement is needed, and whether access is limited to the vendor’s documented role. Reassess the map when the app adds integrations, analytics tools, cloud services, or new data uses, and compare actual practices with privacy notices and user-facing claims.
What privacy rules apply to consumer health apps outside HIPAA?
An app outside HIPAA is not necessarily free from privacy obligations. The FTC Act generally prohibits unfair or deceptive practices, which can include misleading claims about how health information is collected, protected, or shared. The FTC’s Health Breach Notification Rule may also apply to certain vendors of personal health records, related entities, and service providers when unsecured health information is breached; it does not apply to every health app in the same way. The FTC’s Mobile Health Apps Interactive Tool helps developers consider which federal rules may apply, and the FTC’s Health Breach Notification Rule page describes the Rule’s scope.
Other federal or state requirements may also apply depending on the app, the information involved, and the business relationship. Teams should avoid treating “not covered by HIPAA” as a complete privacy analysis: assess applicable rules, make clear and accurate disclosures, and align data practices with those disclosures. In short, determine who provides the app and for what purpose, establish the right agreements where PHI is handled on behalf of a covered entity, and protect health data under the laws that apply.
FAQs
Is a digital therapeutics app automatically subject to HIPAA?
No. HIPAA applies based on whether an entity is a covered entity or business associate and how it handles PHI—not simply because an app provides treatment or collects health data. An independent consumer app may fall outside HIPAA even when users enter information from their medical records.
Does an app developer need a business associate agreement?
A BAA is generally required when the developer handles PHI on behalf of a covered entity as a business associate. An app that a person independently selects to receive information at their direction does not become a business associate solely because it receives that information.
Does HIPAA require a specific security technology?
No. The HIPAA Security Rule requires appropriate safeguards, but it does not mandate one specific security technology for every organization. Regulated entities must assess their risks and select and document safeguards that meet the Rule’s requirements.
What rules may protect health data in apps outside HIPAA?
Depending on the app and its data practices, the FTC Act and the FTC Health Breach Notification Rule may apply, along with other federal or state requirements. The Health Breach Notification Rule applies to certain entities and breach situations, not automatically to every app.
Table of Contents
- When does HIPAA apply to digital therapeutics apps?
- When is an app developer a HIPAA business associate?
- When is a business associate agreement required?
- What safeguards protect electronic protected health information in treatment apps?
- How should teams assess app data flows and vendor access?
- What privacy rules apply to consumer health apps outside HIPAA?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today