Ask Guide. It answers from the facts.

The operating crew for rehab and behavioral health centers. Seven agents read payer rules, check sessions, notes and claims, and draft follow-ups. Your team makes every call.

No. Confirmity works alongside the EHR and billing tools you already use. It reads what is there and points to what is missing.

Four steps. Guide sets you up: your payers, programs and staff list, typed in for you, and you confirm each step. Scout starts reading every payer and state source you bill. The crew checks sessions, notes and auths against the six gates. Nothing goes out until a person on your team says yes.

Guide sets up your center with you, Scout starts reading your payers, and the crew runs your real workflow while your team approves every step. Pre-contract pilots use made-up sample data until a BAA is signed.

Minutes 0 to 10: Scout pulls the current rules for one payer you bill and shows what changed. Minutes 10 to 20: we follow a sample claim through all six gates. Minutes 20 to 30: we map your roles to seats. You leave with a written summary.

No. Every demo, walkthrough and pre-contract pilot uses made-up sample data. We do not ask for patient data before a BAA is signed.

We start with Ohio Medicaid and the managed care plans most behavioral health centers bill there. For other states, ask us.

Walkthrough requests are usually answered the same business day, and always within one business day. A person reads every message sent to hello@confirmity.app.

We sign a business associate agreement (BAA) with your center before any real client data goes in. Today Confirmity runs on sample data. Hosting on Vercel and our database on Neon both run under signed BAAs, and every view is logged. See Security and our BAA.

Only the people whose seat needs them. Michael, a therapist, sees clinical notes for his own clients. Dana in billing sees claims and authorizations, not clinical notes. Juan, the owner, sees totals and trends. The server decides; the browser cannot ask for more.

Part 2 records are tagged as their own data class. Before one is shared, Confirmity looks for the client's consent that covers it. If consent is missing, the share stops and the item goes to a person on your team.

Who opened what, who decided what, and when. The log is append-only: entries are added and never edited or removed. Staff and agents write to the same log. Passwords and session tokens never go in it.

Every person signs in as themselves, with no shared logins. Idle sessions end after 15 minutes by default, and your admin can set that anywhere from 5 to 60 minutes. No session lasts longer than 12 hours.

No. Each center is its own tenant, and requests are scoped on the server, so one center can never read another's records.

Email hello@confirmity.app with the subject "BAA request", your center's legal name and who will sign. We send our BAA, subprocessor list and security policies to your compliance lead. If you use your own BAA form, send it and we will review it.

Six checks every claim clears, in order: provider, payer, service, authorization, clinical and claim. When one fails, the claim stops there and the gap goes to a named person. See the platform.

Never. Agents prepare the work and show the evidence. A named person on your staff approves every send, change or approval, and that okay is recorded.

It waits in a hold queue with the reason in plain words and an owner. For example, Checker holds a claim when Michael has not signed the group noteSep 29. Fix it, then release it.

SeverityMediumImpactHold

The ones on your contracts, including Ohio Medicaid and its managed care plans like AmeriHealth Caritas, CareSource and Molina. Scout reads them every morning at 6:00 AM.

Scout reads payer and state sources daily, with the source, date and effective date on every change, and shows which clients each change touches. You decide what the center does.

Yes. Collector checks units used against units approved and flags renewals early. When a client is about to run out, Angie in intake gets the renewal.

Vercel (hosting) and Neon (database), both under signed BAAs. They are our only subprocessors. See subprocessors.

No. We use PHI only to provide the service to your center, as the BAA allows. We do not sell it, use it for advertising, or use it for our own purposes.

Confirmity works alongside your current tools, and external connector adapters are an optional module. For which systems we connect to today, ask us.

Customer data, including PHI, is returned or destroyed as your agreement and BAA say, where feasible.