Built by operators who ran ABA clinics.

An EHR built for ABA. Not adapted to it.

Trial-by-trial data, treatment plans, payer-aware notes, and authorization tracking as first-class records — with billing, scheduling, and a built-in phone on the same chart.

not a generic EHR adapted

ABA-native

AES-256, full audit trail

HIPAA-grade

clinical, billing & ops

One record

with human sign-off

Agentic AI

What is ABA EHR software?

The system of record for an ABA practice — built for behavior analysis.

ABA EHR software (electronic health record — used interchangeably with EMR in ABA) is the clinical system of record: client charts, treatment and behavior intervention plans, real-time data, session notes, documents, authorizations, and communication, plus the workflows around them.

The difference that matters is fit. A generic behavioral-health EHR is built for talk therapy and treats ABA’s essentials — trial-by-trial data, supervision ratios, EVV, authorization units, ABA billing codes — as workarounds. Wilma® is the ABA-native record: those things are first-class, and the same record runs billing, scheduling, and telephony so nothing is stitched together.

One ABA-native chart — intake to graduation.

Client demographics, insurance, authorizations, treatment plans, behavior intervention plans, real-time data, session notes, documents, and communication history — all on one record. The EHR an ABA practice actually needs, not a medical EHR with ABA bolted on.

Unified client chart

Demographics, coverage, auth, clinical history in one view.

Treatment & behavior plans

BIPs and goal banks linked to the data that drives them.

Document management

Consents, assessments, reports stored against the client.

Full activity history

Every note, call, and change timestamped and attributed.

An EHR whose notes survive an audit.

In ABA, the EHR isn’t just a record — it’s what determines whether you get paid. Wilma checks documentation completeness against payer-specific requirements before claims ship, so notes match what your funder requires and clawbacks don’t arrive 90 days later.

Payer-aware notes

Required elements and medical-necessity language by payer.

Gap detection pre-claim

Missing signatures or data flagged before submission.

Audit-ready trail

Defensible edit history on every clinical record.

Data-grounded drafts

Notes drafted from collected session data (AI add-on).

Whether you call it an EHR or an EMR, it’s built for behavior analysis.

Generic behavioral-health EHRs assume talk-therapy workflows: a note per visit, no trial-by-trial data, no RBT/BCBA supervision model, no authorization-unit tracking. Wilma is the ABA-native electronic health record — discrete-trial data, supervision ratios, EVV, and ABA billing codes are first-class, not workarounds.

ABA data model

Trial-by-trial, ABC, task analysis — native, not free-text.

Supervision built in

BCBA/RBT model and BACB ratios understood by the system.

Authorization-aware

Units, cycles, and service codes tracked on the record.

ABA billing codes

CPT® 97151–97158 and HCPCS, not generic E/M coding.

An EHR that prepares the work, not just stores it.

Legacy EHRs record what humans did. Wilma drafts session notes from data, scrubs claims, assembles authorization-renewal packets, and drafts parent updates — within your rules, pending BCBA sign-off. The record works for you between sessions.

Drafts, you approve

Every AI output reviewed and signed by a clinician.

Renewal prep

Progress data and history assembled before the cycle closes.

Parent updates

Clinical language translated to parent-friendly drafts.

Documentation QA

Gaps surfaced before they become denials.

The EHR is the platform — billing, scheduling, and phone included.

Because the record is shared, a signed note feeds the claim, the schedule respects the authorization, and an intake call threads into the chart. No interface engine, no nightly sync, no reconciling a clinical EHR against a separate billing system.

EHR + RCM

Insurance capture, claims, ERA, denials native to the record.

EHR + scheduling

Authorization-aware scheduling with built-in EVV.

EHR + telephony

Native phone/IVR; calls logged to the client chart.

No integration tax

One database, one login, one source of truth.

Buyer's Checklist

Evaluating an ABA EHR? Demand every line.

FAQ

Questions operators ask about ABA EHRs.

What is ABA EHR software?

Is there a difference between an ABA EHR and an ABA EMR?

How is an ABA EHR different from a generic behavioral-health EHR?

Is Wilma HIPAA compliant?

Can I migrate from my current EHR?

Does the EHR include billing and scheduling, or are those separate?

How does AI fit into the EHR?

