Skip to content

Class: ChemicalExposure

Description: A chemical exposure is an intake of a particular chemical entity.
classDiagram class ChemicalExposure ExposureEvent <|-- ChemicalExposure Attribute <|-- ChemicalExposure ChemicalExposure <|-- DrugExposure ChemicalExposure : category ChemicalExposure : deprecated ChemicalExposure : description ChemicalExposure : equivalent_identifiers ChemicalExposure : full_name ChemicalExposure : has_attribute ChemicalExposure --|> Attribute : has_attribute ChemicalExposure : has_attribute_type ChemicalExposure --|> OntologyClass : has_attribute_type ChemicalExposure : has_qualitative_value ChemicalExposure --|> NamedThing : has_qualitative_value ChemicalExposure : has_quantitative_value ChemicalExposure --|> QuantityValue : has_quantitative_value ChemicalExposure : id ChemicalExposure : information_content ChemicalExposure : iri ChemicalExposure : name ChemicalExposure : provided_by ChemicalExposure : synonym ChemicalExposure : timepoint ChemicalExposure : type ChemicalExposure : xref

Inheritance

Slots

Name Cardinality and Range Inheritance Examples
has_quantitative_value:
connects an attribute to a value
*
QuantityValue		 direct
timepoint:
a point in time 		0..1
TimeType		 ExposureEvent
name:
The human-readable 'attribute name' can be set to a string which reflects its context of interpretation, e.g. SEPIO evidence/provenance/confidence annotation or it can default to the name associated with the 'has attribute type' slot ontology term. 		0..1
LabelType		 Entity, Attribute
has_attribute_type:
connects an attribute to a class that describes it 		1
OntologyClass		 Attribute
has_qualitative_value:
connects an attribute to a value 		0..1
NamedThing		 Attribute
iri:
An IRI for an entity. This is determined by the id using expansion rules. 		0..1
IriType		 Entity, Attribute
id:
A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI 		1
String		 OntologyClass, Entity
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
information_content:
Information content (IC) value for a term, primarily from Automats. 		0..1
Float		 NamedThing
equivalent_identifiers:
A set of identifiers that are considered equivalent to the primary identifier of the entity. This attribute is used to represent a collection of identifiers that are considered equivalent to the primary identifier of an entity. These equivalent identifiers may come from different databases, ontologies, or naming conventions, but they all refer to the same underlying concept or entity. This attribute is particularly useful in data integration and interoperability scenarios, where it is important to recognize and link different representations of the same entity across various sources. 		*
Uriorcurie		 NamedThing
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
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: chemical exposure
description: A chemical exposure is an intake of a particular chemical entity.
from_schema: https://w3id.org/biolink/biolink-model
exact_mappings:
- ECTO:9000000
- SIO:001399
is_a: attribute
mixins:
- exposure event
slots:
- has quantitative value