Clearinghouse

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The legal term describes a function

Under current 45 CFR 160.103, a health care clearinghouse is a public or private entity that processes health information from nonstandard format or content into standard data elements or a standard transaction, or processes a standard transaction into nonstandard format or content for a receiving entity. Billing services, repricing companies, and certain networks qualify when they perform that function.

Health care clearinghouses are HIPAA covered entities. A company name or sales label cannot settle its legal role; the actual functions and relationships do. A routing vendor may also perform billing, claims administration, analytics, or other services.

HHS business-associate guidance gives a clearinghouse that translates a provider's nonstandard claim and forwards it to a payer as an example of a business associate. HHS also explains that one covered entity can act as another covered entity's business associate. Classify every contracted function, document the required written arrangements, and route legal conclusions to qualified privacy or legal reviewers.

A clearinghouse carries transactions between systems

The CMS Electronic Billing and EDI Transactions page describes Medicare fee-for-service exchanges among providers, clearinghouses or billing services, and contractors. Clearinghouses can support claims, eligibility, claim status, remittance, or other transactions, depending on their connections and contract.

Keep these states separate:

CMS's March 2026 Medicare claim-status fact sheet illustrates one Medicare fee-for-service route: the Medicare Administrative Contractor issues a 999 after initial front-end edits that determine whether the file is readable; after that stage passes, individual-claim checks against basic HIPAA implementation-guide requirements can produce a 277CA Health Care Claim Acknowledgment. That Medicare sequence does not define every payer, receiver, or clearinghouse route. A clearinghouse dashboard label by itself does not prove payer receipt unless the mapped artifact and the route's trading-partner instructions support that meaning.

Authorization, claim transmission, payer intake, any payer-defined clean-claim status, adjudication, remittance, and payment answer different questions. A successful clearinghouse step supplies evidence for that step alone.

Verify the exact route before launch

Build a payer-product route register. For each connection, record:

• transaction, adopted version, licensed implementation guide, and applicable companion guide
• payer, product, receiver ID, submitter ID, provider enrollment or trading-partner setup, and effective date
• vendor transformations, default values, edits, and responsibility for rule updates
• original outbound file, transformed file when available, every acknowledgment, and export rights
• practice claim ID, batch ID, clearinghouse IDs, payer control number, remittance trace, and payment trace
• rejected-file and rejected-claim ownership, response windows, escalation contacts, and outage process
• retry rules, duplicate controls, corrected-claim handling, termination support, and record retention
• fees for connections, enrollment, claims, rejections, resubmissions, attachments, support, and data access

The CMS adopted-standards page lists ASC X12 Version 5010 as the adopted format for nonpharmacy transactions and identifies the standards used for claims, eligibility, claim status, and remittance. Detailed requirements remain in the applicable licensed guide and trading-partner materials.

The CMS Medicare Fee-for-Service companion-guide page explains that its guides supplement the X12 implementation guides for named Medicare transactions. Scope each guide to the entity, transaction, route, product, and version it covers.

Preserve clinical and billing authority

The clearinghouse receives the claim transaction or other billing data the practice releases for that route. A transport, translation, or edit result does not by itself establish that an ABA service occurred, that documentation supports the claim, or that the coding decision is correct. The authorized clinical author or supervisor is responsible for clinical content and amendments within that person's scope; practice policy and applicable law govern amendment and signature requirements. A qualified coding or billing reviewer maps supported facts to the claim and approves administrative corrections within assigned authority.

Software and clearinghouse edits may flag missing or inconsistent data. Send clinical questions to the responsible clinician and billing-route questions to the qualified billing owner. Preserve the submitted version, rejection, correction source, user, time, and approval. A retry should link to its prior attempt instead of replacing its history.

One claim trace should connect the internal charge, released claim version, vendor receipt, transformation, acknowledgments, payer control number, status responses, remittance, ledger entries, and payment when present. Missing evidence stays visible with an owner and age.

A fictional batch shows four different yields

A fictional ABA practice releases 25 claims through a contracted route. The clearinghouse's claim-level report rejects two and marks 23 as forwarded. Clearinghouse forward yield is 23 of 25, or 92%.

The route expects a payer claim acknowledgment for each forwarded claim. By the defined cutoff, 22 are matched: 20 payer-accepted claims and two payer-rejected claims. One remains missing. Acknowledgment completeness is 22 of 23, or 95.7%. Acceptance among acknowledged claims is 20 of 22, or 90.9%. Known payer-intake yield from the original released batch is 20 of 25, or 80%.

Each denominator answers a different question. The two clearinghouse rejections, two payer rejections, and one missing acknowledgment remain in their own worklists. None of these rates measures adjudication or payment.

Measure the service and its controls

Useful measures include:

• route coverage: payer-product routes with passed testing and production-release evidence by the as-of date divided by routes due to be active by that date
• clearinghouse reject rate: released claim versions rejected by named clearinghouse edits divided by released claim versions with a final clearinghouse result
• payer-acknowledgment completeness: mature forwarded claim versions with a matched route-required claim-level acknowledgment divided by mature forwarded claim versions for which the route requires one
• end-to-end intake yield: mature released claim versions with documented acceptance for payer adjudication divided by all mature released claim versions
• status latency: median and 90th-percentile elapsed time between defined stage events
• duplicate rate: unintended duplicate submissions divided by mature released claim versions
• unresolved age: count and oldest age at each missing or rejected stage

Report counts with percentages and segment by payer, product, transaction, route, vendor, and workflow version. Set maturity windows before measurement. A fast route with missing acknowledgments or poor traceability needs correction.

The current HHS Security Rule summary says covered entities and business associates must protect ePHI with reasonable and appropriate administrative, physical, and technical safeguards. After classifying each function and relationship, have a qualified privacy or legal reviewer determine which BAA and other written arrangements are required. Review each applicable agreement's permitted uses, subcontractors, access, transmission security, audit records, incident duties, continuity, data return, and deletion terms. A signature is one control within the practice's privacy and security program.