HIPAA-Compliant Vendor Risk Management for Speech-Language Pathology Practices

Kevin Henry

Risk Management

Published Updated

8 minutes read
Share this article
HIPAA-Compliant Vendor Risk Management for Speech-Language Pathology Practices

Speech-language pathology practices often rely on electronic health record systems, scheduling tools, billing services, cloud storage, and communication platforms. If your practice is a HIPAA covered entity, managing vendors means understanding where protected health information (PHI) goes, deciding which vendors are business associates, and addressing risks throughout each relationship. A vendor’s assurances or a signed contract alone do not make your practice HIPAA compliant.

Which vendors handle protected health information in a speech-language pathology practice?

Start by listing every organization that may create, receive, maintain, or transmit patient information for your practice. Depending on your services and systems, this may include:

  • Electronic health record, practice-management, and patient-portal providers.
  • Billing, claims-submission, payment-processing, and eligibility-verification services.
  • Cloud hosting, data backup, email, file-sharing, and secure messaging providers.
  • Telehealth platforms, transcription or documentation services, and software that processes patient audio or video.
  • IT support, data migration, shredding, and records-storage providers.

A vendor is generally a business associate when it performs a service for your practice involving PHI. A company that only sells software and cannot access PHI may not be a business associate; a transmission-only conduit may also fall under a limited exception. Assess what the vendor actually does and can access, rather than relying on its product label. HHS guidance on business associates

HIPAA applies to health care providers that conduct certain standard transactions electronically, such as claims transactions. Confirm whether your practice meets the covered-entity definition before applying these vendor obligations. HHS guidance on covered entities

How to map patient data across practice systems and vendors

Create a practical data map that follows information from collection through storage, use, sharing, backup, and deletion. Include information in clinical notes, evaluations, referrals, claims, patient communications, and, where identifiable and related to care, recordings or transcripts of speech and language sessions.

For each system or vendor, record what information it receives, why it receives it, where it is stored, who can access it, whether it is shared with subcontractors, and how it is returned or deleted. Note integrations and copies as well as the primary record: for example, an appointment platform may send patient details to a messaging provider, while an EHR may send claims data to a billing service.

Use the map to identify unnecessary disclosures, unmanaged accounts, duplicate storage, and vendors missing from your risk review. HHS risk-analysis guidance specifically points organizations to identify ePHI and consider external sources, including vendors and consultants. HHS guidance on Security Rule risk analysis

How to assess vendor security before onboarding

Before sharing PHI, assess the service in the context of your practice’s HIPAA Security Rule risk analysis. Consider the sensitivity and amount of information involved, the vendor’s access, likely threats, and the potential effect on the confidentiality, integrity, and availability of electronic protected health information (ePHI). The required risk analysis covers ePHI held by your organization; it should account for relevant systems and vendors rather than treating a vendor questionnaire as a substitute. HHS risk-analysis guidance

Ask for specific, supportable information about access controls, authentication, encryption, audit logging, backups, incident response, workforce access, and subcontractor practices. Establish how the vendor will alert you to incidents and help investigate them. Review the vendor’s answers and available evidence against your own needs; a report or security certification by itself does not establish that your practice has met its HIPAA obligations.

Document unresolved concerns before onboarding. If the vendor cannot provide adequate assurances, or the remaining risk is unacceptable, delay access to PHI, select another service, or consider whether changes to the service or data shared would reduce the risk.

What a HIPAA Business Associate Agreement should cover

When a vendor is your business associate, put a Business Associate Agreement (BAA) in place before allowing it to handle ePHI. The agreement should describe permitted and required uses and disclosures, prohibit other uses or disclosures, require appropriate safeguards, and require the vendor to bind relevant subcontractors to applicable protections. HHS summarizes the required BAA terms in its sample Business Associate Agreement provisions.

Address breach notification obligations and reporting of other impermissible uses or disclosures, including who to contact, how quickly to report, and what information the vendor must provide to support your response. Specify cooperation with access, amendment, and accounting requests when applicable. A BAA should also describe the vendor’s obligations when the relationship ends, including return or destruction of PHI where feasible and the protections that apply if it cannot be returned or destroyed.

