Direct answer
Can an AWV team prefill the health risk assessment from the EHR?
An AWV team can assemble authorized chart and scheduling information for staff review before a visit, but it should not silently turn that information into the patient's current health risk assessment. CMS calls for patient self-reported information and says the patient or practitioner may update the assessment before or during the AWV. Keep source, date and missing answers visible; let accountable staff reconcile them with the patient.
Authorized chart context
Patient-reported HRA
Staff reconciliation
Visit team review
Make two lanes rather than one prefilled questionnaire
CMS describes the AWV health risk assessment as patient self-reported information that may be updated before or during the visit. Its minimum elements include a health-status self-assessment, psychosocial and behavioral risks, and functional ability and safety. Existing chart information can help a team prepare, but it cannot speak for how the patient feels or functions today.
Put authorized historical facts in a chart-context lane and the patient's current responses in an HRA lane. Show the provenance and date beside each item. A blank patient response remains blank, even when an older note looks similar. This is a workflow design principle, not a claim that CMS prescribes a particular software layout.
- Chart context: last visit date, documented providers, medication-list timestamp and known scheduling details, subject to the organization's access rules.
- Patient response: current self-assessed health, activity, mood and safety questions in the organization's approved HRA process.
- Reconciliation: staff asks about disagreement, missing information and accessibility or language support rather than selecting an answer on the patient's behalf.
A small, testable work-queue example
Suppose an authorized scheduling feed shows an upcoming AWV, but the medication list was last reviewed months ago and the patient's HRA has not been returned. A safe queue might say: confirm the correct patient and appointment, invite the patient to complete the approved HRA, and ask staff to review the medication list at the visit. It should not copy the old medication list into a current patient attestation or label the HRA complete.
The example contains no real patient information and does not determine coverage, clinical priority or a billing code. Before implementing such a rule, the organization must decide what data use is authorized, who owns each exception, when information becomes stale and which communication channel is permitted.
Review the four failure points before outreach
- Identity: match the appointment and source record to the right person; route uncertain matches to staff rather than guessing. ONC's SAFER patient-identification guidance treats reliable matching as a safety practice.
- Freshness: show the chart item's source and date. An old list may be useful context but is not a confirmed current answer.
- Access: restrict the queue to approved roles and fields; HHS minimum-necessary guidance calls for defining who needs protected information and under what conditions.
- Communication: use the organization's approved language, accessibility, consent and contact-preference process. Never infer a person's preferred channel from a record alone.
Measure the workflow without claiming a clinical result
A pilot can count candidate records reviewed by staff, HRAs returned through approved channels, unresolved identity exceptions, stale-source flags and the time an exception waits for an owner. Define the denominator, window and data source for every count. Do not turn those process measures into claims about patient outcomes, completed AWVs, reimbursement or reduced staff time without separate evidence.
Swasth is Synodha's EHR-agnostic AWV preparation and outreach workflow agent. Its intended role is to organize authorized data and staff-review queues above existing systems of record, not to fill in a patient's answers, decide eligibility, send unapproved messages or replace a clinician. Data access and actions must be defined with each enterprise.
Limits and next step
This guide is an operational evaluation aid, not clinical, billing, legal or compliance advice. CMS requirements and a healthcare organization's policies may change. Confirm the current CMS AWV components and the organization's HRA workflow before configuration; do not treat any vendor example as proof of compliance or endorsement.
How this guide was prepared
Synodha's editorial team prepared this guide from the official sources listed below and checked product statements against the current documented enterprise scope. No independent clinical, legal, compliance, customer, or EHR-vendor review is claimed. This guide is an evaluation aid, not clinical, legal, compliance, billing, or reimbursement advice.
Last reviewed September 27, 2026. Recheck the linked sources and the healthcare organization's current instructions before acting on health information.
Primary sources and scope
These sources establish the current program and health IT context used for this checklist. They do not endorse Synodha or establish that any product or deployment is compliant.
Related Synodha resources
Frequently asked questions
Can we complete the AWV HRA from existing chart data?
No. Chart data can help staff prepare, but CMS calls for patient self-reported HRA information. Preserve the patient's own current response and reconcile it with chart context through the organization's approved process.
Must the patient finish the HRA before the visit?
CMS says the patient or practitioner may update the HRA before or during the AWV. Follow the organization's current workflow and confirm the applicable CMS requirements.
What if the patient's answer differs from the chart?
Keep both sources and their dates visible, then route the difference to accountable staff. Do not silently overwrite a patient response or treat an older record as today's attestation.
Does Swasth decide AWV eligibility or reimbursement?
No. Swasth is positioned to prepare authorized work queues for human review. The healthcare organization owns clinical, coverage, documentation and billing decisions; no outcome or reimbursement is guaranteed.