Skip to main content

Care coordination guide

Closing the care follow-up gap

A clinical decision becomes operational work when someone knows what to do, when to do it and how to establish that it is resolved.

The gap often appears after an otherwise useful consultation. The practitioner has explained the next steps. The note records them. A team member sends a message. At the next encounter, someone still has to reconstruct which actions happened and which did not.

The first question is whether the practice has a shared account of the work. A clear account connects the original decision with its owner, timing, review requirements and outcome. Software can help organize that account, but the team needs to agree what the states and responsibilities mean.

This guide concerns operational coordination. It does not recommend clinical treatment or replace a practice's professional procedures.

Separate the decision, the communication and the outcome

These events answer different questions. The decision establishes the reviewed next step. A communication explains or requests something. The outcome records what actually happened. Treating them as one event can make an open action disappear too early.

For example, a team may send an instruction asking a patient to contact the practice about an outstanding item. The communication can be marked as accepted by the sending service. That status does not establish that the patient received it, responded or completed the original next step.

Keep a separate record for the underlying action. The practice should define the evidence needed to close it and who can make that determination. An operational record can then remain open without misrepresenting the communication history.

Describe an action well enough for another person to take it over

A task such as "follow up" gives the next team member very little context. A useful action should preserve the following information in a form the authorized team can understand.

  1. The source decision

    What was reviewed or agreed, and which encounter or approved instruction explains it?

  2. The next step

    What specific work must occur, and what is outside the person's responsibility?

  3. The owner

    Which person or role owns the next move? If ownership changes, the handoff should be visible.

  4. The timing

    When is the action due, or when should it be reviewed again? Timing should follow the appropriate practitioner instruction or practice procedure.

  5. The completion evidence

    What information would allow an authorized person to mark the action as resolved?

  6. The exception route

    Who should review the item when it is delayed, blocked or associated with information requiring clinical attention?

The purpose of these details is continuity. A different authorized team member should be able to understand the current position without guessing what the original owner meant.

Agree what each status means

Status labels are useful only when the team shares their meaning. A proposed action is waiting for a decision. Approved work has the required authority. In-progress work has an owner taking the next step. A blocked item needs something before it can move. Completed work has the evidence the practice requires.

A due date passing may make an item overdue, but it does not explain why. The next useful action may be an administrative check, clarification of responsibility or clinical review. The practice should define the escalation route rather than treating every overdue item as the same clinical event.

Cancellation also deserves a reason. A practitioner may change the plan, the patient may decline the next step or the item may have been duplicated. Those situations should remain distinguishable where they matter to the care record.

Make the handoff and the uncertainty visible

Consider a fictional practice in which a coordinator is waiting for confirmation that an agreed next step occurred. The coordinator leaves for the day, and another team member takes over. A useful record shows the source instruction, the last contact, the current owner and the outstanding question.

It should also show uncertainty honestly. If an outbound communication has an unclear outcome, repeating it immediately can create confusion. First establish what is known about the earlier attempt and who is responsible for resolving the uncertainty.

The same principle applies to incomplete information from the patient. A response can be recorded as a response without becoming a verified clinical conclusion. Information that requires interpretation should reach the appropriate practitioner or authorized reviewer.

Test the process at the next encounter

Before a follow-up visit, ask whether the practitioner can quickly understand the prior plan and the interval that followed it. Which actions were completed? Which remain unresolved? What changed? Which decisions need to be revisited?

If answering those questions still requires several people to search separate inboxes, the workflow has a visibility problem worth examining. Begin with one recurring process and observe the handoffs. Record the manual effort, unresolved items and reasons for delay before deciding which part to automate.

A useful evaluation can measure time spent reconstructing context, completeness of approved action capture and the time before an overdue item becomes visible. These are operational measures to collect. They should not be presented as improved results until the practice has actual evidence.

How this relates to Pexify

Pexify is being developed around this connection between the clinical decision, reviewed plan and work between visits. The intended Patient Journey and care-plan model give those activities a shared context. Capabilities and deployment scope remain subject to confirmation.

Talk to Pexify

Please use business information and fictional examples when contacting the team.

Back to insights