Medicare ABNs: Provider Documentation and Modifier Guide

This guide addresses the general CMS-R-131 workflow for Original Medicare. It does not replace the special notices used in every institutional setting, and it does not govern Medicare Advantage plan notices. CMS instructions, the Medicare Claims Processing Manual, the applicable benefit rules, and the patient's circumstances control. The information is current through October 7, 2026 and is educational, not individualized legal advice.

ABN workflow at a glance

1. Decide whether an ABN is the right notice

CMS describes the ABN as an advance notice used by providers, physicians, practitioners, suppliers, independent laboratories, home health agencies, and hospices in specified Original Medicare situations when payment is expected to be denied. The first control is scope. Confirm that the patient is enrolled in Original Medicare for the service, that the expected denial basis is one for which the ABN process applies, and that another setting-specific notice is not required.

Do not use an ABN as a universal financial-consent form. It should not be used to shift liability through a vague statement that Medicare may not pay. CMS distinguishes mandatory notice situations from voluntary notice for items that Medicare never covers or excludes by law. It also limits delivery in emergency or urgent circumstances when the beneficiary cannot make an informed choice. Document the reason for the notice-type decision before asking for a signature.

2. Complete CMS-R-131 specifically

Use the current CMS form and instructions. The item or service description should be understandable to the beneficiary and specific enough to connect the notice to the later claim. The reason should explain the expected Medicare issue in plain language instead of using only internal codes. The estimated cost should be a good-faith estimate for the item or service at issue, not an open-ended statement that the patient may owe any amount.

• Match the beneficiary name to the registration and Medicare record.
• Identify the notifier clearly and consistently with the billing or furnishing entity.
• Describe the item or service in terms a patient can recognize.
• State the expected denial reason with claim-specific facts.
• Enter a reasonable good-faith cost estimate or explain the permitted estimation method.
• Leave the beneficiary's option selection for the beneficiary or authorized representative.
• Complete additional information only when it helps explain the notice; do not obscure required language.
• Give the beneficiary a legible copy and retain the provider copy in the record.

3. Deliver notice before the patient is committed

An ABN is an advance decision document. Deliver it before the item or service and early enough for the beneficiary to consider the alternatives. A notice presented after treatment, after sedation, at discharge, or when cancellation is no longer realistic may not support a valid transfer of financial liability. Staff should be able to explain the item, expected denial reason, estimated cost, and each option without pressuring the patient to choose a preferred answer.

If a representative signs, preserve the basis for representative authority and the circumstances that prevented or supported the beneficiary's own participation. For remote delivery, follow CMS requirements for delivery, review, signature, and copy retention. Do not backdate the notice or recreate a signature after a denial.

4. Respect the beneficiary's three choices

1. The beneficiary may want the item or service and ask the provider to submit a claim to Medicare, preserving a Medicare decision and appeal path.
2. The beneficiary may want the item or service but choose not to have a Medicare claim submitted, accepting the payment arrangement described on the notice.
3. The beneficiary may decline the item or service.

The intake note should not contradict the checked option. If the patient selected submission to Medicare, the billing workflow should not suppress the claim merely because staff expects denial. If the patient declined the service, the clinical and scheduling record should reflect that outcome. Changes require a contemporaneous, transparent record rather than silent alteration of the signed notice.

5. Match the modifier to the actual facts

These modifiers are not interchangeable denial tools. The claim must reflect the service, coverage rationale, and notice actually provided. A GA modifier does not cure an untimely, generic, coerced, incomplete, or otherwise invalid ABN. A GZ modifier should not be replaced with GA after the fact. GX and GY often appear together in voluntary-notice situations, but the exact claim depends on CMS instructions and the service.

6. Audit the notice-to-claim chain

• Original Medicare enrollment and notice jurisdiction confirmed.
• Expected denial basis documented before service.
• Current CMS-R-131 used without prohibited alteration.
• Service, reason, and estimate are specific and understandable.
• Delivery occurred before the service with meaningful choice.
• Patient or representative selection and signature are complete.
• Copy delivery and representative authority are documented.
• Claim submission follows the selected option.
• GA, GX, GY, or GZ use matches the actual coverage and notice facts.
• Patient statements, collections, and appeal records remain consistent with the ABN.

Common failure patterns

Related Millennova Legal resources

See Millennova Legal's patient and client intake services, Original Medicare claim appeals guide, HIPAA documentation guide, and No Surprises Act notice-and-consent guide.

Primary CMS sources