Data dictionary · provenance + exported fields

Provenance model

Provenance is a side table, not a footnote. For each exported field in a record there is a corresponding provenance row recording the source identifier, source URL, source class, and effective value state. Values without commercial-use cleared provenance are excluded from the paid export path.

{
  "field":         "field_name",
  "value":         "...",
  "source":        "clinicaltrials-gov",
  "source_class":  "government | registry | manufacturer | aggregator | derived",
  "source_url":    "https://clinicaltrials.gov",
  "effective":     true,
  "superseded_at": null
}

Export shape

The primary entity is trials. The export combines the canonical entity table with active provenance from 7 sources. JSON responses and the full JSON download include nested provenance. CSV, Parquet, and SQLite are explicitly curated flat extracts and do not carry nested or separate provenance tables.

Key fields

These fields are selected from the field catalog as the main dimensions for filtering, grouping, matching, and API usage:

• -idTrialBase DB canonical trial identifier. Multiple registry records can resolve to the same canonical id.Identity and registry
• -primary_registrySource registry selected as the canonical record, using a sources.code value such as clinicaltrials-gov, eu-ctis, eudract, isrctn, or drks.Identity and registry
• -registry_idIdentifier for the canonical source registry record, for example an NCT, EudraCT, CTIS, or ISRCTN id.Identity and registry
• -registry_idsCross-registry identifiers attached to the canonical trial, shaped as objects with registry, id, and hard or soft match method.Identity and registry
• -source_record_urlCanonical public registry page for the source record used in the exported row.Identity and registry
• -sponsor_nameLead sponsor name drawn from the public trial registry record.Sponsor
• -conditionsCondition terms associated with the trial.Conditions and interventions
• -countriesCountries associated with trial recruitment or study locations, used by country filters.Conditions and interventions
• -intervention_typesIntervention categories reported by the source registry.Conditions and interventions
• -interventionsIntervention names associated with the trial.Conditions and interventions
• -outcomesSource-owned primary and secondary outcome definitions from the licensed ISRCTN registry contribution.Outcomes and publications
• -outputsISRCTN output/publication metadata and exact PMID or DOI assertions; external links are relationships, not licenses to copy their targets.Outcomes and publications
• -publicationsCitation-only PubMed metadata for exact accepted ISRCTN PMID assertions, including identifiers, title, journal, dates, authors, publication types and retraction/comment links.Outcomes and publications
• -regulatory_recordsHealth Canada CTD authorization observations linked through exact protocol-number evidence plus at least two independent exact agreements.Regulatory
• -lead_conditionFirst listed condition, materialized as a cheap facet and index for common searches.Conditions and interventions
• -completion_dateOverall study completion date where reported.Enrollment and dates

Field catalog

The catalog below contains 30 documented fields from the same field model rendered on this page. Field types and descriptions come from the export contract and source registry. Nullable means unknown or not applicable; it does not mean zero, false, or inferred.

NULL policy

A missing field on a record is a missing field: not a zero, not a negative assertion, and not an imputed value. Fields that do not apply to a record are explicitly NULL. Coverage gaps are visible by design.

Audit trail

Every provenance row carries the observed value, source code, source record URL, effective state, and ingest context. Snapshot manifests and source licence notes document which upstream records were cleared for commercial use.