Clearinghouse Inside the EHR vs a Standalone: What Changes

Put the clearinghouse inside the EHR when your claims are built from chart activity and worked by the same people who chart. Keep a standalone when you already own live payer enrollments or bill across several systems. Ona supports both: Ona Clearing House on Stedi, or your own Claim.MD account connected by API key.

Quick answer:

• Inside the EHR: one queue, one login, no second contract, and the claim assembled from the signed note instead of retyped from a printout.
• Standalone: a separate portal and vendor, with enrollments you own outright and can point at more than one practice or system.
• Cost is not the argument. The decision is where the claim is built and who has to carry it across a gap.

The question underneath the question

Nobody buys a clearinghouse because they want one. It is the translation layer between your practice and the payers: it takes the claim your system produces, converts it into the format each payer expects, transmits it, and carries the response back. The job is identical wherever it is performed, and you cannot submit electronically without it.

So "which clearinghouse is best" is rarely the decision in front of you. The decision is where it sits relative to the record you chart in, and which parts of the work land on a human being as a result. Four things settle that.

1. Who builds the claim

This is the one that shows up in your rejection rate.

When the clearinghouse lives outside the record, something has to carry the visit across the gap: an export, an upload, or a person reading codes off one screen and typing them into another. Every one of those is a place where a digit changes.

When it lives inside, the claim is assembled rather than transcribed. In Ona the chain is gated on purpose. An eligibility check runs first, sending a 270 request and storing the 271 response as a badge on the patient record, which Ona's documentation calls "the cheapest place to catch a problem". The clinician signs the note, because in Ona's own words you "can't bill without a signed note". The completed visit produces a superbill, described as "a frozen, CMS-1500-style snapshot". Only then does a claim exist, already carrying the service lines, linked diagnoses, rendering NPI and place-of-service default.

The scrubbing happens in the same place. Billing rules check units on billable CPT codes, a diagnosis on every line item, the 8-minute rule on timed codes, prior authorization flags, the Medicare monthly unit cap, plan-of-care signatures and timely filing deadlines, with custom rules that warn, fix codes or block submission outright. The principle is stated flatly on that page: "A rejection costs days of turnaround; a rule that catches the same problem before submission costs nothing."

A standalone clearinghouse will also scrub. What it cannot do is reach back into the note and fix the cause, because it never saw the note.

2. How many systems are open at four in the afternoon

Watch a biller work a rejection and count the windows. With the clearinghouse outside, the reason code is in one system and the evidence is in another: read the rejection, switch to the chart, find the visit, check what was documented, switch back, correct, resubmit, then note somewhere that you did.

Inside Ona, it is one screen. Claims carry two readings at once: the payer status (Draft, Submitted, Acknowledged, Accepted, Rejected, Denied, Paid) and a workflow bucket your team controls (Untriaged, Review, Hold, Payments, Pending, Settled, Patient Billing, Closed). What the payer thinks and what your biller is doing stop fighting over one field. Every correction creates a new version, labelled so you can compare v1 against v3 and see exactly what changed, and the History tab holds the timestamped clearinghouse exchange including the payer's control number.

The distinction that saves the most hours is the one the queue makes for you. A rejection means "the claim never really got in the door", so you fix data and send again. A denial means "the payer looked and said no", so the route is appeal or patient billing. Two different jobs, sorted before anyone opens them.

3. What you already own

Payer enrollments are the asset nobody puts on the quote, and they are the strongest argument for keeping a standalone.

An enrollment authorizes your organization to transact with a specific payer through a specific clearinghouse. They are not portable. Move clearinghouse and you re-enroll, payer by payer. Ona's setup guide says most payers require enrollment before they accept claims, that it commonly takes two to six weeks, and that some still want paper forms. Stedi is more optimistic, saying most enrollments complete within 24 to 48 hours while some payers take up to 30 days. Both numbers are real. Plan against the slower one.

If your enrollments are live and your rejection rate is under control, that portfolio has value you should not casually throw away. A practice in that position has a third option, covered below, that keeps the enrollments and still moves the work next to the chart.

4. What happens when you grow

Two systems is an arrangement. Two systems across four locations, three tax IDs and a dozen clinicians is a project.

