A Security Risk Assessment Guide for Digital Physical Therapy App Companies
Which digital physical therapy app data is subject to HIPAA risk analysis?
Start by determining whether your company is a HIPAA covered entity, a business associate, or neither. A digital physical therapy app company is not automatically subject to HIPAA just because it handles health information. A provider is generally a covered entity when it conducts certain standard transactions electronically; an app company may be a business associate when it creates, receives, maintains, or transmits protected health information (PHI) on behalf of a covered entity. Review HHS guidance on covered entities and business associates and its app-specific business associate guidance.
When the HIPAA Security Rule applies, its risk analysis covers all electronic protected health information (ePHI) the regulated organization creates, receives, maintains, or transmits. That may include patient-linked therapy plans, range-of-motion measurements, pain scores, exercise videos, progress notes, messages, appointment details, and billing or referral data. Whether a particular data item is PHI depends on its context and identifiability; don’t assume that every wellness metric or device signal is automatically ePHI.
Include ePHI wherever it exists—not just in the app’s main database. Consider mobile devices, clinician dashboards, application programming interfaces, cloud storage, backups, support tools, test environments, and vendor systems. HHS explains that the risk analysis scope includes ePHI across electronic media and systems, regardless of its source or location, in its HIPAA Security Rule risk analysis guidance.
How to map ePHI across app data flows and vendors
Build an inventory that shows what ePHI the app handles, where it travels, and who can access it. Map the patient journey from account creation and intake through exercise sessions, clinician review, messaging, billing, support, data export, retention, and deletion.
- Record data elements and sources: Identify information entered by patients and therapists, data imported from an electronic health record, and any relevant device or wearable inputs.
- Trace each transfer and storage location: Document mobile and web clients, APIs, databases, cloud services, logs, backups, analytics tools, crash reporting, and test or development environments.
- Identify people and organizations with access: Include employees, clinicians, contractors, hosting providers, support teams, and subcontractors—not only users with direct database access.
- Document boundaries and lifecycle: Show where data is encrypted, decrypted, copied, retained, exported, or deleted, and what happens when a patient closes an account or a vendor relationship ends.
For every vendor, assess what information it can access and whether it performs a service on behalf of a covered entity or business associate. Where a vendor is a business associate or subcontractor handling ePHI on their behalf, determine whether the required business associate agreements (BAAs) are in place and whether the agreement and operating practices match the actual data flow. HHS notes that an app developer’s role and relationship with a covered entity determine whether a BAA is required; simply facilitating an individual’s access to an app does not by itself create a business associate relationship. See HHS examples of business associates.
Which threats and vulnerabilities should the assessment cover?
Assess reasonably anticipated threats and weaknesses that could compromise ePHI confidentiality, integrity, or availability. A threat is a possible harmful event; a vulnerability is a weakness that could let the event affect your systems or data. Evaluate how likely each threat-vulnerability combination is and the harm it could cause, rather than treating a vulnerability list as a complete risk analysis. HHS describes these elements in its risk analysis guidance.
For a physical therapy app, scenarios to consider may include account takeover, reused or weak credentials, excessive employee permissions, exposed API endpoints, insecure storage on a phone, cloud misconfiguration, compromised vendor accounts, lost devices, ransomware, accidental disclosure through support tools, and unauthorized data collection by analytics or advertising components. Also consider service outages, corrupted exercise plans or clinical notes, failed backups, and loss of access to records needed for care.
Make the scenarios specific to your architecture and operating model. For example, evaluate whether an attacker could use a compromised patient account to view another patient’s therapy records, whether a staff account can export more data than its role requires, or whether an outage would prevent clinicians from accessing current treatment plans.
How to evaluate administrative, physical, and technical safeguards
Compare existing safeguards with the risks identified, and check whether the controls are actually implemented and working as intended. The Security Rule requires appropriate administrative, physical, and technical safeguards to protect ePHI; the details should reflect the organization’s size, complexity, capabilities, and risk environment. HHS summarizes these requirements in its HIPAA Security Rule overview.
- Administrative safeguards: Review security responsibility, risk management, workforce access decisions, security awareness and training, incident procedures, contingency planning, vendor oversight, and periodic evaluation.
- Physical safeguards: Examine how you protect workstations, employee devices, servers, and facilities; control physical access; and securely handle or dispose of devices and media that may contain ePHI.
- Technical safeguards: Evaluate access controls, unique user identification, authentication, audit controls, integrity protections, and transmission security.
For each safeguard, record its owner, scope, evidence, and any gap. A written policy is not enough if the relevant system settings, staff practices, or vendor controls do not match it. Security incident response should include identifying and responding to suspected or known incidents, mitigating harmful effects where practicable, and documenting incidents and their outcomes, as described in HHS guidance on Security Rule incident procedures.
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk AssessmentHow to assess authentication, encryption, tracking, and third-party access
Review how patients, therapists, administrators, and vendors authenticate and what each identity is allowed to do. Check for unique accounts, role-appropriate permissions, timely removal of access, secure session handling, and safeguards for sensitive actions such as downloading records or changing a treatment plan. Evaluate whether authentication controls address the risks of stolen credentials and unauthorized account access.
Assess ePHI encryption at rest and in transit across the app, APIs, databases, backups, logs, and vendor connections. Under the current Security Rule, encryption is an addressable implementation specification: the organization must assess whether it is reasonable and appropriate in its circumstances. If it determines the specification is not reasonable and appropriate, it must document that decision and implement an appropriate equivalent alternative when required. See HHS guidance on HIPAA encryption. Encryption is an important control, but it does not replace access management, monitoring, or other safeguards.
Inventory analytics, advertising, crash-reporting, customer-support, and monitoring tools. Determine what data each component collects or receives, whether it could include ePHI, how it is used, and whether it is shared onward. Review third-party permissions, contract terms, security evidence, incident reporting commitments, and access revocation. A BAA is needed when the relevant business associate relationship and ePHI handling require one; it is not a substitute for assessing the vendor’s actual access and controls.
Connect these checks to your security incident and breach response procedures. A security incident does not automatically mean a reportable breach; the Breach Notification Rule applies to breaches of unsecured PHI, with specific assessment and notification requirements. Keep the periodic security risk analysis distinct from any breach-specific risk assessment. See HHS’s Breach Notification Rule guidance.
How to document findings and prioritize risk mitigation
Document the assessment so someone else can understand what you examined, what you found, and what decisions followed. HIPAA does not prescribe a particular risk-analysis format, but HHS says the analysis must be documented and should inform risk management. A practical record includes:
- Assessment scope, date, systems, ePHI, data flows, vendors, and assumptions.
- Threats, vulnerabilities, existing safeguards, and supporting evidence.
- Likelihood and potential impact for each relevant risk, plus the method used to rate them.
- Risk level, proposed mitigation, accountable owner, target date, and current status.
- Residual risk after mitigation, along with documented decisions and reasons for any accepted risk.
Prioritize issues based on their potential effect on ePHI confidentiality, integrity, and availability, while considering how exposed the vulnerable system is and whether safeguards reduce the likelihood or impact. Assign clear owners and deadlines, then verify that remediation worked. The assessment tool can help organize evidence and tasks, but using a tool does not itself establish HIPAA compliance: HHS states that no single method guarantees compliance and that risk analysis is part of a broader, ongoing process.
When should a physical therapy app company reassess security risks?
Reassess when meaningful changes could affect ePHI or the effectiveness of existing safeguards. Examples include adding a wearable integration, changing cloud providers, launching a new analytics tool, introducing a new care workflow, changing access models, acquiring another company, or responding to a security incident. HHS describes risk analysis as ongoing and recommends updating it in response to environmental or operational changes and newly recognized risks.
The Security Rule does not set one universal risk-analysis interval. Set a documented schedule that fits your organization and risk environment, and review it when changes or incidents make an earlier update necessary. Also conduct periodic technical and nontechnical evaluations of how well policies and safeguards meet Security Rule requirements. For details, see HHS guidance on ongoing risk analysis.
In short, a sound assessment begins with determining your HIPAA role, mapping ePHI through the app and its vendors, testing safeguards against realistic threats, and tracking mitigation to completion. Treat the process as ongoing—not as a one-time tool output or a substitute for organizational security responsibilities.
FAQs.
When does HIPAA apply to a digital physical therapy app company?
HIPAA applies when the company is a covered entity or acts as a business associate handling PHI on behalf of a covered entity or another business associate. A consumer app is not automatically covered simply because people enter health information into it. The company’s role, contracts, data flows, and services determine whether HIPAA applies. Review HHS guidance on covered entities and business associates.
What systems and vendors should an ePHI risk assessment include?
Include every system and location that creates, receives, maintains, or transmits ePHI: mobile and web apps, APIs, databases, clinician portals, cloud infrastructure, backups, logs, support systems, test environments, and relevant vendor or subcontractor systems. Map the information each vendor can access and determine whether the relationship requires a BAA.
Does using an assessment tool establish HIPAA compliance?
No. A tool can help inventory systems, record findings, or track remediation, but it cannot by itself determine whether your safeguards are appropriate, whether your BAAs and policies fit your operations, or whether identified risks have been addressed. HIPAA security compliance requires an ongoing process tailored to the organization.
When should a company update its security risk assessment?
Update it periodically and when significant operational or environmental changes, new technologies, newly recognized threats, or security incidents could affect ePHI. HIPAA does not specify one universal assessment frequency; choose and document a schedule appropriate to your environment and revisit it when circumstances change.
Table of Contents
- Which digital physical therapy app data is subject to HIPAA risk analysis?
- How to map ePHI across app data flows and vendors
- Which threats and vulnerabilities should the assessment cover?
- How to evaluate administrative, physical, and technical safeguards
- How to assess authentication, encryption, tracking, and third-party access
- How to document findings and prioritize risk mitigation
- When should a physical therapy app company reassess security risks?
- FAQs.
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk Assessment