THE CARE COMPLETION PROJECT

Clinical intent is easy.
Follow-through is where health-tech leaks.

Continuum is an enterprise product architecture concept engineered by Emmanuella Oseni. It demonstrates how to turn dead-end discharge plans into stateful, trackable care obligations—capturing real-world patient data, routing clinical exceptions, and enforcing safety boundaries at scale.

See the Interactive Concept Workspace  → Contact creator  ↗
THE CARE OBLIGATION LIFECYCLE

Discharge

Care plan completed

Obligation

Care obligations created

Condition

Change detected, needs attention

Clinical Review

Licensed decision required

Resolution

Verified and closed

Why Continuum exists
The hospital can record what it intended. Continuum follows what happened next.

Discharge is a handoff, not an ending.

A patient can leave with the right diagnosis, the right prescription and the right follow-up plan — and still fail to complete the care that plan depends on.

The appointment may never happen. The medication may not be started. A follow-up call may go unanswered. A new symptom may appear. A measurement may cross a threshold.

The clinical team documented the intention. But the health system still needs to know what happened in the days and weeks that followed.

Continuum is built around that missing middle: the space between “this should happen” and “this actually happened.”
A synthetic care journey

Follow one case from discharge to resolution.

Continuum does not treat follow-through as a checkbox. It gives every obligation an identity, a state, an owner, evidence requirements and a path to resolution.

OBL-0921
Patient P-2048 · Hypertension · Day 7 post-discharge · General Medicine
Current workflow stateException detected
OBL-0921 · POST-DISCHARGE CARE

OBL-0921

Care journey · operational case record
Resolution not established
Patient P-204856 years · Hypertension · Day 7 post-discharge · General Medicine
POST-DISCHARGE FOLLOW-UP3 elevated blood-pressure readings this week. Follow-up verification is overdue.
CARE MILESTONEDay 7 follow-up
ADHERENCEUnconfirmed
OWNERNurse Ada
INTENTOBLIGATIONEVIDENCEEXCEPTIONREVIEWRESOLUTION

Hospital discharge

Discharge plan and instructions recorded.

Care obligations created

Expected follow-up actions and checkpoints assigned.

Day 3 follow-up checkpoint

First check-in completed and evidence received.

Day 7 follow-up checkpoint

Three elevated readings detected. Follow-up outcome is unconfirmed.

Next action: second outreach attempt · Owner: Nurse Daniel
Escalation: clinical review if threshold remains unresolved at SLA breach

Day 14 evidence gate

Required evidence must be established before the journey can advance.

Day 30 care review

Final review before closure.

Care obligation resolved

Destination state: required checkpoints completed and verified.

Clinical operationsCARE MANAGER
Clinical review routeElevated BP protocol — Rule 12AOperational escalation only. Clinical interpretation remains with Clinical Reviewer.
Current state
Exception · review required
SLA38m remaining
Why this is flagged

3 abnormal readings + unresolved follow-up + evidence timestamp conflict.

Assigned to

Nurse Ada

Latest accepted physiological data
158 / 98 mmHg
Baseline average
126 / 78 mmHg
WHAT WE KNOW
  • 3 abnormal readings detected — latest 158/98 mmHg
  • Elevated BP protocol triggered — Rule 12A
WHAT WE DON'T KNOW
  • Whether the patient has been reached
  • Whether a clinical decision has been made
  • Whether the reading has returned to baseline
Evidence provenance
DEVICE BP readingAccepted
PATIENT handwritten log62% time
SYSTEM discharge planVerified
🔒 Clinical decision gateCare Managers can route, contact, correct evidence extraction and escalate. They cannot clinically dismiss or close this physiological exception. A licensed Clinical Reviewer must record the decision.
Recent auditAPPEND-ONLY
11:24:18.341Exception created · Rule 12A
11:24:19.002Assigned · Nurse Ada
11:31:42.718Evidence conflict · timestamp mismatch
System of record
Source clinical record · no silent overwriteSYNC READY
The operating model

From clinical intent to verified resolution.

Every post-discharge commitment becomes a stateful obligation. Evidence moves the case forward; conflicts, missed checkpoints and SLA risk create exceptions. Exceptions route according to role, ownership and clinical authority, with resolution reopened when subsequent evidence invalidates closure.

01

Intent

The discharge plan becomes an explicit clinical commitment.

02

Obligation

Expected actions and checkpoints are created and assigned.

03

Evidence

The workspace records what is confirmed and what remains unknown.

04

Exception

Signals that break the expected path become visible and routable.

05

Review

Clinical decisions remain inside the appropriate authority boundary.

06

Resolution

A journey closes only when the required outcome is verified.

Designed for operations at scale

One patient makes the problem human. The queue makes it operational.

Continuum is not a replacement for the clinical record. It is the operational layer for the people responsible for hundreds of care obligations — with visibility into what is waiting, overdue, escalated, evidence-conflicted, unresolved and ready for review.

SYNTHETIC DEMO DATA · NOT CONNECTED TO A LIVE CLINICAL SYSTEM
214Total tracked care obligations
24Requiring attention
6Overdue verification checkpoints
2Escalated to clinical review