The operational decision
Distinguish a logo or roadmap item from a configured and permitted workflow. 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
Ask what is connected, which operation was tested and what remains conditional; keep all current pilot examples free of patient-system data.
Example wording for approval
“Is this a working connection for the proposed scope, or a future possibility? The current Ava launch does not access EHR records or schedule medical visits.”
Worked example
A proposal displays an EHR logo and says integration available. Ask whether that means a tested operation for this deployment, a generic API possibility or future development. Require the exact action and prerequisites in writing. The current public-information pilot should stay separate regardless of the logo. A successful demonstration of a synthetic record elsewhere is useful evidence about a possibility, but it does not by itself authorize patient access or activate scheduling for this office.
Handoff record
Record these task-specific fields: system name, claimed action, evidence, unresolved dependency.
Acceptance check
Present a screenshot of an integration logo as the only evidence. The review should remain incomplete rather than treating the logo as a passed connection test.
Try Ava with your business’s public information ↗