Insurance programs from a demonstration
Prove an eligibility answer without sending policyholder data to a model
A repeating eligibility or coverage check has to stay on your computer: policyholder data, portal credentials, and a coverage answer you must prove. OpenAdapt compiles a demonstration into a program. Later healthy runs make no generative-model API calls. VERIFIED means an independent check of the write passed. A Seal is the signed receipt of that check. A green banner is not.
The last mile is the payer portal or claims-admin screen when no supported API completes the check. An incomplete eligibility response still leaves a person in that portal. If a working 270/271 path already completes the check, use it. OpenAdapt is the remaining GUI lookup.
See the loop on a real open-source insurance system. A synthetic policyholder and service are looked up in openIMIS, the demonstration is compiled, and the browser result is checked against an independent read-only SQL query. An eligible policy returns VERIFIED. An expired policy whose browser result conflicts with the system record returns HALTED. Both paths recorded zero model API calls.
Local is $0. MIT. Hosted is $29/month. Enterprise goes through qualification.
Real application footage
openIMIS 25.10: eligible policies VERIFIED, expired policies HALTED
The source demonstration and the VERIFIED replay sit next to the SQL-refuted halt. Guided overlays bind to retained runtime frames. Raw footage removes the presentation layer. Pinned local synthetic data.
Guided view synchronized to the exact retained runtime timeline; raw footage remains unchanged.
- 1DemonstrateCapture the task and its evidence.
- 2ExecuteReplay the compiled workflow locally.
- 3Verify or haltProve the effect, or stop for review.
A green banner is not proof the policy is in force
A populated field proves only what the current screen rendered. In this reference, OpenAdapt accepts eligibility only when a separate read-only SQL query confirms the policy, product, service, and effective-date state. When that independent result disagrees, the run halts instead of reporting success. HALTED does not mint a Seal.
Portal work the API doesn't finish
Use it for eligibility and coverage checks that still live in a portal because no supported API reaches the required workflow. It also fits a bounded status-update or document-attachment step at the edge of an otherwise API-driven claims pipeline.
Dental front-desk eligibility is a different workflow, on /solutions/dental. An unverified banner is not accepted. After an uncertain delivery, there is no blind retry.
Qualify one eligibility workflow
Bring one repeated portal lookup and the policy or claim record that proves the coverage answer.