HIPAA Compliance for Behavioral Health Telehealth Startups
Building a behavioral health telehealth service means protecting sensitive information across clinical care, software, and vendor relationships. Whether your startup is subject to HIPAA depends on its role and how it handles protected health information (PHI)—not simply on whether it offers a health-related app.
If your startup is covered by HIPAA, a practical compliance program should connect privacy policies, security controls, vendor contracts, incident response, and documentation. The following guide explains the key requirements and decisions to address.
Which HIPAA rules apply to behavioral health telehealth startups?
The HIPAA Privacy Rule governs how covered entities use and disclose PHI and establishes individual rights concerning that information. The HIPAA Security Rule sets safeguards for electronic protected health information (ePHI), while the Breach Notification Rule addresses notification after certain breaches of unsecured PHI. HIPAA applies to covered entities and business associates, rather than automatically to every health-related business. See HHS guidance on covered entities and business associates.
Behavioral health information is generally protected under the same Privacy Rule framework as other PHI. Psychotherapy notes, however, receive special treatment when they meet HIPAA’s definition: they are a mental health professional’s notes documenting or analyzing counseling-session conversations and are kept separate from the rest of the medical record. Most disclosures of psychotherapy notes require the patient’s authorization, subject to specific exceptions. See HHS guidance on mental health information and psychotherapy notes.
For a telehealth business, determine whether it is acting as a provider, a technology or services vendor for a provider, or both. If the startup is subject to HIPAA, it must address privacy, security, and breach notification obligations in the parts of its operations involving PHI. Other laws or contractual obligations may also apply, so HIPAA status should not be treated as a complete legal analysis.
How should a startup assess whether it is a covered entity or business associate?
Start by mapping the startup’s services, customers, data flows, and contracts. A health care provider is a HIPAA covered entity if it conducts certain transactions electronically, such as submitting claims in a standard electronic format. Health plans and health care clearinghouses are also covered entities. A company’s marketing language or use of clinical terminology does not, by itself, determine its status.
A startup may be a business associate when it performs services for a covered entity that involve creating, receiving, maintaining, or transmitting PHI on the entity’s behalf. Examples may include hosting clinical records, providing patient messaging, supporting billing, or operating a telehealth platform for a provider. The actual functions and data access matter more than a vendor’s label. HHS explains that even a cloud service provider that stores encrypted ePHI may be a business associate; encryption alone does not remove that status. See HHS guidance on HIPAA and cloud computing.
A direct-to-consumer service does not become a business associate merely because it collects sensitive wellness or behavioral information. If it is neither a covered entity nor a business associate, the HIPAA Rules may not apply to it, though other privacy and security requirements may. Assess each business line and relationship separately, especially if your company both serves consumers directly and supplies software or services to HIPAA-covered providers.
Record the basis for your determination and revisit it when your customers, services, data practices, or contracts change. When the analysis is uncertain, seek advice from qualified privacy or legal professionals before accepting or using PHI.
How can telehealth platforms protect electronic protected health information?
The HIPAA Security Rule requires covered entities and business associates to conduct an accurate and thorough risk analysis of potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. A Security Risk Assessment (SRA) can help organize this work, but completing a tool is not a substitute for identifying the systems, people, vendors, and workflows that actually handle your data. See HHS guidance on the Security Rule risk analysis.
Use the risk analysis to select and manage safeguards appropriate to your environment. A startup’s plan will commonly address:
- Access control: Give each workforce member an individual account, limit access according to job responsibilities, and remove or revise access promptly when roles change or employment ends.
- Authentication: Verify user identity before granting access. Multi-factor authentication is a valuable risk-reduction measure, particularly for remote and administrative access.
- Audit controls: Record and regularly review system activity so the organization can identify unusual access, investigate incidents, and assess whether safeguards are working.
- Transmission security and encryption: Protect ePHI as it moves between users, systems, and vendors. Encryption is an addressable Security Rule implementation specification: assess whether it is reasonable and appropriate, and document the decision and any alternative measures when applicable. See HHS guidance on encryption under the Security Rule.
- Availability and recovery: Plan how to back up ePHI, restore access after an outage, and continue essential clinical operations during a disruption.
- Workforce and device practices: Train staff on your organization’s policies, secure devices used for care, and establish procedures for protecting information in home or shared work settings.
HIPAA does not prescribe one technical architecture for every startup. The risk analysis should inform your safeguards, and the organization should document why its choices are reasonable and appropriate. OCR describes risk analysis as foundational to selecting and managing safeguards in its Summary of the HIPAA Security Rule.
What safeguards are needed for video visits, messaging, and clinical records?
Choose video, messaging, scheduling, and record systems based on how they handle PHI—not on a vendor’s general claim that a product is “secure.” Check whether the vendor will sign a business associate agreement when it is acting as a business associate, what information it stores, who can access it, how it supports security controls, and how it handles incidents and data return or deletion.
For video visits, use settings that limit participation to the intended patient and clinician. Use appropriate authentication, avoid discussing care where others can overhear, and establish procedures for confirming that the person joining the visit is the intended participant. HHS advises providers to use private settings where feasible and reasonable safeguards where they cannot. See HHS guidance on remote communication technologies for telehealth.
Messaging and clinical records need similarly deliberate controls. Limit who can read, create, export, and modify records; keep clinical notes in approved systems; and determine whether the service creates or retains messages, recordings, transcripts, or other PHI. If your startup records a visit or uses automated tools to process its content, include those data flows in the risk analysis and set clear access, retention, and deletion practices.
Ordinary video conferencing tools are not automatically appropriate for HIPAA-covered visits. A covered provider must use technology that supports compliance with the HIPAA Rules; when the vendor acts as a business associate, the relationship generally requires a BAA. The temporary COVID-19 telehealth enforcement discretion ended after its transition period on August 9, 2023. Do not rely on that temporary policy as a current exception. See HHS information on HIPAA and telehealth.
Also remember that a product’s “HIPAA-compliant” label or a private certificate does not, by itself, establish that your organization or its configuration meets HIPAA requirements. OCR does not certify products or endorse specific technology. See HHS guidance on cloud services and HIPAA claims.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayHow should startups manage business associate agreements and vendors?
Identify each vendor that may create, receive, maintain, or transmit PHI for your startup or a provider customer. Depending on the arrangement, a BAA may be required between a covered entity and your startup, and between your startup and a subcontractor that handles PHI on your behalf. A software vendor that has no access to PHI may not be a business associate solely because it sells software; assess the real access and services involved.
A BAA should describe permitted uses and disclosures of PHI, require appropriate safeguards, address incident reporting, and require relevant subcontractors to accept applicable protections. It should also establish how the vendor will support the customer’s obligations and handle PHI when the services end. HHS provides more detail in its Business Associates guidance.
Maintain a vendor inventory that records the service, PHI involved, business associate status, contract and BAA status, security review, and renewal or reassessment dates. Review changes to vendors’ products, subprocessors, or data practices when they may affect risk. A signed BAA is important, but it does not replace your own risk analysis, security controls, or ongoing vendor management.
What should an incident response and breach notification plan include?
Prepare a written plan for suspected security incidents before one occurs. Name the people responsible for triage, technical investigation, privacy and legal review, communications, and escalation to provider customers. Include a way for employees and vendors to report concerns promptly, and keep response procedures available to the people expected to use them.
When an incident is reported, act quickly to contain it, preserve relevant evidence, and determine what information and systems may be affected. Document the timeline, known facts, response steps, and any corrective action. For an impermissible use or disclosure of unsecured PHI, assess whether it constitutes a breach under the applicable rule and document the analysis; do not assume that every suspected incident is automatically a reportable breach or that every incident is exempt.
If a covered entity discovers a breach of unsecured PHI, it generally must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. Breaches affecting 500 or more individuals must also be reported to the Secretary without unreasonable delay and within that same 60-day maximum; breaches affecting fewer than 500 individuals are reported to the Secretary within 60 days after the end of the calendar year in which they were discovered. A business associate must notify the covered entity under the applicable rule and agreement; the BAA may require faster notice. See HHS’s Breach Notification Rule guidance.
Make your incident process account for the startup’s role. If you are a business associate, promptly notify the covered entity as the BAA requires and provide information needed for its assessment and notices. If your startup is a covered entity, assign responsibility for deciding and making required notifications. Check whether other legal or contractual notification duties apply as well.
How can startups document compliance and prepare for audits?
Keep a current, organized record of how your compliance program works. Useful evidence includes your risk analysis and remediation plan, security and privacy policies, workforce training records, access reviews, vendor inventory and BAAs, incident logs, system activity reviews, backup and recovery tests, and periodic evaluations of safeguards. Tie each identified risk to a control, owner, and follow-up date so unresolved work is visible.
Review and update documentation when your systems, services, workforce, vendors, or operating environment change. The Security Rule requires covered entities and business associates to retain required Security Rule documentation for six years from its creation or the date it was last in effect, whichever is later. See HHS’s Security Rule summary and documentation guidance.
Prepare for an audit or customer review by being able to show both written policies and evidence that staff follow them. Training should explain your organization’s actual procedures and the responsibilities relevant to each role; a training completion certificate does not establish that the organization is HIPAA-compliant. Likewise, HIPAA does not impose a universal annual certificate-renewal requirement. Review and refresh training according to your policies, risks, and operational changes.
In short, behavioral health telehealth startups should first establish whether they are covered entities, business associates, or outside HIPAA’s scope for a particular service. Those that are regulated should connect a documented risk analysis to practical safeguards, carefully managed vendors, a workable incident response plan, and records that show the program is maintained over time.
FAQs
Does HIPAA apply to a behavioral health telehealth startup?
It depends on the startup’s role. HIPAA applies when the business is a covered entity, such as a qualifying health care provider that conducts specified electronic transactions, or when it is a business associate handling PHI on behalf of a covered entity. A direct-to-consumer health app is not automatically covered by HIPAA just because it handles sensitive health information.
Do telehealth platforms need a business associate agreement?
A platform generally needs a BAA when it creates, receives, maintains, or transmits PHI on behalf of a covered entity or business associate and is acting as a business associate. The need depends on the specific services and data flow; a vendor that merely provides software without access to PHI may not have the same status.
Can clinicians use ordinary video conferencing tools for HIPAA-covered visits?
Not automatically. Clinicians should use a service and configuration that meet applicable HIPAA requirements. If the vendor handles PHI as a business associate, a BAA is generally required. The temporary COVID-19 telehealth enforcement discretion ended after its transition period on August 9, 2023, so clinicians should not rely on it as a current exemption.
What should a startup do after a suspected breach of patient information?
Contain the incident, preserve evidence, investigate what information and people may be affected, document the response, and promptly involve the people responsible for security, privacy, and legal review. Assess whether the event is a breach of unsecured PHI and follow applicable notification duties and BAA timelines. A business associate should notify the covered entity as required by the agreement and HIPAA rules.
Table of Contents
- Which HIPAA rules apply to behavioral health telehealth startups?
- How should a startup assess whether it is a covered entity or business associate?
- How can telehealth platforms protect electronic protected health information?
- What safeguards are needed for video visits, messaging, and clinical records?
- How should startups manage business associate agreements and vendors?
- What should an incident response and breach notification plan include?
- How can startups document compliance and prepare for audits?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today