HIPAA Compliance by Vertical

HIPAA Compliance for Medical Billing Companies

HIPAA compliance for medical billing — a business associate of every client, directly liable under the Security Rule, with many clients' PHI on one platform.

Key takeaways

  • PHI in scope: Patient demographic and insurance data, Diagnoses, procedure codes, and clinical context, Insurance claims and EOBs, Patient statements and collections data.
  • Start with these controls: A BAA with every client, with the signed version tracked; Subcontractor inventory with a BAA for each subcontractor that handles PHI; Access controls that keep each client's PHI separate, with documented reviews.
  • The most common mistake: No record of which BAA version each client signed
  • A signed BAA is required with every vendor that creates, receives, maintains, or transmits PHI on your behalf, and no tool is HIPAA compliant on its own.

PHI handled in this environment

  • Patient demographic and insurance data
  • Diagnoses, procedure codes, and clinical context
  • Insurance claims and EOBs
  • Patient statements and collections data
  • Denied claims and appeal documentation

Common compliance pain points

  • A BAA with every client: A billing company is a business associate of every covered entity it serves, and each relationship needs a BAA. Clients often send their own templates, so a billing company can end up on dozens of different terms, including different breach-notice deadlines. Track which version each client signed.
  • Subcontractor BAAs: Billing companies often use subcontractors: coders, collection agencies, offshore staffing firms, and AI tools. HIPAA requires a BAA with each subcontractor that handles PHI (45 CFR 164.502(e)(1)(ii) and 164.504(e)(5)). Many client BAAs also require the billing company to disclose or get approval for its subcontractors.
  • PHI segregation across clients: A business associate may only use and disclose each client's PHI as that client's BAA permits. Staff and systems should not expose one client's patients to another client, and access controls should be documented and reviewable.
  • Workforce access in offshore operations: HIPAA does not prohibit offshore work, but the obligations follow the PHI: workforce training, BAAs with offshore staffing firms, documented data flows, and any client BAA restrictions on offshore access.

Priority controls

  • A BAA with every client, with the signed version tracked
  • Subcontractor inventory with a BAA for each subcontractor that handles PHI
  • Access controls that keep each client's PHI separate, with documented reviews
  • Workforce HIPAA training, including offshore staff
  • Encryption of ePHI in transit and at rest (addressable today; proposed as required in HHS's January 2025 NPRM)
  • Audit logs and regular review of information system activity (45 CFR 164.308(a)(1)(ii)(D) and 164.312(b))

Common mistakes

  • No record of which BAA version each client signed
  • Subcontractor list out of date; an offshore coding firm has no current BAA
  • Platform permissions that let staff or users see another client's patients
  • No documented workforce HIPAA training for offshore staff
  • Terminated employees keeping access for weeks after departure

Enforcement context

Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit, and OCR can investigate a billing company directly. Because one billing platform can hold PHI for many covered entities, a single incident can trigger breach notifications from every affected client. HHS's January 2025 Security Rule proposal (90 FR 898) would, if finalized, also require business associates to verify their technical safeguards to covered entities at least once every 12 months; it is a proposal, not current law.

Frequently asked questions

What PHI do medical billing company organizations handle?

Patient demographic and insurance data; Diagnoses, procedure codes, and clinical context; Insurance claims and EOBs; Patient statements and collections data; Denied claims and appeal documentation. Any of these, combined with an identifier, is protected health information when a covered entity or business associate holds it, and in electronic form it brings the Security Rule into scope.

What are the priority HIPAA controls for medical billing company?

A BAA with every client, with the signed version tracked; Subcontractor inventory with a BAA for each subcontractor that handles PHI; Access controls that keep each client's PHI separate, with documented reviews; Workforce HIPAA training, including offshore staff; Encryption of ePHI in transit and at rest (addressable today; proposed as required in HHS's January 2025 NPRM); Audit logs and regular review of information system activity (45 CFR 164.308(a)(1)(ii)(D) and 164.312(b)).

What are the most common HIPAA mistakes in medical billing company?

No record of which BAA version each client signed; Subcontractor list out of date; an offshore coding firm has no current BAA; Platform permissions that let staff or users see another client's patients; No documented workforce HIPAA training for offshore staff; Terminated employees keeping access for weeks after departure.

What does HIPAA enforcement look like for medical billing company?

Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit, and OCR can investigate a billing company directly. Because one billing platform can hold PHI for many covered entities, a single incident can trigger breach notifications from every affected client. HHS's January 2025 Security Rule proposal (90 FR 898) would, if finalized, also require business associates to verify their technical safeguards to covered entities at least once every 12 months; it is a proposal, not current law.