clinical_attribute_config.yaml

# metamodel_version: 1.7.0# version: 3.5.4id: clinical_attribute
schema_generating: true
description: Attributes relating to a clinical manifestation
display_name: clinical attribute
document_category: clinical attribute
weight: 20
fields:
- id: id
  description: A unique identifier for an entity. Must be either a CURIE shorthand
    for a URI or a complete URI
  display_name: id
- id: type
  display_name: type
  cardinality: multi
- id: description
  description: a human-readable description of an entity
  display_name: description
- id: has_attribute
  description: connects any entity to an attribute
  display_name: has attribute
  cardinality: multi
- id: provided_by
  description: 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.
  display_name: provided by
  cardinality: multi
- id: xref
  description: 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.
  display_name: xref
  cardinality: multi
- id: full_name
  description: a long-form human readable name for a thing
  display_name: full name
- id: synonym
  description: Alternate human-readable names for a thing
  display_name: synonym
  cardinality: multi
- id: category
  description: "Name of the high level ontology class in which this entity is categorized.\
    \ Corresponds to the label for the biolink entity type class.\n * In a neo4j database\
    \ this MAY correspond to the neo4j label tag.\n * In an RDF database it should\
    \ be a biolink model class URI.\nThis 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`,\
    \ ...\nIn 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}"
  display_name: named thing_category
  cardinality: multi
- id: name
  description: 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.
  display_name: attribute_name
- id: has_attribute_type
  description: connects an attribute to a class that describes it
  display_name: has attribute type
- id: has_quantitative_value
  description: connects an attribute to a value
  display_name: has quantitative value
  cardinality: multi
- id: has_qualitative_value
  description: connects an attribute to a value
  display_name: has qualitative value
- id: iri
  description: An IRI for an entity. This is determined by the id using expansion
    rules.
  display_name: iri