Automate new patient record entry
Registration and intake re-keying — demographics from a referral, a form, or an existing structured source entered into the EMR or PMS — demonstrated once by your team, compiled, and replayed per patient with the fields as parameters.
Compile this workflow shape from your team’s recording. The related references show its execution and verification mechanisms.
Runs on
Your clinic’s own EMR or practice management system, from a recording of your team entering one record. A separate local synthetic OpenEMR fixture tests effect contracts against stored state and catches a dropped write behind a “Saved” screen.
Steps to record
- 1Open the new-patient or registration form in your EMR or PMS
- 2Enter the demographic fields — each one a parameter, substituted per patient at replay
- 3Enter coverage or referral details as demonstrated
- 4Save the record
Parameters: the demographic and coverage fields your team demonstrated — one parameter each — recorded values are the defaults; every replay can override them.
How the outcome is verified
Write-shaped steps are auto-classified as irreversible at compile time, which arms the low-confidence refusal: the program halts rather than saving into ambiguity. lint reports any step that acts without an identity check before you deploy, and certify can refuse the bundle under a strict policy. Where your EMR exposes a database, API, or export, the save can use an effect contract. The local synthetic OpenEMR fixture tests this path, including a silent dropped write behind a “Saved” screen.
- irreversible-write classification and refusal arming
- lint coverage gate before deploy
- effect contract on the saved record where a system of record exists
Related measured references
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 openadaptInstall the OpenAdapt launcher, compiler, and included browser capability.
openadapt flow record --url https://your.app --out recRecord 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-taskCompile the recording into a deterministic bundle with auto-classified risk per step.
openadapt flow lint bundle --strictReport coverage gaps. Complete the required identity, effect, idempotency, and postcondition contracts before governed use.
openadapt flow replay bundle --url https://your.appRehearse 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.