The Infrastructure for the Plan Is Not the Infrastructure for Continuity

Healthcare has spent decades building sophisticated infrastructure around a central clinical question:

What is the right plan?

A patient presents with a problem. A clinician gathers information, evaluates symptoms, reviews history, orders tests, makes a diagnosis, and determines what should happen next.

Medication may be prescribed. Therapy may be recommended. A procedure may be scheduled. Behavior may need to change. Measurements may need to be monitored. Follow-up may be required.

This is the essential work of episodic care.

And healthcare has built extraordinary infrastructure to support it: hospitals, medical practices, laboratories, imaging systems, electronic health records, clinical decision support, scheduling systems, referral systems, and increasingly sophisticated diagnostic technologies.

All of them help clinicians answer the question:

What is the right plan for this patient?

But once the plan has been established, a different problem begins.

The patient goes home.

And healthcare must now answer two very different questions:

Is the plan being followed?

Is the plan working?

That is the work of continuous care. And it requires a different infrastructure.

The plan leaves the clinic

A treatment plan may be created during a thirty-minute encounter. Its success or failure unfolds over the hundreds of hours that follow.

Medications must be taken. Symptoms change. Blood pressure fluctuates. Weight increases or decreases. Sleep deteriorates. Anxiety rises. Diet changes. Appointments are missed. Transportation falls through. Instructions are misunderstood. Side effects appear. Family support changes.

Most of this happens outside the institution that created the treatment plan.

The medical record can document what the clinician intended. It cannot, by itself, continuously determine whether that intention is becoming reality.

That distinction is fundamental.

An infrastructure designed to create and document a plan is not necessarily an infrastructure designed to follow that plan through the patient’s life.

Question one: Is the plan being followed?

Following a treatment plan is rarely a binary matter.

A patient may take some medications but not others. A prescription may never have been filled. A medication may be taken incorrectly. Dietary recommendations may be difficult to follow. Daily measurements may stop. A follow-up appointment may be missed because transportation failed.

Sometimes the barrier is clinical. Sometimes it is behavioral. Sometimes it is financial or social. Sometimes the patient simply does not understand what was expected.

If healthcare is responsible for outcomes, these distinctions matter.

It is not enough for the treatment plan to exist in the medical record. The system needs some way of understanding whether the plan is actually being carried out in the world.

That requires continuity.

Question two: Is the plan working?

Even perfect adherence does not guarantee that a treatment plan is working.

A patient may take every medication exactly as prescribed and still deteriorate.

Symptoms may worsen. Weight may rise. Blood pressure may remain uncontrolled. Depression may deepen. Function may decline. A new condition may emerge. A treatment may create unintended effects.

So continuous care cannot simply monitor compliance with instructions. It must continuously interpret what is happening to the person.

That interpretation is inherently longitudinal.

A measurement in isolation tells us relatively little. Its meaning comes from the patient’s baseline, history, conditions, medications, previous responses, behaviors, and the sequence of events that preceded it.

The question is not simply:

What is today’s blood pressure?

It is:

What does today’s blood pressure mean for this person, given everything we know about what has been happening?

That requires persistent understanding.

When the answer is no

The two questions naturally lead to a third:

If the plan is not being followed, or if it is not working, who needs to act?

Sometimes the appropriate action belongs to the patient. Sometimes a caregiver can help. Sometimes a nurse needs to intervene. Sometimes a social or practical barrier needs to be resolved.

And sometimes the evidence suggests that the treatment plan itself needs to change.

At that point, continuous care reconnects with episodic clinical care. The clinician evaluates the new information, applies clinical judgment, and determines whether the plan should be modified.

Then the cycle begins again.

The plan returns to the patient’s life, where continuity infrastructure once again asks:

Is it being followed?

Is it working?

Two jobs. Two infrastructures.

This distinction helps explain why adding more features to the electronic health record cannot, by itself, create continuous care.

The EHR is extraordinarily important infrastructure for episodic medicine. It helps clinicians understand what has happened, document the encounter, communicate clinical information, and establish the treatment plan.

Continuous care has a different operating requirement.

It must remain connected to what happens after the encounter. It must maintain an evolving understanding of the person, recognize meaningful change, determine whether the treatment plan is being followed, assess whether it appears to be working, identify when attention is required, engage the appropriate participant in the Care Circle, and follow the resulting action to completion.

These are not competing infrastructures.

They are complementary infrastructures built for different parts of care.

One helps determine what should happen.
The other helps determine what actually happens.

The missing half of the treatment plan

This becomes particularly important in value-based care.

Fee-for-service healthcare can largely complete its economic transaction when the encounter is completed. Value-based care cannot.

If an organization is responsible for the patient’s outcome, its responsibility continues after the treatment plan leaves the clinic.

The plan may be clinically excellent. But if it is not followed, the outcome may still be poor. And if it is followed but does not work, the outcome may still be poor.

Value-based care therefore requires infrastructure capable of remaining with the treatment plan over time.

That is Healthcare Continuity Infrastructure.

Ibis™ maintains persistent understanding of the member and the care context. It uses accumulated knowledge in HealthGraph™ to interpret what is happening now. The Ibis Operating System detects meaningful change, determines what needs attention, orchestrates the appropriate participant in the Care Circle, and helps close the loop.

The purpose is not to replace the clinician’s role in determining treatment.

It is to provide the infrastructure for what happens next.

From a treatment plan to a continuous care loop

The architecture of healthcare can therefore be understood as two connected systems.

Episodic care asks: What is the right plan?

The clinician evaluates, diagnoses, and determines treatment.

Then continuous care takes over a different responsibility:

Is the plan being followed?

Is the plan working?

When the answer to either question suggests that something needs to change, the appropriate person is brought back into the loop. If clinical judgment is required, the clinician reassesses and adjusts the plan. Then continuity resumes.

The result is not episodic care replaced by continuous care.

It is episodic care made more effective because continuity surrounds it.

Healthcare has built extraordinary infrastructure for deciding what care a patient should receive.

Now it needs equally capable infrastructure for what happens after that decision—when the plan leaves the clinic and enters the patient’s life.