Attended execution demo · synthetic data

Handle every pause from one clear mobile screen.

Try all six request types. The phone records an operator answer. The customer-controlled runner checks the live application and returns a distinct result.

See the full governed workflow

Try the mobile decision experience

Switch among all six pause types. Answer inside the phone, then inspect the distinct result returned by the customer-controlled runner.

Interactive phone experience · synthetic data

Six reasons a workflow can ask for help.

Choose a request type. Then answer it inside the phone to see the customer-controlled runner result.

6 request types

Public simulatorThe phone below uses synthetic tasks. A live phone receives signed tasks from the paired customer runner. This OpenEMR fixture supplies the word “patient”; a qualified live task supplies its reviewed entity class.

1
Open securelyScan the QR code, sign in, then enable alerts.
2
Answer one requestThe phone shows only permitted actions.
3
Verify on the runnerThe runner rechecks and returns a receipt.

See the complete live sequence

Desktop connects the customer runner to its configured control plane.
The runner projects one signed decision task to the authenticated phone view.
The operator opens that view with the QR code and signs in.
The phone shows only the actions Flow permits. It has no execution authority.
The customer runner checks the live application again, then returns a receipt.

OpenAdapt customer runner

⌕

Record identityNot sent

OpenAdapt needs your help

Open the intended patient record.

The record identity did not match. OpenAdapt stopped before Save.

ActionNot sentCheckPatient record

Retained OpenEMR patient screen from the reference run — Captured when OpenAdapt stopped · synthetic patient data · not live

After your answerOpenAdapt will check the patient identity and target again.

The phone records an answer. The runner checks the live application again. Only the runner can return a verified result.