Vendor Risk Management for NCI-Designated Cancer Centers: HIPAA Compliance
NCI-designated cancer centers may rely on vendors for clinical care, research operations, laboratory services, billing, information technology, and data storage. When a vendor handles protected health information (PHI) on behalf of a HIPAA-regulated organization, the center needs to determine the vendor’s role, establish appropriate contractual protections, and address risks to electronic PHI.
NCI designation recognizes a center’s research leadership; it does not, by itself, determine whether the center is a HIPAA covered entity. The NCI describes its designation as recognition of cancer research capabilities, while HIPAA status depends on the organization’s activities and structure. National Cancer Institute: NCI-Designated Cancer Centers
Which HIPAA requirements apply to cancer center vendors handling PHI?
HIPAA applies to covered entities—health plans, health care clearinghouses, and health care providers that conduct certain standard electronic transactions—and to business associates in specified circumstances. A provider’s electronic billing or similar transactions may establish covered-entity status even if another organization performs them on the provider’s behalf. HHS: Covered Entities and Business Associates
When a covered entity engages a business associate to perform a service involving PHI, it generally must have a written business associate agreement (BAA) or other arrangement that meets HIPAA requirements. The business associate is also subject to certain HIPAA obligations directly. The HIPAA Security Rule requires covered entities and business associates to protect the confidentiality, integrity, and availability of electronic PHI through reasonable and appropriate safeguards. HHS: Summary of the HIPAA Security Rule
For a cancer center, relevant services may include hosted electronic health record systems, billing, laboratory or pathology support, data hosting, patient communications, and certain clinical-trial technology services. A vendor’s label or marketing claims do not decide its HIPAA status; the center should assess what the vendor actually does and whether PHI is involved.
Not every vendor that works with a center is a business associate. HIPAA includes exceptions, and a vendor that does not meet the business associate definition may still present operational or cybersecurity risks that the center should address through its broader procurement and security processes.
How do cancer centers identify vendors that qualify as business associates?
Start with the vendor’s work, not its name or the department that hired it. A business associate generally is a person or organization that, on behalf of a covered entity, performs a function or service involving the creation, receipt, maintenance, or transmission of PHI. A subcontractor may also be a business associate when it handles PHI on behalf of another business associate. HHS: Business Associates Frequently Asked Questions
For each vendor, document:
- The service and business purpose: For example, billing, clinical data hosting, laboratory support, patient scheduling, or software maintenance.
- The information involved: Identify whether the vendor creates, receives, maintains, or transmits PHI, including electronic PHI, and what data types and systems are in scope.
- The data flow and access: Record how information reaches the vendor, who can access it, whether the vendor connects to center systems, and how information is returned, retained, or deleted.
- The vendor’s role: Determine whether it acts on the center’s behalf, whether it uses or discloses information for its own purposes, and whether subcontractors are involved.
Potential examples to review include a cloud provider storing ePHI, a company handling patient billing, or a service provider maintaining clinical systems that contain ePHI. By contrast, a research disclosure is not automatically a business-associate relationship: HHS explains that a researcher conducting research for their own purposes is not necessarily a business associate simply because the center discloses PHI. The disclosure must still be permitted under the Privacy Rule. HHS: Business Associates Frequently Asked Questions
Keep the assessment current when a service changes, the vendor gains new access, a new system integration is added, or subcontractors change. Record the rationale for the classification and involve privacy, security, procurement, legal, and the relevant clinical or research owner as appropriate.
What should a HIPAA security risk assessment cover for vendor relationships?
The HIPAA Security Rule requires a covered entity or business associate to conduct an accurate and thorough security risk analysis for the electronic PHI it holds. HHS guidance specifically identifies vendors and consultants as potential external sources of ePHI to consider. The regulation does not prescribe one assessment method or a fixed review interval; the analysis should fit the organization and its environment. HHS: Guidance on Risk Analysis
For vendor relationships, the center’s security risk analysis should connect the vendor to its overall ePHI environment. Consider:
- Information and systems: What ePHI the vendor can access, where it is stored or transmitted, and which applications, interfaces, devices, or accounts are involved.
- Threats and vulnerabilities: Plausible human, technical, environmental, and operational threats, including unauthorized access, service disruption, data loss, and weaknesses in vendor or subcontractor practices.
- Likelihood and impact: The chance of each risk and its potential effect on confidentiality, integrity, and availability, including effects on clinical operations where relevant.
- Existing safeguards and gaps: Whether controls are in place, appropriately configured, and used, and what vulnerabilities or residual risks remain.
- Risk treatment: The security measures, owners, deadlines, and follow-up needed to reduce risks to a reasonable and appropriate level.
In a cancer-care setting, the assessment may need to account for the clinical and research workflows supported by the vendor—for example, whether a service supports access to patient records, laboratory results, or scheduling systems, and what disruption or exposure could mean for those workflows. A center should document its assessment and revisit it when risks or operations change. HHS describes risk analysis as an ongoing process, but does not set one universal annual schedule. HHS: Guidance on Risk Analysis
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 AssessmentWhich security controls should vendor due diligence review?
Vendor due diligence should evaluate safeguards in context rather than rely on a single questionnaire or certification. The HIPAA Security Rule identifies administrative, physical, and technical safeguards; the appropriate measures depend on the organization’s circumstances and risk analysis. HHS: Summary of the HIPAA Security Rule
- Administrative safeguards: Review security responsibilities, workforce access procedures, security training, incident response, contingency planning, and risk management. Ask how the vendor handles access changes when a worker’s role ends or changes.
- Physical safeguards: Consider physical access to facilities and devices that store or process ePHI, as well as protections for workstations and equipment.
- Technical safeguards: Review user access controls, authentication, audit logging, integrity protections, and transmission security for systems handling ePHI. Examine how vendor and center accounts, interfaces, and remote access are managed.
- Resilience and recovery: Assess backups, disaster recovery, service availability, and the vendor’s ability to support recovery in a way appropriate to the service and the center’s operational needs.
- Subcontractor controls: Identify which subcontractors may create, receive, maintain, or transmit ePHI and how the vendor ensures they protect it.
Request evidence proportionate to the vendor’s access and risk, such as relevant policies, assessment results, penetration-test summaries, incident-response procedures, or independent audit reports. Treat these materials as evidence to evaluate—not as automatic proof of HIPAA compliance. HHS states that a certification does not replace the required business-associate contract. HHS: Business Associates Cannot Replace the Required Contract With Certification
HIPAA does not prescribe one universal security-control checklist for every vendor. The center should consider whether safeguards are reasonable and appropriate for the risks. Where a Security Rule implementation specification is addressable, the organization must assess whether it is reasonable and appropriate and, when it is not, document that decision and implement an equivalent alternative measure when reasonable and appropriate. HHS: Guidance on Risk Analysis
What should a Business Associate Agreement require?
A BAA establishes what the business associate may and must do with PHI and sets required privacy and security commitments. HHS identifies required provisions in 45 CFR § 164.504(e); its sample provisions can help centers check that an agreement addresses the applicable requirements. HHS: Business Associate Contract Provisions
Among other applicable requirements, a BAA should:
- Describe permitted and required uses and disclosures of PHI, and prohibit other uses or disclosures except as allowed by the agreement or required by law.
- Require appropriate safeguards, including compliance with the Security Rule for electronic PHI, and require reporting of impermissible uses or disclosures, security incidents, and breaches as applicable.
- Require the business associate to ensure that relevant subcontractors agree to applicable restrictions and conditions for PHI.
- Address the business associate’s assistance with applicable individual rights and its availability of records to HHS for compliance purposes.
- Provide for return or destruction of PHI at the end of the relationship when feasible, and address termination when the business associate materially violates the agreement.
Centers may also negotiate operational terms that go beyond HIPAA’s minimum contract requirements, such as a specific incident-notification timeline, named security contacts, audit or evidence rights, service-continuity commitments, and procedures for reviewing subcontractors. Identify these as negotiated terms rather than universal federal requirements, and ensure the BAA aligns with the main services agreement. HHS: Business Associate Contract Provisions
How can centers monitor and mitigate vendor and supply-chain risks?
Maintain a vendor inventory that records each service, its business associate status, the PHI and systems involved, the BAA, the vendor’s risk level, and accountable owners. A supply-chain risk assessment can help the center prioritize review by considering data sensitivity, system access, service criticality, subcontractors, and the consequences of disruption.
Set review and escalation practices appropriate to each vendor’s risk. For higher-risk relationships, centers may choose to request updated security evidence, review incidents and remediation, confirm that access remains necessary, and reassess significant changes to services or subcontractors. These are practical risk-management measures; HIPAA does not impose one universal vendor-review schedule.
The HIPAA Security Rule does require regulated organizations to review information-system activity, respond to and document security incidents, and periodically evaluate security measures. HHS says risk analysis should be ongoing, with updates made as needed based on the organization’s environment and circumstances. HHS: Guidance on Risk Analysis
If a covered entity knows of a material breach or violation of the BAA, it must take reasonable steps to cure the breach or end the violation and, if unsuccessful, terminate the agreement when feasible. If termination is not feasible, the covered entity must report the problem to HHS. This response obligation is distinct from a general federal requirement to continuously monitor every vendor’s day-to-day safeguards. HHS: Covered Entity Responsibilities for Business Associates
Effective vendor risk management brings the process together: classify vendors by their actual work, assess their access to PHI and ePHI, address identified risks through appropriate safeguards and agreements, and revisit the relationship when circumstances change. This supports HIPAA compliance while helping protect the clinical and research operations that depend on trusted vendors.
FAQs
Is an NCI-designated cancer center automatically a HIPAA covered entity?
No. NCI designation recognizes a center’s research capabilities; it does not automatically establish HIPAA covered-entity status. A health care provider is generally a covered entity if it conducts certain standard electronic transactions, including when those transactions are conducted on its behalf. Assess the relevant legal entity and its activities. HHS: Covered Entities and Business Associates
Does a vendor handling PHI need a Business Associate Agreement?
If the vendor is a business associate performing a covered function or service involving PHI on behalf of a covered entity, the covered entity generally must obtain a written contract or other arrangement that meets HIPAA’s requirements. Not every vendor that receives PHI qualifies as a business associate; the role, purpose, and any applicable exception must be assessed. HHS: Business Associates Frequently Asked Questions
Are business associates directly liable under HIPAA?
Yes. Business associates are directly liable for certain requirements and prohibitions under the HIPAA Rules, including specified Security Rule and Privacy Rule obligations. Direct liability applies to those provisions that govern business associates; it does not mean every HIPAA requirement applies to every business associate in the same way. HHS: Direct Liability of Business Associates
How often should cancer centers reassess vendor security risks?
HIPAA does not set one fixed reassessment interval for all vendors or require a universal annual review. HHS describes security risk analysis as ongoing and says the appropriate frequency varies with the organization’s circumstances. Centers should reassess when material changes, new threats, incidents, or identified weaknesses may affect ePHI security, and set other review intervals according to vendor risk. HHS: Guidance on Risk Analysis
Table of Contents
- Which HIPAA requirements apply to cancer center vendors handling PHI?
- How do cancer centers identify vendors that qualify as business associates?
- What should a HIPAA security risk assessment cover for vendor relationships?
- Which security controls should vendor due diligence review?
- What should a Business Associate Agreement require?
- How can centers monitor and mitigate vendor and supply-chain risks?
- 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