Skip to content

Class: ClinicalTrial

Description: A clinical trial is a research study that prospectively assigns human participants or groups of humans to one or more health-related interventions to evaluate the effects on health outcomes.
classDiagram class ClinicalTrial Study <|-- ClinicalTrial ClinicalTrial : category ClinicalTrial : clinical_trial_phase ClinicalTrial --|> ResearchPhaseEnum : clinical_trial_phase ClinicalTrial : clinical_trial_primary_purpose ClinicalTrial : creation_date ClinicalTrial : deprecated ClinicalTrial : description ClinicalTrial : equivalent_identifiers ClinicalTrial : full_name ClinicalTrial : has_attribute ClinicalTrial --|> Attribute : has_attribute ClinicalTrial : has_study_results ClinicalTrial --|> StudyResult : has_study_results ClinicalTrial : id ClinicalTrial : information_content ClinicalTrial : iri ClinicalTrial : name ClinicalTrial : provided_by ClinicalTrial : synonym ClinicalTrial : type ClinicalTrial : xref

Inheritance

Slots

Name Cardinality and Range Inheritance Examples
clinical_trial_phase:
The phase that a clinical trials study represents
0..1
ResearchPhaseEnum		 direct
clinical_trial_primary_purpose:
The primary purpose of a clinical trial as determined by clinicaltrials.gov. The most common values are TREATMENT and PREVENTION. Other possible values include BASIC_SCIENCE, SUPPORTIVE_CARE, DIAGNOSTIC, HEALTH_SERVICES_RESEARCH, SCREENING, DEVICE_FEASIBILITY, OTHER, and (null). 		0..1
String		 direct
creation_date:
date on which an entity was created. This can be applied to nodes or edges 		0..1
Date		 direct
has_study_results:
Connects an study to instances of its study result 		*
StudyResult		 Study
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
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

Usages

used by used in type used
ClinicalTrial clinical_trial_primary_purpose domain ClinicalTrial

Valid ID Prefixes

Instances of this class should have identifiers with one of the following prefixes, ordered with the most preferred first:

ID Prefix Usage
CLINICALTRIALS ClinicalTrial

LinkML Source

name: clinical trial
id_prefixes:
- CLINICALTRIALS
description: A clinical trial is a research study that prospectively assigns human
  participants or groups of humans to one or more health-related interventions to
  evaluate the effects on health outcomes.
from_schema: https://w3id.org/biolink/biolink-model
exact_mappings:
- NCIT:C71104
- SIO:001000
is_a: study
slots:
- clinical trial phase
- clinical trial primary purpose
- creation date