Skip to content

Class: Consent

An entity that can be used to capture consent code and other relevant data about consent for a study.

URI: bdchm:Consent

classDiagram class Consent click Consent href "../Consent" Entity <|-- Consent click Entity href "../Entity" Consent : consent_code Consent --> "0..1" DataUseEnum : consent_code click DataUseEnum href "../DataUseEnum" Consent : id Consent : valid_from Consent --> "0..1" TimePoint : valid_from click TimePoint href "../TimePoint" Consent : valid_to Consent --> "0..1" TimePoint : valid_to click TimePoint href "../TimePoint"

Inheritance

Slots

Name Cardinality and Range Description Inheritance
consent_code 0..1
DataUseEnum		 Data Use Restrictions that are used to indicate permissions/restrictions for ... direct
valid_from 0..1
TimePoint		 The point in time from which the consent record is valid direct
valid_to 0..1
TimePoint		 The point in time after which the consent record is invalid direct
id 1
Uriorcurie		 The 'logical' identifier of the entity within the system of record Entity

Usages

used by used in type used
Participant consents range Consent
ResearchStudy consents range Consent

Identifier and Mapping Information

Schema Source

  • from schema: https://w3id.org/nhlbidatastage/bdchm

Mappings

Mapping Type Mapped Value
self bdchm:Consent
native bdchm:Consent

LinkML Source

Direct

name: Consent
description: An entity that can be used to capture consent code and other relevant
  data about consent for a study.
from_schema: https://w3id.org/nhlbidatastage/bdchm
is_a: Entity
attributes:
  consent_code:
    name: consent_code
    description: 'Data Use Restrictions that are used to indicate permissions/restrictions
      for datasets and/or materials, and relates to the purposes for which datasets
      and/or material might be removed, stored or used. Based on the Data Use Ontology
      : see http://www.obofoundry.org/ontology/duo.html'
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    domain_of:
    - Consent
    range: DataUseEnum
    multivalued: false
  valid_from:
    name: valid_from
    description: The point in time from which the consent record is valid.
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    domain_of:
    - Consent
    range: TimePoint
  valid_to:
    name: valid_to
    description: The point in time after which the consent record is invalid.
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    domain_of:
    - Consent
    range: TimePoint

Induced

name: Consent
description: An entity that can be used to capture consent code and other relevant
  data about consent for a study.
from_schema: https://w3id.org/nhlbidatastage/bdchm
is_a: Entity
attributes:
  consent_code:
    name: consent_code
    description: 'Data Use Restrictions that are used to indicate permissions/restrictions
      for datasets and/or materials, and relates to the purposes for which datasets
      and/or material might be removed, stored or used. Based on the Data Use Ontology
      : see http://www.obofoundry.org/ontology/duo.html'
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    alias: consent_code
    owner: Consent
    domain_of:
    - Consent
    range: DataUseEnum
    multivalued: false
  valid_from:
    name: valid_from
    description: The point in time from which the consent record is valid.
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    alias: valid_from
    owner: Consent
    domain_of:
    - Consent
    range: TimePoint
  valid_to:
    name: valid_to
    description: The point in time after which the consent record is invalid.
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    alias: valid_to
    owner: Consent
    domain_of:
    - Consent
    range: TimePoint
  id:
    name: id
    description: The 'logical' identifier of the entity within the system of record.  The
      simple value of this attribute stands for an identifier of this data object
      within the system, it can be used as a reference from other objects within the
      same system (i.e. primary and foreign keys), and it should be unique per type
      of object. The same data object copied to a different system will likely have
      a different "id" in the new system since "id" values are system specific and
      do not represent persistent business identifiers. Business identifiers are assigned
      outside the information system and are captured in the "identifier" field. The
      "id" field is more likely to be a serially or randomly generated value that
      is assigned to the data object as it is created in a system.
    from_schema: https://w3id.org/nhlbidatastage/bdchm
    rank: 1000
    slot_uri: schema:identifier
    identifier: true
    alias: id
    owner: Consent
    domain_of:
    - Entity
    range: uriorcurie
    required: true