Public correction record
Trust includes showing the repair.
Material errors, omissions and availability failures are logged with the affected surface, the correction and the control added afterward.
- Entries
- 05
- Latest entry
- 2026-08-30
These entries were identified during canary verification. They do not claim clinical review and do not replace the current prescribing source.
01 Availability
Static pages were not carried into a fresh Worker version.
BeforeA new deployment could attempt to render static pages inside the Worker and time out even though the build had completed.
CorrectedBuild-time pages are now shipped in the Workers Static Assets incremental cache and internal links use reliable document navigation.
PreventionThe deployment runbook requires the OpenNext build/upload path, version-level testing and a live route verifier before traffic moves.
02 Label data
A table was classified by its existence instead of its meaning.
BeforeThe Rybelsus source contains a product-switching table. A broad detector could label any table as a titration table.
CorrectedSchedule-table detection now requires dose-stage semantics. The switching table is not presented as a titration schedule.
PreventionThe build fails if a switching table is reclassified as a dose ladder.
03 Label data
Strengths from a second brand could leak across a combined label.
BeforeA combined prescribing document can contain product blocks for more than one brand. Reading all of section 3 can mix their marketed strengths.
CorrectedStrength extraction is now bounded to the requested brand block before the presentation inventory is published.
PreventionA label gate checks the Rybelsus inventory for only its captured 3 mg, 7 mg and 14 mg strengths.
04 Schedule format
Only the first valid schedule table was retained.
BeforeThe current Wegovy prescribing record carries separate injection and tablet schedule tables. Selecting the first table omitted the second route.
CorrectedThe schedule model now preserves and labels every valid schedule table in the captured document.
PreventionThe live verifier requires both Wegovy routes to remain visible.
05 Price data
A 28-day renewal must not be described as a calendar month.
BeforeA single “monthly” label would make provider prices with different billing cadences look directly equivalent.
CorrectedThe Sesame record and exports state “Every 28 days” and explain that this cadence can produce 13 charges in 364 days.
PreventionBilling cadence is a required provider field and the live gate checks the 28-day language.