SageWorks ABA connects treatment, live session data, documentation, authorizations, billing, payroll and compliance in one continuous record — so care stays clinical and revenue stays defensible.
Purpose-built for ABA · Human-led clinical decisions · Intelligence with evidence
One session. One source of truth. Click a stage — it is the same session throughout. Everything shown is synthetic; no real record appears on this site.
Hours are worked and paid. Weeks later the note is missing, the filing window has closed, and nobody can say when it stopped being recoverable.
Units are counted, not projected. The renewal is requested after the authorization is exhausted, and the choice is unpaid care or a gap in a child's treatment.
A narrative says no challenging behaviour occurred. The behaviour log for the same session says otherwise. Both are in the system, and nothing compares them.
None of these are software failures. They are what happens when clinical truth, operational truth and financial truth are three records that have to be brought into agreement by hand.
The claim is a view of the session, not a second copy of the work. Payroll reads the same ledger. Reconciliation is not a nightly job, because disagreement is structurally impossible.
Every sentence carries the events it rests on. Click "independently on 4 of 6 trials" and the six trials are there. A sentence with no supporting record is not produced at all.
Trials, timers, visit verification, unit maths, entitlement and claim gating are deterministic rules. There is a kill switch, and turning it off changes nothing about whether the practice can operate.
A therapist pulls an entitlement lease while there is still signal and carries it into the home. Work recorded with no connection is never rejected on sync — the claim is held with a reason, and the record of care stands.
A credential lapsing next week does not stop today's session and does stop what is booked for next month. Caught at booking, not on the doorstep.
Every block in the system is administrative: a claim, a payroll export, a booking. Nothing can interrupt a clinical encounter, and no automated decision arrives without the records that produced it.
| Level | What it permits |
|---|---|
| 0 · Observe | Analyses. Writes nothing anyone sees in the workflow. |
| 1 · Suggest | Appears in the rail. Dismissible without a reason. |
| 2 · Warn | Persists until acknowledged. May create a review task. |
| 3 · Confirm | An administrative action cannot proceed unattended. A named person confirms. |
| 4 · Block | Claim release, payroll export, scheduling. Reserved for the rules engine — no model holds it. |
Every model output is recorded with who reviewed it and what happened next. The audit chain is hashed per practice and append-only: reads are recorded too, because in healthcare who looked is a finding of its own.
We would rather tell you this now than have you find it out in a demo.
Eight domain services behind an edge and two separate front doors. The clinical ledger, the entitlement rules engine, claims with scrubbing and an 837P draft, workforce reconciliation, offline capture, intake and scheduling, the hash-chained audit, the practice console and an offline tablet client. The whole suite is checked by an automated verification run on every change.
No practice is live on this. The payer rule graph holds one illustrative payer, and it is built payer by payer with someone who knows the companion guides. Clearinghouse transport is not connected, so an 837P is a structural draft and says so. HIPAA readiness is a programme — agreements, encryption, access reviews, retention, training — and the architecture supports it rather than constituting it.
We are not open for self-service sign-up, and that is deliberate: before a practice puts a child's record into this software there needs to be an agreement covering it. Leave your details and a person will come back to you.
We will be in touch at the address you gave. If it is urgent, write to hello@sageworksaba.com.