Software & Tools
SimplePractice for Dietitians: What Works, What Doesn't
An honest SimplePractice review for dietitians — where its polish and mature claims pipeline shine, where nutrition-specific gaps like MNT coding show up, and who it fits.
Disclosure: this review is written by the team behind Alva, a billing-automation platform for dietitians — so we compete with SimplePractice for some practices. We have kept this review factual and fair; SimplePractice is genuinely good software, and for a meaningful share of RDs it is the right choice.
Ask in any RD community which software to use and SimplePractice comes up within three replies — usually from someone who's happy with it. It's one of the most widely adopted private-practice platforms in the country, and that adoption isn't an accident: the product is polished in a way most healthcare software simply isn't.
The question for you isn't whether SimplePractice is good. It's whether software built for private practice in general fits a practice built on medical nutrition therapy in particular. That's where this review lives.
What genuinely works
The UX polish is real. Scheduling, the client portal, telehealth, payments, reminders — everything feels finished. Clients rarely get confused, and you rarely hunt for a setting. That day-to-day smoothness is worth more than it sounds.
The claims pipeline is mature. This matters most for insurance-based RDs. Electronic claim creation, submission through an integrated clearinghouse, status tracking, ERA handling — refined across an enormous user base and years of edge cases. Claims that leave SimplePractice are formatted correctly and get where they're going. If you've been hand-filing CMS-1500s, this alone is a life upgrade.
Huge adoption means the paths are paved. Tutorials, community answers, and support articles exist for nearly everything. Your biller has probably used it. Your therapist office-mate definitely has.
The template library is large and customizable. You can build ADIME notes, nutrition intake forms, and consent flows. The raw material is there.
Where dietitians feel friction
None of what follows is a defect. It's the predictable result of software designed around general private practice — historically, heavily, behavioral health.
The concepts lean therapy. "Treatment plans," diagnosis-centric workflows, and progress-note framings map naturally onto counseling and less naturally onto MNT. You can adapt them — RDs do, every day — but you're translating, and the translation is setup work the software won't do for you. If you chart in ADIME rather than SOAP, you'll be building that structure yourself.
MNT billing nuances are on you. SimplePractice will submit whatever claim you build — correctly and reliably. But building it correctly is your job:
- Code and unit selection. You pick 97802 vs. 97803 and count 15-minute units yourself, including the 8-minute-rule math. A 58-minute follow-up is 4 units of 97803; nothing stops you from typing 1.
- Preventive vs. medical routing. Many commercial plans pay nutrition counseling under the preventive benefit with specific diagnosis pairings (and some payers reject Z71.3 as primary — check the payer's policy). Whether a claim routes preventive or medical is determined by the codes you enter; the software has no nutrition-specific guardrails to warn you.
- MNT-specific payer rules. Medicare MNT's referral requirement and hour caps, visit-limit tracking against verified benefits, unit ceilings per payer — all tracked in your head or your spreadsheet.
Eligibility is still your morning phone call. SimplePractice offers eligibility features, but confirming nutrition-specific benefits — visit limits, preventive coverage, telehealth rules — typically still means a call or portal dig before each new client.
Documentation is typed, not generated. No AI charting from sessions. Your 20 minutes of post-session notes stay yours (or a separate scribe subscription's).
Honest scorecard
| Area | Verdict for RDs |
|---|---|
| Scheduling, portal, telehealth, payments | Excellent — best-in-class polish |
| Claim submission & tracking | Mature and reliable — you build, it delivers |
| Nutrition-specific documentation | DIY — adaptable templates, therapy-leaning defaults |
| MNT coding & unit math | Entirely manual — errors surface as denials |
| Eligibility verification | Largely manual for nutrition benefits |
| Ecosystem & support | Massive — answers exist for everything |
Who it fits well
- Multi-disciplinary practices. If you share a practice with therapists, psychologists, or other license types, one polished platform everyone knows beats two specialized ones nobody shares.
- Therapy-adjacent RDs. Eating-disorder-focused practices working closely with behavioral health teams often find the therapy-shaped concepts a feature, not a bug.
- RDs who want reliability over specialization. If you know your MNT billing cold and just want claims delivered flawlessly, SimplePractice delivers.
Who outgrows it
The pattern we see: an RD's insurance caseload grows, and the manual layer — verification calls, code and unit entry, denial detective work on rejected nutrition claims, ERA review — grows linearly with it. SimplePractice executes your instructions perfectly; it never starts doing the instructing. At 15–25+ insurance sessions a week, that gap is measured in evenings.
Complement or replace?
Two rational paths:
- Complement: keep SimplePractice as your practice hub and accept the manual MNT layer as the cost of its polish — reasonable for lighter insurance volume or multi-disciplinary settings.
- Replace (or don't adopt): if you're nutrition-only and insurance-heavy, weigh platforms where the MNT layer is the product — nutrition-native records, or full billing automation. Our platform-by-practice-type guide maps the options.
Either way, decide based on the manual hours, not the demo. SimplePractice will never embarrass you. The question is how much of your week it leaves on your desk.
How Alva helps: Everything SimplePractice leaves manual for RDs — eligibility checks, charting, MNT code and unit generation, claim validation, ERA posting — is exactly what Alva automates, for a flat $99/month. If the manual layer is your bottleneck, see the difference on your own caseload: Start a 7-day free trial.
Frequently asked questions
Is SimplePractice good for dietitians?
Yes, with caveats. It is polished, reliable general private-practice software with a mature insurance claims pipeline. But it was not built specifically for nutrition, so MNT-specific work — code and unit selection, preventive versus medical benefit routing, nutrition documentation structure — remains on you. Many RDs run happily on it; some outgrow the generic fit.
Can SimplePractice submit insurance claims for nutrition services?
Yes. SimplePractice supports electronic claim creation, submission through its integrated clearinghouse, status tracking, and ERA handling. What it does not do is choose your MNT codes or count your 15-minute units — you enter 97802 or 97803, the units, and the diagnosis pairing yourself, and errors there come back as denials.
Does SimplePractice have nutrition-specific templates?
It has a large template library and customizable forms, and you can build ADIME or nutrition-focused SOAP templates yourself. Out of the box, though, its documentation concepts lean toward therapy — treatment plans, diagnoses, progress notes framed for behavioral health — so RDs typically invest setup time adapting templates to MNT workflows.
Who should choose SimplePractice over a dietitian-specific platform?
RDs in multi-disciplinary or therapy-adjacent settings, practices that share admin or billing staff with other license types, and anyone who values mature, battle-tested claims infrastructure over nutrition-native features. If your practice is nutrition-only and insurance-heavy, a nutrition-specific or automation-first platform may fit better.