A clearinghouse receives claims from dental practices, checks and translates them into the format each payer expects, routes them to the payer, and returns acknowledgments and remittances.
Why they exist
In principle, HIPAA standardized healthcare transactions: everyone uses the X12 837D for dental claims, 835 for remittances, 270/271 for eligibility. In practice, “we support the standard” still yields payer-by-payer variation.
Each payer publishes or applies its own companion-guide requirements for situational fields, identifiers, edits, and delivery. Submitter enrollment and connection methods also vary. A dental office may bill a Delta Dental member company, several national carriers, and one or more Medicaid administrators, each with its own routing and enrollment records.
A practice contracting with fifteen dental payers would otherwise need fifteen connections, fifteen enrollment processes, fifteen sets of format rules, and fifteen monitoring endpoints. A clearinghouse collapses that into one.
What a clearinghouse actually does
Enrollment support is the most underrated criterion. The claim-transmission function is close to commoditized. The part that costs a new group months is getting EDI, ERA, and EFT enrolled across every payer, and clearinghouses differ enormously in how well they handle it. Weight it heavily when choosing.
The dental trio: 837D, attachments, eligibility
Dental clearinghouses differ less in basic claim transport than in the workflow around it. Three capabilities are especially relevant:
- The 837D: the dental claim with CDT codes and tooth-level detail. Clearinghouses vary in edits, payer connectivity, reporting, and dental-field support.
- Attachments: dental payers may require radiographs, periodontal charts, and narratives. Proprietary repositories became common before adoption of a HIPAA attachment standard. A workflow may upload documentation, return a reference number such as an NEA number, and place that reference on the claim.1 The 2026 federal rule adopts the X12 275 attachment standard with compliance due in May 2028. Ask vendors about implementation plans before signing a long-term contract.2
- 270/271 eligibility: electronic eligibility is useful before treatment, although the response may not contain the full benefit detail needed for a patient estimate.
Some dental-focused clearinghouses, including DentalXChange and Vyne Dental, offer claims, attachments, and eligibility in one product family. Other networks may support the 837D while using a separate attachment workflow.3 Evaluate the exact payer connections, attachment method, enrollment support, and reporting in the proposed configuration. See CDT & the 837D.
Payer IDs
Each clearinghouse maintains payer identifiers for routing. Payer IDs may be clearinghouse-specific, and different Delta Dental member companies can use different routes. Validate the payer, transaction type, product, and receiver ID in the selected clearinghouse.
This is why switching clearinghouses requires remapping every payer in your PMS, and why a claim can reject as “payer not found” when the ID was fine at your previous vendor. Every clearinghouse publishes a payer list; treat it as the canonical source. See Payer enrollment and submission links.
Batch-era vs API-era
Two generations coexist:
Batch/legacy. Built on SFTP file drops and scheduled processing. You upload a batch of claims, wait, and download responses. Portal-first, with an API bolted on later if at all. This describes most incumbent clearinghouses, dental-native ones included.
API-first. Built around real-time REST/JSON endpoints, with X12 available for compatibility. Eligibility returns synchronously; claims and remittances are retrievable programmatically; everything the portal does is available to code. Newer entrants such as Stedi are examples of this generation.4
The access model matters when a group wants automated eligibility, adjustment analytics, or per-entity dashboards. Compare API coverage, batch files, webhooks, export rights, data latency, and the transactions actually available for each payer.
See Choose a clearinghouse and The clearinghouses, compared for the criteria that matter and how the vendors stack up.
Do you get to choose?
Often not. Many practice management systems embed a clearinghouse and make it difficult or impossible to use another.
Ask before you sign the PMS contract, not after. Confirming that a PMS permits your choice of clearinghouse, and getting that in writing, is far easier than changing clearinghouses later, which means remapping every payer, re-enrolling EDI and ERA across your whole payer list, and running parallel for a period.
The 2024 Change Healthcare outage
The Change Healthcare incident is a recent example of concentration risk in claims infrastructure.
On February 21, 2024, Change Healthcare, a UnitedHealth Group subsidiary and one of the largest clearinghouses in the country, discovered it had been compromised by ransomware. Attackers had accessed its systems from February 17, reportedly through a Citrix remote access service that lacked multi-factor authentication. Change Healthcare took systems offline.5
The 2024 Change Healthcare incident demonstrated the concentration risk in claims infrastructure. An American Hospital Association survey in March 2024 found that 74% of nearly 1,000 responding hospitals reported a direct patient-care impact.6 Dental practices using the network also experienced disruption to claims, attachments, eligibility, or payments, and the ADA publicized emergency funding resources.7
Practices could not submit claims, could not receive remittances, and in many cases could not verify eligibility. Cash flow stopped for weeks. UnitedHealth Group ultimately confirmed a $$22 million ransom payment, and the data of an estimated 100 million individuals was affected.8
Operational lessons:
- A single vendor outage can disrupt a large share of healthcare revenue.
- Many practices lacked a contingency. They had no secondary clearinghouse, paper fallback, or cash reserve sized for a multi-week revenue interruption.
- Vertical integration can increase concentration. A large payer’s corporate parent also owned infrastructure that carried many claims.
- Basic security hygiene mattered. A remote access service without MFA.
What to do about it:
- Hold cash reserves sized for a material interruption in collections. The appropriate period depends on claim volume, payer mix, payroll, debt service, and available backup routes.
- Know your fallback before you need it: which payers accept direct submission or portal entry, and whether a secondary clearinghouse could be stood up.
- Ask vendors about incident history and security posture during selection, and read their SOC 2 report.
- Keep your data portable. If your claim and remittance data is only inside a vendor’s portal, you cannot move.
Sources
- Vyne Dental, FastAttach; GEHA, NEA FastAttach payer instructions.
- Administrative Simplification: Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures, 91 Fed. Reg. 14350 (Mar. 24, 2026), compliance May 26, 2028. Federal Register.
- DentalXChange, ClaimConnect services and integrated attachments; Vyne Dental, payer connectivity; BCBSM, companion guide noting 837D via Availity (PDF).
- Stedi, Healthcare clearinghouse APIs.
- HIPAA Journal, Change Healthcare Responding to Cyberattack; Congressional Research Service, The Change Healthcare Cyberattack.
- American Hospital Association, Change Healthcare Cyberattack Underscores Urgent Need to Strengthen Cyber Preparedness.
- ADA News, Funding assistance available to dentists impacted by Change Healthcare cyberattack.
- IBM, Change Healthcare discloses USD 22M ransomware payment.