Resolving encounter alerts

The Alerts panel surfaces things worth fixing before you submit — a missing Medicare number, a missing postcode, plus anything the form flags as you fill it in.

The rail shows the Alerts tool as a highlighted tile with a count of the items to review – orange, or red when any is critical. The count falls as you resolve each issue, and clears when there's nothing left to flag.

Categories

• Patient — issues with the customer record (identifiers, address). Usually fixed by editing the customer.
• Encounter — issues with what's been entered on the form itself, raised live as you fill it in.
• Site — issues with the site's configuration (an integration that needs reconnecting, a missing setting). Usually fixed by an admin, not at the chair.

What gets checked

The current Patient alerts only surface for services that submit vaccinations to AIR — they don't apply to encounters that won't lead to an AIR submission or a PPA claim.

• Medicare number missing. Required for PPA claims, and used to confirm the patient's identity with AIR. Fix by editing the customer.
• Postcode missing. Required for Special Medicare Number (SMN) claims. Fix by editing the customer's address.

How to clear an alert

• Patient alerts link out to the customer edit sheet.
• Encounter alerts clear when the underlying field is corrected.
• Site alerts link to the relevant settings page. Flag to an admin if you don't have permission to act on one.

You can submit the encounter with alerts still open — they're guidance, not gates — but open alerts often turn into claim or AIR rejections later, so it's worth clearing them now.