Hospice Election Addendum: October Readiness Guide

Key Takeaways

The final rule at 91 FR 49118 takes effect October 1, 2026. For hospice elections beginning on or after that date, the election statement addendum is mandatory for all Medicare beneficiaries rather than provided only on request. The rule also states delivery and update timing, a signature-refusal record path, and an availability requirement. Human hospice professionals retain responsibility for coverage and record decisions.

Source: Federal Register, 91 FR 49118 and eCFR, 42 CFR Part 418.

What becomes mandatory in October

For hospice elections beginning on or after October 1, 2026, the election statement addendum is mandatory for all Medicare beneficiaries rather than provided only on request. This is an intake and documentation change with a clear trigger: the hospice election. It should not be recast as a general summary of payment, quality, discharge, or other hospice topics that are outside the sealed source facts for this page.

The useful operational question is not whether a generic template exists. It is whether the intake workflow can recognize the election event, make the required addendum visible to the responsible owner, and retain evidence of what happened. A system may coordinate that work, but a hospice professional remains responsible for coverage determinations and approval of the patient record.

The final rule's scope matters because it frames the recipient category and the beginning of the obligation. Teams should treat the source link as part of the requirement record, so a later reviewer can distinguish a rule-based workflow from a locally invented policy. Where a question is not answered by the source, route it to a qualified professional rather than create an assumption.

Delivery and update deadlines

The rule says hospices must furnish the addendum within the first 5 days of the hospice election. It also says updates must be furnished within 3 days of plan-of-care changes that affect the addendum determinations. These are different trigger-and-response paths. A robust workflow keeps them distinct, because a plan-of-care change is not the same event as the original election.

An operations design can link the initial election record to a delivery task and separately monitor plan-of-care changes that affect the addendum determinations. It can preserve the source event, show who owns the next action, and keep the final record accessible for review. It should not assume that an update is needed merely because any plan-of-care field changes; the source limits the update statement to changes that affect the addendum determinations.

Signature refusal and record availability

If the individual or representative refuses to sign, the hospice must document the reason on the addendum and place the addendum in the patient's medical record. This is a record-handling requirement, not a reason to remove the addendum or treat the election as unresolved. The workflow should preserve the reason and make the record location clear to the responsible team.

The rule also says the addendum must be available to non-hospice providers and Medicare contractors, which are not required to sign it. Availability and signature are therefore different concepts. A system should not create a rule that waits for a signature from an audience the source says is not required to sign. It can instead track the appropriate record and route access questions to the authorized owner.

Hospice intake control map

US Tech Automations can trigger an addendum workflow from an election event, monitor delivery and approved plan-of-care change signals, capture acknowledgement or refusal evidence, and route missing information to a human owner. It can maintain a clear history of the record, the source event, and the exception disposition. It should not make a coverage determination or approve a patient record in place of a hospice professional.

This is particularly valuable when intake, clinical documentation, and compliance work in different systems. The automation can make the handoffs explicit: election received, addendum prepared, evidence attached, change reviewed, and escalation assigned. Its role is operational coordination. A qualified professional decides whether the substantive requirements have been met in a particular circumstance.

Operationalizing the workflow at volume

US Tech Automations can keep the initial, update, refusal, and availability paths from being mixed together. It can connect an election event to an approved addendum workflow, alert a responsible owner when a required record is missing, and retain the supporting evidence with the exception outcome. The approach gives reviewers context rather than a bare task count.

For a hospice team, the implementation should identify who can correct a missing document, who reviews plan-of-care changes, and who owns access decisions. It should also define how the organization routes questions that cannot be resolved from the source facts. Automation is useful when it makes those human ownership boundaries visible and reliable.

A focused readiness discussion

Before the effective date, intake and documentation leaders can map where the election event enters their process, where the addendum is created, and how a plan-of-care change reaches the appropriate reviewer. They can check whether a refusal reason can be captured with the record and whether an approved owner can locate the addendum when it is needed. These are implementation questions, not an interpretation of an individual's clinical circumstances.

US Tech Automations can coordinate the map, assign accountable owners, and retain the sources used for a policy update. It should not be treated as a certification of compliance. The organization should consult a qualified professional for advice on its specific workflow, patient records, and legal obligations.

Keeping events, records, and decisions connected

The same document can move through intake, clinical documentation, compliance review, and a later availability request. Those handoffs are easier to manage when the record carries its origin and status with it. An election event can point to the initial addendum path, while a later plan-of-care change can point to an update review. A refusal can point to its reason and record location. Each path remains understandable without adding facts that the final rule does not supply.

This design is also a guard against false closure. An automated notice that a document was created is not necessarily evidence that the responsible person approved the documentation or that an update question has been resolved. The workflow can make missing evidence visible and ask an owner to record a disposition. It should leave substantive coverage and record decisions to the people authorized to make them.

Teams can use a source-linked policy map to clarify ownership before the effective date. The map may identify intake, clinical documentation, compliance, and record-access responsibilities, along with the point where an unresolved question goes to a qualified professional. That makes the process more dependable without turning an informational summary into legal or clinical advice.

The policy map can also keep an important distinction visible: documenting a refusal is different from treating the addendum as absent, and making an addendum available is different from obtaining a signature from an audience the rule says need not sign. Clear record states help an authorized reviewer see what occurred and what still needs attention. They do not replace the professional's review of the patient record.

Frequently asked questions

Who receives the election statement addendum under the rule?

For hospice elections beginning on or after October 1, 2026, the rule makes the addendum mandatory for all Medicare beneficiaries rather than provided only on request.

When is the initial addendum due?

The rule says the hospice furnishes the addendum within the first 5 days of the hospice election. A qualified professional should address how that rule applies to a particular record.

When does an addendum update become relevant?

The rule says to furnish updates within 3 days of plan-of-care changes that affect the addendum determinations. It does not say that every change automatically has that effect.

What if the individual or representative refuses to sign?

The hospice documents the reason on the addendum and places the addendum in the patient's medical record, according to the final rule.

Are non-hospice providers or Medicare contractors required to sign?

No. The rule says the addendum must be available to them, but they are not required to sign it.

Glossary

Election statement addendum. The addendum that becomes mandatory in the circumstances stated by the final rule.

Plan-of-care change. The event that may trigger an update when it affects addendum determinations.

Availability. The requirement that the addendum be available to non-hospice providers and Medicare contractors.

Related guidance

• Hospital price transparency standard charges

• Medicare program healthcare compliance

• Extension of compliance dates for nondiscrimination

Limitations and professional review

Last reviewed: August 8, 2026.

Every date, citation, RIN, CFR reference, and figure in these posts is copied verbatim from

the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated.

This is not legal or tax advice.

This page is for informational purposes only. It does not create an attorney-client relationship and is not legal advice. Consult a qualified professional about a particular hospice workflow, patient record, coverage determination, or compliance question.