How much does Wilma cost?

Customer Story · Switching & Migration

Switching ABA software in a week — without losing data or downtime

How a practice moved off its old system mid-operation and came out ahead.

See an EHR that was actually built for ABA.

Thirty minutes. Bring your charts, your payers, and your current EHR’s worst workaround. We’ll show you the record done right.

CPT® is a registered trademark of the American Medical Association.

Choosing an EHR

How to evaluate an ABA EHR

Behavioral health EHRs and ABA EHRs are not the same product. The difference shows up in the record model — whether the system understands programs, targets, authorizations and supervision, or treats an ABA session as a therapy appointment with notes attached.

• 1Does the record model understand ABA, or general behavioral health?A general behavioral health EHR models an encounter and a note. ABA needs programs, targets, trial-level data, prompt levels, task analyzes, authorizations that decrement, and supervision relationships. Retrofitting those onto an encounter model produces a system where the clinical work lives in attachments — searchable by nobody, reportable on never.Red flag: Program data stored as uploaded documents or free text rather than structured, graphable fields.
• 2Is the audit trail complete enough to defend?An EHR holds protected health information, so every access and change should be logged with who, what and when — including reads, not just writes. This is the thing you never think about until an audit or a breach investigation, at which point it is the only thing that matters.Red flag: Audit logging on edits only, or logs that cannot be exported for a date range and a specific record.
• 3How does information get in and out?You will need to exchange with school districts, diagnosticians, primary care, and eventually another system. Ask concretely what import and export look like, in what formats, and whether the structured clinical data travels or only the documents.Red flag: Interoperability described entirely as PDF export.
• 4Does role-based access match how a practice actually works?An RBT should see their clients, a BCBA their caseload, a biller financial data without clinical detail they do not need, and a multi-site director their region. Access that is effectively all-or-nothing forces practices into workarounds like shared logins, which is both a compliance failure and an audit-trail failure.Red flag: Roles that cannot be scoped by location or caseload, only by job title.
• 5Is a BAA standard, and what is actually in it?A Business Associate Agreement is required, not a bonus. Read what it says about breach notification timelines, subcontractors, data location and what happens to your data on termination. A vendor that treats the BAA as a formality is telling you something.Red flag: A BAA offered only on request, or one that is silent on subcontractor obligations.

Before you sign

Questions worth asking on the demo

• Show me the audit log for a single client record, including who viewed it.
• How is program and trial-level data stored — can I report across it, or is it attachments?
• What can a biller see, and can I scope access by location as well as by role?
• What does an export contain, and does structured clinical data come with it or only documents?
• Is a BAA standard with every agreement, and what is the breach notification timeline in it?
• Where is data hosted, and are any subcontractors involved in processing it?

Glossary

The terms you will hear

EHR vs EMR

An electronic medical record is a practice's own chart; an electronic health record is designed to travel between providers. In ABA the terms are used loosely and largely interchangeably by vendors.

Business Associate Agreement

The contract required under HIPAA between a covered entity and a vendor handling protected health information, setting out safeguards, breach notification and subcontractor obligations.

Role-based access control

Restricting what each user can see and do by role and scope, so access matches job need. Practically it must be scopeable by caseload or location, not only by job title.

Audit trail

An immutable log of who accessed or changed a record and when, including reads. The primary evidence in an audit or breach investigation.

Protected health information

Individually identifiable health information held or transmitted by a covered entity or business associate, in any form. What HIPAA's safeguards apply to.

Interoperability

The ability to exchange information with other systems in a form the receiving system can use. Document export is the weakest version; structured data exchange is the useful one.

Keep reading

Related guides on running an ABA practice — the same operation, from a different angle.

• ABA EMR softwareWhat "EMR" means in an ABA setting, and which parts you genuinely need.
• HIPAA-compliant ABA softwareBAAs, audit logs, access control and the compliance questions to ask any vendor.
• ABA software for BCBAsCaseload, programs, data review and supervision from the BCBA’s side of the desk.
• ABA parent portalProgress, scheduling and secure messaging that keeps caregivers in the loop.
• ABA revenue cycle managementAuthorization through ERA posting, tracked as one cycle instead of four disconnected steps.
• ABA practice management softwareOne platform for the whole ABA practice, from first call to paid claim.