Home › Methodology
Methodology and data sources
Licensed Compounder republishes public records about compounding pharmacies, with the publisher's own wording and date, and adds nothing to them. This page says exactly where each record comes from, how often it is refreshed, and the lines we will not cross.
How a record gets here
Every record on this site is downloaded from the regulator that publishes it, at the moment the site is built, and rendered with the date that regulator put on it. No value is retyped, edited or rounded on the way through. Where the FDA posts the underlying document — a Form 483, a warning letter — the page links that document rather than describing it.
If a source fails to download during a build, the build does not silently continue with nothing: it falls back to the last good snapshot, loudly, and the page keeps showing that snapshot's date. A stale date you can see is honest; a fresh-looking page built on old data is not.
Sources
| Record | Publisher | Refresh | Covers |
|---|---|---|---|
| 503B outsourcing facility register | U.S. FDA | Every site build; currently as of 2026-09-02 (FDA states weekly updates) | All 97 registered 503B facilities: registration dates, last inspection, Form 483, recall, action taken, sterile-from-bulk |
| State pharmacy permits (503A) — Florida | Florida DOH, Division of Medical Quality Assurance | Every site build; board data as of 2026-09-02 | The board's own permit record for the pharmacies carried here: permit number, status, issue and expiry dates, address of record, discipline and public-complaint flags |
| State pharmacy licenses (503A) — every other state | State boards of pharmacy via the NABP directory | Linked, not embedded, until that board's bulk data is verified | Every other 503A compounding pharmacy; we link the authoritative lookup rather than copy it |
What we will not do
- Characterise a record. We reproduce the FDA's columns and wording. We do not call a facility safe, unsafe, good or bad, and we explain what a Form 483 and an “Open” classification actually mean so a reader does not over-read them.
- Give medical advice. Nothing here is about your dose, your drug, or your health. Where a page describes a drug category, it quotes the FDA or a statute and links it.
- Let anyone pay to change a record. No pharmacy, facility or telehealth brand can pay to alter, remove or feature its record. Where a link on this site may compensate us, it is marked and disclosed — how we make money.
- Publish a page without a record behind it. A facility page exists because the FDA holds a record with these fields. State-level pages will exist only where a board publishes verifiable bulk data.
- Claim freshness we don't have. Every record carries the publisher's date. If a source fails to download at build, the site serves the last good snapshot and keeps that snapshot's date on the page.
How often each source is re-read
| Job | Runs | What proves it ran |
|---|---|---|
| FDA 503B register | Every site build | The as-of date on every register and facility page, taken from the FDA's own page, currently 2026-09-02 |
| Federal Register docket for the 503B bulks list | Every site build | The dated docket line in the status box on each compounded GLP-1 page |
| Florida board permits | Every site build | The board's “data as of” date on each Florida pharmacy record |
| Quoted-sentence check | Every release | A build gate that fetches each page and fails if a quoted regulator sentence is not a verbatim match for the citation ledger |
The last row is the one that matters most on a site built out of other people's words. Every sentence attributed to a regulator is stored in a ledger with its source URL and the date it was read, and a page cannot ship with a quotation that does not match the ledger character for character. A paraphrase strengthened into a quotation is the failure mode we are guarding against.
Corrections
If a record here differs from the FDA's page or a state board's lookup, the regulator is right and we are stale: the next build will match. If you believe we have parsed a record incorrectly, write to us and we will check it against the source and publish the correction on the page concerned.