Revenue cycle work runs on PHI: demographics, insurance details, diagnosis and procedure codes, clinical documentation for appeals and payment histories. Billing companies, coding vendors, collection agencies and clearinghouses typically handle that data for dozens or hundreds of provider clients at once, which concentrates risk — one compromised account can expose many clients’ patients.
The first compliance question is which role you play. HIPAA treats a health care clearinghouse as a covered entity in its own right, while most billing companies are business associates of the providers they serve. Some organizations do both. Getting this right determines which parts of the rules apply to you directly and how your contracts should be written.
Clearinghouse or billing company?
Under §160.103, a health care clearinghouse is an entity that processes health information received in a nonstandard format into standard data elements or a standard transaction (or the reverse). The label on the business does not decide it; the function does. A billing service that performs this conversion can be a clearinghouse even if it does not call itself one.
| Organization | Typical HIPAA role | Notes |
|---|---|---|
| Health care clearinghouse | Covered entity — and usually also a business associate of the providers and plans it serves | When acting as a business associate, the Privacy Rule applies to a clearinghouse in a more limited way (§164.500(b)); the Security Rule applies in full |
| Billing company or RCM vendor submitting claims through a clearinghouse | Business associate of each provider client | Needs BAAs with clients and with its own subcontractors, such as the clearinghouse it uses, hosting and offshore staffing vendors |
| Coding, audit or denial-management firm | Business associate | Often handles full clinical documentation, so minimum necessary and access scoping matter |
| Collection agency handling patient accounts | Typically a business associate of the provider | Fair debt collection and state laws also apply; disclosures to the agency should be limited to what collection requires |
Risk areas in billing operations
Payer portal and EHR credentials
Billing staff often log into client EHRs and dozens of payer portals. Shared credentials, credentials stored in spreadsheets and accounts that stay active after a client relationship ends are recurring findings. Each portal is a path into PHI and should be inventoried and managed.
Minimum necessary
§164.502(b) requires reasonable efforts to limit PHI to the minimum necessary for the purpose. For billing, that usually means role-based access to client systems and limiting coders to the encounters they work rather than whole charts by default.
Offshore and remote workforces
HIPAA does not prohibit offshore work, but the risk analysis must account for it, and many client BAAs, payer contracts and some government program rules restrict it. Know which clients prohibit offshore access before assigning work queues.
Patient statements and print-and-mail
Statement vendors, lockbox services and print-and-mail houses receive PHI and need BAAs. Misaddressed or mis-collated statements are a classic source of small breaches that still require a documented risk assessment.
Breach notification as a business associate
When a billing company discovers a breach of unsecured PHI, §164.410 requires it to notify the affected covered entity without unreasonable delay and no later than 60 calendar days after discovery, identifying the affected individuals where possible. Many client BAAs shorten that window considerably. Because a single incident may affect many clients, each with different contractual deadlines, billing companies benefit from a pre-built client notification matrix.
Challenges specific to billing companies
- Dozens of client BAAs with inconsistent terms and no central tracking of obligations.
- Client offboarding that leaves system access and stored data in place.
- Rapid hiring during client onboarding, with training and access reviews lagging behind.
- Email used to exchange remittances, EOBs and appeal documentation with clients.
How we tailor billing and RCM engagements
We usually begin by confirming the HIPAA role of each business line, then run a HIPAA risk assessment covering client system access, payer portals, workforce locations and subcontractors. Business associate compliance work organizes your client and subcontractor BAAs into a register of obligations you can operate against.
Billing companies whose clients send security questionnaires or ask for evidence often add HIPAA audit readiness support, and many benefit from rehearsing a multi-client incident through HIPAA breach response consulting.
Workforce security in a high-volume operation
Billing companies are workforce-intensive: coders, billers, follow-up specialists and customer service staff working through queues of client accounts, often remotely. The Security Rule’s administrative safeguards apply directly to business associates, including workforce security procedures (§164.308(a)(3)), security awareness training (§164.308(a)(5)) and a sanctions policy for workforce members who violate security policies.
In practice, the controls that matter most are fast provisioning and de-provisioning tied to HR events, access scoped to the clients a person actually works on, periodic access reviews per client, and clear rules for remote workers about printing, screen privacy and personal devices. Training works best when it uses billing scenarios — a remittance emailed to the wrong practice, a payer portal password shared with a teammate, a patient calling about a balance — rather than hospital-centric examples that staff cannot relate to their work.
Starting checklist for billing companies
- 1
Classify each service line
Decide with counsel whether any service performs clearinghouse functions, and document your role for each client relationship.
- 2
Build a BAA obligations register
Record each client’s notification window, offshore restrictions, audit rights and data return terms in one place.
- 3
Inventory credentials
List every client EHR and payer portal account, who holds it and whether it is unique to that person.
- 4
Tighten offboarding
Create a checklist for removing access and returning or destroying data when a client or employee leaves.
- 5
Rehearse a multi-client breach
Run a tabletop exercise where one compromised mailbox affects several clients with different deadlines.
Frequently asked questions
Is a medical billing company a covered entity?
Usually not. Most billing companies are business associates of the providers they serve. A billing company that converts nonstandard data into standard transactions may meet the definition of a health care clearinghouse, which is a covered entity. The answer depends on what you actually do.
Can we use offshore coders or billers?
HIPAA does not prohibit it, but your risk analysis must address it, and client BAAs, payer contracts or government program requirements may restrict it. Check each client’s terms before assigning offshore staff.
How quickly must we notify a client of a breach?
The regulatory outer limit is 60 calendar days after discovery, and notice must be without unreasonable delay. Many BAAs require faster notice, sometimes within days, so follow the shortest applicable contractual deadline.
Do we need BAAs with our own vendors?
Yes, where they create, receive, maintain or transmit PHI on your behalf. Clearinghouses, hosting providers, statement vendors and staffing firms commonly qualify as your subcontractors.
Authoritative sources
- eCFR — 45 CFR Part 164
- HHS — Breach Notification Rule
- HHS — Sample Business Associate Agreement Provisions
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.