GLPwatch

Methodology

Every page on GLPwatch is structured data and direct quotes from official sources, linked back to the source. We never write long-form medical content or interpret study results.

Data sources & refresh cadence

SourceCadenceWhat we use it for
PubMed (E-utilities)Weekly + daily newResearch papers by molecule MeSH terms.
NIH iCiteDailyCitation counts, relative citation ratio, NIH percentile.
ClinicalTrials.gov API v2DailyTrial status, phase, sponsor, conditions, outcomes.
openFDADaily (FAERS: quarterly, ~3-month lag)Labels, adverse events, shortages, recalls, NDC, Drugs@FDA.
DailyMedDailyCurrent SPL labels and label-change dates.
Semantic ScholarDaily newPre-built paper TLDR summaries, recommendations, citation graph.
SEC EDGARQuarterlyManufacturer revenue, R&D spend, guidance.
FDA press & warning lettersWeeklyEnforcement actions, compounding-pharmacy letters.

Where we use AI

AI (Mistral) is used only for narrow, structured tasks: tagging which conditions a paper covers, classifying on-label vs off-label use, producing short plain-English trial-protocol summaries, normalizing adverse-event terms, and phrasing one-line changelog entries. We use the small model by default and escalate to the larger model whenever the small model’s output fails an automated validity check, because trust comes first. Every AI output is cached and validated against our controlled vocabularies. We do not use AI to write drug or condition overviews, summarize papers (we use Semantic Scholar’s own TLDRs), or make any clinical claim.

Ranking

Leaderboards rank by transparent, source-derived metrics — citation count and citation velocity for papers, FAERS report counts for side effects, enrollment and status changes for trials. No editorial weighting is applied.

Known limitations