Dental programs from a demonstration
Automate the payer-portal work behind your front desk.
Eligibility and claims-status checks have to stay on the practice computer: PHI, payer-portal credentials, and a coverage answer you must prove. OpenAdapt compiles a recording of your team into a program and replays it on that machine. Later healthy runs make no generative-model API calls, so those lookups don't send patient data to a model.
Sign in to the payer portal. Look up the member. Read coverage and benefits, or the claim state. Carry the answer into the practice management system. Your staff open and supervise the sessions, including MFA. OpenAdapt does the re-keying. Anything it cannot verify lands in a queue for a person to finish.
Local is $0. MIT. The core is free on the front-desk PC.
The two front-desk lookups
- Insurance eligibility verification. Sign in to the payer portal, look up the patient by member ID and date of birth, open the coverage and benefits view, and record the eligibility result where your workflow puts it: the PMS, a worksheet, or the schedule. Credentials are secret parameters, never written to the recording.
- Claims status checks. Look up a submitted claim in the payer portal, read its current state, and carry the status into the PMS record your billing follow-up already works from.
See the eligibility workflow step by step →
The wrong-patient defense
It halts instead of writing a wrong record.
A compiled step can carry identity checks derived from the demonstration. The program verifies it is looking at the right member before it reads or writes, and when the portal or the PMS shows something it never saw demonstrated, it halts and puts the case in a ready-to-finish queue instead of guessing. A halt does not mint a Seal. The public safety gallery shows the exact look-alike record cases behind this defense.
See the wrong-patient defense →Review the runtime safety model →
It runs on the front-desk PC you already use
Original recordings stay local, and live observations can contain PHI, so dental workflows run on a practice-controlled machine. The same front-desk computer your staff already use, inside portal sessions your staff open and supervise. The default healthy path makes no generative-model API calls, so routine verifications send nothing to a model endpoint.
We have not published a dental PMS trial matrix. The public verify-or-halt footage is an openIMIS eligibility fixture, on the insurance page, not a dental practice-management system.
Qualify one front-desk workflow
Bring the payer portals you check most, your PMS and its version, weekly volume, and the exceptions your staff handle today.