Ruleweld

RULEWELD / PRACTICAL GUIDE

HIPAA basics for small vendors.

A clear first pass for service providers that work with health organizations or their information.

i

General information only. This guide is not legal advice or an assessment of your organization. It is not a certification or guarantee of HIPAA compliance.

IN THIS GUIDE

Who may be coveredPractical dutiesSmall-organization resourcesSources and authority

START WITH THE ROLE

HIPAA follows the work, not the headcount.

The HIPAA Rules apply to covered entities and business associates. Covered entities are health plans, health care clearinghouses, and health care providers that transmit health information electronically in a transaction for which HHS has adopted a standard. A company is not covered just because it works in health care. HHS: covered entities↗·45 CFR § 160.103↗

TWO ROLES TO DISTINGUISH

Ask what the organization actually does

01

Covered entities provide or pay for care

The covered-entity categories are specific: health plans, clearinghouses, and qualifying health care providers. For providers, the definition includes an electronic transaction test. Use the regulatory definitions and HHS decision guidance to check the organization’s actual role. Binding text: 45 CFR § 160.103↗·HHS: covered entities↗

02

Business associates perform work involving PHI

A vendor may be a business associate when it performs a regulated function or service for a covered entity, involving protected health information (PHI). HHS examples include claims processing, billing, data analysis, practice management, cloud storage, and IT support that involves access to electronic PHI. A subcontractor that creates, receives, maintains, or transmits PHI for a business associate may also be a business associate. The service relationship and actual handling matter; a vendor label alone does not decide it. HHS: business associate examples↗·45 CFR § 160.103↗

03

Small size or low volume is not a general exemption

The definitions do not create a blanket safe harbor for a small vendor or a vendor handling little PHI. A provider’s covered-entity definition includes its own electronic-transaction condition, but a vendor’s business-associate status turns on the service, relationship, and PHI involved. Check the applicable definition rather than relying on employee count or volume. Binding definitions: 45 CFR § 160.103↗·HHS: business associates↗

IF YOUR ROLE IS IN SCOPE

Four areas to put in order

These are orientation points, not a complete compliance checklist. The rules, contracts, and facts of each relationship matter.

A / AGREEMENT

Keep PHI within the BAA

A business associate agreement (BAA) sets permitted and required uses and disclosures. It must limit further use or disclosure to what the agreement or law allows, require appropriate safeguards, and pass relevant restrictions to subcontractors. At termination, it generally addresses returning or destroying PHI when feasible. Read the actual agreement and map each service to it. Binding text: 45 CFR § 164.504(e)↗

B / SAFEGUARDS

Protect PHI and ePHI

The Security Rule requires applicable administrative, physical, and technical safeguards for electronic PHI. Business associates must comply with applicable Security Rule requirements; BAA terms also define responsibilities for PHI and for any Privacy Rule work the business associate performs for the covered entity. Business associates are also directly liable under certain provisions of the HIPAA Rules. HHS: business associate duties↗·45 CFR § 164.306↗

C / INCIDENTS

Escalate incidents and breaches

Follow the BAA’s security-incident reporting terms. If a breach of unsecured PHI occurs at or by a business associate, it must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery; the BAA may require faster notice. The covered entity generally handles notices to individuals and HHS. 45 CFR § 164.314(a)(2)(i)(C)↗·Binding text: 45 CFR § 164.410↗·HHS: breach notification↗

D / RISK ANALYSIS

Assess risks, then manage them

The Security Rule requires an accurate and thorough risk analysis of potential threats and vulnerabilities to ePHI, followed by risk management. The method may fit the organization, but the risk-analysis requirement remains. Document the systems and data in scope, risks found, and actions taken. Binding text: 45 CFR § 164.308(a)(1)↗

FLEXIBLE DOES NOT MEAN OPTIONAL

Use the rules and tools to fit your organization

The Security Rule allows reasonable and appropriate security measures to reflect size, complexity, capabilities, infrastructure, cost, and the probability and criticality of risks. Those factors shape implementation; they do not erase applicable safeguards or the risk-analysis requirement. 45 CFR § 164.306(b)↗·HHS: guidance on risk analysis↗

HHS GUIDANCE

Start with risk analysis

HHS explains the required risk-analysis objectives and notes that methods can vary with an organization’s size, complexity, and capabilities. ONC and HHS OCR’s Security Risk Assessment Tool is designed to help smaller health care practices and can assist business associates. It is a resource, not a certification or proof of compliance.

HHS OCR: risk-analysis guidance↗·ONC/OCR: Security Risk Assessment Tool↗

PRIMARY REGULATORY TEXT

Verify the requirements directly

  • 45 CFR § 160.103 — definitions↗
  • 45 CFR § 164.504(e) — business associate contracts↗
  • 45 CFR § 164.306 — security standards↗
  • 45 CFR § 164.308 — administrative safeguards↗
  • 45 CFR § 164.314 — security incident reporting↗
  • 45 CFR § 164.410 — business associate breach notices↗
  • HHS: sample BAA provisions↗

This page is general information, not legal advice. It does not determine whether HIPAA applies to any organization, assess an organization’s safeguards, provide certification, or guarantee compliance. For a specific arrangement, get qualified legal, privacy, or security advice.

Read the Ruleweld GDPR guide·Read the Ruleweld FAQ

FAQGDPR guideHIPAA guideSOC 2 catalogSOC 2 guide