Make the next step someone’s responsibility
Care coordination becomes tangible at a handoff. Someone has a question, a plan changes, or a service becomes necessary. The practical issue is whether the next person knows what is needed and can respond.
A shared record helps only when the surrounding work is clear. Who keeps the plan current? Who follows an unresolved question? How does a person or caregiver correct information? Those are useful starting questions for health systems, home care teams, and community partners building a shared approach.
Distinguish a framework from a delivery model
The AHRQ Care Coordination Measures Atlas (opens in a new tab) is a reference for examining coordination, with perspectives that include patients, professionals, and systems. It helps organize measurement; it is not a specific service that an organization can enroll in.
WHO’s ICOPE handbook (opens in a new tab), second edition published September 22, 2025, offers guidance for person-centered assessment and care pathways in primary and community settings. It connects assessment with personalized planning and implementation.
The CMS GUIDE Model (opens in a new tab) is a different kind of model: a defined test of dementia care delivery and payment with requirements for participants. These resources answer different questions. A measurement framework, a practice pathway, and a payment model should retain their own names and boundaries.
Follow one handoff all the way through
Consider a hypothetical transition from a hospital to home. A family receives information about a community service. The hospital records that the referral was sent, but the family is unsure whether they should call or wait. The community organization receives an incomplete request and cannot arrange the first conversation.
Counting that referral as completed would hide the unfinished work. A more informative local record would distinguish an invitation sent, a referral received, a conversation held, and an agreed next step. It would also identify a person responsible for resolving missing information.
This is an example of how to design a review, not a claim about an existing customer or evidence that a particular referral system reduces hospital use.
Write plans people can use
We recommend keeping the operational plan focused on information the next person needs: the person’s stated goal, the agreed activity, who owns it, and when to review it. Where a task depends on an outside organization, record that dependency instead of implying that the service is already arranged.
Give the person receiving care and their chosen supporters a practical way to ask questions or identify an error. A plan should not become authoritative merely because it appears in software. For organizations sharing information, permissions and responsibility need to be worked out alongside the workflow.
A simple local exercise is to ask two people involved in the same handoff to describe the next step independently. Different answers reveal a coordination issue worth resolving before adding more technology.
Evaluate the whole experience
A service team may want to review response times and incomplete handoffs. Families may care more about repeating their story or knowing who can help. Both views can inform improvement, but one should not be substituted for the other.
For GUIDE-related work, check current CMS requirements (opens in a new tab) rather than relying on a general description of coordinated care. An organization’s role in a software workflow does not by itself establish that it is an approved model participant or partner.
genusConnect’s research pages connect these sources to questions about shared care. The practical proposition is that clear roles and usable information deserve deliberate design. Whether a particular implementation improves experience, service use, or health outcomes must be examined with a study or evaluation suited to that claim.