HIPAA-Compliant Vendor Risk Management for Direct-to-Consumer Lab Testing Companies
When does HIPAA apply to a direct-to-consumer lab testing company?
Selling tests directly to consumers does not, by itself, make a company subject to HIPAA. HIPAA applies to covered entities—health plans, health care clearinghouses, and certain health care providers—and to business associates that handle protected health information (PHI) on behalf of covered entities. A health care provider generally qualifies as a covered entity only if it conducts certain standard electronic transactions. HHS guidance on covered entities
Determine HIPAA status by examining what your company actually does and whose behalf it acts on. A direct-to-consumer company may operate outside HIPAA for its consumer-facing services, yet separately act as a business associate when it performs work for a covered provider or health plan. The same analysis applies to each vendor in your service chain; a vendor’s access to health-related information alone does not automatically make it a business associate.
Keep HIPAA status separate from other privacy, consumer-protection, laboratory, and state-law obligations. If your organization is not a covered entity or business associate, that does not establish that its collection or use of health information is unrestricted.
How to determine whether a vendor is a business associate
Start with the relationship and the work performed—not the vendor’s marketing claims or the title used in a contract. A vendor may be a business associate when, on behalf of a covered entity or another business associate, it creates, receives, maintains, or transmits PHI to perform a regulated function or service. HHS business associate guidance
Map the information flow for each service: who provides the information, who controls the service, what the vendor does with it, and whether the vendor acts on behalf of a covered entity. Consider laboratory information systems, cloud hosting, report delivery, customer support, specimen logistics, analytics, and subcontractors. A direct-to-consumer vendor may not be a business associate for a standalone consumer service if it is not working on behalf of a covered entity; however, a different service relationship may produce a different result. HHS guidance on app relationships and PHI
When the relationship does make the vendor a business associate, put a HIPAA business associate agreement (BAA) in place before allowing the vendor to handle PHI. A BAA cannot turn a vendor into a business associate if the underlying relationship does not meet the definition, nor does signing one establish that the vendor’s safeguards are adequate.
Which vendors can access samples and test results?
Create an inventory of everyone who can handle a specimen, its identifying information, or the associated test result. Depending on your operating model, that can include the performing laboratory, collection-site or courier services, fulfillment and kit providers, customer-support teams, portal and cloud providers, report-delivery services, and approved subcontractors.
For each vendor, record the information or material it receives, why access is needed, where it is stored or transferred, who can access it, and when access ends. Distinguish a specimen from the identifying or health information linked to it: assess the complete workflow, including labels, requisitions, account records, and results, rather than assuming that a specimen or coded record is automatically outside the privacy analysis.
Limit disclosure to what the vendor needs for the contracted task. Where HIPAA applies, the Privacy Rule’s minimum-necessary requirements and the Security Rule’s access-control standards are relevant to managing PHI access. HHS summary of the HIPAA Security Rule
How to assess vendor safeguards for health data
Use a documented security risk analysis to identify where electronic PHI is created, received, maintained, or transmitted, the threats and vulnerabilities that could affect it, and the controls used to reduce risk. HHS says the Security Rule requires an accurate and thorough risk analysis for regulated entities and does not prescribe one specific methodology. HHS risk analysis guidance
For each vendor, assess safeguards in proportion to the sensitivity of the data and the service’s access. Review policies, system architecture, workforce access, security incident response, recovery and backup arrangements, and how the vendor manages its own subcontractors. Ask for evidence that supports the vendor’s answers; a questionnaire or a general “HIPAA compliant” statement alone is not a substitute for your assessment.
- Access control: Check whether access is limited to authorized users and appropriate roles, and how access is changed or removed when work assignments change.
- Technical safeguards: Review authentication, transmission and storage protections, and safeguards against improper alteration or destruction of ePHI. Assess encryption in the context of the vendor’s systems and documented risk management.
- Access control audit logs: Determine whether systems record and allow review of relevant activity involving ePHI. HIPAA’s Security Rule includes access-control and audit-control standards. HHS Security Rule summary
- Incident handling: Confirm how the vendor identifies, escalates, and reports security incidents, and whether contractual notification terms give your organization enough time and information to meet its own obligations.
- Independent evidence: Review available audit reports or other security assessments, their scope and date, and any exceptions or remediation plans. Treat certifications and reports as evidence to evaluate—not proof that every legal requirement is met.
For a regulated entity, vendor due diligence supports—but does not replace—its own security risk analysis and risk-management responsibilities. HHS guidance on risk management and safeguards
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 AssessmentWhat should a vendor risk assessment and agreement cover?
Document the assessment, decision, and any conditions for approval. A practical record identifies the vendor and service, information and systems involved, access level, relevant safeguards, known gaps, responsible owners, and the date for review. Reassess when the service, data flow, vendor, or threat environment materially changes.
If the vendor is a business associate, the BAA must specify permitted and required uses and disclosures of PHI, restrict other uses and disclosures, require appropriate safeguards, address applicable Security Rule duties, and require the vendor to report security incidents and breaches as required. It must also address subcontractors, support for relevant covered-entity obligations, and return or destruction of PHI at termination where feasible. HHS business associate agreement requirements
Use the service agreement alongside the BAA to set operational details such as security contacts, incident-escalation timelines, service responsibilities, data return format, retention limits, and cooperation with investigations. Confirm that the agreements do not conflict. HHS recommends understanding a cloud provider’s service and risk-management implications and aligning service terms with the BAA. HHS guidance on cloud services and ePHI
Contract terms are only one part of risk management. Maintain a process to address known material violations; HHS states that covered entities must take reasonable steps to cure or end a known material breach and, if unsuccessful, terminate the arrangement where feasible. HHS guidance on business associate violations
How do CLIA and FDA oversight affect vendor due diligence?
HIPAA review and laboratory oversight answer different questions. If an outside laboratory performs testing, verify the facility and certificate information in the CMS CLIA lookup, including the laboratory’s name, location, certificate type, and expiration date. CMS says the listing is updated weekly and reflects the data source date shown in the system. CMS CLIA laboratory lookup
A CLIA certificate is relevant to the laboratory’s authority and testing responsibilities; it does not establish that a technology vendor has appropriate data safeguards or that every test claim has FDA authorization. Confirm which facility actually performs the testing, and assess the laboratory’s role separately from platform, logistics, and other vendors.
FDA requirements depend on the test and its intended use. FDA explains that some direct-to-consumer tests are reviewed while others are not, and that regulatory pathways vary by test type and risk. Review the test’s intended-use claims, labeling, and applicable regulatory pathway instead of assuming that all consumer tests receive the same review. FDA guidance on direct-to-consumer tests
For laboratory-developed tests, verify current requirements rather than relying on descriptions of the 2024 FDA final rule: FDA states that a federal district court vacated that rule on March 31, 2025, and that FDA issued a rule on September 19, 2025, restoring the earlier regulatory text. FDA’s current laboratory-developed test information
How to manage result interpretation, data retention, and vendor offboarding
Make sure the organization responsible for the test controls how results are released and what support accompanies them. Assess whether reports accurately explain their intended use and limitations, who can answer consumer questions, and how clinically significant or unexpected results are escalated. FDA advises consumers not to use direct-to-consumer results as the sole basis for medical decisions and to discuss relevant results with a qualified health care provider. FDA consumer guidance on test results
Set retention rules by record type, applicable law, and operational need; do not treat HIPAA as a single universal medical-record retention period. CLIA requires laboratories to retain or be able to retrieve original test reports for at least two years, while other record categories and applicable state requirements may differ. Confirm that a vendor’s retention and deletion schedule supports the performing laboratory’s obligations and any longer applicable requirements. CMS CLIA retention guidance
At offboarding, revoke user and system access, stop new data transfers, retrieve needed records in a usable format, and obtain confirmation of return or deletion where appropriate. HIPAA generally requires a BAA to provide for return or destruction of PHI at termination where feasible; if that is infeasible, the agreement must preserve protections and limit further uses and disclosures. HHS guidance on PHI after a service ends
Strong vendor risk management connects the legal relationship, data flow, security evidence, laboratory credentials, test claims, and exit plan. Revisit that picture whenever your service or vendor changes, and keep the supporting decisions documented.
FAQs
Does HIPAA apply to every direct-to-consumer lab testing company?
No. HIPAA applies to covered entities and their business associates, not automatically to every company that sells tests directly to consumers. A company may have different HIPAA roles across different services, depending on whether it handles PHI on behalf of a covered entity. HHS guidance on covered entities and business associates
When does a laboratory or technology vendor become a HIPAA business associate?
A laboratory or technology vendor may be a business associate when it creates, receives, maintains, or transmits PHI on behalf of a covered entity or another business associate to perform a covered function or service. Assess the actual service relationship and information flow; a contract label by itself does not settle the question. HHS business associate guidance
What should a business associate agreement cover for lab testing vendors?
A BAA should define permitted and required PHI uses and disclosures, require appropriate safeguards, address applicable Security Rule duties and incident reporting, and set requirements for subcontractors. It should also cover support for relevant covered-entity obligations and return or destruction of PHI when the relationship ends, where feasible. HHS BAA requirements
How can a company verify a vendor’s CLIA status and data security safeguards?
For a laboratory, check its facility details, CLIA certificate type, and expiration date in the CMS CLIA laboratory lookup. Separately assess the vendor’s security program, access controls, audit logging, incident response, subcontractor oversight, and supporting evidence. A CLIA listing does not verify a vendor’s data security safeguards.
Table of Contents
- When does HIPAA apply to a direct-to-consumer lab testing company?
- How to determine whether a vendor is a business associate
- Which vendors can access samples and test results?
- How to assess vendor safeguards for health data
- What should a vendor risk assessment and agreement cover?
- How do CLIA and FDA oversight affect vendor due diligence?
- How to manage result interpretation, data retention, and vendor offboarding
- 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