One employer. One record. Every episode it has ever run.
Authored episodes for demonstration only. No employer identity, no pilot, no production deployment, no realized or verified saving. Reuses existing catalogue situations. Every recurrence and cumulative figure below is computed only from these authored episodes.
Episodes on record
7
Distinct patterns
5
Recurring pattern
3×
Unresolved to date
7
“Employer execution failure” has now appeared 3 times. The most recent occurrence is more valuable than the first because the earlier ones are already on this record.
Every episode keeps these nine separate — never merged into one status, never a composite score
EPISODE-01Episode 1 of 7 in this record Record now tracks 1 pattern 1 unresolved to date1st occurrence of “Treatment never initiated” in this record
Jan 2024· reuses CASE-03-CEmergency Medicine
A covered patient left the emergency department without being seen.
Activity performed
Patient registered and triaged; visit opened in the system.
Obligation status
Owed: initiate treatment for the presenting complaint.
Acceptance state
Visit opened and triage acknowledged — the obligation was accepted.
Execution state
Treatment was never started — not executed.
Evidence status
Registration + triage timestamps present. No treatment-start artifact.
Responsible party
Emergency department intake
Delay
Visit closed with no treatment initiated
Outcome
Left without being seen; no care delivered.
Economic consequence
No economic result established. Inspectable only. No economic figure asserted for this episode.
Engine Answer — Activity happened (registration) and the obligation was accepted, but it was never executed — and no evidence of treatment exists. Acceptance is not execution.
EPISODE-02Episode 2 of 7 in this record Record now tracks 2 patterns 2 unresolved to date1st occurrence of “Medication management failure” in this record
Mar 2024· reuses CASE-02-DCardiology
New atrial fibrillation identified without appropriate anticoagulation started.
Activity performed
Diagnosis recorded; anticoagulation indicated in the note.
Obligation status
Owed: start and document indicated anticoagulation.
Acceptance state
Indication documented in the note — obligation accepted.
Execution state
No prescription or administration occurred — not executed.
Evidence status
Diagnosis note present. No prescription or administration artifact.
Responsible party
Treating cardiologist
Delay
No therapy initiation on record after diagnosis
Outcome
Indicated therapy not demonstrably started.
Economic consequence
No economic result established. Inspectable only. No economic figure asserted for this episode.
Engine Answer — A recorded diagnosis (activity, accepted) is not executed therapy, and the note is not evidence that therapy occurred.
EPISODE-03Episode 3 of 7 in this record Record now tracks 3 patterns 3 unresolved to date1st occurrence of “Employer execution failure” in this record
May 2024· reuses CASE-25-AOccupational Medicine
A delayed return-to-work handoff after a cleared associate.
Activity performed
Return-to-work clearance issued and filed.
Obligation status
Owed: place cleared associate onto appropriate duties.
Acceptance state
Clearance received and filed by the site — obligation accepted.
Execution state
Placement onto cleared duties never happened — not executed.
Evidence status
Clearance document present. No scheduling/placement artifact.
Responsible party
Site operations supervisor
Delay
Clearance not carried into scheduling
Outcome
Cleared associate not placed onto appropriate duties.
Economic consequence
No economic result established. Inspectable only. No economic figure asserted for this episode.
Engine Answer — First appearance of an employer-execution failure in this record: a clearance was accepted, but operational execution did not follow.
EPISODE-04Episode 4 of 7 in this record Record now tracks 4 patterns 4 unresolved to date1st occurrence of “Diagnostic pathway incomplete” in this record
Jul 2024· reuses CASE-01-CANGastroenterology
A positive fecal immunochemical test with no completed diagnostic colonoscopy.
Activity performed
Screening test resulted positive and filed.
Obligation status
Owed: complete the diagnostic colonoscopy.
Acceptance state
Positive result acknowledged and referral opened — obligation accepted.
Execution state
Diagnostic colonoscopy was never completed — not executed.
Evidence status
Positive result present. No completed-procedure artifact.
Responsible party
Referring / GI coordination
Delay
Diagnostic follow-through not completed
Outcome
Diagnostic pathway left open.
Economic consequence
No economic result established. Inspectable only. No economic figure asserted for this episode.
Engine Answer — A positive result (evidence of a finding, accepted) is not evidence that the owed diagnostic step was executed.
EPISODE-05Episode 5 of 7 in this record Record now tracks 5 patterns 5 unresolved to date1st occurrence of “Surveillance failure” in this record
Oct 2024· reuses CASE-09-CEndocrinology
Persistently uncontrolled diabetes without therapeutic intensification.
Activity performed
Repeated elevated labs recorded across visits.
Obligation status
Owed: intensify therapy on repeated treatment failure.
Acceptance state
Elevated labs recorded and acknowledged across visits — obligation accepted.
Execution state
No therapy change was ever made — not executed.
Evidence status
Serial labs present. No therapy-change artifact.
Responsible party
Managing endocrinologist
Delay
Multiple cycles without intensification
Outcome
Uncontrolled status persisted.
Economic consequence
No economic result established. Inspectable only. No economic figure asserted for this episode.
Engine Answer — Monitoring activity accumulated and was acknowledged, but the owed response to it was never executed.
EPISODE-06Episode 6 of 7 in this record Record now tracks 5 patterns 6 unresolved to date2nd occurrence of “Employer execution failure” in this record
Dec 2024· reuses CASE-25-AOccupational Medicine
A second return-to-work handoff that again did not reach scheduling.
Prior knowledge used from this record
EPISODE-03
This record already contains EPISODE-03 (May 2024): the same “Employer execution failure”, same responsible role (Site operations supervisor), same site. Because that episode is already on record, this is now the 2nd occurrence — not an isolated incident.
Activity performed
Return-to-work clearance issued and filed.
Obligation status
Owed: place cleared associate onto appropriate duties.
Acceptance state
Clearance received and filed by the site — obligation accepted.
Execution state
Placement again never happened — not executed.
Evidence status
Clearance document present. No placement artifact — same gap as before.
Responsible party
Site operations supervisor
Delay
Clearance again not carried into scheduling
Outcome
Cleared associate again not placed onto appropriate duties.
Economic consequence
No economic result established. Inspectable only. Recurrence is now visible: same pattern, same responsible role.
Engine Answer — Second appearance of the same employer-execution failure. Because EPISODE-03 already exists in this record, the recurrence — not just the incident — is the finding.
EPISODE-07Episode 7 of 7 in this record Record now tracks 5 patterns 7 unresolved to date3rd occurrence of “Employer execution failure” in this record
Mar 2025· reuses CASE-25-EOccupational Medicine
An accepted six-week work restriction was not carried into floor operations.
Prior knowledge used from this record
EPISODE-03EPISODE-06
The record already holds EPISODE-03 (May 2024) and EPISODE-06 (Dec 2024): two prior “Employer execution failure” events, same responsible role, same site. This is the 3rd occurrence, and the first where a bounded demonstrable avoidable cost can be shown. The pattern was known before this episode arrived.
Activity performed
Work restriction issued, accepted, and documented.
Obligation status
Owed: enforce the accepted restriction on the floor.
Acceptance state
Restriction explicitly accepted and documented — acceptance is strongest here.
Execution state
Restriction never enforced across its window — not executed.
Engine Answer — Third appearance of the same employer-execution failure — and the one where a bounded economic result can be demonstrated. The record already knew this pattern before this episode arrived: that is why it is worth more than the first.
Recurrence across episodes
Computed only from the authored episodes above — no catalogue figure is used. A pattern appears here only when this record holds it more than once.
Escalate the recurring employer-execution failure and require placement confirmation
Informed by these episodes on the record
EPISODE-03EPISODE-06EPISODE-07
Basis (why the record supports it)
Three episodes on this record (EPISODE-03, EPISODE-06, EPISODE-07) share one pattern — “Employer execution failure” — with the same responsible role at the same site, culminating in the one episode carrying a demonstrable avoidable cost. No single episode establishes this; only the accumulated record does.
Action
Escalate the recurring pattern to site operations ownership and require a placement/enforcement confirmation artifact for every future clearance or restriction before the obligation is treated as executed.
Boundary
Authored demonstration decision only. Not an actual escalation, contract change, termination, legal action, or realized/verified saving. Shown to demonstrate that a decision is better informed once multiple episodes exist.
Cumulative economics across the record
Demonstrable avoidable cost (total)
$17,500
From 1 of 7 episodes · reused from the one economically-demonstrated catalogue case.
Realized saving (total)
$0
No realized saving is asserted anywhere in this record.
Verified saving (total)
$0
No verified saving record exists; this stays $0 by construction.
Realized saving $0 · Verified saving $0. The only economic figure shown is a single demonstrable avoidable cost from the one economically-demonstrated catalogue case.