It is not that a standalone cannot scale. It is that each additional site tends to arrive with its own inherited arrangement, its own login list and its own renewal date, usually set up by somebody who has since left. Consolidation is the moment practices discover how many clearinghouse relationships they actually have.

Ona is a general ambulatory platform rather than a small-practice tool, and its homepage puts the range plainly: "From solo clinics to enterprise systems, cash-pay or insurance-based - Ona scales with you, supporting in-person and remote care alike." Location runs as a thread through visits, calendars, inventory and claims rather than as a separate install per site, and every Ona Clearing House plan carries unlimited providers and unlimited payer enrollments, so hiring a clinician or adding a payer changes what you wait for, not what you sign. The exclusion is inpatient and hospital workflows.

Can you run both at once?

Partly, and the limit is worth knowing before you plan a cutover. Claims can be split. Remittances cannot. Stedi's transaction enrollment FAQ states it directly: "ERAs can only be sent to a single clearinghouse. Once you enroll for ERAs through Stedi, the payer will stop sending ERAs to your previous clearinghouse." One clearinghouse per payer per provider, for the money coming back.

So a parallel run is a reasonable way to de-risk claim submission for a few weeks. It is not a way to hedge on ERAs, and a migration plan that assumes otherwise will surprise somebody in the first payment cycle.

How the configurations compare

Ranked by how far a claim travels from the chart before it reaches a payer. This is not a quality ranking and not a price ranking. Every vendor statement here was checked against that vendor's live pages on September 17, 2026.

Rank	Configuration	How the claim is built	What you sign up for	What it includes	Best fit
1	Ona with Ona Clearing House, on Stedi	Assembled from the signed note through superbill to claim, scrubbed by billing rules, worked in the claims queue	One contract with Ona. No clearinghouse account, credentials or second invoice	Five volume tiers, unlimited providers and payer enrollments on every plan, 10% off annually	Turning insurance billing on, or consolidating sites onto one record
2	Ona with your own Claim.MD account	Same chain, same queue, same claim versions; Claim.MD status events land in the claim history	Two contracts. You keep Claim.MD and connect it by API key, so existing enrollments carry over	Ona seats plus your existing Claim.MD subscription	Already submitting at volume through Claim.MD and unwilling to re-enroll
3	An EHR with a paid claims add-on, such as Healthie with its ClaimMD integration	Built in the EHR, submitted through a third-party integration you subscribe to separately	Two contracts, with the integration switched on inside the EHR	The EHR plan plus a separately subscribed ClaimMD integration with a setup fee	An EHR that already fits, with modest claim volume
4	An EHR with per-claim billing assistance, such as SimplePractice with Insurance Navigator, which SimplePractice lists as coming soon	Built in the EHR, with claim handling charged per claim rather than per month	One vendor, with claim handling bought as an add-on	The EHR plan plus a per-claim usage charge	Low, predictable claim counts
5	Any EHR plus a standalone clearinghouse portal	Exported, uploaded or keyed into a second system, then worked there	Two logins and two invoices, renewed on different dates	Two vendors, two subscriptions, enrollments held by you	Billing operations serving several practices on different records

Row 5 is not a strawman. It is how a large number of US practices bill today, and for a billing company covering clients on five different records it is the correct answer.

The honest case for keeping a standalone

Three situations where the separate account wins, stated without hedging.

Your enrollments are live and working. Re-enrolling costs weeks per payer and buys you nothing that a connected account does not already deliver.

One billing operation, many systems. If your biller covers practices on several EHRs, a single clearinghouse across all of them is fewer moving parts, not more.

The line item is already settled. If your finance team has locked a per-claim cost you are happy with, proximity to the chart is not going to move that number, and this page is not going to argue it should.

What a plan buys instead is one predictable monthly number that already contains your providers and your enrollments, on the same invoice as the rest of the practice software, with the claim built from the note rather than from a person's attention.

What Ona does either way

