Workflow templatePattern for your recording

Automate dental insurance eligibility checks

Check a patient’s coverage in the payer portal, then carry the answer into the PMS, a worksheet, or the schedule. Your team records and qualifies each execution surface it uses.

Compile this workflow shape from your team’s recording. The related references show its execution and verification mechanisms.

Runs on

Your practice’s payer portal and the destination for the result. One browser bundle can cover one tab and same-origin routes. A new origin, tab, native PMS, application, or backend uses a separate qualified bundle. An external orchestrator performs the handoff and an end-to-end verifier checks the final result. There is no canned connector for a payer portal. The openIMIS reference shows policyholder resolution and database-checked writes.

Source in openadapt-flow →

Steps to record

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 in the PMS, worksheet, or schedule through the same qualified tab and origin, or through an externally orchestrated handoff to a separate destination bundle

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

Each qualified bundle checks that it has the right member before it reads or writes anything. An undemonstrated portal state halts the run. When the result moves to another bound target, an external orchestrator coordinates the bundles and an end-to-end verifier checks the destination system of record. Flow does not compose the bundles.

pre-action target-identity checks
halt on undemonstrated portal state
end-to-end effect contract on the recorded result

Related measured references

Automate health insurance claim intake in openIMISMeasured reference Automate patient triage note entryMeasured reference

Try it from the command line

The compiler and runtime are open source and MIT licensed. The default healthy path runs locally and makes no generative-model API calls.

pip install openadapt

Install the OpenAdapt launcher, compiler, and included browser capability.

openadapt flow record --url https://your.app --out rec

Record one browser tab and same-origin route set; Ctrl-C to finish. A task that crosses an origin, tab, application, or backend needs separately qualified bundles and external orchestration.

openadapt flow compile rec --out bundle --name my-task

Compile the recording into a deterministic bundle with auto-classified risk per step.

openadapt flow lint bundle --strict

Report coverage gaps. Complete the required identity, effect, idempotency, and postcondition contracts before governed use.

openadapt flow replay bundle --url https://your.app

Rehearse locally. This command does not certify the bundle. Governed certification and execution also require a deployment configuration with the declared policy, identity, effect, and runtime bindings.

Qualify this workflow

Bring your version of this workflow and the record that proves its outcome. We'll map the deployment, verification, shadow run, and supervised rollout.

Evaluate a workflow Read docs

Would you rather we ran this for you? OpenAdapt offers a managed version of this workflow to single-location dental practices at $500/month. See the dental founding-cohort offer →