Hospice Incident Reports, Adverse Events, and Missed Visit Documentation

When an Incident Report Is Required

Not every unexpected event in hospice bereavement care triggers an incident report. The threshold is an event that caused or could have caused harm to a patient, family member, or staff member, or that represents a deviation from the plan of care or agency policy.

In bereavement-specific contexts, reportable incidents include:

• A bereaved family member disclosing suicidal ideation during a follow-up call where the bereavement coordinator did not activate the escalation protocol
• A HIPAA violation — disclosing the deceased patient's medical information to a family member who was not authorized to receive it
• A misdirected mailing (condolence letter sent to the wrong family, or sent to a family who explicitly declined bereavement services)
• A missed scheduled visit or call for a high-risk (BRAT Level 4 or 5) family that resulted in a gap of more than 30 days without any documented contact
• A volunteer bereavement call where the volunteer exceeded their scope of practice by providing clinical advice or making a referral without coordinator approval

The incident report is an internal document. It is not part of the clinical record. Its purpose is to capture the event, identify contributing factors, and drive corrective action through the agency's QAPI process.

How to Document the Incident

Effective incident reporting in hospice follows an objective, chronological format:

What happened. Describe the event in factual, observable terms. "On [date] at [time], a scheduled 6-month bereavement check-in call for [family identifier] was not completed as planned. The call was assigned to [staff/volunteer name] and was due by [date]."

What was supposed to happen. Reference the specific policy, care plan, or protocol that was not followed. "Per the individualized bereavement plan of care, Level 4 families receive telephone contact at minimum monthly intervals."

What actually occurred. Document the sequence of events that led to the deviation. "The assigned bereavement coordinator was on leave from [date] to [date]. No reassignment of the caseload was completed. The family's chart was not flagged for follow-up by the covering staff."

What harm resulted or could have resulted. "The family went 47 days without clinical contact during a period when the 6-month milestone frequently triggers acute grief recurrence. No adverse outcome was identified upon subsequent contact on [date]."

Immediate corrective action. "The bereavement coordinator completed the call on [date]. The family reported manageable grief symptoms. A follow-up call was scheduled for [date] to resume the standard cadence."

Do not include opinions, blame attributions, or emotional commentary. The phrase "this should never have happened" has no place in an incident report. Neither does speculation about what the family "might have" experienced during the gap.

Missed Visit Documentation

Hospice agencies must maintain a structured process for missed visits that satisfies both the Medicare Conditions of Participation and internal quality standards. When a scheduled bereavement contact cannot be executed, the clinician must document:

• The date and type of the planned contact (phone call, home visit, mailing)
• The reason it did not occur (staff illness, family not reachable, scheduling error, caseload conflict)
• Notification of the clinical manager and bereavement coordinator (with dates and times)
• The rescheduled contact date
• Whether the Medical Director was notified per the agency's daily missed visit reporting protocol

Bereavement missed visits are particularly risky because the families are not calling the agency to complain. A patient on active service who misses a nursing visit will usually call. A bereaved widow who does not receive her 6-month check-in call simply does not hear from the hospice — and the gap goes unnoticed until a chart audit or survey reveals it.

The systemic fix is automated caseload tracking that flags approaching and overdue contacts. Manual tracking using spreadsheets and paper calendars creates exactly the kind of human-error gap that missed-visit incidents exploit.

Adverse Event Reporting and Regulatory Obligations

True adverse events in bereavement care are uncommon but have serious consequences. A bereaved family member who attempts suicide after a missed high-risk contact. A HIPAA breach that results in a family filing a complaint with the Office for Civil Rights. A volunteer who crosses a boundary in a way that causes emotional harm.

Adverse events trigger multiple reporting tracks:

• The internal incident report (described above)
• The QAPI root-cause analysis
• State reporting if required by the state's hospice licensure rules (requirements vary significantly by state)
• For a breach of unsecured PHI, notify affected individuals without unreasonable delay and no later than 60 days after discovery, regardless of the number affected. Notify the HHS Secretary through OCR within 60 days for breaches affecting 500 or more individuals; for breaches affecting fewer than 500, report within 60 days after the end of the calendar year in which the breach was discovered.
• Follow the accreditor's event policy. The Joint Commission expects accredited organizations to identify and investigate sentinel events, but self-reporting them to TJC is voluntary.

The Hospice Worker's Family Bereavement Support Toolkit includes incident documentation frameworks and escalation decision trees that help agencies trace from the initial event through root-cause analysis and corrective action — the full chain that surveyors and accreditors expect to see when they ask "show me your last three incident reports and what you did about them."

Clinical Error vs. System Error

When an incident report is filed, the instinct is to identify who made the mistake. Effective QAPI analysis asks a different question: what system allowed the mistake to happen?

A bereavement coordinator who misses a high-risk contact because they were carrying 75 active families with no backup coverage did not commit a clinical error. The agency committed a system error by setting an unsustainable caseload ratio. The corrective action is not retraining the coordinator — it is adjusting staffing, establishing cross-coverage protocols, or implementing automated tracking that catches gaps before they become incidents.