Trust · public record

Corrections log

A record you can cite needs a visible correction history. When a published figure or claim on this site is wrong, the correction is logged here — dated, append-only, newest first. Spot an error we haven't? Tell us.

Date	What	What was wrong	Corrected to
23 Jul 2026	“Tracked notices” count, MSN coverage %, and per-medicine recurrence	The Internet Archive had captured some posts several times under different tracking query strings (?unlid=…), and each capture was counted as a separate notice. Tracked notices read 333; MSN coverage read “305 of about 364 — roughly 83%”; Tresiba showed “notified short 6 times” and Glucagon 5 when each had been notified once.	One notice per canonical post URL. Tracked notices 307, MSN coverage 277 of about 364 (roughly three quarters), Tresiba 2 and Glucagon 1. The corrected coverage figure is lower than what we published.
23 Jul 2026	“SSPs in force” headline figure	The homepage and UK Shortage Index counted protocols by the expiry derived from announcement posts (which are taken down, so the dates truncate) and showed 2, while the register page showed 7 using the authoritative NHSBSA expiry.	Both use the register expiry the methodology names as authoritative. One question, one answer: 7.
23 Jul 2026	“What this protocol permits” quotes on SSP pages	Excerpts presented as quoted verbatim were character-corrupted on at least 10 protocols — text wrapped in the source PDF lost its leading characters (“accordance”→“ordance”, “tablet”→“let”) — and some lost or mixed in text from a neighbouring cell.	An excerpt is published only if it appears in the source PDF as a contiguous run of text and passes completeness checks; anything else is withheld. Quantity is no longer reproduced at all. Fewer quotes, each provably verbatim.
22 Jul 2026	“In force for” on the UK Shortage Index and press page	Counted a protocol's scheduled future end-date as elapsed time — SSP061 showed “in force 2.4 years” when 2.2 years had elapsed.	Elapsed time and scheduled end-date are separate figures, labelled as such.
22 Jul 2026	“Tracked notices” headline count	Included 5 source editorial posts (news items, not supply notices) in the headline count and the register.	The register and every count exclude non-notice editorial records.
22 Jul 2026	“Last checked” date	Showed when source content last changed, not when we last checked — a quiet source week displayed as a stale check.	Checks and source changes are recorded and shown as distinct signals.
22 Jul 2026	Homepage description of the dataset	Said records are “coded to dm+d” while dm+d product coding is still in progress.	The claim is removed until the coding layer ships; the API docs state the current notice-level reality.

Source-preserved anomalies (a typo in an official document, a reference that doesn't follow the source's own scheme) are not corrections — they are preserved and flagged ⚠ in place, per the methodology.