Feature dictionary

The feature dictionary is the curated bridge between reader-facing phenotype names and machine-readable output names. The maintained source is docs/data/phenotype_dictionary.yml; this page explains how to read it and gives representative examples.

Modality
All modalities
Pipeline step
Documentation registry and output-contract validation
Outputs
Feature name, unit, source modality, exact output column, related pages, evidence status
Maturity
Source-audited reference page

Dictionary fields

FieldMeaning
canonical_idStable documentation identifier for the feature concept
display_nameReader-facing feature name
exact_output_columnCurrent CSV column string when the feature is emitted
unitUnit displayed for interpretation
source_modalityAcquisition or modality family supporting the feature
feature_familyPhenotype family used for grouping
evidence_statusImplementation/reference status for documentation use
related_pagesWebsite pages that document the feature

Representative rows

Display nameFeature familySource modalityUnitOutput column
Left ventricular end-diastolic volumeVentricular structureCine short-axismLLV: V_ED [mL]
Left ventricular ejection fractionVentricular functionCine short-axis%LV: EF [%]
Left atrial maximum volumeAtrial structureCine long-axismLLA: V_max [mL]
Atrioventricular plane displacementCross-chamberCine long-axiscmAV: AVPD [cm]
Aortic valve annulus diameterLVOT structureLVOT cinemmLVOT: Aortic Valve Annulus Diameter [mm]
Aortic regurgitant fractionFlowPhase-contrast flow%Aortic Flow: Regurgitant Fraction [%]
Native myocardial T1Myocardial tissueNative T1 mappingmsNative T1: Myocardium-Global [ms]

Dictionary rule

Promoted phenotype pages should have linked dictionary rows for their current output columns. The generic phenotype validator checks this for pages with source-output contracts.

Source audit

  • Dictionary role and fields were checked against docs/data/phenotype_dictionary.yml.
  • Source-output validation behavior was checked against website/scripts/validate-phenotype-pages.cjs.
  • Textbook context boundary: broad clinical textbook context is not surfaced here because this page documents a registry contract.