The operational decision
Evaluate what the proposed service does when the conversation leaves a prepared sales script. Evaluate the specific workflow you are buying rather than a broad list of features. An integration logo, fluent demonstration or sales statement is not evidence that your office connection is configured and tested.
Prepare the workflow
Request a fictional hours question followed by a patient-specific request; ask the supplier to show the boundary and resulting records.
Example wording for approval
“Please demonstrate an office-hours answer, then a request for a test result. Show that the second request is redirected without patient-detail collection.”
Worked example
A supplier demonstrates a perfect parking answer, then explains that patient boundaries will be added later. Keep the boundary requirement open. Ask for the fictional test-result request in the actual proposed configuration and inspect what gets stored afterward. A verbal assurance or a roadmap slide does not show the behavior. The procurement record should identify the observed gap and who must resolve it before activation, without providing a real patient interaction as a more convincing test case.
Handoff record
Record these task-specific fields: scenario, supplier response, observed record, unanswered question.
Acceptance check
A supplier merely describing a future safeguard has not passed. Require evidence of the tested behavior in the proposed configuration.
Try Ava with your business’s public information ↗