Choose the workflow
Identify the specialty, encounter type, documentation requirements, and current burden. Check how the proposed tool captures information and integrates with the existing record.

Clinical operations, technology & privacy teams
Documentation support needs to be evaluated by the time and attention it saves after review—not simply by how quickly it produces a draft.
Start with a business question. No records or commitment required.
FROM THE QUESTION TO THE EVIDENCE
Identify the specialty, encounter type, documentation requirements, and current burden. Check how the proposed tool captures information and integrates with the existing record.
Review patient notice and consent, retention, access, vendor terms, data uses, and the responsibilities of the organization. Specific privacy and security requirements need appropriate review.
Evaluate drafts for omissions and errors, clinician editing time, and final-note quality. Clinicians must review and approve documentation; automated output is not a substitute for professional judgment.
MAKE THE FIRST STEP SPECIFIC
A high-level summary is enough to begin. The team can help clarify the question before requesting detailed information.
BEFORE YOU CONTINUE
No. The workflow should assign qualified clinicians responsibility for checking, correcting, and approving the record. An AI-generated draft can contain errors or omissions.
Those outcomes should not be assumed. A pilot should measure the specific workflow, review time, documentation quality, and implementation costs before drawing conclusions.
YOUR SITUATION SETS THE SCOPE
Tell David what prompted the question, what needs to keep working, and any timing that matters.