Skip to content

Closed-loop work and action ownership

Code: LOOP — action ownership and closed loop.

Scope

This finding asks whether safety-relevant information becomes work with a known destination, accountable owner, priority, due time, acknowledgement, escalation path, outcome and clinical closure. Storage, transmission, viewing or filing can be intermediate states; none alone proves that the required care was completed.

What recurs in the current series

  • A result can be filed without clinical completion. Stephen Rhodes (representative case) anchors the distinction between filing and action, while Eric Thompson (representative case) illustrates availability without dependable delivery and escalation.
  • Hybrid notification can fail without an acknowledged owner. In Caliel Smith-Kwami, an abnormal newborn-screening result was entered in the electronic record without dependable active notification while the parallel paper notice was lost. The report connected the missed result and referral with delayed diagnosis, but the electronic record was one component of the hybrid process rather than an isolated cause.
  • A digital channel can terminate in the wrong operational stream. In Stephen Stringer (representative case), a patient enquiry entered an administrative route, did not enter the patient record and was not seen by a doctor.
  • A transfer record can exist outside the receiving workflow. In Morris Reddington (representative case), the ambulance ePRF required separate credentials and unfamiliar navigation, and routine review at handover was unreliable.
  • Task messages can lack enough content to prioritise them. Jennifer Trigger concerns a bleep without a task description or urgency; the resulting work did not carry a structured acceptance or escalation state.
  • A reminder or message can identify risk without creating owned work. Pauline Pryor concerns an incomplete lithium-monitoring reminder and an email that was neither seen nor chased; Stephen Tidey concerns an emailed multi-agency safeguarding referral without dependable acknowledgement, triage or follow-up.
  • Future and population work can remain latent. Hugo Carlos concerns a future surveillance entry that was visible only when the record was opened; John Singleton concerns detection of failed medication collection through local reports rather than an automatically owned exception workflow.
  • Migration can erase an open-work state. In Margaret Spencer, follow-up was prematurely closed during migration to Lorenzo and no assured reconciliation exposed the omitted surveillance work. The report placed this among wider administrative, training and clinical failures and does not support attributing the death to Lorenzo alone.
  • Multiple unfinished actions can compound. Bernard Compton concerns review of a markedly raised troponin and completion of a requested repeat ECG, without a dependable process ensuring either action was closed.

The recurring distinction is between information state and work state. A safe work state makes non-acceptance, delay, reassignment, cancellation and partial failure observable.

Variation and limits

  • Closed-loop controls apply to results, referrals, medication review, messages, monitoring tasks, handover and population recalls, but the appropriate deadlines and escalation routes differ.
  • An electronic task list is not necessarily the answer. The safety property may be delivered through integrated workflow, team-visible queues, structured handover or another controlled process.
  • Several reports combine task design with staffing, demand, training or policy concerns. The dataset does not isolate one universal technical cause.
  • A coroner may identify a future risk without finding that the workflow issue caused the death; those statements must not be collapsed.

The current review counts demonstrate recurrence of LOOP coding within the targeted series. They do not estimate how frequently open-loop work occurs in clinical practice, and they cannot be summed with other code counts.

Defence implications — analytical translation

The following are analytical translations for DPHC and CORTISONE, not coronial directions:

  • represent destination, owner, priority, due time, acceptance, escalation and closure as separate auditable states;
  • keep work team-visible when staff post, deploy, go off shift or lose access to an individual inbox;
  • test rejection, reassignment, cancellation, delayed connectivity and unacknowledged work—not only the nominal successful path; and
  • distinguish administrative receipt, clinical triage, record incorporation and completed clinical action.

See the DPHC and Programme CORTISONE analysis.

Evidence basis: included-case dataset, coding framework, and current review counts.