Co-Founder & CEO, Lumenality
Arthur Anderson is the co-founder of Lumenality. He spent years inside healthcare organizations and hospitals. He then spent more than a decade working alongside providers. For an ABA practice, he designed the revenue-cycle, reporting, credentialing, and authorization workflows. He also handled its payer contracts, audits, and appeals.
From that seat, Arthur kept seeing the same problem. Practices ran scheduling, clinical notes, billing, data collection, and compliance in separate systems. Every handoff between those systems was a chance for data to get lost and claims to get denied. He built Lumenality so an ABA practice can run that work on one record.
His articles are practical guides for practice owners, BCBAs, and billers. Each one draws on that operational work: what payers ask for, where claims and authorizations break, and what to check before choosing software.
EHR lock-in is mostly about data. Here is what an ABA practice should get in writing before signing. Cover export scope, file formats, exit timing, fees and what happens to records after you leave.
A practical security checklist for ABA practice owners: eight questions to put to any EHR vendor before you sign. Each one explains what a strong answer sounds like and how Lumenality's single-tenant design answers it.
What an EHR really costs an ABA practice over several years. Compare per-seat, percentage-of-collections and flat-rate pricing, the hidden line items, and the cost of switching later.
The HIPAA Security Rule asks ABA practices to show administrative, physical and technical safeguards. Here is what each one requires, and how a dedicated database and practice-specific encryption keys make them easier to prove.
A step-by-step way for a small ABA practice to choose an EHR. Map your workflows, run scripted demos, check security and the BAA, price the full term and get exit terms in writing.
ABA claim denials follow patterns. Learn to read 835 reason and remark codes and to tell rejections from denials. Then fix each cause at the source and stop repeat denials before claims go out.
A step-by-step guide to credentialing BCBAs and RBTs. It covers BACB requirements, NPIs, CAQH ProView, payer applications, effective dates and the renewal calendar that keeps providers billable.
How Lumenality handles ABA billing: session notes become claim lines, rule-based checks run before submission, and built-in Stedi tracks claims and payments. AI features are optional, off by default and admin-controlled.
A practical blueprint for ABA prior authorizations: verify benefits, request units by CPT code, document medical necessity, track drawdown and reauthorize on time. Includes the federal decision timeframes now in effect.
Which ABA workflows an EHR must fit without custom work: data collection methods, treatment plans and BIPs, RBT supervision, and authorizations tracked by CPT code.
Performance in an ABA EHR is not a benchmark number. It is whether RBTs can record and sign without waiting, and whether billers can send claims built from the same record. Here is what to look for.
Single-tenant and multi-tenant EHRs can both protect ABA client data. Here are the honest trade-offs in isolation, performance, control and cost, and the cases where a multi-tenant system is a reasonable choice.
Each ABA service code has its own provider level, authorized units and supervision role. Here is how to track RBT supervision under BACB rules and draw down authorizations by CPT code.
Credentialing gaps turn into denied claims. See how unenrolled rendering providers, effective dates and recredentialing lapses hit ABA revenue, and the routine that prevents them.