Automate dental insurance eligibility checks
The front-desk workflow every practice runs dozens of times a day: sign in to the payer portal, look up the patient, read coverage and benefits, and carry the answer into the practice management system — demonstrated once by your own team, then compiled and replayed per patient.
This is a workflow shape, not a canned connector: you compile it from a recording of your own team in your own applications. The execution and verification mechanics it relies on are proven on the linked reference templates.
Runs on
Your practice’s own payer portals and practice management system, from a recording of your team performing one verification. There is no canned connector for any specific payer portal — each workflow is compiled from your demonstration and qualified against your applications. The verified-write mechanics are proven on the openIMIS insurance reference, where policyholder resolution and the resulting write are checked against the insurance database itself.
The demonstrated steps
- 1Sign in to the payer portal — credentials are secret parameters, never written to the recording or the bundle
- 2Look up the patient by member ID and date of birth — the per-patient parameters
- 3Open the coverage and benefits view
- 4Read the eligibility result and the benefit fields your practice actually uses
- 5Record the result where your workflow puts it — the PMS, a worksheet, or the schedule
Parameters: member ID · date of birth · payer selection — as demonstrated by your team — recorded values are the defaults; every replay can override them.
How the outcome is verified
Every step carries identity checks derived from the demonstration — the compiled program verifies it is looking at the right member before it reads or writes anything, and halts and asks instead of proceeding when the portal shows something it never saw demonstrated. Where the result lands in a system with a database, API, or export you control, the write is bound to an effect contract and checked against that system of record, not the screen.
- pre-action target-identity checks
- halt on undemonstrated portal state
- effect contract on the recorded result where a system of record exists
Proven on
Try it from the command line
The compiler and runtime are open source and MIT licensed. Healthy runs are local and make no model calls.
pip install openadapt-flowInstall the open-source compiler and runtime.
openadapt-flow record --url https://your.app --out recOpen a headed browser on your app and demonstrate the workflow once; Ctrl-C to finish.
openadapt-flow compile rec --out bundle --name my-taskCompile the recording into a deterministic bundle with auto-classified risk per step.
openadapt-flow lint bundle && openadapt-flow certify bundle --policy permissiveSurface coverage gaps, then gate the bundle against a policy before it ever deploys.
openadapt-flow replay bundle --url https://your.app --param name=valueReplay against your app; recorded values are defaults and --param overrides them.
Put this workflow into production
Bring your version of this workflow and the record that proves its outcome. We'll map the deployment, verification, shadow run, and supervised rollout.