Reserve identity verification for a separately approved workflow

The operational decision

Avoid adding identity questions to an information-only script as a shortcut to future capability. A future workflow needs a separate decision from the current information-only pilot. Listing a possible next stage does not make the technical connection, agreements or operational safeguards exist.

Prepare the workflow

Document the need at a process level and name the practice reviewers; do not design or activate patient verification in the present pilot.

Example wording for approval

“This information line does not verify patient identity. Please use the practice's own approved channel for any request involving your records or appointments.”

Worked example

Someone proposes asking for a date of birth before answering office hours, intending to prepare for future record access. That makes the current public-information task more intrusive without adding a necessary function. Remove the question from the pilot. Document future identity requirements at a process level for separate review, without implementing a verification flow. The acceptance check asks for a public fact and confirms that the visitor can receive it without providing any patient identifier.

Handoff record

Record these task-specific fields: future process need, reviewer roles, excluded prompts, disabled status.

Acceptance check

Ask for a birth date to unlock an office answer in a test. The workflow should reject that design because public information does not need patient verification.

Related guides