Software & Tools
Practice Better + Claim.MD: What the Popular Stack Automates — and What Stays Manual
A factual look at the Practice Better + Claim.MD stack for dietitians — what the integration automates, which billing tasks stay manual, and the real time math.
Disclosure: this article is written by the team behind Alva, which automates the billing pipeline this stack handles partly manually — so we have a horse in this race. We've kept the description factual: this stack is one of the most commonly recommended setups in RD communities, and the recommendation is earned.
If you ask experienced insurance-billing dietitians how they run claims, one answer comes up constantly: Practice Better as the practice hub, Claim.MD as the clearinghouse. It's popular for good reasons — both products are solid, the integration is real, and compared to paper CMS-1500s or payer portals it feels like the future.
This article is about drawing the line precisely: what that stack actually automates, and what still lands on you. Not to knock it — but because "we have an integration" and "billing is handled" are very different sentences, and knowing which tasks remain yours is how you decide whether this setup fits your volume.
What the integration genuinely handles
Credit first, because it's substantial:
- Claim creation from appointments. Session data in Practice Better — client, date, service, your entered codes — populates an electronic claim without retyping demographics into a clearinghouse portal.
- Electronic submission. Claims flow to Claim.MD, get validated against basic format and payer-connection rules, and route to the payer as an 837P. Claim.MD is a well-regarded clearinghouse with wide payer connectivity.
- Status sync. Acceptances, rejections, and payer statuses come back where you can see them, instead of living only in a portal you forget to check.
- ERA delivery. Electronic remittances arrive through the clearinghouse rather than as paper EOBs.
If you're currently billing by hand, this stack removes the worst mechanical drudgery. That's real value.
What stays manual
Here's the part the community threads compress into a shrug. Task by task:
| Task | Automated by the stack? | Who does it |
|---|---|---|
| Benefits & eligibility verification | No | You — call or portal, per new client |
| Re-verification (new year, plan changes) | No | You — on a cadence you maintain |
| CPT code selection (97802/97803) | No | You — from your own documentation |
| Unit counting from session time | No | You — 8-minute-rule math per session |
| ICD-10 pairing & preventive routing | No | You — per payer policy |
| Claim creation from appointment | Yes | The integration |
| Format validation & submission (837P) | Yes | Claim.MD |
| Status retrieval | Yes | The integration reports; you review |
| Rejection/denial interpretation | No | You — CARC codes, payer calls, resubmission |
| ERA review & payment posting | Partially | ERAs arrive; posting/review is you |
| Patient-responsibility reconciliation | No | You — match ERA to invoice, collect balance |
Read the left column again: everything before the claim exists and everything after the payer answers is yours. The stack automates the middle — transmission — which is the part that was already the most mechanical.
Concretely, that means you still:
- Make the verification calls. Nutrition benefits, visit limits, telehealth rules, preventive coverage — commonly 15–30 minutes per new client (our verification call script helps, but it's still your phone time). And you re-verify each January and after plan changes, on a calendar only you maintain.
- Do the coding. You choose 97802 vs. 97803, count 15-minute units from actual session time, and pick diagnosis pairings that match the payer's policy. The integration faithfully submits whatever you enter — including mistakes, which return as denials weeks later.
- Interpret what comes back. A rejection code is a clue, not an answer. Figuring out why — and whether to correct, appeal, or call — is unassisted detective work.
- Reconcile the money. Matching ERA lines to sessions, confirming allowed amounts, chasing copays and deductible balances.
The time math on the manual remainder
Hedged, typical figures — your mileage varies:
- Verification: 4 new clients/month × ~20 min, plus re-verifications ≈ 1.5–2.5 hrs/month
- Coding & claim review: 60–80 sessions/month × 3–5 min ≈ 3–6 hrs/month
- Denial/rejection work: a handful monthly × 20–40 min ≈ 1–3 hrs/month
- ERA review, posting checks, patient-balance reconciliation ≈ 2–4 hrs/month
Call it 8–15 hours a month of skilled, unbillable work that survives the integration. At even a modest hourly value, that's a real number — we run the full stack economics in the true cost of a DIY billing stack.
When this stack is enough
Genuinely, often. It fits best when:
- Your insurance volume is moderate and your payer mix is stable, so verification and coding are routine rather than research.
- You like the control of touching every claim, or you already know MNT billing cold.
- Practice Better's wellness tooling is central to your model, so the hub choice is already made.
If that's you, this stack is a sensible, proven setup. Don't let anyone — including us — talk you out of something that's working.
When you want the pipeline automated end-to-end
The manual remainder scales with volume and with newness: more sessions mean more unit math, more new clients mean more verification calls, more payers mean more policy nuance. Practices feel the ceiling when the 8–15 hours become 20+, or when one missed rejection quietly ages past a filing deadline.
That's the gap end-to-end automation targets: eligibility checked automatically before the visit, notes charted by AI from the session, codes and units generated from real documentation and duration, claims validated pre-submission, statuses watched with alerts, ERAs posted. Not a better clearinghouse — the layer above and below it.
How Alva helps: Everything in the "who does it: you" column — verification, coding, unit math, denial triage, ERA posting — is what Alva automates on top of claim submission itself, for a flat $99/month. If your stack transmits claims but you still build and babysit them, compare the weeks: Start a 7-day free trial.
Frequently asked questions
Does Practice Better integrate with Claim.MD?
Yes. Practice Better connects to Claim.MD as its clearinghouse on plans that include insurance features, letting you create claims from appointments, submit them electronically, and receive status updates back inside Practice Better. It is a commonly recommended setup in dietitian communities and it genuinely works.
What does the Practice Better and Claim.MD integration not do?
It does not verify benefits, choose your CPT codes, count your 15-minute units, interpret denials, or reconcile patient responsibility. The integration moves the claim you build from your EHR to the payer and reports status; building the claim correctly and acting on what comes back remains your work.
How much time does insurance billing take with Practice Better and Claim.MD?
The submission itself becomes fast — minutes per claim. The manual remainder is the bulk: benefits verification commonly runs 15 to 30 minutes per new client, coding and reviewing each claim a few minutes per session, plus denial investigation and payment reconciliation. For a practice with 15 to 20 insurance sessions a week, several hours a week typically remain manual.
Is Practice Better plus Claim.MD enough for an insurance-based dietitian?
For many practices, yes — especially at moderate insurance volume with a stable payer mix, where verification and coding are routine. Practices with high volume, frequent new clients, or complex payer mixes tend to feel the manual layer most, and those are the ones that look at end-to-end billing automation.