Mahmood Ahmad
Tahir Heart Institute
author@example.com

Protocol: CT.gov Strict-Proxy Repeaters

This protocol isolates the strict U.S.-nexus drug-biological-device proxy inside eligible older closed interventional ClinicalTrials.gov studies and ranks named sponsors with at least 50 proxy-core studies. Primary outputs compare strict-core missing-results stock and rate across sponsors, sponsor classes, and condition families, with black-box stock as a secondary severity marker. The aim is to move from sector summaries to specific repeaters inside the regulated-looking subset. Because the subset is proxy-defined, the outputs describe a conservative regulated-looking core rather than formal ACT or FDAAA legal determinations.

Outside Notes

Type: protocol
Primary estimand: Named-sponsor and sponsor-class missing-results stock inside the strict U.S.-nexus proxy core
App: CT.gov Strict-Proxy Repeaters dashboard
Code: https://github.com/mahmood726-cyber/ctgov-strict-proxy-repeaters
Date: 2026-03-29
Validation: FULL REGISTRY RUN

References

1. ClinicalTrials.gov API v2. National Library of Medicine. Accessed March 29, 2026.
2. DeVito NJ, Bacon S, Goldacre B. Compliance with legal requirement to report clinical trial results on ClinicalTrials.gov: a cohort study. Lancet. 2020;395(10221):361-369.
3. Zarin DA, Tse T, Williams RJ, Carr S. Trial reporting in ClinicalTrials.gov. N Engl J Med. 2016;375(20):1998-2004.

AI Disclosure

This work represents a compiler-generated evidence micro-publication built from structured registry data and deterministic summary code. AI was used as a constrained coding and drafting assistant for interface generation, packaging, and prose refinement, not as an autonomous author. The analytical choices, interpretation, and final outputs were reviewed by the author, who takes responsibility for the content.