Hospice Election and Revocation Statement Processing Form
Track hospice election and revocation details in one compliant intake form, with patient, representative, and signature fields organized for clear Medicare processing and audit trail support.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Hospice Care · Home Health · Palliative Care · Senior Care
Overview
This Hospice Election and Revocation Statement Processing Form template organizes the core information needed to record a hospice election or a hospice revocation in a structured workflow. It includes submission type, effective date, patient identifiers, representative authority, election acknowledgments, revocation details, and signature capture so staff can process the record without chasing missing information.
Use this template when your team needs a clear intake path for Medicare hospice election statements, revocations, or related acknowledgments that must be documented in a consistent way. The structure supports conditional logic, so election-only and revocation-only fields can appear only when relevant. That makes the form easier to complete and reduces the chance of collecting unnecessary PII.
Do not use this template as a general hospice admission packet, clinical assessment, or care plan form. It is also not the right fit if you need broad patient history, symptom tracking, or unrelated consent forms. Keep the scope narrow: document the election or revocation event, who signed, what was acknowledged, and any authority documentation needed when a representative acts on the patient’s behalf.
Standards & compliance context
- Collect only the minimum necessary PII needed to process the hospice election or revocation, consistent with data minimization principles.
- Use clear consent and disclosure language so the signer understands what information is being submitted and how it will be used.
- If an authorized representative signs, retain the authority documentation in the record to support the signature trail.
- Structure the form so required fields are explicit and the submission can be audited later for who signed, when, and under which submission type.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Type
This section determines whether the record follows the election path or the revocation path, which controls the rest of the form.
- Submission Type
-
Effective Date
Enter the date the election or revocation becomes effective.
-
Reason for Submission
Briefly describe the reason for this election or revocation. Do not include unnecessary medical details.
Patient Information
This section captures the minimum identifying details needed to match the submission to the correct beneficiary record.
- Patient Full Name
-
Date of Birth
Optional unless needed to resolve a duplicate record or verify identity.
-
Medicare Beneficiary Identifier (MBI)
Collect only if needed for billing or eligibility verification.
- Patient Phone Number
Representative or Authorized Person
This section documents who is signing on the patient’s behalf and why that person is allowed to do so.
- Is a representative or authorized person completing this form?
- Representative Name
- Relationship to Patient
-
Authority Documentation
Upload supporting documentation only if required by your organization.
Hospice Election Details
This section records the election acknowledgment and related details needed to process a hospice benefit election.
-
I acknowledge that I am electing hospice coverage and understand the scope of the hospice benefit.
This acknowledgment confirms the election of hospice services and understanding that hospice coverage is limited to hospice-related care under the applicable Medicare benefit.
- Primary Hospice Provider
-
Attending Physician Name
Optional unless required for your internal workflow.
- Scope of Benefit Acknowledgment
- Questions or Clarifications
Hospice Revocation Details
This section captures the revocation acknowledgment and any notes explaining the change in hospice status.
- I understand that I am revoking my hospice election and that hospice coverage will end on the effective date entered above.
- Reason for Revocation
-
Additional Comments
Provide only information necessary for processing and audit trail purposes.
Consent, Disclosure, and Signature
This section creates the final consent and signature record, including what was disclosed and when the submission was signed.
-
Consent to Process Personal Information
I consent to the collection and processing of the personal information in this form for hospice election or revocation processing, recordkeeping, and audit trail purposes.
- I acknowledge that the information provided will be used only for hospice benefit processing and related compliance purposes.
- Signature
- Signature Date
How to use this template
- Set the submission type first so the form can show the correct election or revocation fields through conditional logic.
- Enter the patient’s identifying details using structured fields, and collect only the minimum necessary PII needed to match the record.
- If a representative is signing, mark that option and attach the authority documentation before accepting the submission.
- Capture the hospice election or revocation acknowledgments, the effective date, and any required provider or physician details in the designated fields.
- Review the completed record for missing signature data, unclear authority, or inconsistent dates, then route it to the team member who finalizes the hospice election file.
Best practices
- Use a date picker for the effective date and signature date so staff do not enter ambiguous free text.
- Make representative fields conditional so they appear only when has_representative is selected.
- Mark required versus optional fields clearly, and keep optional comments limited to information that will actually be used.
- Collect only the identifiers needed for processing and avoid adding unrelated clinical or demographic fields.
- Include a plain-language disclosure line that tells the signer what happens after submission and who will review it.
- Require authority documentation whenever someone signs as an authorized representative, and do not accept the submission without it.
- Use validation on Medicare beneficiary ID and phone fields to reduce rework from formatting errors.
- Keep election and revocation paths separate in the workflow so staff do not mix acknowledgments from different submission types.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this form be used?
Use this form when a patient is electing hospice benefits, revoking a prior hospice election, or documenting a related change that affects Medicare hospice processing. It is designed to capture the minimum necessary details for that event, not to replace the full clinical intake record. If the patient is only asking general questions and has not made an election or revocation, this form is usually premature.
Can this form be used for both election and revocation?
Yes. The Submission Type section lets you route the record to the correct path and show only the fields that apply. Use conditional logic so election-specific acknowledgments do not appear on a revocation-only submission, and vice versa. That keeps the form shorter and reduces confusion for staff and patients.
Who should complete this form?
It is typically completed by hospice admissions staff, case managers, or another authorized intake role, with the patient or authorized representative providing the required acknowledgments and signature. If a representative signs, the form should capture the authority documentation that supports that action. The goal is to make the signer and their authority clear in the record.
What patient information should be collected?
Collect only the identifiers needed to match the election or revocation to the correct beneficiary record, such as name, date of birth, Medicare beneficiary ID, and a contact phone number if your workflow uses it. Avoid adding fields that are not needed for processing, such as unrelated clinical history or extra demographic details. This supports data minimization and reduces rework.
How does this form support compliance and audit trail needs?
The form creates a structured record of the election or revocation acknowledgment, the effective date, the signer, and the disclosure language shown to the patient. That makes it easier to prove what was submitted, when it was signed, and who authorized it. If your process requires it, keep the completed submission with an audit trail in your records system.
What are the most common mistakes when using this template?
Common mistakes include leaving the submission type unclear, collecting too many optional details, and failing to document representative authority when someone signs on the patient’s behalf. Another frequent issue is missing the signature date or using free-text fields where a date picker or structured field would be clearer. Those gaps can slow processing and create avoidable follow-up.
Can this template be customized for different hospice workflows?
Yes. You can adjust the field labels, add conditional logic for organization-specific acknowledgments, and tailor the provider or physician fields to match your intake process. Keep the core structure intact so the form still captures the election or revocation, the signer, and the disclosure language. If you add fields, confirm they are truly needed before collecting them.
How should this form be rolled out across a hospice team?
Start by assigning one owner for intake review, then define who enters the submission, who verifies authority documentation, and who finalizes the record. Test the form with a few real scenarios, including patient signing, representative signing, election, and revocation. After that, train staff on which fields are required and what happens after submission so the workflow is consistent.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
Mobile capabilities help local government field teams stay connected, access SOPs offline, and boost productivity anywhere.
-
See how MangoApps Community Suite improves customer experience through visual communication, onboarding, collaboration, and knowledge management in one...
-
MangoApps is named a Leader in the IDC MarketScape for Content Management in Authenticated Digital Workspaces. See what sets our intranet platform apart.
Ready to use this template?
Get started with MangoApps and use Hospice Election and Revocation Statement Processing Form with your team — pricing built for small business.