Identify any subcontractors that may handle PHI and require the vendor to establish appropriate subcontractor agreements. HIPAA requires a business associate to ensure that subcontractors handling PHI agree to applicable restrictions and conditions. HHS business associate and subcontractor guidance

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

Which safeguards should practices verify in vendor systems?

Review safeguards against your risk analysis and the actual service configuration. In electronic systems, check whether access is limited to authorized people and software, each user has a unique identifier, access can be removed promptly, and audit logging records and supports review of relevant activity. Confirm that authentication and safeguards for transmitting ePHI are appropriate to the service and risk. HHS summary of the HIPAA Security Rule

Ask how the vendor protects the integrity and availability of records, backs up data, restores service after disruption, and handles security incidents. Confirm that the practice can retrieve its records in a usable format and maintain access during a transition. For remote access, verify that the vendor’s configuration supports the practice’s access policies and that access is limited to the information needed for each role.

Encryption specifications in the Security Rule are addressable, not a blanket instruction to ignore encryption if a vendor does not offer a particular feature. The practice must evaluate whether the measure is reasonable and appropriate in its circumstances and document its decision, including any equivalent measure where appropriate. HHS guidance on Security Rule safeguards

How to document vendor risks and remediation steps

Keep a vendor risk record that links each service to the data it handles, the relevant risk analysis, the BAA status, the safeguards reviewed, and any subcontractor concerns. Record the evidence reviewed, identified gaps, risk owner, planned corrective action, target date, and the decision to accept, reduce, avoid, or transfer the risk.

Track remediation to completion and revisit the assessment when a vendor changes its service, access, subcontractors, or data practices, or when an incident or new threat changes the risk. HIPAA requires regulated entities to maintain documentation required by the Security Rule; HHS describes a six-year retention period for required documentation, measured from the later of its creation or the date it was last in effect. HHS Security Rule summary and documentation guidance

If you learn of a material breach or violation of a BAA, take reasonable steps to cure the breach or end the violation. If those steps are unsuccessful, termination may be required if feasible. HHS guidance on responding to business associate violations

What to do when a vendor relationship ends

Use the contract’s offboarding process to preserve access to records, export needed information, end vendor and workforce access, and confirm what data remains in active systems, backups, and subcontractor systems. Coordinate the transition before disabling accounts so clinical and administrative records remain accessible to the practice.

Under the BAA, the vendor generally must return or destroy PHI at termination when feasible. If return or destruction is infeasible, the agreement must extend its protections to the retained information and limit further uses and disclosures to the purposes that make deletion or return infeasible. Ask the vendor to explain any exception and document the disposition of the data. HHS guidance on PHI retention after services end

In short, effective vendor risk management connects a current data map, a documented risk assessment, appropriate BAAs, verified safeguards, and a controlled offboarding process. Keep these steps part of ongoing practice operations, not just the vendor’s initial onboarding.

FAQs.

When does a speech-language pathology practice need a Business Associate Agreement?

If your practice is a HIPAA covered entity and a vendor performs a service involving PHI on its behalf, you generally need a BAA before the vendor handles that information. Some limited exceptions apply, such as a vendor that cannot access PHI or a transmission-only conduit. Assess the vendor’s actual role and access. HHS business associate guidance

Do vendors’ security measures make a practice HIPAA compliant?

No. Vendor safeguards and a signed BAA are important, but they do not replace your practice’s own risk analysis, policies, safeguards, documentation, and oversight. HIPAA compliance is an ongoing process shaped by the practice’s systems and risks. HHS Security Rule guidance

Which security safeguards should a practice review before hiring a vendor?

Review access restrictions, unique user identification, authentication, audit logging, transmission protections, data integrity, backups, incident response, subcontractor controls, and the practice’s ability to retrieve records. Determine what is reasonable and appropriate based on the information and service involved, and document the assessment.

What should happen to protected health information when a vendor contract ends?

The vendor should return or destroy PHI as specified in the BAA when feasible. If that is infeasible, the agreement must continue to protect the retained information and restrict further use or disclosure to the purposes that prevent return or destruction. Confirm data disposition, retain needed records, and remove access when the transition is complete. HHS guidance on termination and retained PHI

Share this article

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

Related Articles