Successful EHR Implementation for ABA Practices Made Easy
Picture go-live Monday at an Applied Behavior Analysis (ABA) clinic that rushed its new electronic health record (EHR) system. By Wednesday, two Registered Behavior Technicians (RBTs) are back on paper data sheets, and a Board Certified Behavior Analyst (BCBA) is re-entering targets that never migrated. Meanwhile, the billing manager is watching a claims queue that won't move, because nobody has entered the payor IDs.
Most of that's preventable with the right EHR implementation sequence.
We've seen that the clinics that switch systems smoothly tend to follow the same order. This EHR implementation plan walks through the six steps in order with a realistic timeline and budget, plus the checks to run in your first 90 days.
What is EHR implementation?
EHR implementation is the process of choosing, configuring, and rolling out an electronic health record system. The process ends a few months after go-live, once the new workflows are stable.
Many ABA platforms bundle clinical documentation with practice management tools for scheduling, billing, and intake. This means that one rollout reaches your clinical team, front desk, and billing staff in the same weeks.
EHRs are close to universal in medicine. By 2024, 91% of office-based physicians used a certified EHR, according to the federal Office of the National Coordinator for Health Information Technology (ONC).
Many ABA clinics, though, come to their first EHR with a mix of paper data sheets, spreadsheets, and separate billing software, which makes the implementation a complex project.
For a starting point, ONC's Health IT Playbook lists pre-implementation steps like setting up governance, redesigning workflows, and training staff. The steps below adapt that kind of process to how ABA clinics work.
Before you sign: Four main things to settle with your vendor
The smoothest implementations get decided at the contract stage. Before you sign, get written answers about:
- Migration scope: Which records will the vendor move for you, such as active treatment plans, authorizations, and past session data? Ask how many years back the move covers and what it costs.
- Export format: If you leave in 3 years, what do you get back, and in what format? Ask for a sample export file. (A vague answer here is a telling reply.)
- Training hours: How many live training hours are included, by role, and what does extra training cost after go-live?
- Support response times: Who answers the phone during go-live week, how fast, and does that change once you're live?
These four points will shape your timeline and your budget more than any feature demo could.
Also ask who the vendor's implementation specialist will be. They're the person who configures the system with you, plans the data migration, and helps your staff through go-live. Get a sense of their working schedule and style, if you can.
How to implement an EHR in an ABA clinic: 6 steps
Get the order right, and you avoid most rework: a clinic that configures before it maps workflows or trains before the data is in ends up redoing the configuration or the training. The timeline table further down names an owner for each step.
Step 1: Build your implementation team
Every role on the team needs assigning before kickoff. In a smaller clinic, one person may hold two or three of these positions:
- Executive sponsor (owner, CEO, or COO): Approves scope, budget, and the go-live date. Has final say when clinical and billing priorities collide.
- Project lead (often the operations director): Runs the timeline, the weekly check-in, and the vendor relationship.
- Clinical lead (a BCBA or clinical director): Owns treatment plan and session note templates, plus how goals, targets, and data collection get set up.
- Billing lead: Owns payor and authorization setup, billing codes and rates, and test claims. That includes enrolling with your clearinghouse, the service that checks electronic claims and forwards them to payors.
- Scheduling and intake lead: Owns calendars, staff availability, and the intake pipeline for new learners.
- Super users: One BCBA and one RBT per location who learn the system early and answer their colleagues' questions on go-live day.
Bring the whole team in early. The existing workflows live in their heads, and they'll be the first to spot where a default setting won't work for your payors.
Step 2: Pick a pilot group and set your baseline
Decide who goes first: one location, one service line, or one BCBA's caseload. A pilot gives you a small, forgiving group to help surface configuration problems before the whole clinic depends on the system.
Then measure the old system before you leave it by pulling four baseline numbers from the last 2 or 3 months:
- Average time from session end to a signed session note
- First-pass claim denial rate (the share of claims denied on first submission)
- Authorization utilization (authorized hours used vs. hours approved)
- Scheduled vs. delivered session hours
These become your success criteria. Without a baseline, "the new EHR is working" is just a feeling, and you'll have a hard time defending it to anyone who preferred the old system.
Step 3: Map your workflows and configure the system
Walk through how work moves today, from first contact with a family to a paid claim. Write down every handoff, workaround, and spreadsheet. Those spreadsheets are where your next configuration decisions are hiding.
With the workflow map in hand, configure the system around it:
- Payors and authorizations: Load each payor, its billing rules, and every active authorization with its approved units and expiration dates.
- Clinical setup: Build treatment plan and session note templates that match each payor's documentation requirements. Then add goals, targets, and data collection programs.
- Billing setup: Enter billing codes with their rates and modifiers. Then add rendering provider details for every BCBA and RBT.
- Roles and permissions: Decide who can see, edit, and sign what. RBTs usually don't need billing access, and your billing team doesn't need to edit treatment plans.
This is also a good chance to drop steps you don't need. If a workflow exists only because the old system couldn't do something, don't rebuild it. Our guide to workflow optimization for small ABA clinics has more detail.
If the EHR needs to connect to other tools, like a clearinghouse, payroll, or accounting software, list each connection now and name who builds and tests it. We cover the technical side in our EHR integration overview.
Step 4: Plan and run your data migration
Decide your migration scope before anyone exports a file, because every record you move has to be mapped, imported, and checked.
Day-one data
For every active learner, your team usually needs these records first:
- Demographics, guardians, and insurance details
- Current treatment plans, goals, and targets
- Active authorizations, with remaining units and expiration dates
- Recent session data and progress graphs needed for reauthorization
- Staff credentials and rendering provider details
Lookback window
There's no universal rule for how much history to move. When one hospital moved 20 outpatient clinics to a new EHR, physicians judged a 3-year lookback window to be enough for commonly trended lab values. Other (rarely repeated) tests kept 10 years or their full history.
A 2020 review of EHR switches ties the decision to access: migrate more if the old system is going away soon, and less if you'll keep read-only access.
For most ABA clinics, active learners plus 1 to 3 years of history (a few authorization cycles' worth) is a sensible place to start.
Manual entry or batch import
Manual entry works for a smaller caseload. It doubles as cleanup and training, since entering your own learners is a quick way to learn the new screens.
Batch import is faster at volume but needs a clean, mapped file (one whose columns line up with the new system's fields), so ask the vendor to import a test batch first. Save the final import for after configuration, since migrated records need the payors, codes, and templates from Step 3 to land in.
Validation
Spot-check a sample of migrated learners against the source system, starting with payor IDs, authorization units, and active targets.
Archive
Keep older records reachable through read-only access to the old system or a full export, for as long as your state's record-retention rules and payor contracts require. Work down any outstanding claims in the old system.
If you're also changing how sessions get recorded, our roundup of ABA data collection software covers what to look for in the clinical side of the platform.
Step 5: Train your team by role
Even a well-configured EHR can stall if people don't trust it. Structured training helps: in a 2023 study of 14 staff members at one primary care center, a 6-month EHR training program raised their knowledge and practical skills, though the study had no comparison group.
Five main habits make training stick:
- Train by role: BCBAs learn treatment planning and program setup, and RBTs learn data collection and note signing on the device they'll carry. Billing staff focus on claims and authorizations, while front desk staff learn scheduling and intake.
- Practice on realistic data: Run mock sessions with test learners and sign the notes. Then generate a test claim and pull a progress report before go-live.
- Train close to go-live: Schedule most role training in the final 1 to 2 weeks, so staff put new skills to use right away.
- Lean on your super users: They answer the "where's that button" questions so your BCBAs can stay focused on clinical work.
- Plan refreshers: Short follow-up sessions in the first month catch the habits that drift.
If you already use behavioral skills training with your staff, use it here, too. Our guide to ABA staff training walks through this approach.
Step 6: Choose your go-live strategy and run go-live week
You have two main ways to switch over: a big bang go-live, where every location starts using every function on the same day, or a phased rollout that brings on locations or service lines one at a time.
| π Approach | β Works best for | β οΈ Watch for |
|---|---|---|
| Big bang | One location, simple payor mix, strong super users | Every problem hits everyone on day one |
| Phased by location or service line | Multi-site groups, or ABA plus speech or occupational therapy practices | Two systems running side by side for a while |
Your Step 2 pilot is already a small phased rollout. A single-location clinic can switch everyone else over once the pilot is stable, while multi-site groups bring each location on after the previous one settles.
Lighten schedules in the first week or two where you can, and warn your billing team that claim volume may lag. In a 2014 study of 26 primary care practices adopting an EHR, visits per physician fell 8% in the first 6 months and were still about 4.5% lower more than a year later.
Here's a checklist to make go-live week smoother:
- Hardware test: Every tablet and laptop logs in, syncs, and works on the clinic Wi-Fi. Test the back room, where the signal always drops.
- Logins: Every user has working credentials and the right permissions before day one.
- On-call team: Super users and the vendor's support contact are reachable all week, with a posted "who to call for what" list.
- First-day scope: Decide what runs in the new system on day one (sessions, notes, scheduling) and what waits a week (new intakes, custom reports).
- Daily huddle: Fifteen minutes at the end of each day to log issues and assign fixes.
- Test claims: Send a small first batch to each major payor and confirm acceptance before releasing full claim volume.
EHR implementation timeline for ABA clinics
Oracle Health, a large EHR vendor, puts implementation at 3 to 4 months for smaller medical offices and clinics, and 15 months or longer for each facility in a large hospital system.
Our planning recommendation for a growing ABA clinic that has already picked its vendor is roughly 10 to 16 weeks from kickoff through go-live week, then about 3 months of review. Here's a typical breakdown:
| π Phase | β±οΈ Weeks | π€ Owner |
|---|---|---|
| Step 1: Team gathering and kickoff | 1β2 | Executive sponsor, project lead |
| Step 2: Pilot scope and baseline | 1β2 | Project lead |
| Step 3: Workflow mapping and configuration | 4β6 | Clinical lead, billing lead |
| Step 4: Data migration and validation | 3β4 (starts during Step 3; the final import and checks add about 2 weeks after it) | Billing lead, vendor |
| Step 5: Role-based training | 1β2 | Super users, vendor |
| Step 6: Go-live and stabilization | 1β2 | Whole team |
| 30/60/90-day review | 13 after go-live | Project lead |
Multi-location groups rolling out in phases should add about a week or two for each additional site.
EHR implementation cost
EHR implementation cost goes well beyond the subscription. Medesk estimates first-year total cost of ownership at $16,400 to $68,400 per provider for a small- to mid-sized practice. This is just one EHR provider's estimate, though, and the figures aren't sourced.
Plan your budget in three buckets:
Upfront costs
- Setup and configuration: Implementation or onboarding fees, if your vendor charges them
- Data migration: Vendor import fees, or staff hours for manual entry
- Devices: Tablets or phones for RBTs, plus any laptop or Wi-Fi upgrades
Ongoing costs
- Subscription: Usually priced per user, per provider, or per learner
- Clearinghouse fees: Per-claim or monthly fees for submitting claims electronically
- Add-ons and support: Extra modules, premium support tiers, or additional training
Indirect costs
- Productivity dip: Fewer sessions or slower notes during go-live (see Step 6)
- Training time: Paid hours for every staff member, including backfill for RBTs
- Running two systems: Paying for the old platform while you finish old claims and archive records
Whichever vendors you compare, Passage Health included, ask each for a written first-year total that covers all three buckets, so you're comparing like with like.
After go-live: Your 30/60/90-day review
Go-live starts the part of the project where you find out whether it worked. Put three reviews on the calendar before launch day, and compare each one with the baseline you set in Step 2.
Day 30: Check adoption
- Is every session documented in the system, or are paper data sheets still circulating?
- Is the time from session end to signed note back to (or better than) baseline?
- Have the first claims been submitted, accepted by the clearinghouse, and paid?
- What are the five questions your super users hear most? Turn the answers into a one-page cheat sheet.
Day 60: Check revenue
- Denial rate: Compare first-pass denials with your baseline, and group them by reason. Early denials often trace back to a setup error (a wrong rate, a missing modifier, a rendering provider mismatch) that you should only have to fix once.
- Authorization utilization: Are learners getting the hours their authorizations allow? Unused authorized hours mean lost care and lost revenue.
- Templates: Which session note templates or programs still need edits?
Day 90: Decide what's next
Compare all four baseline numbers. If they're at or better than where you started, roll out to the next location or service line, or retire the old system (keeping read-only access for record retention).
If they're not, schedule refresher training on the weakest workflow before you expand.
Common EHR implementation challenges (and how to get ahead of them)
Most implementation problems are predictable. Here are the main issues ABA clinics run into, and how to head off each one:
- Staff resistance: Team members used to paper notes or an older system may push back on new software, especially if it slows their sessions at first. Involve super users early (Step 1), and show RBTs which paper steps go away, like re-entering data sheets, so they can see the broader payoff.
- Billing disconnect: When billing setup falls behind clinical setup, sessions get delivered and documented but claims stall, and unworked denials pile up. Give your billing lead equal weight in Step 3, so payor setup is done before the first session needs billing.
- Data migration errors: The 2020 review of EHR switches lists data integrity among the main migration challenges, since mismatched structures between systems can leave records inconsistent. The spot-check in Step 4 is where you catch these errors before they reach a session or a claim.
- The wrong vendor: A system built for general medicine often needs workarounds for ABA authorizations, units, and session data collection. Settle the four contract questions above and ask for a demo built around your own payors and programs.
- Interoperability: A connection that passed testing can still fail later if someone changes the session types or billing settings it depends on. Retest each one after any major settings change.
- Underfunded training: A 2020 scoping review of EHR research named poor or insufficient training as a frequent barrier to adoption. Fund role-based training as an indirect cost before kickoff.
- Change fatigue: A new EHR, new forms, and a new schedule are a lot to absorb. Where you can, hold back nonessential process changes until after your day-90 review.
EHR implementation with Passage Health
Passage Health is an all-in-one practice management platform designed for ABA, so your clinical, scheduling, and billing setups take place in a single EHR implementation.
Here's how the platform supports each stage of the rollout:
- 1:1 onboarding and planning: Your onboarding contact helps you plan a big bang or phased rollout by location, using our example timelines as a starting point.
- Custom permissions by role: Create roles with their own access levels for scheduling and session notes, while fallback roles cover the rest of the platform.
- Mobile data collection to treatment reports: RBTs collect data and complete session notes in the mobile app, with timers that can start automatically for frequency, duration, and rate targets. That data feeds graphs and customizable treatment reports for reassessment.
- Scheduling with authorizations in view: The upgraded calendar shows color-coded event types, staff availability, and how each booking counts against a learner's authorization. Schedulers can reassign canceled or unassigned sessions from the Action Items panel, and staff with scheduling access can create and edit events in the mobile app.
- Electronic billing and reporting: Turn completed sessions into claims and submit them through our clearinghouse integration. Authorization utilization and session reports then give you several of the numbers for your 30/60/90-day reviews.
- Client Intake: Leads move from the first form to active client in one pipeline.
Book a demo to walk through an EHR implementation plan for your clinic.
Frequently asked questions
How long does EHR implementation take for an ABA clinic?
We plan for 10 to 16 weeks from kickoff to the end of go-live week (once you've chosen your EHR) then a 90-day review. Multi-location groups, phased rollouts, and large data migrations take longer.
How much does EHR implementation cost?
Your EHR implementation cost includes up-front setup, ongoing fees, and indirect costs like the productivity dip during go-live. One vendor, Medesk, estimates first-year costs at $16,400 to $68,400 per provider for small- to mid-sized practices.
What's the best way to migrate existing learner data?
The best way to migrate learner data is to clean it first and move only what your team will use. Start with each active learner's insurance, treatment plan, and authorizations, add recent session data, and archive older records in a read-only format.
What does an EHR implementation specialist do?
An EHR implementation specialist sets up your new system and coaches your staff through the switch. They usually work for the EHR vendor, though some clinics hire a consultant or assign the role to an internal project lead.
Is practice management system implementation different from EHR implementation?
Yes, the two differ in scope: practice management system implementation sets up scheduling, billing, and authorizations, while a standalone EHR implementation sets up clinical records like treatment plans and session notes. When one platform handles both, you only have to plan, train, and go live once.
References
Barker, W. (2026). Office-based physician electronic health record adoption, 2008β2024 (ONC Data Brief No. 84). Office of the National Coordinator for Health Information Technology. https://healthit.gov/data/data-briefs/office-based-physician-electronic-health-record-adoption-2008-2024/
Fleming, N. S., Becker, E. R., Culler, S. D., et al. (2014). The impact of electronic health records on workflow and financial measures in primary care practices. Health Services Research, 49(1 Pt 2), 405β420. https://doi.org/10.1111/1475-6773.12133
Huang, C., Koppel, R., McGreevey, J. D., III, et al. (2020). Transitions from one electronic health record to another: Challenges, pitfalls, and recommendations. Applied Clinical Informatics, 11(5), 742β754. https://doi.org/10.1055/s-0040-1718535
MacKenzie, B., Anaya, G., Hu, J., et al. (2021). Defining data migration across multidisciplinary ambulatory clinics using participatory design. Applied Clinical Informatics, 12(2), 251β258. https://doi.org/10.1055/s-0041-1726032
Musa, S., Dergaa, I., Al Shekh Yasin, R., et al. (2023). The impact of training on electronic health records related knowledge, practical competencies, and staff satisfaction: A pre-post intervention study among wellness center providers in a primary health-care facility. Journal of Multidisciplinary Healthcare, 16, 1551β1563. https://doi.org/10.2147/JMDH.S414200
Office of the National Coordinator for Health Information Technology. (2025, May 7). Electronic health records. Health IT Playbook. https://playbook.healthit.gov/playbook/electronic-health-records/
Tsai, C. H., Eghdam, A., Davoody, N., et al. (2020). Effects of electronic health record implementation and barriers to adoption and use: A scoping review and qualitative analysis of the content. Life, 10(12), 327. https://doi.org/10.3390/life10120327



