Care that stays connected.

See the workflow, then introduce it alongside your current system.

Access opens in stages. Start on a clinic that is not yours, prove the work with your team, then bring in only the data and workflow you are ready to govern.

1. Try the synthetic workflow

   A working clinic with clients, authorizations, session notes and held claims, with every role. It contains no real patient data, cannot send anything to a payer or family, and account availability is confirmed before a sandbox opens.

2. Bring your own data

   For a self-serve workspace, a signed BAA and a verified active Type-2 organization NPI come first. Then import clients from a CSV, and nothing is created until you confirm. Production use also follows a separate readiness approval. CentralReach exports are an assisted overlay migration; automated live-workspace import is not available yet.

3. Expand deliberately

   A setup ledger shows what is left: team invited, payers added and the first note signed. Your clinic keeps its existing system of record while the team proves each ABACare workflow and completes production readiness.

One thread from session to follow-through.

Each case brings its evidence, the rule checked, the proposed next step and the person responsible into view. Teams can see what is ready, what needs review and what must wait.

• Authorization renewal. The renewal window is open and the packet is drafted. A BCBA has not approved it.
• Held claim. The rule check stopped it: the session note behind it is unsigned.
• Note to attest. The AI draft is waiting for the clinician who ran the session to read it and sign.
• Denial follow-up. An appeal is drafted from the denial code and the signed note. A biller decides.
• Weekly family update. Sealed by the BCBA, released to the family, receipt on file.
• Supervision hours. An RBT is behind the 5 percent supervision minimum. A person has to schedule it.

Illustrative cases, drawn with the same chain the product uses. The six links: evidence, rule, proposal, approval, action, audit.

Every decision has a clear record.

See who reviewed a step, what evidence and rule they used, and what changed. The history is part of the workflow, so the team can follow the decision later.

• The signature binds the content. A signed note stores a hash of what was signed, tied to the reviewer and the time. Release checks it against the current revision, so an edit after signing is caught.
• The AI draft is kept, never overwritten. The draft and the signed version both stay on record. The difference between them is the evidence that a practitioner actually reviewed the work.
• Evidence links are append-only. A reviewed video event supports a sentence, the sentence belongs to a signed note, and the note supports the claim. Each link is written once and never edited.
• Payer rules carry their source. A rule pack lists where each rule came from, when it was retrieved and whether anyone reviewed it. A claim is checked against a pack that was locked at the time.

Five people, five seats, one record.

• Owner. One feed of what will cost care or money, who owns it, and by when.
• BCBA. Notes to attest, with the draft, the evidence under it and what changed.
• RBT. The shift: next session, the brief, one-handed capture that survives a dead signal.
• Billing. A held claim arrives with the rule, its source and the correction.
• Parent. A weekly update their child's BCBA has sealed. A participant, not a recipient.

What is live, gated and next.

• The demo and the sandbox run on a fictional clinic. No real patient data is used on this site, and nothing here is a customer story or a measured clinic result.
• Access is staged. A person confirms each new account; a sandbox is synthetic; real-data activation needs a signed BAA, a verified active Type-2 organization NPI and a separate readiness review.
• A Business Associate Agreement comes before any production PHI.
• Today, billing staff submit a validated 837P through the payer's own portal and attest to it. ABACare records that it did not transmit the claim; uploaded 835 remittances are then matched and reconciled.
• AI never signs a clinical note and never releases a family update on its own.
• Texas has the deepest payer-rule pack. The case, the chain and the seal are built so they are not specific to Texas, or to ABA.