Class: CommonDataElement
Description: A Common Data Element (CDE) is a standardized, precisely defined question, paired with a set of allowable responses, used systematically across different sites, studies, or clinical trials to ensure consistent data collection. Multiple CDEs (from one or more Collections) can be curated into Forms. (https://cde.nlm.nih.gov/home)
classDiagram
class CommonDataElement
InformationContentEntity <|-- CommonDataElement
CommonDataElement : category
CommonDataElement : creation_date
CommonDataElement : deprecated
CommonDataElement : description
CommonDataElement : format
CommonDataElement : full_name
CommonDataElement : has_attribute
CommonDataElement --|> Attribute : has_attribute
CommonDataElement : id
CommonDataElement : iri
CommonDataElement : license
CommonDataElement : name
CommonDataElement : provided_by
CommonDataElement : rights
CommonDataElement : synonym
CommonDataElement : type
CommonDataElement : xref
Inheritance
- Entity
- NamedThing
- InformationContentEntity
- CommonDataElement
- InformationContentEntity
- NamedThing
Slots
Name | Cardinality and Range | Inheritance | Examples |
---|---|---|---|
license: None |
0..1 String |
InformationContentEntity | |
rights: None |
0..1 String |
InformationContentEntity | |
format: None |
0..1 String |
InformationContentEntity | |
creation_date: date on which an entity was created. This can be applied to nodes or edges |
0..1 Date |
InformationContentEntity | |
provided_by: The value in this node property represents the knowledge provider that created or assembled the node and all of its attributes. Used internally to represent how a particular node made its way into a knowledge provider or graph. |
* String |
NamedThing | |
xref: A database cross reference or alternative identifier for a NamedThing or edge between two NamedThings. This property should point to a database record or webpage that supports the existence of the edge, or gives more detail about the edge. This property can be used on a node or edge to provide multiple URIs or CURIE cross references. |
* Uriorcurie |
NamedThing | |
full_name: a long-form human readable name for a thing |
0..1 LabelType |
NamedThing | |
synonym: Alternate human-readable names for a thing |
* LabelType |
NamedThing | |
id: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI |
1 String |
Entity | |
iri: An IRI for an entity. This is determined by the id using expansion rules. |
0..1 IriType |
Entity | |
category: Name of the high level ontology class in which this entity is categorized. Corresponds to the label for the biolink entity type class. In a neo4j database this MAY correspond to the neo4j label tag. In an RDF database it should be a biolink model class URI. This field is multi-valued. It should include values for ancestors of the biolink class; for example, a protein such as Shh would have category values biolink:Protein , biolink:GeneProduct , biolink:MolecularEntity . In an RDF database, nodes will typically have an rdf:type triples. This can be to the most specific biolink class, or potentially to a class more specific than something in biolink. For example, a sequence feature f may have a rdf:type assertion to a SO class such as TF_binding_site, which is more specific than anything in biolink. Here we would have categories {biolink:GenomicEntity, biolink:MolecularEntity, biolink:NamedThing} |
1..* Uriorcurie |
Entity | |
type: None |
* String |
Entity | |
name: A human-readable name for an attribute or entity. |
0..1 LabelType |
Entity | |
description: a human-readable description of an entity |
0..1 NarrativeText |
Entity | |
has_attribute: connects any entity to an attribute |
* Attribute |
Entity | |
deprecated: A boolean flag indicating that an entity is no longer considered current or valid. |
0..1 Boolean |
Entity |
LinkML Source
name: common data element
description: A Common Data Element (CDE) is a standardized, precisely defined question,
paired with a set of allowable responses, used systematically across different sites,
studies, or clinical trials to ensure consistent data collection. Multiple CDEs
(from one or more Collections) can be curated into Forms. (https://cde.nlm.nih.gov/home)
from_schema: https://w3id.org/biolink/biolink-model
close_mappings:
- NCIT:C19984
is_a: information content entity