Continuity-of-Care Plan¶
Service continuity mechanism — instantiates Continuity Preservation
Keeps a patient's treatment, records, and responsibility unbroken as they move between providers or settings — by naming who owns the handoff and confirming afterward that nothing was dropped.
A continuity-of-care plan is a structured artifact and protocol that preserves one specific person's treatment, information, and support as they cross a care boundary — hospital to home, one provider to another, one coverage state to another. It does this by explicitly assigning who is responsible for the handoff, carrying the clinical picture forward, telling the patient what happens next and whom to call, and verifying afterward that no gap opened. Its defining idea is that the continuity at stake here is a single individual's care not falling into the space between organizations, and the mechanism's core move is closing that accountability gap with a named owner — not smoothing a curve, translating a format, or scheduling a window.
Example¶
A 78-year-old is discharged after surgery for a hip fracture, moving from the hospital to a skilled nursing facility for rehab and then home with a visiting nurse. Each of those seams is a place where care can silently break: the nursing facility never learns she is on a blood thinner, her follow-up orthopedic appointment is never booked, her home medications duplicate the new ones. A continuity-of-care plan closes those gaps. The discharge nurse is named as the handoff owner, accountable until the receiving side confirms receipt. She assembles a reconciled medication list, the active diagnoses, pending lab results, and scheduled follow-ups, and does a live "warm handoff" call to the facility's intake nurse rather than faxing a summary into a void. The patient and her daughter get a plain-language sheet — where you are in your recovery, what changes next, who to call if something goes wrong. Forty-eight hours after each transfer, someone calls to confirm the medications were filled and the appointment was kept. The outcome is a discharge with no unserved care gap and no dropped responsibility.
How it works¶
The plan is built around a closed loop, not a document drop. Clinical information travels with the patient in a transfer packet; a single named owner stays accountable for the transition until the receiving side acknowledges it; the patient is taught what to expect and what to watch for; and a follow-up check confirms the transfer actually landed. What distinguishes it from generic discharge paperwork is that continuity is treated as someone's job through the whole crossing and is verified afterward, rather than assumed to have happened because a form was generated.
Tuning parameters¶
- Handoff richness — a full clinical packet versus a minimal summary. Richer transfers reduce information loss but take time and can bury the critical items in noise.
- Owner assignment — sending-side clinician, receiving-side clinician, or a dedicated transition coordinator. A dedicated coordinator closes the gap most reliably but costs a role; leaving it to either side risks each assuming the other has it.
- Confirmation strength — fire-and-forget versus closed-loop acknowledgment. Requiring the receiver to confirm receipt catches dropped handoffs but adds a step that busy staff may skip.
- Follow-up window and modality — how soon after transfer, and by phone, portal, or visit. Sooner catches early failures; later is cheaper but risks the gap having already caused harm.
- Patient-facing detail — how much the plan tells the patient and family. More detail builds self-advocacy but can overwhelm; too little leaves them unable to notice a lapse.
When it helps, and when it misleads¶
Its strength is protecting the most vulnerable dependency — a person — across the most fragmented boundaries, where each organization's metrics can look fine while the patient falls through the gap between them. A well-run plan turns a set of separate encounters into one continuous course of care. The discipline of reconciling every medication at each transfer point is the canonical safety practice here.[n1]
Its central failure mode is continuity theater: a plan that exists on paper but that no one actually owns, or a packet that is sent but never read, so the form is complete while the care is not. The classic misuse is an auto-generated discharge summary faxed to a general number, checked off as "handoff done," with no confirmation that a human on the other side received or acted on it. The guarding discipline is to require a single accountable owner and closed-loop confirmation — the handoff is not finished when the document is sent, only when the receiver acknowledges it and a follow-up shows no gap opened.
How it implements the components¶
A continuity-of-care plan fills the ownership-and-verification slots of the archetype's machinery — the parts a person-centered service protocol can hold:
handoff_owner— it names the individual accountable for the transition across the organizational boundary, closing the gap where each side assumes continuity is the other's responsibility.affected_state_or_value— it defines precisely what must remain continuous: this patient's treatment, medications, information, and support, not continuity in the abstract.communication_marker— the plain-language summary tells the patient where they are in the transition, what protections exist, and whom to call, so the crossing feels governed rather than arbitrary.monitoring_signal— the follow-up check tracks whether a gap actually opened after transfer, catching failures the paperwork alone would hide.
It does not construct an intermediate technical bridging artifact (bridging_state — that belongs to Compatibility Layer) or compute a graduated curve softening a numeric change (smoothing_rule — that belongs to Interpolation and Tapering Strategy). Its nearest twin is the Compatibility Layer: both bridge a transfer, but a care plan carries continuity across the gap by assigning a human owner, whereas a compatibility layer does it with translation code and no owner at all.
Related¶
- Instantiates: Continuity Preservation — a continuity-of-care plan is the service-side bridge that keeps a person's care unbroken across provider and setting changes.
- Sibling mechanisms: Compatibility Layer · Grandfathering Rule · Interpolation · Phase-In Policy · Sliding Scale Rule · Tapering Strategy · Transition Period · Handoff Protocol · Grace Period
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Keeps a patient's treatment, records, and responsibility unbroken as they move between providers or settings — by naming who owns the handoff and confirming afterward that nothing was dropped, making its operative form a repeatable ordered procedure or handoff sequence coordinating action.
Independent corroboration: The frozen evidence defines Continuity-of-Care Plan as 'Keeps a patient's treatment, records, and responsibility unbroken as they move between providers or settings — by naming who owns the handoff and confirming afterward that nothing was dropped', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Clinical care-transition practice cohered continuity plans that reconcile treatment and records, name the handoff owner, and verify receipt after a patient crosses settings.
Review resolution: Both reviewers identify medicine_healthcare as primary. Coordination across clinicians is internal to the established continuity-of-care lineage rather than an independently originating organizational-management mechanism.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Medication reconciliation — the practice of building a single, accurate list of all a patient's medications and comparing it against orders at every transition of care to catch omissions, duplications, and dosing errors. It is the archetypal continuity check at a care boundary, which is why it anchors the transfer packet above. ↩