Ona Clearing House runs on Stedi, Ona's clearinghouse partner, and Ona holds that relationship, so there is no separate account to open, contract to sign, credential to manage or second bill to reconcile. Stedi says it connects to "virtually every U.S. healthcare payer - over 3,500", with complete coverage across Medicare, Medicaid, medical and dental. Plans run $69 for 100 claims, 100 ERAs and 200 eligibility checks per month, through to $1,099 for 2,500 claims, with unlimited providers and payer enrollments on every tier and higher volumes quoted individually.

If you would rather keep what you have, Ona connects your own Claim.MD account with an API key, which its setup guide warns to "Treat this key like a password. Anyone holding it can submit claims as your practice." Waystar and Office Ally are listed as coming soon in Ona's clearinghouse settings, so confirm where they stand before you plan around either.

Cash-pay practices need no clearinghouse plan at all. Billing works without one: invoices from the signed note, payment plans, superbills a patient submits themselves, and card, Apple Pay, Google Pay or HSA and FSA payments.

The labour is not all or nothing either. Ona's insurance page notes that many small practices run billing in-house on Ona, while higher-volume groups keep their RCM partner and let them work inside the same claims queue.

Decide in ten minutes

• Starting insurance billing, or opening a new location. Inside. There is no enrollment portfolio to protect, and every account you do not open is a week you do not lose.
• Already submitting cleanly through Claim.MD. Connect it. Keep the contract and the enrollments, move the work next to the chart.
• Consolidating several sites with several inherited arrangements. Inside, and treat the enrollment timeline as the critical path.
• A billing company covering clients on several EHRs. Standalone. Proximity to one chart is not what you are optimizing for.
• Cash-pay only. Neither. Skip the plan entirely.

For how the built-in version behaves day to day, read what changes when the clearing house is inside the EHR. For the platform as a whole, including where it falls short, there is an honest review of Ona.

Frequently asked questions

Should the clearinghouse be part of my EHR?

Yes, if the people who chart are the people who bill, and if you are starting insurance billing or consolidating locations. In that case the claim is built from the signed note and worked in the same queue, with one login and no second contract. Keep a standalone if you already hold live payer enrollments that work, or if one billing operation serves several practices on different systems.

Can I run two clearinghouses at once?

Only partly. Claims can be split between clearinghouses, but ERAs cannot. Stedi's own documentation states that ERAs can only be sent to a single clearinghouse, and that once you enroll for ERAs through Stedi the payer stops sending them to your previous clearinghouse. So a parallel run is realistic for claim submission during a cutover, and not realistic for remittances, which land in exactly one place per payer per provider.

What does a built-in clearinghouse actually remove from the week?

A second login, a second contract, a second invoice, and the export or retype step between the chart and the claim. The claim is assembled from the signed note, scrubbed by billing rules and worked in the same queue where the note lives, so a rejection is fixed next to the evidence rather than across two systems.

What happens to my payer enrollments if I switch clearinghouses?

They do not travel. Enrollments authorize your organization to transact with a specific payer through a specific clearinghouse, so a move means re-enrolling payer by payer. Ona's setup guide says payers often take two to six weeks and some still require paper forms. Stedi says most enrollments finish within 24 to 48 hours, with some payers taking up to 30 days. Plan for the slower number and start before you need it.

Does an EHR with a built-in clearinghouse work for a multi-location group?

Yes. Ona is a general ambulatory platform that scales from solo clinics to enterprise systems, and location runs as a thread through visits, calendars, inventory and claims rather than as a separate install per site. Every Ona Clearing House plan includes unlimited providers and unlimited payer enrollments, so adding a site or a clinician changes the volume tier, not the contract structure. Inpatient and hospital workflows are the exclusion.

Can my billing company still work my claims if the clearinghouse is inside the EHR?

Yes. Ona's insurance page says higher-volume groups often keep their RCM partner and let them work inside the same claims queue. The partner gets the same statuses, the same workflow buckets, the same claim versions and the same clearinghouse history as your staff, which removes the weekly reconciliation between their system and yours.

Next step

Take the last rejection your team worked and time it twice: once the way you work it now, once with the note, the eligibility result and the payer's reason on one screen. That difference, repeated across a month of claims, is the whole argument. Book a 15-minute demo and bring a real rejection with you, or start the 14-day free trial with full access and no credit card.