HIPAA for business associates
HIPAA applies to business associates directly, and that includes training their own workforce.
First steps for a new business associate
- Write down why the company is a business associate: it creates, receives, maintains, or transmits protected health information for a covered entity or another business associate (160.103).
- Sign each client's business associate agreement before patient information arrives, and note its incident reporting window (164.504(e); 164.314(a)).
- Complete a risk analysis of the electronic patient information the company holds, then a plan to reduce the risks it finds (164.308(a)(1)(ii)(A) and (B)).
- Name a security official and train everyone in the workforce, management included (164.308(a)(2) and (a)(5)).
- Sign agreements with every subcontractor that handles the information for you (164.502(e)(1)(ii); 164.308(b)(2)).
A vendor that creates, receives, maintains, or transmits protected health information for a covered entity is a business associate, and the HITECH Act of 2009 made it directly liable under HIPAA. The Security Rule applies to it in full (45 CFR 164.302): a risk analysis of the electronic patient information it holds, a named security official, written policies, and a security awareness and training program "for all members of its workforce (including management)" (164.308(a)(5)(i)). It must also report breaches to its clients no later than 60 days after discovery (164.410(b)) and sign agreements with its own subcontractors.
Training is one of those requirements, not proof of the rest. A certificate shows that one person completed a course on a date. It does not show that the company complies with HIPAA, and HHS has said a business associate cannot self-certify or be certified by a third party in place of the business associate agreement (FAQ 237).
Who counts as a business associate
The definition turns on what a company does with patient information for a covered entity (a health plan, a health care clearinghouse, or a health care provider that conducts standard transactions electronically). A business associate is a person who, on behalf of a covered entity and other than as a member of its workforce, "creates, receives, maintains, or transmits protected health information for a function or activity regulated by this subchapter, including claims processing or administration, data analysis, processing or administration, utilization review, quality assurance, patient safety activities listed at 42 CFR 3.20, billing, benefit management, practice management, and repricing" (45 CFR 160.103). The second branch covers "legal, actuarial, accounting, consulting, data aggregation (as defined in § 164.501 of this subchapter), management, administrative, accreditation, or financial services" to or for a covered entity "where the provision of the service involves the disclosure of protected health information" from the covered entity, or from another of its business associates, to the person.
The definition also names health information organizations, e-prescribing gateways, and other data transmission services that need routine access to the information, a company that offers a personal health record on a covered entity's behalf, and "a subcontractor that creates, receives, maintains, or transmits protected health information on behalf of the business associate." It excludes a health care provider receiving information "concerning the treatment of the individual," a plan sponsor receiving information from its group health plan to the extent the requirements of 164.504(f) apply and are met, a government agency determining eligibility for or enrollment in a government health plan run by another agency, to the extent authorized by law, and a covered entity performing a function for an organized health care arrangement it participates in. A carrier that only transports information falls under HHS's narrow conduit exception, covered in the medical couriers guide (HHS FAQ 245).
Status does not depend on signing anything. In the 2013 Omnibus rule HHS wrote: "The final rule establishes that a person becomes a business associate by definition, not by the act of contracting with a covered entity or otherwise. Therefore, liability for impermissible uses and disclosures attaches immediately when a person creates, receives, maintains, or transmits protected health information on behalf of a covered entity or business associate and otherwise meets the definition of a business associate" (78 FR 5598). HHS's cloud computing guidance reaches the same result for cloud and hosting companies: a cloud provider that maintains electronic patient information for a covered entity or another business associate is a business associate even if it stores only encrypted data and holds no decryption key, and it must comply whether or not it signed an agreement.
Common business associates
The vendors that usually meet the definition
Claims and billing
Billing, coding, claims, and practice management companies
Claims processing or administration, billing, and practice management are named in the definition (45 CFR 160.103). Comstar, a company that bills for ambulance services, settled with OCR in 2025.
Technology
IT, hosting, cloud, and software vendors
A vendor that maintains or transmits electronic patient information for a covered entity or another business associate is a business associate. HHS applies that to a cloud provider that stores only encrypted data and holds no decryption key.
Professional services
Accountants, lawyers, consultants, and management firms
Legal, actuarial, accounting, consulting, management, administrative, and financial services count when the work involves receiving protected health information. BST & Co., an accounting firm, settled with OCR in 2025.
Plans and benefits
Third-party administrators and wellness vendors
Benefit management and data analysis for a health plan are named functions. Consociate Health, a third-party administrator, and Health Fitness Corporation, a wellness vendor, both settled with OCR.
Down the chain
Subcontractors of a business associate
A subcontractor that creates, receives, maintains, or transmits protected health information on behalf of a business associate is itself a business associate under 160.103, with the same direct duties.
Not a business associate
Workforce, treating providers, and conduits
People under the covered entity's direct control are its workforce. A provider receiving information for treatment is excluded by 160.103, and so is a carrier that only transports it (HHS FAQ 245).
Direct liability
What OCR can hold a business associate liable for
| Duty | Rule | What it requires |
|---|---|---|
| Use and disclose patient information only as the agreement allows | 45 CFR 164.502(a)(3) | Only as permitted or required by the business associate agreement or as required by law. Using a client's data for a purpose the agreement does not cover, such as the vendor's own marketing, is an impermissible use. |
| Limit information to the minimum necessary | 164.502(b) | Make reasonable efforts to limit each use, disclosure, and request to the minimum necessary for its purpose, which in practice means access rights that match the job. |
| Comply with the Security Rule | 164.302; 42 U.S.C. 17931 | Risk analysis, risk management, a security official, workforce training, incident procedures, contingency planning, access and audit controls, and written policies kept six years. |
| Report breaches to the covered entity | 164.410 | Without unreasonable delay and no later than 60 calendar days after discovery, identifying each affected individual to the extent possible. |
| Sign agreements with subcontractors | 164.502(e)(1)(ii); 164.308(b)(2) | Obtain satisfactory assurances, in a written agreement, from every subcontractor that creates, receives, maintains, or transmits the information. |
| Act on a subcontractor's known violations | 164.504(e)(1)(iii) | Take reasonable steps to cure a known pattern of material breach by a subcontractor, and end the contract if those steps fail and termination is feasible. |
| Provide electronic copies for access requests | 164.502(a)(4)(ii) | Disclose electronic copies to the covered entity, the individual, or the individual's designee, as the agreement specifies, when the covered entity needs them to answer an individual's request for an electronic copy. |
| Cooperate with HHS | 160.310; 164.502(a)(4)(i) | Keep the records and submit the compliance reports the Secretary requires, cooperate with investigations and compliance reviews, and give access to pertinent facilities, books, and records. |
| Do not retaliate | 160.316 | No threats, intimidation, or other retaliation against anyone who files a complaint, takes part in an investigation, or opposes a practice they believe in good faith is unlawful, if the opposition is reasonable and does not involve an impermissible disclosure of patient information. |
HHS stated the core of the list in the Omnibus rule: "Business associates are directly liable under the HIPAA Rules for impermissible uses and disclosures, for a failure to provide breach notification to the covered entity, for a failure to provide access to a copy of electronic protected health information to either the covered entity, the individual, or the individual's designee (whichever is specified in the business associate agreement), for a failure to disclose protected health information where required by the Secretary to investigate or determine the business associate's compliance with the HIPAA Rules, for a failure to provide an accounting of disclosures, and for a failure to comply with the requirements of the Security Rule." The next sentence matters as much to a vendor: "Business associates remain contractually liable for other requirements of the business associate agreement" (78 FR 5598 to 5599). A shorter reporting window, an audit right, or a training requirement in the agreement is enforced by the client under the contract.
OCR's 2019 fact sheet, Direct Liability of Business Associates, lists the provisions it can enforce against a business associate, and gives one example of a limit: OCR cannot enforce the reasonable, cost-based fee limit for access copies (164.524(c)(4)) against a business associate. Liability also runs through the company's people. A business associate is liable for a civil money penalty for a violation based on the act or omission of any agent, "including a workforce member or subcontractor, acting within the scope of the agency" (45 CFR 160.402(c)(2)). The HIPAA violation penalty calculator shows the civil penalty tiers.
The training requirement for a business associate's workforce
The Security Rule's training standard is one sentence: "Implement a security awareness and training program for all members of its workforce (including management)" (45 CFR 164.308(a)(5)(i)). It reaches business associates because the whole Security Rule does (164.302). Workforce is a defined term that covers "employees, volunteers, trainees, and other persons whose conduct, in the performance of work for a covered entity or business associate, is under the direct control of" the entity, whether or not it pays them (160.103), so contractors under the vendor's direct control are in scope.
The standard has four implementation specifications, all addressable: security reminders, protection from malicious software, log-in monitoring, and password management (164.308(a)(5)(ii)). Addressable does not mean optional. The business associate must assess whether each one is reasonable and appropriate, implement it if so, and if not, document why and implement an equivalent alternative measure if that is reasonable and appropriate (164.306(d)(3)). The same section lets a small vendor scale its measures to its size, complexity, capabilities, technical infrastructure, costs, and the probability and criticality of its risks (164.306(b)).
The Privacy Rule's training standard is written for covered entities: "A covered entity must train all members of its workforce on the policies and procedures with respect to protected health information" (164.530(b)(1)). A business associate takes on Privacy Rule requirements through its agreement, which must require it, "to the extent the business associate is to carry out a covered entity's obligation under this subpart," to comply with the requirements that apply to the covered entity (164.504(e)(2)(ii)(H)). Staff also have to follow the Privacy Rule limits the company is directly liable for, which is why vendor training covers permitted uses, minimum necessary, and incident reporting alongside security.
The Security Rule sets no fixed interval for training. A client can write a schedule, such as annual training, into the business associate agreement, and the vendor is then bound by it as a contract term. The records matter as much as the sessions. The rule requires written policies and a written record of any action, activity, or assessment it requires to be documented, kept "for 6 years from the date of its creation or the date when it last was in effect, whichever is later" (164.316(b)(2)(i)).
HHS published a proposed rewrite of the Security Rule on January 6, 2025, titled HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (90 FR 898). It is a proposal, and until a final rule takes effect the current regulation governs.
When comparing training for a vendor team, check that the course:
- covers the Security Rule safeguards the company runs, not only the Privacy Rule;
- covers incident and breach reporting to clients, including the 60-day outer limit and any shorter window an agreement sets;
- covers permitted uses under the agreement, minimum necessary, and subcontractors;
- ends with an assessment and a dated certificate a client can verify;
- leaves a record of who completed it and when that you can keep for six years.
Enforcement
OCR settlements with business associates, 2020 to 2026
| Announced | Business associate | Service | People affected | Paid to OCR | What happened and what OCR found |
|---|---|---|---|---|---|
| Sept. 23, 2020 | CHSPSC LLC | IT and health information management services for hospitals and physician clinics indirectly owned by Community Health Systems | More than 6 million | $2,300,000 | Attackers used compromised administrator credentials to reach its system through a VPN. OCR cited longstanding, systemic Security Rule noncompliance, including no risk analysis. |
| Jan. 8, 2025 | USR Holdings, LLC | A Florida business associate | 2,903 | $337,750 | An unauthorized third party deleted electronic patient information. OCR found no accurate and thorough risk analysis and a lack of procedures to regularly review system activity and keep retrievable exact copies of the data. |
| Mar. 21, 2025 | Health Fitness Corporation | Wellness plans, headquartered in Lake Forest, Illinois | About 4,304 | $227,816 | A misconfiguration on its servers exposed patient information, and it filed four breach reports for its clients between October 2018 and January 2019. OCR found it had not performed a risk analysis. |
| May 30, 2025 | Comstar, LLC | Billing and collection for nonprofit and municipal ambulance services, more than 70 covered entities at the time | 585,621 | $75,000 | Ransomware in March 2022. OCR found its risk analysis was not accurate and thorough. |
| Aug. 18, 2025 | BST & Co. CPAs, LLP | Tax advice and tax returns for a physician group, Community Care Physicians | 170,000 | $175,000 | A phishing email let ransomware into its network in December 2019. OCR found no accurate and thorough risk analysis. |
| Mar. 5, 2026 | MMG Fusion, LLC | Maryland software company whose software communicates with covered entities' patients | About 15 million | $10,000 (OCR considered its financial condition) | An intruder accessed its system in December 2020, and the data later appeared on the dark web. OCR found an impermissible disclosure, a deficient risk analysis, and no breach notice to its covered entity clients. |
| Apr. 23, 2026 | Consociate Health | Third-party administrator of employer-sponsored benefit programs | 136,539 | $225,000 | A July 2020 phishing attack gave an intruder access to a server, and systems were encrypted in late 2021. OCR found no accurate and thorough risk analysis. |
OCR does not reach vendors only through their clients. The USR Holdings and BST & Co. investigations began with the vendor's own breach report, and MMG Fusion's began with a complaint about an incident the company had not reported. OCR monitors each corrective action plan for two or three years, and the plans for CHSPSC, BST & Co., and MMG Fusion require workforce training along with a new risk analysis. In the MMG Fusion case, OCR said it considered the company's financial condition in reaching the settlement.
Comstar, BST & Co., and Consociate Health were ransomware cases, and the BST and Consociate attacks began with phishing. Security awareness training, with its specification on protection from malicious software (164.308(a)(5)(ii)(B)), is the Security Rule's control for that entry point.
Subcontractors: the same duties one level down
A business associate that hands patient information to its own vendor, such as a cloud host, an offshore coding team, a shredding company, or a support desk tool, has to get the same assurances its client got from it. It may disclose the information to a subcontractor, and let the subcontractor create, receive, maintain, or transmit it on its behalf, "if the business associate obtains satisfactory assurances, in accordance with § 164.504(e)(1)(i), that the subcontractor will appropriately safeguard the information" (45 CFR 164.502(e)(1)(ii)). The Security Rule's version for electronic information says "only if" (164.308(b)(2)), and the subcontract has to meet the agreement requirements "in the same manner as such requirements apply to contracts or other arrangements between a covered entity and business associate" (164.314(a)(2)(iii)).
The covered entity does not have to get those assurances itself. The rule says "A covered entity is not required to obtain such satisfactory assurances from a business associate that is a subcontractor" (164.502(e)(1)(i)), so the vendor in the middle owns the subcontract. Its own agreement with the client must require it to "ensure that any subcontractors that create, receive, maintain, or transmit protected health information on behalf of the business associate agree to the same restrictions and conditions that apply to the business associate with respect to such information" (164.504(e)(2)(ii)(D)).
Knowing about a subcontractor's problem creates a duty to act. A business associate that knew of a subcontractor's pattern of activity or practice that materially breached its agreement is out of compliance "unless the business associate took reasonable steps to cure the breach or end the violation, as applicable, and, if such steps were unsuccessful, terminated the contract or arrangement, if feasible" (164.504(e)(1)(iii)). Health Fitness Corporation's corrective action plan includes a review of its vendor and contractor relationships to confirm that business associate agreements are in place where required.
When an incident happens at a business associate
Two reporting duties apply, and they differ in size. The business associate agreement must require the vendor to "report to the covered entity any security incident of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410" (45 CFR 164.314(a)(2)(i)(C)). A security incident is "the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system" (164.304), which reaches well past breaches, so read how each agreement defines what must be reported and how fast.
The breach rule itself says a business associate "shall, following the discovery of a breach of unsecured protected health information, notify the covered entity of such breach," and do so "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach" (164.410(a)(1) and (b)). The notice must identify, to the extent possible, each individual whose information has been, or is reasonably believed to have been, accessed, acquired, used, or disclosed, along with any other available information the covered entity needs for its notices to individuals, sent with the notice or "promptly thereafter as information becomes available" (164.410(c)).
Discovery is not the day management hears about it. A breach is treated as discovered on the first day it is known to the business associate or, by exercising reasonable diligence, would have been known. The company is deemed to know of a breach that is known, or by exercising reasonable diligence would have been known, to any employee, officer, or other agent other than the person who committed it, with agency judged under the federal common law of agency (164.410(a)(2)). An employee who knows about a breach and says nothing does not stop the clock.
The covered entity then decides on notices to individuals, HHS, and the media. When a vendor skips its own step, OCR treats that as a violation in itself: the MMG Fusion findings include the failure to notify its covered entity clients. The breach notification deadline calculator works out the outer-limit dates from a discovery date.
Checklist
A business associate compliance checklist
| Requirement | Rule | Evidence to keep |
|---|---|---|
| Business associate status | 160.103 | A list of clients, the information each one sends, and the service it supports. |
| A business associate agreement with each client | 164.502(e); 164.504(e); 164.314(a) | Signed agreements, with each one's incident reporting window noted where staff can find it. |
| Risk analysis | 164.308(a)(1)(ii)(A) | A dated, accurate and thorough assessment of the risks to the electronic patient information the company holds. |
| Risk management | 164.308(a)(1)(ii)(B) | A plan that brings the risks found down to a reasonable and appropriate level, with owners and dates. |
| Sanction policy | 164.308(a)(1)(ii)(C) | A written policy and a record of sanctions applied to workforce members who failed to comply with security policies. |
| Information system activity review | 164.308(a)(1)(ii)(D) | Records of regular reviews of audit logs, access reports, and security incident tracking reports. |
| Security official | 164.308(a)(2) | A written designation of the person responsible for security policies and procedures. |
| Security awareness and training | 164.308(a)(5) | Training dates, attendees, topics, and certificates for everyone in the workforce, management included. |
| Security incident procedures | 164.308(a)(6) | An incident log showing the response, the mitigation, and the outcome of each incident. |
| Contingency plan | 164.308(a)(7) | A data backup plan that keeps retrievable exact copies, a disaster recovery plan, and an emergency mode operation plan. |
| Evaluation | 164.308(a)(8) | A periodic technical and nontechnical evaluation, with its date and findings. |
| Subcontractor agreements | 164.502(e)(1)(ii); 164.308(b)(2) | A signed agreement with each subcontractor that handles the information. |
| Physical safeguards | 164.310 | Facility access controls, workstation use and security rules, and device and media controls. |
| Technical safeguards | 164.312 | Access control, audit controls, integrity controls, person or entity authentication, and transmission security. |
| Policies, documentation, and retention | 164.316 | Written policies and required records, reviewed periodically and kept for six years. |
| Breach reporting to clients | 164.410 | A procedure that gets breach facts to each client within its agreement's window and no later than 60 days. |
| Use, disclosure, and minimum necessary limits | 164.502(a)(3); 164.502(b) | Access rules that match what each agreement permits and what each job needs. |
The physical and technical safeguards are set out in 164.310 and 164.312. Encryption is an addressable specification under access control (164.312(a)(2)(iv)), so a vendor that does not encrypt stored data has to document why and implement an equivalent alternative measure if one is reasonable and appropriate (164.306(d)(3)). For the risk analysis itself, the risk assessment cost guide compares the free HHS tool with paid options.
What a HIPAA certificate does for a business associate
No federal agency certifies business associates. In FAQ 2003, HHS says it does not endorse or otherwise recognize private organizations' certifications regarding the Security Rule, and that such certifications do not absolve covered entities of their legal obligations. In FAQ 237, asked whether business associates can self-certify or be certified by a third party instead of entering into a contract, HHS answers no: the covered entity still needs the written agreement that 164.504(e) describes.
A training certificate documents that one person completed a course on a date. It is the record a client can ask for in a vendor review, and the evidence a business associate shows when asked about its training program. A USA HIPAA certificate shows the learner's name, the course, the completion date, a verification code, and an expiration date one year after issue, and a client can check it on the public verification page. Completing training shows that staff were trained. Whether the company complies with HIPAA depends on its risk analysis, its safeguards, its agreements, and its records.
Training
HIPAA training for a business associate team
| Team | Course | Price per learner |
|---|---|---|
| Billing, coding, IT, software, consulting, accounting, and other vendor staff | HIPAA for Vendors & Business Associates | $29 |
| Vendor staff who work inside a client's clinical workflow, such as scribes or on-site support | HIPAA Essentials (Privacy + Security) | $39 |
| Vendor teams that handle patient information in Texas | Texas HB300 Training Online, alongside the HIPAA course | $19 |
USA HIPAA's vendor course covers business associate agreements, subcontractors, permitted uses, access discipline, security safeguards, client communication, and incident reporting, and ends with an assessment and a certificate with a one-year term that a client can verify. For a team, the vendor course is priced from $22 per learner for 2 to 9 learners down to $12 for 100 to 1,000, and team training adds seat assignment and completion tracking.
Help me choose matches each role to a course. You can also see how HIPAA certification works, how online HIPAA training providers compare, and current pricing. Vendors with Texas clients should also read the Texas HB 300 guide, because Texas law defines a covered entity more broadly than HIPAA does.
Primary sources
- 45 CFR 160.103, definitions of business associate, subcontractor, and workforce; 160.310 and 160.316, cooperation with HHS and retaliation; 160.402, civil money penalties and liability for agents.
- The Security Rule: 45 CFR 164.302, 164.304, 164.306, 164.308, 164.310, 164.312, 164.314, and 164.316.
- 45 CFR 164.410, notification by a business associate; 164.502, 164.504(e), and 164.530(b), uses and disclosures, business associate contracts, and Privacy Rule training.
- HITECH Act sections 13401 and 13404, 42 U.S.C. 17931 and 42 U.S.C. 17934 (text as published by the Legal Information Institute).
- The Omnibus final rule, 78 FR 5566 (January 25, 2013), discussion of business associate status and direct liability at 5598 to 5599, and the proposed Security Rule changes, 90 FR 898 (January 6, 2025).
- HHS guidance: the direct liability fact sheet, the business associate guidance, the cloud computing guidance, and FAQs 237, 245, and 2003.
- HHS announcements of the settlements with CHSPSC, USR Holdings, Health Fitness, Comstar, BST & Co., MMG Fusion, and Consociate Health, and the resolution agreements index.
Regulatory text read November 20, 2026. Educational information about federal law, not legal advice. USA HIPAA is not affiliated with or endorsed by HHS or OCR. Regulatory text changes, so check the current text and ask qualified counsel before relying on it for a specific decision.
Related
Tools and guides for vendors that handle patient information
Free tool
HIPAA Covered Entity Checker
Answers whether an organization is a covered entity, a business associate, or neither.
Check your statusFree tool
HIPAA BAA Generator
Drafts a business associate agreement built on the HHS sample clauses, with your names and terms.
Draft the agreementFree tool
HIPAA Risk Assessment Tool
A self-check of cited safeguards that organizes follow-up work. It does not replace a formal risk analysis.
Start the self-checkFree tool
Breach Notification Deadline Calculator
Works out the federal outer-limit dates, including a business associate's notice to its client.
Calculate the deadlinesGuide
HIPAA Risk Assessment Cost
The free HHS tool, software prices, outside assessors, and the staff time each option takes.
Compare the costsFree tool
Who Needs HIPAA Training
Sorts employees, contractors, and vendors into who needs training and who needs an agreement.
Plan the rosterFAQs
Questions about HIPAA for business associates
Do business associates need HIPAA training?
Yes. The Security Rule applies directly to business associates (45 CFR 164.302), and it requires a security awareness and training program for all members of the workforce, including management (164.308(a)(5)(i)). The Privacy Rule's training standard at 164.530(b) is written for covered entities, but a business associate agreement can require privacy training, and staff still have to follow the use, disclosure, and minimum necessary limits the company is directly liable for. Keep the training records for six years (164.316(b)(2)(i)).
Are business associates directly liable under HIPAA?
Yes, for a defined set of requirements. In the 2013 Omnibus rule, HHS said business associates are directly liable for impermissible uses and disclosures, failing to notify the covered entity of a breach, failing to provide electronic copies for access requests as the agreement specifies, failing to disclose protected health information when HHS requires it to investigate the business associate's compliance, failing to provide an accounting of disclosures, and failing to comply with the Security Rule (78 FR 5598 to 5599). The rules also require agreements with subcontractors and bar retaliation. Other terms of the business associate agreement bind the vendor as a contract.
Is there a HIPAA certification for business associates?
Not from the government. HHS does not endorse or recognize private organizations' certifications regarding the Security Rule (FAQ 2003), and HHS FAQ 237 answers no to whether a business associate can self-certify or be certified by a third party instead of entering into a contract. A certificate from a training provider shows that one person completed a course. USA HIPAA's vendor course ends with an assessment and a certificate a client can verify online.
How long does a business associate have to report a breach?
No later than 60 calendar days after discovery, and without unreasonable delay (45 CFR 164.410(b)). The business associate agreement can set a shorter window, and the vendor is bound by it as a contract term. A breach counts as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to any employee, officer, or other agent of the business associate other than the person who committed it (164.410(a)(2)).
Does a vendor that never signed a business associate agreement still have to comply?
Yes. In the 2013 Omnibus rule HHS wrote that a person becomes a business associate by definition, not by the act of contracting, and that liability for impermissible uses and disclosures attaches immediately once the definition is met (78 FR 5598). The covered entity that shared the information without an agreement is out of compliance too, because 164.502(e) requires satisfactory assurances before it discloses.
How often should a business associate retrain its staff?
The Security Rule sets no fixed interval. It requires a security awareness and training program, lists security reminders (periodic security updates) as an addressable specification (164.308(a)(5)(ii)(A)), and requires documentation to be reviewed periodically and updated as needed in response to environmental or operational changes affecting the security of the information (164.316(b)(2)(iii)). A client can set a schedule in the business associate agreement. USA HIPAA certificates carry an expiration date one year after issue, which fits an annual cycle.
Does a business associate need its own risk analysis?
Yes. The risk analysis specification covers electronic protected health information held by the covered entity or business associate (164.308(a)(1)(ii)(A)), so a vendor cannot rely on its client's assessment. OCR's settlements with CHSPSC, USR Holdings, Health Fitness, Comstar, BST & Co., MMG Fusion, and Consociate Health each included a finding about the risk analysis.
Is a cloud or software company that stores only encrypted data a business associate?
Yes, if it maintains electronic protected health information for a covered entity or another business associate. HHS's cloud computing guidance says such a provider is a business associate even if it holds no decryption key and cannot view the data, and that the rules are flexible enough to account for that limited access. It still has to report breaches to its customer.
Get certified today
HIPAA for Vendors & Business Associates for $29
Role-specific training for vendor teams on BAAs, permitted uses, security safeguards, and incident reporting, with a downloadable certificate.
One-time payment is available. Optional annual plan shown at checkout.
Team price per learner
- 2-9 learners$22
- 10-24 learners$18
- 25-49 learners$16
- 50-99 learners$14
- 100-1,000 learners$12
More than 1,000 learners? Contact us.
USA HIPAA