DEV Community

Cover image for Adding Billing to Your EHR: Build, Buy or Both?
Nirmitee.io
Nirmitee.io

Posted on Originally published at nirmitee.io

Adding Billing to Your EHR: Build, Buy or Both?

Four ways to add claims to an EHR, what each costs and controls, and the five questions that settle the choice.

Originally published on Nirmitee.io: Build vs Buy: Adding Medical Billing to Your EHR

Every EHR eventually gets asked for billing. It is the stickiest, highest-margin module an EHR can ship, and its absence pushes customers toward all-in-one competitors.

So the question for most EHR product leaders is not whether to add claims capability, but how. There are four ways to do it, and the right one depends on five questions, not on any vendor's pitch.

The four options at a glance

  • Traditional clearinghouse (for example Waystar, Availity, Optum). Batch file transfer plus newer APIs, with sales-led contracts. Pricing is quote-based, with agreements per EHR. You build everything above the connection.
  • API-first clearinghouse (for example Stedi, Claim.MD). Modern web APIs and self-serve signup, with published pricing of roughly $0.10 to $0.30 per claim and no minimums. You still build everything above the connection.
  • Embedded RCM as a service (for example Candid Health, Apero). Billing operations behind an API, priced by subscription or a percentage of collections. Your control is limited: their workflow, and their data.
  • Build with a partner. A specialist engineering firm builds your billing layer on option 1 or 2. You pay for the project plus your per-claim costs, and you own the code and the data.

What each option really means

Traditional clearinghouses offer maximum payer reach and enterprise credibility. The source notes Waystar alone touches thousands of payer connections. The realities: contracts are per EHR and sales-led, connectivity is often batch file transfer, payer enrollment takes weeks per payer, and handling the acknowledgements that tell you whether a claim was accepted is entirely your problem.

API-first clearinghouses modernize the transport layer with real documentation and published prices. Stedi lists claims at $0.10 to $0.30 and eligibility checks at $0.08 to $0.30 per transaction, with no monthly minimum. What they deliberately do not solve: claim scrubbing rules, denial work queues and payment posting logic. That product layer is still yours to build.

Embedded RCM platforms are the fastest route to revenue, because billing operations arrive as a service. The trade-offs grow with scale. Percentage-of-collections pricing grows as your customers' collections grow. The denial workflow follows their roadmap, not yours. And the remittance and denial data that could train your own rules and AI features builds up in their warehouse.

Building takes realistic time. Per the source, a basic billing module runs 3 to 5 months with 3 to 4 engineers, and a fuller platform 8 to 12 months, plus calendar time for clearinghouse credentialing and payer enrollment. The part most "build" articles leave out: you still need a clearinghouse underneath, because nobody connects to thousands of payers directly.

There is also a resilience reason. The source cites HFMA: the 2024 Change Healthcare outage took down roughly 40% of US claims flow through a single clearinghouse. Owning your claims layer above a clearinghouse you can swap is now a resilience argument, not just a control argument.

Five questions that settle it

Build vs buy decision framework for EHR billing: five questions on volume, complexity, denials control, data and margin

Five questions that settle build vs buy. Source: Nirmitee.io

  1. Volume. At $0.10 to $0.30 a claim, transaction fees are small. The real choice is paying a percentage of collections versus owning the workflow.
  2. Specialty complexity. For single-specialty professional claims, API rails nearly suffice. For institutional or multi-specialty billing, the depth of claim scrubbing dominates.
  3. Denials control. If denial management is part of your product's value, and for an EHR it is, renting it caps your roadmap.
  4. Data ownership. Remittance and denial data is what trains your future rules and AI features.
  5. Margin. At scale, owned billing is the highest-margin module an EHR sells.

The original article lays out each option's cost model and how much control you keep, side by side.

The hybrid most teams land on

Hybrid EHR billing architecture: own the claims data model and denial UX, rent clearinghouse pipes

The hybrid: own the workflow, rent the pipes. Source: Nirmitee.io

Own the claims data model and the denials experience; rent the pipes. That means an API-first clearinghouse underneath with your product on top, built either by your own team over 6 to 12 months or with a partner who has built acknowledgement handling and payment posting before.

It is faster than a solo build. And unlike renting RCM, everything you learn stays with you.

If you are at this decision, the source suggests one practical step: spend an hour mapping your answers to the five questions onto the four options. The full article links to guides on payer enrollment timelines and common claims integration traps.


Nirmitee.io builds claims engines, payment posting and denial workflows inside EHRs, on whichever clearinghouse fits. For the full comparison with published pricing, read the original: Build vs Buy: Adding Medical Billing to Your EHR on Nirmitee.io.

Dinesh Thorat is Healthtech Growth Partner at Nirmitee.io.

Originally published at nirmitee.io.

Top comments (0)