HIPAA Audit Readiness Guide for Telehealth-Only Primary Care Companies
Which HIPAA rules apply to a telehealth-only primary care company?
Operating exclusively online does not, by itself, exempt a primary care company from HIPAA. A healthcare provider is generally a HIPAA covered entity if it conducts certain standard transactions electronically, such as claims or eligibility inquiries. If your company is a covered entity, the HIPAA Privacy, Security, and Breach Notification Rules apply to its protected health information (PHI), including information handled through virtual visits. Confirm your status based on how the business operates, not simply on its use of telehealth. See HHS guidance on covered entities and business associates.
The Privacy Rule governs permitted uses and disclosures of PHI and patients’ privacy rights. The Security Rule requires administrative, physical, and technical safeguards for electronic PHI (ePHI). The Breach Notification Rule sets notification obligations for breaches of unsecured PHI. HIPAA is not the only possible requirement: state privacy, security, medical-record, and telehealth laws may also apply.
Map where PHI is created, received, maintained, and transmitted across your virtual-care operation. That may include the electronic health record (EHR), video and messaging systems, scheduling, billing, patient portals, company devices, cloud services, backups, and vendors that handle data on your behalf. This map gives your compliance program a practical starting point for the HIPAA Security Rule and audit preparation.
How should the HIPAA Security Risk Analysis cover virtual care systems?
The Security Rule requires an accurate and thorough assessment of risks and vulnerabilities to the confidentiality, integrity, and availability of all ePHI your company creates, receives, maintains, or transmits. A Security Risk Analysis (SRA) should cover the full virtual-care environment—not just the video platform. HHS explains the scope and elements of a risk analysis.
Start with an inventory of systems, devices, data flows, and the people or vendors that can access them. Include remote-work endpoints and networks, EHR integrations, patient communications, cloud storage, identity and access systems, and any recordings or transcripts your company retains. For each relevant system, document threats and vulnerabilities, existing safeguards, likelihood and potential impact, and the resulting risk level.
Turn the findings into a risk management plan that names corrective actions, owners, priorities, and target dates. Record decisions about safeguards, including why a measure was selected or why an alternative is reasonable and appropriate for the identified risk. Reassess when technology, vendors, workflows, staffing, or threats change, and after significant security events. HHS states that the Security Rule does not set a universal risk-analysis schedule; the process should be ongoing and updated as circumstances warrant.
Include availability and recovery risks, not only unauthorized access. Identify which systems and data are critical to care, and document how the company will maintain or restore essential operations during an outage or other emergency. HIPAA’s contingency-plan provisions include backup, disaster-recovery, emergency-mode, testing-and-revision, and application-and-data-criticality components. Your contingency plan testing should be documented, and identified gaps should lead to tracked follow-up actions. See the HHS OCR Audit Protocol and the HHS Security Rule summary.
What evidence should be ready for an OCR audit or investigation?
Keep an organized, current set of records showing both what your policies require and how the company follows them. OCR’s audit protocol identifies documentation and operational evidence reviewers may examine, including risk-analysis records, security measures, access reviews, contingency planning, and incident response.
- Governance and policies: Current privacy and security policies, assigned responsibilities, workforce training records, sanction procedures, and documented policy reviews.
- Risk and remediation: The system and data inventory, completed SRA, risk ratings, risk management plan, status of corrective actions, and records of periodic reviews or reassessments.
- Access and security activity: User lists, authorization records, access control audit logs, system activity reviews, security incident records, and evidence that access is changed or removed when appropriate.
- Vendors and continuity: Vendor inventory, signed business associate agreements where required, contingency and recovery procedures, test results, and records of revisions or follow-up actions.
- Privacy and breaches: Relevant complaint, disclosure, investigation, breach-assessment, mitigation, and notification records, including documentation supporting a decision that notification was not required.
HIPAA Security Rule documentation must generally be retained for six years from its creation or the date it was last in effect, whichever is later. This is a retention requirement for specified HIPAA documentation, not a general HIPAA requirement to keep every medical record for six years; state law may set medical-record retention periods. See the HHS documentation guidance and HHS’s FAQ on medical-record retention.
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 should workforce access and business associates be managed?
Set access according to job responsibilities, and document how users are authorized, changed, and removed. Use individual user identities so actions can be attributed to a person, rather than relying on shared accounts. HIPAA requires covered entities to implement procedures for regularly reviewing information-system activity, including audit logs and access reports. Establish a documented review process that can flag unusual access and route issues for investigation. See the HIPAA Security Rule text.
Establish onboarding, role-change, and termination procedures for employees, clinicians, contractors, and other workforce members. Train the workforce on the policies relevant to their work, including secure use of telehealth systems, handling PHI, and reporting suspected incidents. Revisit access when duties change and remove it when authorization ends.
Assess vendors based on what they do with PHI. A vendor that creates, receives, maintains, or transmits PHI on behalf of a covered entity may be a business associate; the relationship and services matter, not the vendor’s product label. Before allowing a business associate to handle PHI, put a compliant business associate agreement in place. The agreement should establish permitted uses and disclosures, require appropriate safeguards and incident reporting, and address applicable subcontractors. HHS provides information on business associates and agreements.
A signed agreement does not transfer the covered entity’s responsibility to manage its own HIPAA obligations. Maintain a vendor inventory, know which systems each vendor can access, track agreement status, and review whether the arrangement still reflects the services and data involved.
How can telehealth workflows protect patient information?
Build privacy and security controls into each step of care—from scheduling and identity checks to the visit, documentation, follow-up, and billing. For visits, use private settings when feasible and take reasonable steps to limit incidental disclosures if a private setting is not possible. HHS gives examples such as lowering your voice and avoiding speakerphone. See HHS guidance on where telehealth may be conducted.
Use a consistent process to verify a patient’s identity when needed, and confirm the identity and authority of other participants before sharing information. Explain how a patient can request privacy during a visit if others are nearby. Avoid recording appointments unless there is a defined need and the company has addressed applicable privacy, security, consent, and retention requirements.
Design staff access to support care while limiting unnecessary exposure of PHI. The Privacy Rule’s minimum necessary standard generally calls for reasonable efforts to limit PHI used, disclosed, or requested for a purpose; it does not apply to disclosures to or requests by a healthcare provider for treatment. See HHS guidance on the minimum necessary requirement.
Use approved communication channels for clinical messages and follow-up, verify recipients before sending PHI, and give staff clear procedures for misdirected messages or accidental disclosures. For patient-facing workflows, tell patients how to access the visit securely and what to do if they have trouble connecting. HHS’s telehealth privacy and security guidance offers additional workflow considerations.
What incident response and breach notification procedures are required?
Maintain written procedures to identify, report, investigate, contain, and document suspected security incidents. Make sure staff know how to report issues such as a lost device, misdirected message, compromised account, exposed recording, or unexpected system access. Preserve relevant logs and other evidence, assess affected systems and information, and document response steps and remediation.
An impermissible use or disclosure of unsecured PHI is generally presumed to be a breach unless the covered entity or business associate demonstrates a low probability that the PHI was compromised through a documented assessment of the required factors, or another exception applies. The assessment considers the nature and extent of PHI, who received or accessed it, whether it was actually acquired or viewed, and the extent to which the risk was mitigated. Document the analysis and its conclusion. See the HHS Breach Notification Rule guidance.
When notification is required, covered entities must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. A breach affecting 500 or more individuals must also be reported to the HHS Secretary without unreasonable delay and no later than 60 days; for fewer than 500 individuals, the covered entity maintains a log and reports to HHS within 60 days after the end of the calendar year. A breach affecting more than 500 residents of a state or jurisdiction also requires notice to prominent media outlets serving that area. A business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery, though the agreement may set a shorter period. Keep records of notices given—or the assessment supporting a decision that notice was not required.
For audit readiness, bring the program together: know where ePHI flows, assess and manage its risks, maintain evidence of safeguards and follow-through, and prepare to respond promptly when something goes wrong.
FAQs.
Does HIPAA apply to telehealth-only primary care companies?
It can. A primary care company is generally a HIPAA covered entity if it meets the definition of a healthcare provider that electronically conducts certain standard transactions covered by HIPAA. Providing care only through telehealth does not, by itself, create an exemption. See HHS guidance on covered entities.
What documentation should a telehealth provider keep for a HIPAA audit?
Keep current policies, the SRA and risk management plan, system and vendor inventories, access authorization and review records, audit logs, training records, business associate agreements, incident and breach documentation, and contingency-plan tests and revisions. HIPAA Security Rule documentation generally must be retained for six years from creation or the date it was last in effect, whichever is later. See the OCR Audit Protocol.
How often should a HIPAA Security Risk Analysis be updated?
The Security Rule does not specify a universal interval. Treat risk analysis as an ongoing process, and reassess when changes to systems, operations, vendors, or threats could affect ePHI, as well as after significant security incidents. Set a review cadence suited to your environment and document updates and resulting risk-management decisions. See HHS risk-analysis guidance.
Are telehealth platforms required to sign business associate agreements?
If a platform vendor is a business associate because it creates, receives, maintains, or transmits PHI on behalf of the covered provider, the provider generally must have a compliant written business associate agreement before permitting that handling. Whether a particular vendor qualifies depends on the services and data involved. See HHS guidance on business associates and business associate agreements.
Table of Contents
- Which HIPAA rules apply to a telehealth-only primary care company?
- How should the HIPAA Security Risk Analysis cover virtual care systems?
- What evidence should be ready for an OCR audit or investigation?
- How should workforce access and business associates be managed?
- How can telehealth workflows protect patient information?
- What incident response and breach notification procedures are required?
- 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