Follow-up Care

Care tasks record the task description and due date against patient and assigned clinician. Completion date describes completion when the task reaches that outcome. Status distinguishes Open, in progress, Completed, Escalated and Cancelled. Follow-up Coordinator can therefore separate work still needing action from work completed or deliberately stopped, without assuming that encounter completion finishes the patient’s continuing care.

For a rehearsal, create a follow-up after Milo’s visit to check the agreed care outcome. Select the patient context from the encounter and assign a clinician through staff records. Write a useful task description and enter due date before submission. The workflow rejects missing task text or due information instead of creating an ambiguous request for someone to interpret later.

• Assigned responsibility. Assigned clinician resolves to staff records, whose linked user account must resolve. The follow-up workflow confirms both the linked patient and assigned clinician before routing the task. A typed name outside that reference path is insufficient.
• Working lifecycle. Open describes work available to start, and in progress describes work being performed. The workflow re-confirms identity before recording the task as Open. Completion requires the relevant completion information, including completion date, rather than a status change by itself.
• Exceptions. Escalated and Cancelled remain distinct routes. An escalated task still requires attention; a cancelled task should not be counted as completed care. Agree how staff explain the escalation using the task context and how the receiving coordinator finds it.

Agree who may assign work, who performs it and who handles an Escalated task. Set a convention for descriptions that makes the expected action clear to the receiving clinician. Agree how the receiving clinician checks the assigned workload and how the coordinator reviews overdue work before releasing the handoff.

Check the staff-to-user mapping used by personal task queues. My care tasks should resolve the logged-in person before filtering assigned clinician, while continuing to enforce the underlying patient access. A filter makes a workload easier to read, while the underlying patient access remains governed by the effective clinical assignment.

Choose how the practice reviews due date and completion date. A due-date comparison can identify work needing attention, but it cannot establish that the owner has contacted the client or delivered the clinical action. Require the actual completion information for the configured Completed route and rehearse what happens when it is absent.

Create Milo’s task in Open with a resolved patient, complete description and permitted assignee. Let the assigned clinician move it to in progress, perform the intended follow-up and complete it with completion date. Inspect the resulting record from the coordinator’s queue and the clinician’s personal queue.

Repeat without a due date and check that the creation command is rejected. Try completing the task without a completion date and verify that the workflow blocks the incomplete outcome. Then rehearse an Escalated route so the receiving coordinator can find the unresolved work rather than mistaking its disappearance from a personal view for completion.

Keep the task’s patient reference in mind when the linked encounter has already become Completed or its charge has become Invoiced. Those outcomes concern the visit and billing. Care tasks retain its own lifecycle, allowing Follow-up Coordinator to inspect the remaining clinical work on its actual evidence.

• Open Care Tasks — Review Open, in progress and Escalated tasks with assignee and due information.
• My care tasks — Focus the permitted clinician’s workload using the resolved assigned clinician identity.

Use follow-up care after admission and clinical review. Inspect the completion questions in reports.