HIPAA Compliance by Vertical
HIPAA Compliance for SaaS Selling to Physical Therapy Clinics
HIPAA for SaaS selling to physical therapy clinics: home exercise and patient-app data, referral intake, payer workflows, and the BAAs behind them.
Key takeaways
- PHI in scope: Referrals and intake documents uploaded by clinic staff, Evaluation, progress, and outcome-measure data, Home exercise program assignments and patient adherence data, Insurance authorization and claims data.
- Start with these controls: A BAA with each clinic customer, with the signed version tracked; Subcontractor BAAs for e-fax, messaging, clearinghouse, and analytics vendors that receive PHI; Analytics and crash reporting configured so patient identifiers do not leave your platform without a BAA.
- The most common mistake: Product analytics or crash reporting receiving patient names or emails with no BAA
- A signed BAA is required with every vendor that creates, receives, maintains, or transmits PHI on your behalf, and no tool is HIPAA compliant on its own.
PHI handled in this environment
- Referrals and intake documents uploaded by clinic staff
- Evaluation, progress, and outcome-measure data
- Home exercise program assignments and patient adherence data
- Insurance authorization and claims data
- Patient messages and app activity linked to an identifiable patient
Common compliance pain points
- Home exercise and patient-app data: A home exercise or patient app that receives patient information on a clinic's behalf is a business associate and needs a BAA with that clinic. Adherence data, videos, and messages linked to an identifiable patient are PHI, and so is whatever your analytics and crash-reporting tools receive.
- Referral intake channels: Clinics receive referrals by fax, email, EHR direct messaging, and upload. If your product handles intake, each channel (e-fax service, inbound email, document parsing vendor) needs a subcontractor BAA and a place in your risk analysis.
- Payer and clearinghouse workflows: HIPAA permits disclosing PHI to a health plan for payment purposes, and the minimum necessary standard applies. If your product submits authorizations or claims, the clearinghouse and any billing subcontractor need BAAs with you, and you should document which data goes to whom.
- Clinic marketing features: Testimonials and outcome stories are a common clinic marketing tool and a common HIPAA problem: using a patient's PHI in marketing requires a written authorization that meets 45 CFR 164.508, and the patient can revoke it. If your product publishes reviews or stories, build the authorization step in.
Priority controls
- A BAA with each clinic customer, with the signed version tracked
- Subcontractor BAAs for e-fax, messaging, clearinghouse, and analytics vendors that receive PHI
- Analytics and crash reporting configured so patient identifiers do not leave your platform without a BAA
- A written-authorization step before any patient story or testimonial is published
- Access controls that keep each clinic's patients separate
- Workforce HIPAA training with documented completion
Common mistakes
- Product analytics or crash reporting receiving patient names or emails with no BAA
- An e-fax or inbound email vendor for referrals with no subcontractor BAA
- Publishing patient testimonials without a written authorization
- Clinic users able to see another clinic's patients
- No documented risk analysis to share when a clinic group asks for one
Enforcement context
Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Many PT clinics are small independent practices, and OCR's right of access and risk analysis enforcement has included small providers, so clinics may ask how your product supports records requests and what safeguards you can show. HHS's January 2025 Security Rule proposal (90 FR 898) would add more prescriptive technical requirements if finalized; it is a proposal, not current law.
Frequently asked questions
What PHI do physical therapy SaaS organizations handle?
Referrals and intake documents uploaded by clinic staff; Evaluation, progress, and outcome-measure data; Home exercise program assignments and patient adherence data; Insurance authorization and claims data; Patient messages and app activity linked to an identifiable patient. Any of these, combined with an identifier, is protected health information when a covered entity or business associate holds it, and in electronic form it brings the Security Rule into scope.
What are the priority HIPAA controls for physical therapy SaaS?
A BAA with each clinic customer, with the signed version tracked; Subcontractor BAAs for e-fax, messaging, clearinghouse, and analytics vendors that receive PHI; Analytics and crash reporting configured so patient identifiers do not leave your platform without a BAA; A written-authorization step before any patient story or testimonial is published; Access controls that keep each clinic's patients separate; Workforce HIPAA training with documented completion.
What are the most common HIPAA mistakes in physical therapy SaaS?
Product analytics or crash reporting receiving patient names or emails with no BAA; An e-fax or inbound email vendor for referrals with no subcontractor BAA; Publishing patient testimonials without a written authorization; Clinic users able to see another clinic's patients; No documented risk analysis to share when a clinic group asks for one.
What does HIPAA enforcement look like for physical therapy SaaS?
Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Many PT clinics are small independent practices, and OCR's right of access and risk analysis enforcement has included small providers, so clinics may ask how your product supports records requests and what safeguards you can show. HHS's January 2025 Security Rule proposal (90 FR 898) would add more prescriptive technical requirements if finalized; it is a proposal, not current law.