Protocol Ledger

Data Provenance & Biostatistics Reconciliation Specification

ClinicalTrials.gov API v2 & FDA Drugs@FDA Reconciliation Methodology

Protocol Ledger deterministically unites 54,890 interventional Phase II and Phase III clinical trial protocols from the NIH National Library of Medicine ClinicalTrials.gov REST API v2 (2018 to 2026) with canonicalized physical hospital campuses, biopharma M&A parent lineages, and 5,848 all-time original NDA and BLA regulatory approvals from FDA Drugs@FDA (publication 47c4426df7e9d67d5bfe).

Publication ID: 47c4426df7e9d67d5bfe Retrieved: 2026-11-06 Min Denominator Rule: N >= 15

1. Authoritative U.S. Federal Data Sources

2. Hospital Campus Canonicalization, CRO Masking Isolation & M&A Rollups

Across 948,985 protocol facility location rows, Protocol Ledger separates 155,062 anonymized CRO placeholder slots (such as "Research Site" or numeric site codes used across 40 sponsors) from 793,923 named physical hospital slots (83.66% disclosure). Named facilities are resolved across 49,607 campus merges into 22,436 physical medical centers while keeping multi-state hospital systems (such as Mayo Clinic Rochester, Arizona, and Florida) geographically distinct. On the sponsor axis, 3,327 protocols across 156 acquired biotech subsidiaries are consolidated into 37 corporate parent groups.

Pipeline Quarantine & Hygiene Ledger (Publication 47c4426df7e9d67d5bfe)
Verification Dimension Verified Count / Value Scientific & Epidemiological Integrity Guarantee
Future / Placeholder Start Dates Excluded 487 Prevents post-2026 placeholder dates from distorting historical start vintages
Far-Future Completion Horizons (>2040) 56 Quarantined from velocity medians so 2042 to 2050 placeholders never skew cycle times
Enrollment Outliers (>250,000 Subjects) 3 Population-scale registry outliers isolated from clinical trial sample medians
Anonymized CRO Site Masking Isolation 155,062 slots Zero synthetic hospital entities fabricated from masked commercial site codes
Individual Investigator Contact PII 0 Personal investigator phone numbers, emails, and individual contact names stripped

3. Automated Publication Quality Gate Verification

Every Protocol Ledger build runs automated invariant checks against the reconciled DuckDB and SQLite publication artifact prior to publishing static and API views. All 7 release gates below must pass with zero silent fallbacks.

Quality Gate Verification Checks (Publication 47c4426df7e9d67d5bfe)
Quality Gate Check Actual Value Expected Threshold Status
Primary Cohort Protocols Minimum Threshold 54,890 >= 45,000 PASS
California Protocols Present 10,046 >= 4,000 protocols with California sites PASS
Undisclosed Sites Isolated from Named Entities 0 0 PASS
Mayo Campuses Distinct 3 3 PASS
California Flagship Sites Resolved Verified (true) Verified (true) PASS
FDA NDA BLA Linked to Sponsors 2,830 >= 1,500 linked NDA/BLA approvals PASS
Scene Constellation Populated sites: 140, sponsors: 36, arcs: 203 sites>=100, sponsors>=30, arcs>=120 PASS

4. Engineering Architecture & Related Documentation

Protocol Ledger is engineered by Meru AI as a deterministic public-data reference system. Additional notes on institutional campus reconciliation, cryptographic provenance digests, and release gate verification are documented in Cross-Agency Entity Resolution, Citation-Grade Public Data Architecture, Healthcare Price & Patent Cliff Crosswalk, and Meru AI Public Data Platforms.

Need custom healthcare data pipelines, identifier crosswalks, or workflow automation? Talk to Meru AI