How to Choose the Best EHR for Your Small ABA Practice

Published Oct 7, 2026 · Updated Nov 3, 2026

By Arthur Anderson, Co-Founder · With AI research assistance

Choose an ABA EHR by testing it against your own work, not the vendor's script. Map your workflows and payers, shortlist systems built for ABA and run scripted demos with your own scenarios. Then check security and the BAA, price the full term and get export and exit terms in writing before you sign.

The eight steps below take a small practice from a blank page to a signed contract. Most steps end with questions you can ask on a demo call. Bring the same questions to every vendor so the answers are comparable.

What should you do before the first demo?

Before the first demo, write down how your practice works today. A vendor's demo shows its smoothest path. You need your own list to check that path against.

Step 1: Map your workflows

List everything that happens between a referral and a paid claim. Include intake, assessment, treatment planning, scheduling, sessions, supervision, authorizations and billing. Mark the steps that cause the most re-entry or the most missed deadlines today. Our post on the ABA workflows an EHR must fit breaks the clinical side into a checklist.

Step 2: List your payers and programs

Write down each payer, its authorization rules and how it pays you. Note whether any clients are funded through Medicaid programs. Medicaid.gov explains that the 21st Century Cures Act requires states to implement Electronic Visit Verification for Medicaid personal care and home health services. Your state's rules decide whether any of your services fall under it.

Step 3: Set a growth plan and a budget range

Estimate your headcount, caseload and locations for the next few years. Pricing models react very differently to growth. Our post on why single-tenant delivers long-term value compares per-seat, percentage and flat-rate pricing over several years.

Which questions should you ask on an EHR demo?

Ask the vendor to perform your scenarios live in a working system instead of narrating slides. Give every vendor the same script ahead of the call.

Step 4: Run a scripted demo

Use questions like these:

Data collection: can an RBT record trial-by-trial, frequency, duration and interval data on a phone, and does the BCBA see it graphed?
Plans: do FBA findings carry into the BIP and treatment plan goals, and do progress reports pull from session data?
Supervision: where does the system track supervision hours, and how does a BCBA co-sign a note?
Authorizations: can you watch units draw down by CPT code, and what happens as the limit or end date nears?
Scheduling: does the calendar handle several providers and locations and catch conflicts?
Families: does a guardian portal cover check-in, secure messaging and consent signing?
AI: which AI features exist, are they optional, and who turns them on?

Supervision deserves a close look. The BACB RBT Handbook requires supervision for at least 5% of an RBT's service hours each calendar month. It also requires at least two face-to-face, real-time contacts each month. A system that tracks those hours saves a monthly scramble before the deadline.

Ask the vendor to trace one session to a paid claim

The billing trace is the most revealing request on any demo. In Lumenality, the session note and its data become the claim line, with CPT code, units and authorization taken from the same record. Rule-based checks run before the claim goes out through the built-in Stedi integration. Each 837P claim is tracked through 999 and 277CA acknowledgments, and 835 remittances post payments automatically.

Ask every vendor to show the same path live. Any step that needs an export, a re-entry or a separate portal is work your team will repeat every week.

On AI, look for control rather than promises. In Lumenality, every AI feature is optional, off by default and switched on only by the practice's admin. Today the optional features read incoming intake documents and explain suggested schedule pairings, while claim scrubbing is rule-based. Our post on optimizing ABA billing in Lumenality explains where AI fits and where it does not.

How should you check security and compliance?

Check security by asking for each control in writing and mapping it to the HIPAA Security Rule. The technical safeguards in 45 CFR 164.312 cover access control, audit controls, integrity, authentication and transmission security. Automatic logoff and encryption appear there as addressable specifications.

Step 5: Review security and the BAA

Ask these questions on the call or in a security questionnaire:

Is data encrypted at rest and in transit, and to what standard?
Does each user get a role with only the access the job needs?
Can you show the audit trail of who opened a client record?
Is multi-factor authentication available for every user?
Will the vendor sign a BAA before any client data is loaded?

Lumenality gives every practice a dedicated single-tenant deployment with its own database and its own encryption keys. Data is protected with AES-256 at rest and TLS 1.2+ in transit. Role-based access control, MFA and an audit trail of record access come standard, and we sign a BAA with every customer. Hosting runs on SOC 2-compliant providers, and our post on HIPAA-aligned controls for ABA practices goes deeper.

How do you compare EHR pricing fairly?

Compare total cost over several years, not the first invoice. Ask each vendor for the subscription, clearinghouse fees, setup and training fees, add-ons and the rule that makes the price rise.

Step 6: Price the full term

Per-seat pricing grows with every hire, and percentage-of-collections pricing grows with revenue. Lumenality charges one flat monthly rate per practice by provider count, with plans starting at $599 a month (Solo). Every tier's rate is on our pricing page, and clearinghouse and AI usage are billed at agreed-to rates. There are no per-seat charges, no setup fees and no percentage of collections. Long-term contract pricing is available.

What should the contract say about leaving?

The contract should promise full exports of your data, in a documented format, with clear notice terms and fees. Leaving is easier to negotiate before you sign than after.

Step 7: Get exports and exit terms in writing

Ask for full exports of clinical, billing and operational data on request, the file format, the notice period and any exit fees. Lumenality provides full CSV exports at any time. When a practice leaves, it gets the same exports with 30 days' notice and no exit fees. Our post on avoiding vendor lock-in lists the clauses to look for.

Step 8: Plan the go-live

Ask for a realistic timeline and what it depends on. Most practices go live on Lumenality in about 2 to 6 weeks. The path covers the agreement and BAA, a data-migration assessment, 3 to 5 days of staff training and a one-day go-live. Import scope is confirmed after reviewing sample exports, and some data may need re-keying.

Why put a single-tenant EHR on the shortlist?

A single-tenant EHR gives your practice its own deployment and database instead of a share of a common one. Your data is isolated from other customers, which makes your safeguards easier to describe in a risk assessment. You are not competing with other organizations for resources, and your records have clear boundaries if you ever leave. Our single-tenant vs. multi-tenant comparison covers the trade-offs.

Lumenality is built this way, so clinical, scheduling and billing work come together in one place. See how the pieces fit on our ABA EHR overview, or request a demo and bring your script.

*This article was created with AI assistance and reviewed by the Lumenality team.*