How to approach: Set a fall incident follow-up note with the care manager
In the fall incident follow-up workflow, a client fall reported by a caregiver arrives before anyone confirms the client, the period, or the responsible queue. The fall incident follow-up intake note separates a new request from a correction to an earlier record. For fall incident follow-up, the queue entry names the client, the period, the requester, and the person who can close the question. Review pass 1.1: the home care scheduler files the fall incident follow-up evidence.
The fall incident follow-up working file joins the incident report, the caregiver statement, the care manager review, and the follow-up date on one case reference so the decision can be rebuilt. A fall incident follow-up case without a named owner is treated as unassigned, even when a document is already attached. The fall incident follow-up case begins when a client fall reported by a caregiver reaches the queue and stays open until the care manager records a decision in the incident register. Review pass 1.2: the home care scheduler files the fall incident follow-up evidence.
Confirm the incident report and the caregiver statement
The fall incident follow-up review compares caregiver statement with follow-up date and lists the records that cannot be joined. Every fall incident follow-up value is linked to the field in the incident register that supports it. A fall incident follow-up status update points to a verifiable event in the incident register, not to a feeling about progress. The fall incident follow-up evidence joins the incident report, the caregiver statement, the care manager review, and the follow-up date on one case reference. Review pass 2.1: the home care scheduler files the fall incident follow-up evidence.
A null fall incident follow-up result is published beside a positive one, using the same definitions and exclusions. A fall incident follow-up note that cannot be reproduced from follow-up date is returned to the preparer. The fall incident follow-up reviewer can trace caregiver statement to the exact page or field that produced it. Each fall incident follow-up artifact carries a version label and the time it was exported from the incident register. Review pass 2.2: the home care scheduler files the fall incident follow-up evidence.
Set the decision boundary for the care manager
The care manager approves a fall incident follow-up exception, while the preparer records the evidence and the time of the handoff. The fall incident follow-up template blocks a close when the approver and the preparer are the same person. The care manager owns the fall incident follow-up decision; the assistant may prepare, compare, and route but not approve. A standing instruction for fall incident follow-up needs an end date, and the care manager confirms it is still current. Review pass 3.1: the home care scheduler files the fall incident follow-up evidence.
The fall incident follow-up authority note names the care manager as approver and records any delegation with its end date. When fall incident follow-up changes the incident register, the preparer and the approver remain separate roles. The fall incident follow-up authority limit is written into the template with its scope, amount, and expiry. The fall incident follow-up delegation note names the deputy, the period, and the record that ends the delegation. Review pass 3.2: the home care scheduler files the fall incident follow-up evidence.
Record and release the exception
When the incident closes without a care manager review, the fall incident follow-up case pauses until the incident register shows a corrected value and a named releaser. The fall incident follow-up exception note names the condition, the releaser, and the time work resumed. When the incident closes without a care manager review, the dependent action stops and the conflict is logged in the incident register. Review pass 4.1: the home care scheduler files the fall incident follow-up evidence.
The fall incident follow-up queue marks a paused case with the reason it stopped and the person who can release it. A fall incident follow-up exception that touches the follow-up date record requires a new check of the incident register before release. The failed fall incident follow-up attempt stays with the correction so the cause remains visible. The fall incident follow-up queue marks the exception with its age so a second occurrence is easy to find. Review pass 4.2: the home care scheduler files the fall incident follow-up evidence.
Review the fall incident follow-up pattern
The fall incident follow-up review ends with one change, one owner, and a date to re-measure the same population. The fall incident follow-up review reports a null result as clearly as a positive one. The fall incident follow-up review ends with one testable change, one owner, and a re-measure date. The fall incident follow-up review separates ordinary, reopened, missing-evidence, and cross-owner cases. Review pass 5.1: the home care scheduler files the fall incident follow-up evidence.
A fall incident follow-up exception that repeats becomes a reason code so the queue can show the pattern without retelling it. Open fall incident follow-up items are reported by age and dependency because a stable total can hide an aging tail. A fall incident follow-up pattern is described before it is called a trend, and outliers are explained at case level. Review pass 5.2: the home care scheduler files the fall incident follow-up evidence.
