CDE set

A published definition of one radiology finding on RadElement, grouping the CDE elements that characterize it. Roughly 140 sets are listed in the OIDM mirror of the published definitions, from Acute Aortic Syndrome to TI-RADS, each named and carrying an RDES identifier.¹

A set carries identity and governance fields as well as its elements: id, name, description, set_version, schema_version, current_status, and status_history. The mirror notes that its definitions conform to version 1.0 of the CDE schema rather than the newer version 1.1.¹

In FHIR encodings the set identifier is what labels the parent Observation. The lineage sample codes a radiologist’s finding as RDES195 Pulmonary Nodule with system https://radelement.org, and IHE IDR states that “when encoding CDE Sets from radelement.org, it is preferred to use the CDE Set code here.”²³

Synonyms and near-synonyms

• Finding set is IHE IDR’s term for the same grouping pattern.³
• Finding model is the OIDM counterpart at the same granularity.
• FindingClass is the next-generation replacement node type.
• Element set is the name used in the JSON schema itself.

Identifier form

RDES followed by digits, for example RDES195 (Pulmonary Nodule), RDES267 (Lung-RADS categorization), RDES11 (MR Rectal Tumor Imaging).

Where it is used

CDEs and RadElement and FHIR mapping.

Conflicts

The published RelaxNG set schema and the RadElement JSON API disagree in structure and in field presence: images, modality, biological_sex, and age_range appear in the schema but not the API, while url and body_parts appear in the API but not the schema.⁴ IHE IDR separately records open questions about whether CDE sets may be extended with additional sub-observations and what coding system URI identifies RadElement codes.³

Footnotes

1. common_data_elements repository README ↩ ↩²

2. Radiologist finding Observation coded with a CDE set ↩

3. IHE IDR Phase II extract ↩ ↩² ↩³

4. Differences between the CDE Set schema and the RadElement API ↩