
A medical billing company is a HIPAA business associate, not a covered entity, when it creates, receives, maintains, or transmits protected health information (PHI) on your practice's behalf. So what compliance do medical billing companies need as business associates under HIPAA? The requirements are the same as for any other business associate: a signed Business Associate Agreement (BAA) and full implementation of the HIPAA Security Rule's administrative, physical, and technical safeguards, codified at 45 CFR Part 164, Subpart C.
Under 45 CFR 160.103, a business associate is any person or entity that creates, receives, maintains, or transmits individually identifiable health data, such as diagnosis codes, claim details, and insurance information, on behalf of a covered entity. A billing company meets that definition every time it processes a claim.
If a billing vendor can't produce a signed BAA, a written security policy, and evidence of workforce training, your practice, the covered entity, carries the compliance and breach notification exposure, not just the vendor.
Quick Answer
A medical billing company is a HIPAA business associate, not a covered entity, so it must sign a BAA with each practice it serves and implement the Security Rule's administrative, physical, and technical safeguards. It must also report security incidents and breaches involving PHI and limit PHI use to what the BAA authorizes. Outsourcing billing does not transfer your practice's compliance obligation. Your practice must still verify the vendor actually meets these requirements, not just that it signed a contract.
Key Takeaway
Medical billing companies are HIPAA business associates under 45 CFR 160.103, which means a signed BAA, documented Security Rule safeguards, and a breach notification process are mandatory, not optional. A signed contract alone doesn't prove compliance. Your practice keeps the compliance and breach notification exposure even after billing is outsourced, and that oversight duty applies whether the vendor is a two-person shop or a national processor.
The BAA is the contract that makes a billing vendor's obligations under the HIPAA Security Rule enforceable. It spells out how the vendor may use and disclose PHI, what safeguards it must maintain, and how quickly it must notify you if something goes wrong.
Without a signed BAA, you have no documented commitment that the vendor will protect patient data or return or destroy PHI when the relationship ends. Specific contract language, including subcontractor obligations and indemnification terms, is a legal matter your attorney should review before you sign.
A signed BAA is the starting point, not the finish line. The Security Rule expects covered entities to exercise reasonable diligence over the business associates they choose, which means reviewing how the billing company secures its own systems rather than accepting a signature on a contract.
This is the same vendor-vetting exercise practices go through with other business associates. A chiropractic office outsourcing billing runs through a comparable checklist to the one covered in HIPAA compliance for chiropractors, and the underlying safeguard categories match the ones described in a practice's own healthcare data security plan.
If the billing company sends claim status updates or patient statements by email, confirm those messages use encrypted email built for healthcare rather than standard, unencrypted email, a common and easily overlooked gap.
Vendor Due Diligence Checklist
- Get a signed BAA before any PHI is transmitted to the billing company
- Request the vendor's most recent HIPAA risk analysis or security assessment summary
- Confirm PHI is encrypted in transit and at rest on the vendor's systems
- Ask how the vendor authenticates staff access (individual logins, MFA, role-based permissions)
- Confirm workforce HIPAA training is documented and refreshed annually
- Get the vendor's breach notification timeline and process in writing
- Confirm data return or destruction procedures for when the contract ends
Your Practice Is Still on the Hook for Breach Notification
If your billing company has a security incident involving your patients' PHI, HIPAA still requires notification to affected individuals and, in many cases, to the HHS Office for Civil Rights. Patients associate the incident with your practice's name, regardless of whose systems were affected.
A strong BAA should specify how quickly the vendor must notify you so you can meet your own notification deadline. Review how HIPAA breach penalties are assessed so you understand what's at stake if a vendor's incident isn't reported on time.
A short set of direct questions during vendor evaluation tells you how seriously a billing company treats security. Ask how it handles a lost or stolen employee laptop, whether it subcontracts any billing functions to a fourth party (which would require its own BAA), and how it would walk you through its incident response process if something went wrong.
A vendor with a mature security program answers these specifically. One that responds with vague reassurance is worth a second look before you hand over patient data. The NIST SP 800-66 guide for implementing the HIPAA Security Rule gives smaller billing companies a practical framework for building these controls, and it's a fair benchmark to ask a vendor whether it follows.
These requirements apply regardless of a vendor's size. A small, local billing company has to implement the same safeguard categories as a large national one. It can scale how it implements controls, but it cannot skip a required category.
Talk with a cybersecurity expert
Get a practical review of the access, encryption, and monitoring controls a HIPAA business associate like your billing vendor should already have in place.
Frequently Asked Questions
No. A BAA is a contractual commitment, not proof of compliance. The billing company still has to implement the required administrative, physical, and technical safeguards; the BAA documents that it agreed to.
Both parties can face liability. HHS Office for Civil Rights can investigate the business associate directly, but your practice, as the covered entity, is still expected to show it exercised reasonable oversight in choosing and managing that vendor. This is a legal determination that depends on the facts, so consult counsel if a breach occurs.
Yes. HIPAA Security Rule requirements apply based on whether an entity handles PHI, not its size. Smaller billing companies can scale how they implement controls, but they cannot skip required safeguard categories.
At minimum, permitted uses of PHI, required safeguards, breach notification timelines, subcontractor obligations, and data return or destruction terms at contract end. Specific language should be reviewed by your attorney.
From requirement to defensible practice
Turn HIPAA requirements into safeguards that fit patient care
A useful compliance path makes the obligation clear, identifies the evidence to retain, and connects written policy to the safeguards used every day.
People also look for
Keep exploring HIPAA security
Connect HIPAA requirements to the safeguards, assessments, and everyday decisions a healthcare practice can actually implement.
- Common question: HIPAA cybersecurity requirementsUse the plain-language HIPAA guideUnderstand administrative, physical, and technical safeguards without sorting through legal language.
- Common question: HIPAA security risk assessmentPrepare for a HIPAA risk assessmentIdentify vulnerabilities, document risk, and prioritize the gaps that matter most.
- Common question: HIPAA Security Rule explainedReview the HIPAA Security RuleSee how the standards and implementation specifications fit together.
- Common question: healthcare ransomware protectionReduce healthcare ransomware riskProtect patient data and keep clinical operations recoverable after an attack.
- Common question: HIPAA endpoint securityProtect practice workstations and devicesApply managed endpoint detection to the devices that access protected health information.



