What Is Clearinghouse?
A clearinghouse is a HIPAA-defined entity that processes health information from one format into a standard electronic format and transmits 837 claims, 835 remittances, 270/271 eligibility, and 276/277 claim status transactions between providers and payers.
- The February 2024 cyberattack on Change Healthcare is the concentration-risk case study, and CMS's own response is the sourced measure of the disruption.
- The operating lesson is to know the fallback before it is needed: identify which of your highest-volume payers accept direct submission or portal entry, confirm the credentials are current, and test the route once.
- A second clearinghouse contract is one way to do that, not a universal requirement — for a small practice a documented portal-entry procedure for a handful of payers may be the cheaper equivalent.
Clearinghouse
Also known as: EDI Clearinghouse; Claims Clearinghouse
A clearinghouse is a HIPAA-defined entity that processes health information from one format into a standard electronic format and transmits 837 claims, 835 remittances, 270/271 eligibility, and 276/277 claim status transactions between providers and payers.
Definition
45 CFR 160.103 defines a health care clearinghouse as a public or private entity — the definition names billing services, repricing companies and value-added networks and switches — that processes health information received in a nonstandard format into standard data elements or a standard transaction, or does the reverse for a receiving entity. Clearinghouses used by physician practices include Availity, Optum (Change Healthcare), Waystar, Trizetto Provider Solutions, Office Ally and Inovalon; that list is illustrative and ownership changes hands, so confirm who operates a given connection before relying on it. A clearinghouse routes 837 professional and institutional claims to payer endpoints, passes back the acknowledgments the receiving system generates, delivers 835 ERAs, and supports 270/271 eligibility and 276/277 claim status transactions. The acknowledgments are worth separating from the clearinghouse's own edits: a TA1 interchange acknowledgment, a 999 implementation acknowledgment and a 277CA claim acknowledgment are produced by the system that received the file, and for Medicare fee-for-service that is the MAC's or CEDI's own front end, not the clearinghouse — Medicare Claims Processing Manual, Chapter 24 §50.3.3 sets out that model. On privacy standing, a clearinghouse is itself a covered entity under 45 CFR 160.103, but which obligations attach depends on the capacity it is acting in: 45 CFR 164.500(b) applies a narrowed set of Privacy Rule requirements when a clearinghouse creates or receives protected health information as a business associate of another covered entity, and the full subpart when it does so other than as a business associate. A practice engaging a clearinghouse to process its claims is normally in the first case, which is why the engagement is papered with a business associate agreement — the specifics of any particular arrangement depend on the rule as applied to it and on your own legal advice.
Example
A practice submits an 837P claim batch to its clearinghouse. The clearinghouse runs its own syntax and payer-specific edits and returns those rejections directly, then routes what passes to the payer over a direct connection or a partner network. The payer's front end then issues its own acknowledgments — for Medicare fee-for-service, a TA1, a 999 and a 277CA from the MAC or CEDI — and a claim rejected at that stage is returned before adjudication. Claims that clear both layers are adjudicated, and the 835 ERA travels back along the same path. A typical claim's journey: provider PM → clearinghouse edits → payer front-end acknowledgments → payer adjudication → ERA → clearinghouse → provider PM auto-post.
Common Misconceptions
Clearinghouses are not payers — they are intermediaries. A rejection and a denial are also different events, and the 999 and 277CA are not evidence of a clearinghouse rejection: those are acknowledgments issued by the system that received the file, which for Medicare fee-for-service is the payer's own front end. A rejection stops a claim before adjudication and carries no payment determination; a denial is an adjudicated outcome reported on the 835 with CARC and RARC codes. Appeal rights follow whichever rule applies. For Medicare, the Medicare Claims Processing Manual, Chapter 1 §80.3.1 states that a claim returned as unprocessable for incomplete or invalid information “does not meet the criteria to be considered as a claim, is not denied, and, as such, is not afforded appeal rights.” Commercial appeal and prompt-pay rights are set by the contract and by state law, so do not assume the Medicare treatment carries across.
Practical Application
The February 2024 cyberattack on Change Healthcare is the concentration-risk case study, and CMS's own response is the sourced measure of the disruption. CMS opened Change Healthcare/Optum Payment Disruption accelerated and advance payments on 9 March 2024 for providers and suppliers that could not submit or be paid on claims, and on closing the program reported having issued accelerated payments to over 4,200 Part A providers totaling more than $2.55 billion and 4,722 advance payments totaling more than $717.18 million to Part B suppliers (CMS newsroom, program closed 12 July 2024). The operating lesson is to know the fallback before it is needed: identify which of your highest-volume payers accept direct submission or portal entry, confirm the credentials are current, and test the route once. A second clearinghouse contract is one way to do that, not a universal requirement — for a small practice a documented portal-entry procedure for a handful of payers may be the cheaper equivalent.
Related Terms
X12 (HIPAA EDI)
ASC X12 is the standards body whose X12N subcommittee develops the HIPAA-named electronic data interchange transactions for healthcare administrative data: 837 (claims), 835 (remittance), 270/271 (eligibility), 276/277 (claim status), 278 (prior auth), and 834 (enrollment).
Read definitionPM (Practice Management) System
A Practice Management system is the software that handles the operational and financial workflow of a medical practice — scheduling, registration, eligibility, charge entry, claim submission, payment posting, A/R follow-up, and reporting — typically integrated with or embedded in an EHR.
Read definitionERA (Electronic Remittance Advice / 835)
The ERA (X12 835 transaction) is the HIPAA-standard electronic file payers send to providers detailing claim adjudication results — payments, adjustments, denials with CARC/RARC codes — typically paired with EFT funds transfer.
Read definitionClaim Scrubbing
Claim scrubbing is the automated pre-submission process that runs claims through a rule-set of payer-specific and standards-based edits (NCCI, MUE, HIPAA syntax, payer policies) to identify and correct errors before the claim leaves the practice.
Read definitionWhere This Applies on MedPrecision
Need help with billing?
If this term is showing up in your denials, EOBs, or A/R aging, we can help. Get a free billing audit and we will trace the issue to its root cause.
- No contract
- No setup fees
- Reply within 1 business day