r/dataanalysis • u/iamabigfatnobody • 22h ago
FAERS is a masterclass in why you model the data-generating process before the data
If you want a dataset that punishes naive counting, the FDA's adverse-event database (FAERS, public via OpenFDA) is perfect. Twenty-plus million reports, and almost every property a data scientist relies on is absent or adversarial:
No denominator. Reports are suspicions filed voluntarily. There is no exposed-population count, so no incidence rate can ever be computed — any "rate" derived from it is fabricated.
Duplicates by design. The same case can be submitted by the patient, a pharmacist, and the manufacturer, plus follow-up versions of each. Deduplication and restricting to primary-suspect reports is the first pipeline step, not an optional cleaning nicety.
The collection process reacts to publicity. For semaglutide, reports by year received run: 40 through 2017, 1,142 in 2018, 3,515 in 2020, 6,302 in 2022, 9,483 in 2023, 14,287 in 2024, 19,977 in 2025. That curve tracks adoption and media attention. Treating it as a risk curve is the classic error.
Coding artifacts dominate naive rankings. MedDRA Preferred Terms include administrative entries — "Off Label Use" alone accounts for 7,316 semaglutide reports. Rank raw terms and your top "adverse events" are paperwork.
Missingness is informative and huge. Outcome and age fields are blank in a large share of reports; blank means unknown, not none.
The standard tool that survives all this is disproportionality analysis — ROR/PRR against the full database, with the Evans criteria (PRR ≥ 2, chi-square ≥ 4, ≥ 3 cases) as a screening rule. In an October 2026 snapshot, semaglutide's impaired gastric emptying posts ROR 117.2 (95% CI 112.7–121.9), and 96.9 when restricted to 2023–2026 — a signal that persists after you control for the publicity era. That persistence check is the whole game: a statistic that survives interrogating the generating process.
What other public datasets do people here use to teach "the count is not the phenomenon"?