A consent decree isn't a database row
FDA Radar's warning-letter adapter reads a structured, public database every day. A Warning Letter that goes unanswered can escalate into a federal consent decree of permanent injunction — a court order announced case by case, in a record no adapter here, or in most monitoring built like it, ever touches.
By Connor Griggs — Regulatory & Quality Strategist
FDA Radar’s warning-letter adapter reads a structured, public database every day — the same JSON endpoint this blog has already described column by column. A Warning Letter that goes unanswered can escalate past that database entirely, into a record this pipeline, and most monitoring built like it, never touches.
What happens when a warning letter doesn’t work
Section 302(a) of the FD&C Act — 21 U.S.C. § 332(a) — lets a federal district court restrain a violation of the Act on a complaint from the United States, and FDA refers a case to the Department of Justice to bring one. Litigation this way is slow and public, so DOJ typically proposes a consent decree of permanent injunction first — a settlement, negotiated with the firm, that a court then enters as a binding order. FDA reached exactly that outcome with Philips Respironics: on April 9, 2024, the U.S. District Court for the Western District of Pennsylvania entered a consent decree restricting the firm from manufacturing or selling new CPAP and BiPAP devices at several U.S. facilities until independent auditors certify specific corrections — a standing court order, not a letter with a response deadline.
A Warning Letter asks a firm to correct something by a date. A consent decree tells a firm what it may not do until a court says otherwise.
One is a feed. The other is a docket.
The difference that matters for a monitoring practice isn’t severity — it’s where each record lives. A Warning Letter posts to a database built for exactly that purpose, on a cadence a scraper can rely on. A consent decree is entered into a federal court’s own docket and announced, case by case, through an FDA or DOJ press release — not a queryable endpoint, not a field anywhere that reads “decree: yes.” FDA Radar’s own source list has four adapters: the Federal Register, the warning-letter database, openFDA’s recall data, and openFDA’s 510(k) data. None of them reads a court docket or a press release, because none of the four was ever the record a consent decree gets published in.
The practice
A closed Warning Letter is evidence the letter closed — not evidence the underlying matter did. Tracking a supplier, a CMO, or a predicate’s manufacturer through Warning Letters alone will miss the step where FDA decided a letter wasn’t enough: the announcement lives on FDA’s and DOJ’s press-release pages, and the binding terms live in the court’s own docket, both outside any structured feed this product, or a comparable one, reads today. Whether a specific firm’s history warrants that closer look is a judgment for whoever owns the relationship — this is regulatory intelligence about where the record sits, never regulatory advice about a specific firm. FDA Radar states what it does and doesn’t ingest on the page that lists what we monitor and how often; a consent decree is one more example of what “how often” can’t answer, because the source itself isn’t one FDA Radar reads.
Primary sources
- Cornell LII — 21 U.S.C. § 332, Injunction proceedings (FD&C Act § 302)
- FDA — Federal Court Enters Consent Decree Against Philips Respironics Following Recall of Certain Sleep Therapy Machines
- FDA — Press Announcements
- FDA Radar — what we monitor and how often
Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.