@prefix : . @prefix owl: . @prefix rdf: . @prefix xml: . @prefix xsd: . @prefix rdfs: . @base . rdf:type owl:Ontology ; ; "omop" ; "https://w3id.org/omop/ontology/" ; rdfs:comment "OWL ontology for the Observational Medical Outcomes Partnership Common Data Model (OMOP CDM) version 5.4." ; rdfs:label "OWL ontology for the Observational Medical Outcomes Partnership Common Data Model (OMOP CDM)" . ################################################################# # Annotation properties ################################################################# ### http://purl.org/dc/terms/license rdf:type owl:AnnotationProperty . ### http://purl.org/vocab/vann/preferredNamespacePrefix rdf:type owl:AnnotationProperty . ### http://purl.org/vocab/vann/preferredNamespaceUri rdf:type owl:AnnotationProperty . ### http://www.lesfleursdunormal.fr/static/_downloads/owlready_ontology.owl#python_name rdf:type owl:AnnotationProperty . ### https://w3id.org/omop/ontology/omop_cdm_name rdf:type owl:AnnotationProperty ; rdfs:label "OMOP CDM name" . ################################################################# # Datatypes ################################################################# ### http://www.w3.org/2001/XMLSchema#date xsd:date rdf:type rdfs:Datatype . ################################################################# # Object Properties ################################################################# ### https://w3id.org/omop/ontology/has_admitted_from rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "admitted_from" ; rdfs:comment "For Visit Detail: Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example. If available, map the admitted_from_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=). If a person was admitted from home or was self-referred, set this to 0."@en , "For Visit Occurrence: Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example. If available, map the admitted_from_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=). If a person was admitted from home or was self-referred, set this to 0."@en ; rdfs:label "Has admitted from" ; "visit_detail.admitted_from_concept_id#53 AS Concept" , "visit_occurrence.admitted_from_concept_id#36 AS Concept" . ### https://w3id.org/omop/ontology/has_amount_unit rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "amount_unit" ; rdfs:comment "For Drug Strength: The Concept representing the Unit of measure for the amount of active ingredient contained within the drug product."@en ; rdfs:label "Has amount unit" ; "drug_strength.amount_unit_concept_id#397 AS Concept" . ### https://w3id.org/omop/ontology/has_anatomic_site rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "anatomic_site" ; rdfs:comment "For Specimen: This is the site on the body where the specimen is from. Map the ANATOMIC_SITE_SOURCE_VALUE to a Standard Concept in the Spec Anatomic Site domain. This should be coded at the lowest level of granularity [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Spec+Anatomic+Site&conceptClass=Body+Structure&page=4&pageSize=15&query=)"@en ; rdfs:label "Has anatomic site" ; "specimen.anatomic_site_concept_id#223 AS Concept" . ### https://w3id.org/omop/ontology/has_ancestor rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "ancestor" ; rdfs:comment "For Concept Ancestor: The Concept Id for the higher-level concept that forms the ancestor in the relationship."@en ; rdfs:label "Has ancestor" ; "concept_ancestor.ancestor_concept_id#381 AS Concept" . ### https://w3id.org/omop/ontology/has_care_site rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "care_site" ; rdfs:comment "For Person: The Care Site refers to where the Provider typically provides the primary care."@en , "For Provider: This is the CARE_SITE_ID for the location that the provider primarily practices in. If a Provider has more than one Care Site, the main or most often exerted CARE_SITE_ID should be recorded."@en , "For Visit Detail: This field provides information about the Care Site where the Visit Detail took place. There should only be one Care Site associated with a Visit Detail."@en , "For Visit Occurrence: This field provides information about the Care Site where the Visit took place. There should only be one Care Site associated with a Visit."@en ; rdfs:label "Has care site" ; "person.care_site_id#11 AS CareSite" , "provider.care_site_id#258 AS CareSite" , "visit_detail.care_site_id#50 AS CareSite" , "visit_occurrence.care_site_id#33 AS CareSite" . ### https://w3id.org/omop/ontology/has_cause rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "cause" ; rdfs:comment "For Death: This is the Standard Concept representing the Person's cause of death, if available. There is no specified domain for this concept, just choose the Standard Concept Id that best represents the person's cause of death."@en ; rdfs:label "Has cause" ; "death.cause_concept_id#182 AS Concept" . ### https://w3id.org/omop/ontology/has_cause_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "cause_source" ; rdfs:comment "For Death: If the cause of death was coded using a Vocabulary present in the OMOP Vocabularies (not necessarily a standard concept) put the CONCEPT_ID representing the cause of death here."@en ; rdfs:label "Has cause source" ; "death.cause_source_concept_id#184 AS Concept" . ### https://w3id.org/omop/ontology/has_cdm_version_concept rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "cdm_version_concept" ; rdfs:comment "For Cdm Source: The Concept Id representing the version of the CDM. You can find all concepts that represent the CDM versions using the query: `SELECT * FROM CONCEPT WHERE VOCABULARY_ID = 'CDM' AND CONCEPT_CLASS = 'CDM'`"@en ; rdfs:label "Has cdm version concept" ; "cdm_source.cdm_version_concept_id#343 AS Concept" . ### https://w3id.org/omop/ontology/has_class rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; "class" ; rdfs:comment "For Concept: The attribute or concept class of the Concept. Examples are 'Clinical Drug', 'Ingredient', 'Clinical Finding' etc."@en , "For Note: A Standard Concept Id representing the HL7 LOINC Document Type Vocabulary classification of the note. Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&conceptClass=Doc+Kind&conceptClass=Doc+Role&conceptClass=Doc+Setting&conceptClass=Doc+Subject+Matter&conceptClass=Doc+Type+of+Service&domain=Meas+Value&page=1&pageSize=15&query=). This Concept can alternatively be represented by concepts with the relationship 'Kind of (LOINC)' to [706391](https://athena.ohdsi.org/search-terms/terms/706391) (Note)."@en ; rdfs:label "Has class" ; "concept.concept_class_id#349 AS ConceptClass" , "note.note_class_concept_id#190 AS Concept" . ### https://w3id.org/omop/ontology/has_concept rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "concept" ; rdfs:comment "For Concept Class: A Concept that represents the Concept Class."@en , "For Condition Era: The Concept Id representing the Condition."@en , "For Condition Occurrence: The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition The CONCEPT_ID that the CONDITION_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of \"Condition\" should go in this table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Condition&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Device Exposure: The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to. The CONCEPT_ID that the DEVICE_SOURCE_VALUE maps to."@en , "For Domain: A Concept representing the Domain Concept the DOMAIN record belongs to."@en , "For Dose Era: The Concept Id representing the specific drug ingredient."@en , "For Drug Era: The drug_concept_id should conform to the concept class 'ingredient' as the drug_era is an era of time where a person is exposed to a particular drug ingredient."@en , "For Drug Exposure: The DRUG_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a drug product or molecule otherwise introduced to the body. The drug concepts can have a varying degree of information about drug strength and dose. This information is relevant in the context of quantity and administration information in the subsequent fields plus strength information from the DRUG_STRENGTH table, provided as part of the standard vocabulary download. The CONCEPT_ID that the DRUG_SOURCE_VALUE maps to. The concept id should be derived either from mapping from the source concept id or by picking the drug concept representing the most amount of detail you have. Records whose source values map to standard concepts with a domain of Drug should go in this table. When the Drug Source Value of the code cannot be translated into Standard Drug Concept IDs, a Drug exposure entry is stored with only the corresponding SOURCE_CONCEPT_ID and DRUG_SOURCE_VALUE and a DRUG_CONCEPT_ID of 0. The Drug Concept with the most detailed content of information is preferred during the mapping process. These are indicated in the CONCEPT_CLASS_ID field of the Concept and are recorded in the following order of precedence: Marketed Product, Branded Pack, Clinical Pack, Branded Drug, Clinical Drug, Branded Drug Component, Clinical Drug Component, Branded Drug Form, Clinical Drug Form, and only if no other information is available Ingredient. Note: If only the drug class is known, the DRUG_CONCEPT_ID field should contain 0. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Drug&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Drug Strength: The Concept representing the Branded Drug or Clinical Drug Product."@en , "For Measurement: The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a measurement. The CONCEPT_ID that the MEASUREMENT_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of �Measurement� should go in this table."@en , "For Observation: The OBSERVATION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. The CONCEPT_ID that the OBSERVATION_SOURCE_CONCEPT_ID maps to. There is no specified domain that the Concepts in this table must adhere to. The only rule is that records with Concepts in the Condition, Procedure, Drug, Measurement, or Device domains MUST go to the corresponding table."@en , "For Procedure Occurrence: The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure The CONCEPT_ID that the PROCEDURE_SOURCE_VALUE maps to. Only records whose source values map to standard concepts with a domain of \"Procedure\" should go in this table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Procedure&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Relationship: A foreign key that refers to an identifier in the [CONCEPT](https://ohdsi.github.io/CommonDataModel/cdm54.html#concept) table for the unique relationship concept."@en , "For Specimen: The standard CONCEPT_ID that the SPECIMEN_SOURCE_VALUE maps to in the specimen domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Specimen&standardConcept=Standard&page=1&pageSize=15&query=)"@en , "For Visit Detail: This field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain. Populate this field based on the kind of visit that took place for the person. For example this could be \"Inpatient Visit\", \"Outpatient Visit\", \"Ambulatory Visit\", etc. This table will contain standard concepts in the Visit domain. These concepts are arranged in a hierarchical structure to facilitate cohort definitions by rolling up to generally familiar Visits adopted in most healthcare systems worldwide. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Visit Occurrence: This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain. Populate this field based on the kind of visit that took place for the person. For example this could be \"Inpatient Visit\", \"Outpatient Visit\", \"Ambulatory Visit\", etc. This table will contain standard concepts in the Visit domain. These concepts are arranged in a hierarchical structure to facilitate cohort definitions by rolling up to generally familiar Visits adopted in most healthcare systems worldwide. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Vocabulary: A Concept that represents the Vocabulary the VOCABULARY record belongs to."@en ; rdfs:label "Has concept" ; "concept_class.concept_class_concept_id#365 AS Concept" , "concept_synonym.concept_id#378 AS Concept" , "condition_era.condition_concept_id#321 AS Concept" , "condition_occurrence.condition_concept_id#62 AS Concept" , "device_exposure.device_concept_id#117 AS Concept" , "domain.domain_concept_id#362 AS Concept" , "dose_era.drug_concept_id#314 AS Concept" , "drug_era.drug_concept_id#307 AS Concept" , "drug_exposure.drug_concept_id#78 AS Concept" , "drug_strength.drug_concept_id#394 AS Concept" , "measurement.measurement_concept_id#136 AS Concept" , "metadata.metadata_concept_id#326 AS Concept" , "note_nlp.note_nlp_concept_id#207 AS Concept" , "observation.observation_concept_id#159 AS Concept" , "procedure_occurrence.procedure_concept_id#101 AS Concept" , "relationship.relationship_concept_id#377 AS Concept" , "specimen.specimen_concept_id#217 AS Concept" , "visit_detail.visit_detail_concept_id#43 AS Concept" , "visit_occurrence.visit_concept_id#26 AS Concept" , "vocabulary.vocabulary_concept_id#359 AS Concept" . ### https://w3id.org/omop/ontology/has_condition_era rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "condition_eras" ; rdfs:label "Has condition era" ; "condition_era.person_id#320 AS Person" . ### https://w3id.org/omop/ontology/has_condition_occurrence rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "condition_occurrences" ; rdfs:comment "reversed relation, For Condition Occurrence: The PERSON_ID of the PERSON for whom the condition is recorded."@en , "reversed relation, For Condition Occurrence: The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit. Same rules apply as for the VISIT_OCCURRENCE_ID."@en , "reversed relation, For Condition Occurrence: The visit during which the condition occurred. Depending on the structure of the source data, this may have to be determined based on dates. If a CONDITION_START_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the CONDITION_OCCURRENCE record."@en ; rdfs:label "Has condition occurrence" ; "condition_occurrence.person_id#61 AS Person" , "condition_occurrence.visit_detail_id#72 AS VisitDetail" , "condition_occurrence.visit_occurrence_id#71 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_country rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "country" ; rdfs:comment "For Location: The Concept Id representing the country. Values should conform to the [Geography](https://athena.ohdsi.org/search-terms/terms?domain=Geography&standardConcept=Standard&page=1&pageSize=15&query=&boosts) domain."@en ; rdfs:label "Has country" ; "location.country_concept_id#243 AS Concept" . ### https://w3id.org/omop/ontology/has_currency rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "currency" ; rdfs:label "Has currency" ; "cost.currency_concept_id#287 AS Concept" . ### https://w3id.org/omop/ontology/has_death rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "deaths" ; rdfs:label "Has death" ; "death.person_id#178 AS Person" . ### https://w3id.org/omop/ontology/has_definition rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "definition" ; rdfs:label "Has definition" ; "cohort.cohort_definition_id#406 AS CohortDefinition" . ### https://w3id.org/omop/ontology/has_definition_type rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "definition_type" ; rdfs:comment "For Cohort Definition: Type defining what kind of Cohort Definition the record represents and how the syntax may be executed."@en ; rdfs:label "Has definition type" ; "cohort_definition.definition_type_concept_id#413 AS Concept" . ### https://w3id.org/omop/ontology/has_denominator_unit rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "denominator_unit" ; rdfs:comment "For Drug Strength: The Concept representing the denominator unit for the concentration of active ingredient."@en ; rdfs:label "Has denominator unit" ; "drug_strength.denominator_unit_concept_id#401 AS Concept" . ### https://w3id.org/omop/ontology/has_descendant rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "descendant" ; rdfs:comment "For Concept Ancestor: The Concept Id for the lower-level concept that forms the descendant in the relationship."@en ; rdfs:label "Has descendant" ; "concept_ancestor.descendant_concept_id#382 AS Concept" . ### https://w3id.org/omop/ontology/has_device_exposure rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "device_exposures" ; rdfs:comment "reversed relation, For Device Exposure: The Visit Detail during which the device was prescribed or given. To populate this field device exposures must be explicitly initiated in the visit detail record."@en , "reversed relation, For Device Exposure: The Visit during which the device was prescribed or given. To populate this field device exposures must be explicitly initiated in the visit."@en ; rdfs:label "Has device exposure" ; "device_exposure.person_id#116 AS Person" , "device_exposure.visit_detail_id#128 AS VisitDetail" , "device_exposure.visit_occurrence_id#127 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_discharged_to rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "discharged_to" ; rdfs:comment "For Visit Detail: Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for \"home\". Use concept id = 0 when a person is discharged to home. If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=)."@en , "For Visit Occurrence: Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for \"home\". Use concept id = 0 when a person is discharged to home. If available, map the discharged_to_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=). "@en ; rdfs:label "Has discharged to" ; "visit_detail.discharged_to_concept_id#56 AS Concept" , "visit_occurrence.discharged_to_concept_id#38 AS Concept" . ### https://w3id.org/omop/ontology/has_disease_status rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "disease_status" ; rdfs:label "Has disease status" ; "specimen.disease_status_concept_id#224 AS Concept" . ### https://w3id.org/omop/ontology/has_domain rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "domain" ; rdfs:comment "For Concept: A foreign key to the [DOMAIN](https://ohdsi.github.io/CommonDataModel/cdm54.html#domain) table the Concept belongs to."@en ; rdfs:label "Has domain" ; "concept.domain_id#347 AS Domain" , "cost.cost_domain_id#285 AS Domain" . ### https://w3id.org/omop/ontology/has_dose_era rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "dose_eras" ; rdfs:label "Has dose era" ; "dose_era.person_id#313 AS Person" . ### https://w3id.org/omop/ontology/has_drg rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "drg" ; rdfs:label "Has drg" ; "cost.drg_concept_id#303 AS Concept" . ### https://w3id.org/omop/ontology/has_drug_era rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "drug_eras" ; rdfs:label "Has drug era" ; "drug_era.person_id#306 AS Person" . ### https://w3id.org/omop/ontology/has_drug_exposure rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "drug_exposures" ; rdfs:comment "reversed relation, For Drug Exposure: The PERSON_ID of the PERSON for whom the drug dispensing or administration is recorded. This may be a system generated code."@en , "reversed relation, For Drug Exposure: The VISIT_DETAIL record during which the drug exposure occurred. For example, if the person was in the ICU at the time of the drug administration the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit. Same rules apply as for the VISIT_OCCURRENCE_ID."@en , "reversed relation, For Drug Exposure: The Visit during which the drug was prescribed, administered or dispensed. To populate this field drug exposures must be explicitly initiated in the visit."@en ; rdfs:label "Has drug exposure" ; "drug_exposure.person_id#77 AS Person" , "drug_exposure.visit_detail_id#94 AS VisitDetail" , "drug_exposure.visit_occurrence_id#93 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_encoding rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "encoding" ; rdfs:comment "For Note: This is the Concept representing the character encoding type. Put the Concept Id that represents the encoding character type here. Currently the only option is UTF-8 ([32678](https://athena.ohdsi.org/search-terms/terms/32678)). It the note is encoded in any other type, like ASCII then put 0."@en ; rdfs:label "Has encoding" ; "note.encoding_concept_id#193 AS Concept" . ### https://w3id.org/omop/ontology/has_ethnicity rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "ethnicity" ; rdfs:comment "For Person: This field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between \"Hispanic\" and \"Not Hispanic\". Races and ethnic backgrounds are not stored here. Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. [Accepted ethnicity concepts](http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&standardConcept=Standard&page=1&pageSize=15&query=)"@en ; rdfs:label "Has ethnicity" ; "person.ethnicity_concept_id#8 AS Concept" . ### https://w3id.org/omop/ontology/has_ethnicity_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "ethnicity_source" ; rdfs:comment "For Person: Due to the small number of options, this tends to be zero. If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here."@en ; rdfs:label "Has ethnicity source" ; "person.ethnicity_source_concept_id#18 AS Concept" . ### https://w3id.org/omop/ontology/has_event rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; "event" ; rdfs:comment "For Measurement: If the Measurement record is related to another record in the database, this field is the primary key of the linked record. Put the primary key of the linked record, if applicable, here."@en , "For Note: If the Note record is related to another record in the database, this field is the primary key of the linked record. Put the primary key of the linked record, if applicable, here."@en , "For Observation: If the Observation record is related to another record in the database, this field is the primary key of the linked record. Put the primary key of the linked record, if applicable, here. See the [ETL Conventions for the OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm54.html#observation) table for more details."@en ; rdfs:label "Has event" ; "cost.cost_event_id#284 AS Thing" , "measurement.measurement_event_id#155 AS Thing" , "note.note_event_id#199 AS Thing" , "observation.observation_event_id#176 AS Thing" . ### https://w3id.org/omop/ontology/has_event_field rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "event_field" ; rdfs:comment "For Note: If the Note record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from. Put the CONCEPT_ID that identifies which table and field the NOTE_EVENT_ID came from."@en ; rdfs:label "Has event field" ; "note.note_event_field_concept_id#200 AS Concept" . ### https://w3id.org/omop/ontology/has_gender rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "gender" ; rdfs:comment "For Person: This field is meant to capture the biological sex at birth of the Person. This field should not be used to study gender identity issues. Use the gender or sex value present in the data under the assumption that it is the biological sex at birth. If the source data captures gender identity it should be stored in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm54.html#observation) table. [Accepted gender concepts](http://athena.ohdsi.org/search-terms/terms?domain=Gender&standardConcept=Standard&page=1&pageSize=15&query=). Please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/tag_gender_concept_id.html) for detailed conventions on how to populate this field."@en , "For Provider: This field represents the recorded gender of the provider in the source data. If given, put a concept from the gender domain representing the recorded gender of the provider. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Gender&standardConcept=Standard&page=1&pageSize=15&query=)."@en ; rdfs:label "Has gender" ; "person.gender_concept_id#2 AS Concept" , "provider.gender_concept_id#260 AS Concept" . ### https://w3id.org/omop/ontology/has_gender_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "gender_source" ; rdfs:comment "For Person: Due to the small number of options, this tends to be zero. If the source data codes assigned sex at birth in a non-standard vocabulary, store the concept_id here."@en , "For Provider: This is often zero as many sites use proprietary codes to store provider gender. If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has gender source" ; "person.gender_source_concept_id#14 AS Concept" , "provider.gender_source_concept_id#265 AS Concept" . ### https://w3id.org/omop/ontology/has_ingredient rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "ingredient" ; rdfs:comment "For Drug Strength: The Concept representing the active ingredient contained within the drug product. Combination Drugs will have more than one record in this table, one for each active Ingredient."@en ; rdfs:label "Has ingredient" ; "drug_strength.ingredient_concept_id#395 AS Concept" . ### https://w3id.org/omop/ontology/has_language rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "language" ; rdfs:comment "For Note: The language of the note. Use Concepts that are descendants of the concept [4182347](https://athena.ohdsi.org/search-terms/terms/4182347) (World Languages)."@en ; rdfs:label "Has language" ; "concept_synonym.language_concept_id#380 AS Concept" , "note.language_concept_id#194 AS Concept" . ### https://w3id.org/omop/ontology/has_location rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "location" ; rdfs:comment "For Care Site: The location_id from the LOCATION table representing the physical location of the care_site."@en , "For Person: The location refers to the physical address of the person. This field should capture the last known location of the person. Put the location_id from the [LOCATION](https://ohdsi.github.io/CommonDataModel/cdm54.html#location) table here that represents the most granular location information for the person. For additional information on how to populate this field, please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/populate_person_location_id.html)."@en ; rdfs:label "Has location" ; "care_site.location_id#250 AS Location" , "person.location_id#9 AS Location" . ### https://w3id.org/omop/ontology/has_meas_event_field rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "meas_event_field" ; rdfs:comment "For Measurement: If the Measurement record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from. Put the CONCEPT_ID that identifies which table and field the MEASUREMENT_EVENT_ID came from."@en ; rdfs:label "Has meas event field" ; "measurement.meas_event_field_concept_id#156 AS Concept" . ### https://w3id.org/omop/ontology/has_measurement rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "measurements" ; rdfs:comment "reversed relation, For Measurement: The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code."@en , "reversed relation, For Measurement: The VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit. Same rules apply as for the VISIT_OCCURRENCE_ID."@en , "reversed relation, For Measurement: The visit during which the Measurement occurred. Depending on the structure of the source data, this may have to be determined based on dates. If a MEASUREMENT_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the measurement record. If a measurement is related to a visit explicitly in the source data, it is possible that the result date of the Measurement falls outside of the bounds of the Visit dates."@en ; rdfs:label "Has measurement" ; "measurement.person_id#135 AS Person" , "measurement.visit_detail_id#149 AS VisitDetail" , "measurement.visit_occurrence_id#148 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_modifier rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "modifier" ; rdfs:comment "For Procedure Occurrence: The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review. It is up to the ETL to choose how to map modifiers if they exist in source data. These concepts are typically distinguished by 'Modifier' concept classes (e.g., 'CPT4 Modifier' as part of the 'CPT4' vocabulary). If there is more than one modifier on a record, one should be chosen that pertains to the procedure rather than provider. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?conceptClass=CPT4+Modifier&conceptClass=HCPCS+Modifier&vocabulary=CPT4&vocabulary=HCPCS&standardConcept=Standard&page=1&pageSize=15&query=)."@en ; rdfs:label "Has modifier" ; "procedure_occurrence.modifier_concept_id#107 AS Concept" . ### https://w3id.org/omop/ontology/has_note rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "notes" ; rdfs:comment "reversed relation, For Note: The Visit Detail during which the note was written."@en , "reversed relation, For Note: The Visit during which the note was written."@en ; rdfs:label "Has note" ; "note.person_id#186 AS Person" , "note.visit_detail_id#197 AS VisitDetail" , "note.visit_occurrence_id#196 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_note_nlp rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "note_nlps" ; rdfs:comment "reversed relation, For Note Nlp: This is the NOTE_ID for the NOTE record the NLP record is associated to."@en ; rdfs:label "Has note nlp" ; "note_nlp.note_id#202 AS Note" . ### https://w3id.org/omop/ontology/has_numerator_unit rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "numerator_unit" ; rdfs:comment "For Drug Strength: The Concept representing the Unit of measure for the concentration of active ingredient."@en ; rdfs:label "Has numerator unit" ; "drug_strength.numerator_unit_concept_id#399 AS Concept" . ### https://w3id.org/omop/ontology/has_obs_event_field rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "obs_event_field" ; rdfs:comment "For Observation: If the Observation record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from. Put the CONCEPT_ID that identifies which table and field the OBSERVATION_EVENT_ID came from."@en ; rdfs:label "Has obs event field" ; "observation.obs_event_field_concept_id#177 AS Concept" . ### https://w3id.org/omop/ontology/has_observation rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "observations" ; rdfs:comment "reversed relation, For Observation: The PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code."@en , "reversed relation, For Observation: The VISIT_DETAIL record during which the Observation occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit. Same rules apply as for the VISIT_OCCURRENCE_ID."@en , "reversed relation, For Observation: The visit during which the Observation occurred. Depending on the structure of the source data, this may have to be determined based on dates. If an OBSERVATION_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the observation record. If an observation is related to a visit explicitly in the source data, it is possible that the result date of the Observation falls outside of the bounds of the Visit dates."@en ; rdfs:label "Has observation" ; "observation.person_id#158 AS Person" , "observation.visit_detail_id#170 AS VisitDetail" , "observation.visit_occurrence_id#169 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_observation_period rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "observation_periods" ; rdfs:comment "reversed relation, For Observation Period: The Person ID of the PERSON record for which the Observation Period is recorded."@en ; rdfs:label "Has observation period" ; "observation_period.person_id#20 AS Person" . ### https://w3id.org/omop/ontology/has_operator rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "operator" ; rdfs:comment "For Measurement: The meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/4172703) for '=' is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it's important when devising analyses to not to forget testing for the content of this field for values different from =. Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&standardConcept=Standard&page=1&pageSize=15&query=). The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there's an exact numeric value given (instead of putting '=') or there's no numeric value at all."@en ; rdfs:label "Has operator" ; "measurement.operator_concept_id#141 AS Concept" . ### https://w3id.org/omop/ontology/has_parent_visit_detail rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "parent_visit_detail" ; rdfs:comment "For Visit Detail: Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship. If there are multiple nested levels to how Visits are represented in the source, the VISIT_DETAIL_PARENT_ID can be used to record this relationship."@en ; rdfs:label "Has parent visit detail" ; "visit_detail.parent_visit_detail_id#58 AS VisitDetail" . ### https://w3id.org/omop/ontology/has_payer rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "payer" ; rdfs:comment "For Payer Plan Period: This field represents the organization who reimburses the provider which administers care to the Person. Map the payer directly to a standard CONCEPT_ID with the domain_id of 'Payer' ([Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=)). This vocabulary is not exhaustive so if there is a value missing, please see the [custom concepts](https://ohdsi.github.io/CommonDataModel/customConcepts.html) page."@en ; rdfs:label "Has payer" ; "payer_plan_period.payer_concept_id#270 AS Concept" . ### https://w3id.org/omop/ontology/has_payer_plan_period rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "payer_plan_period" ; rdfs:comment "reversed relation, For Payer Plan Period: The Person covered by the Plan. A single Person can have multiple, overlapping, PAYER_PLAN_PERIOD records"@en ; rdfs:label "Has payer plan period" ; "cost.payer_plan_period_id#299 AS PayerPlanPeriod" , "payer_plan_period.person_id#267 AS Person" . ### https://w3id.org/omop/ontology/has_payer_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "payer_source" ; rdfs:comment "For Payer Plan Period: If the source data codes the Payer in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has payer source" ; "payer_plan_period.payer_source_concept_id#272 AS Concept" . ### https://w3id.org/omop/ontology/has_period_type rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "period_type" ; rdfs:comment "For Observation Period: This field can be used to determine the provenance of the Observation Period as in whether the period was determined from an insurance enrollment file, EHR healthcare encounters, or other sources. Choose the observation_period_type_concept_id that best represents how the period was determined. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en ; rdfs:label "Has period type" ; "observation_period.period_type_concept_id#23 AS Concept" . ### https://w3id.org/omop/ontology/has_place_of_service rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "place_of_service" ; rdfs:comment "For Care Site: This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit. Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=2&pageSize=15&query=). For information about how to populate this field please see the [THEMIS Conventions](https://ohdsi.github.io/Themis/tag_place_of_service.html)."@en ; rdfs:label "Has place of service" ; "care_site.place_of_service_concept_id#249 AS Concept" . ### https://w3id.org/omop/ontology/has_plan rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "plan" ; rdfs:comment "For Payer Plan Period: This field represents the specific health benefit Plan the Person is enrolled in. Map the Plan directly to a standard CONCEPT_ID in the 'Plan' vocabulary ([Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Plan&standardConcept=Standard&page=1&pageSize=15&query=)). This vocabulary is not exhaustive so if there is a value missing, please see the [custom concepts](https://ohdsi.github.io/CommonDataModel/customConcepts.html) page."@en ; rdfs:label "Has plan" ; "payer_plan_period.plan_concept_id#273 AS Concept" . ### https://w3id.org/omop/ontology/has_plan_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "plan_source" ; rdfs:comment "For Payer Plan Period: If the source data codes the Plan in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has plan source" ; "payer_plan_period.plan_source_concept_id#275 AS Concept" . ### https://w3id.org/omop/ontology/has_preceding_visit_detail rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "preceding_visit_detail" ; rdfs:comment "For Visit Detail: Use this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between. The PRECEDING_VISIT_DETAIL_ID can be used to link a visit immediately preceding the current Visit Detail. Note this is not symmetrical, and there is no such thing as a \"following_visit_id\"."@en ; rdfs:label "Has preceding visit detail" ; "visit_detail.preceding_visit_detail_id#57 AS VisitDetail" . ### https://w3id.org/omop/ontology/has_preceding_visit_occurrence rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "preceding_visit_occurrence" ; rdfs:comment "For Visit Occurrence: Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between. This field can be used to link a visit immediately preceding the current visit. Note this is not symmetrical, and there is no such thing as a \"following_visit_id\"."@en ; rdfs:label "Has preceding visit occurrence" ; "visit_occurrence.preceding_visit_occurrence_id#40 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_procedure_occurrence rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "procedure_occurrences" ; rdfs:comment "reversed relation, For Procedure Occurrence: The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code."@en , "reversed relation, For Procedure Occurrence: The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit. Same rules apply as for the VISIT_OCCURRENCE_ID."@en , "reversed relation, For Procedure Occurrence: The visit during which the procedure occurred. Depending on the structure of the source data, this may have to be determined based on dates. If a PROCEDURE_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the PROCEDURE_OCCURRENCE record."@en ; rdfs:label "Has procedure occurrence" ; "procedure_occurrence.person_id#100 AS Person" , "procedure_occurrence.visit_detail_id#111 AS VisitDetail" , "procedure_occurrence.visit_occurrence_id#110 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_production rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; "production" ; rdfs:comment "For Device Exposure: This is the Production Identifier (UDI-PI) portion of the Unique Device Identification."@en ; rdfs:label "Has production" ; "device_exposure.production_id#124 AS Thing" . ### https://w3id.org/omop/ontology/has_provider rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "provider" ; rdfs:comment "For Condition Occurrence: The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record."@en , "For Device Exposure: The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record."@en , "For Drug Exposure: The Provider associated with drug record, e.g. the provider who wrote the prescription or the provider who administered the drug. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the ordering vs administering physician on an EHR record."@en , "For Measurement: The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record."@en , "For Note: The Provider who wrote the note. The ETL may need to make a determination on which provider to put here."@en , "For Observation: The provider associated with the observation record, e.g. the provider who ordered the test or the provider who recorded the result. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record."@en , "For Person: The Provider refers to the last known primary care provider (General Practitioner). Put the provider_id from the [PROVIDER](https://ohdsi.github.io/CommonDataModel/cdm54.html#provider) table of the last known general practitioner of the person. If there are multiple providers, it is up to the ETL to decide which to put here."@en , "For Procedure Occurrence: The provider associated with the procedure record, e.g. the provider who performed the Procedure. The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record."@en , "For Visit Detail: There will only be one provider per **visit** record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record. The additional providers associated to a Visit can be stored in this table where each VISIT_DETAIL record represents a different provider."@en , "For Visit Occurrence: There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table. If there are multiple providers associated with a visit, you will need to choose which one to put here. The additional providers can be stored in the [VISIT_DETAIL](https://ohdsi.github.io/CommonDataModel/cdm54.html#visit_detail) table."@en ; rdfs:label "Has provider" ; "condition_occurrence.provider_id#70 AS Provider" , "device_exposure.provider_id#126 AS Provider" , "drug_exposure.provider_id#92 AS Provider" , "measurement.provider_id#147 AS Provider" , "note.provider_id#195 AS Provider" , "observation.provider_id#168 AS Provider" , "person.provider_id#10 AS Provider" , "procedure_occurrence.provider_id#109 AS Provider" , "visit_detail.provider_id#49 AS Provider" , "visit_occurrence.provider_id#32 AS Provider" . ### https://w3id.org/omop/ontology/has_qualifier rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "qualifier" ; rdfs:comment "For Observation: This field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc. Use your best judgement as to what Concepts to use here and if they are necessary to accurately represent the clinical record. There is no restriction on the domain of these Concepts, they just need to be Standard."@en ; rdfs:label "Has qualifier" ; "observation.qualifier_concept_id#166 AS Concept" . ### https://w3id.org/omop/ontology/has_race rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "race" ; rdfs:comment "For Person: This field captures race or ethnic background of the person. Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. [Accepted Race Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Race&standardConcept=Standard&page=1&pageSize=15&query=)."@en ; rdfs:label "Has race" ; "person.race_concept_id#7 AS Concept" . ### https://w3id.org/omop/ontology/has_race_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "race_source" ; rdfs:comment "For Person: Due to the small number of options, this tends to be zero. If the source data codes race in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has race source" ; "person.race_source_concept_id#16 AS Concept" . ### https://w3id.org/omop/ontology/has_relationship rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; "relationship" ; rdfs:comment "For Concept Relationship: The relationship between CONCEPT_ID_1 and CONCEPT_ID_2. Please see the [Vocabulary Conventions](https://ohdsi.github.io/CommonDataModel/dataModelConventions.html#concept_relationships). for more information."@en ; rdfs:label "Has relationship" ; "concept_relationship.relationship_id#368 AS Relationship" , "fact_relationship.relationship_concept_id#234 AS Concept" . ### https://w3id.org/omop/ontology/has_revenue_code rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "revenue_code" ; rdfs:label "Has revenue code" ; "cost.revenue_code_concept_id#301 AS Concept" . ### https://w3id.org/omop/ontology/has_reverse_relationship rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; "reverse_relationship" ; rdfs:comment "For Relationship: The identifier for the relationship used to define the reverse relationship between two concepts."@en ; rdfs:label "Has reverse relationship" ; "relationship.reverse_relationship_id#376 AS Thing" . ### https://w3id.org/omop/ontology/has_route rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "route" ; rdfs:comment "For Drug Exposure: The standard CONCEPT_ID that the ROUTE_SOURCE_VALUE maps to in the route domain. This is meant to represent the route of administration of the drug. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Route&standardConcept=Standard&page=1&pageSize=15&query=)"@en ; rdfs:label "Has route" ; "drug_exposure.route_concept_id#90 AS Concept" . ### https://w3id.org/omop/ontology/has_section rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "section" ; rdfs:comment "For Note Nlp: The SECTION_CONCEPT_ID should be used to represent the note section contained in the NOTE_NLP record. These concepts can be found as parts of document panels and are based on the type of note written, i.e. a discharge summary. These panels can be found as concepts with the relationship 'Subsumes' to CONCEPT_ID [45875957](https://athena.ohdsi.org/search-terms/terms/45875957)."@en ; rdfs:label "Has section" ; "note_nlp.section_concept_id#203 AS Concept" . ### https://w3id.org/omop/ontology/has_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; "source" ; rdfs:comment "For Condition Occurrence: This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the CONDITION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Device Exposure: This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the DEVICE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Drug Exposure: This is the concept representing the drug source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Drug necessary for a given analytic use case. Consider using DRUG_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the DRUG_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Measurement: This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the MEASUREMENT_SOURCE_VALUE is coded in the source data using a vocabulary supported by OMOP Standardized Vocabularies, insert the CONCEPT_ID representing the source value here."@en , "For Observation: This is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Procedure Occurrence: This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the PROCEDURE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Source To Concept Map: A foreign key to the Source Concept that is being translated into a Standard Concept. This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings."@en , "For Specimen: This is the identifier for the specimen from the source system."@en , "For Visit Detail: If the VISIT_DETAIL_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Visit Occurrence: If the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en ; rdfs:label "Has source" ; "condition_occurrence.condition_source_concept_id#74 AS Concept" , "device_exposure.device_source_concept_id#130 AS Concept" , "drug_exposure.drug_source_concept_id#96 AS Concept" , "measurement.measurement_source_concept_id#151 AS Concept" , "note_nlp.note_nlp_source_concept_id#208 AS Concept" , "observation.observation_source_concept_id#172 AS Concept" , "procedure_occurrence.procedure_source_concept_id#113 AS Concept" , "source_to_concept_map.source_concept_id#386 AS Concept" , "specimen.specimen_source_id#225 AS Thing" , "visit_detail.visit_detail_source_concept_id#52 AS Concept" , "visit_occurrence.visit_source_concept_id#35 AS Concept" . ### https://w3id.org/omop/ontology/has_source_vocabulary rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "source_vocabulary" ; rdfs:comment "For Source To Concept Map: A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept."@en ; rdfs:label "Has source vocabulary" ; "source_to_concept_map.source_vocabulary_id#387 AS Vocabulary" . ### https://w3id.org/omop/ontology/has_specialty rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "specialty" ; rdfs:comment "For Provider: This field either represents the most common specialty that occurs in the data or the most specific concept that represents all specialties listed, should the provider have more than one. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists. If a Provider has more than one Specialty, there are two options: 1. Choose a concept_id which is a common ancestor to the multiple specialties, or, 2. Choose the specialty that occurs most often for the provider. Concepts in this field should be Standard with a domain of Provider. [Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Provider&standardConcept=Standard&page=1&pageSize=15&query=)."@en ; rdfs:label "Has specialty" ; "provider.specialty_concept_id#257 AS Concept" . ### https://w3id.org/omop/ontology/has_specialty_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "specialty_source" ; rdfs:comment "For Provider: This is often zero as many sites use proprietary codes to store physician speciality. If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has specialty source" ; "provider.specialty_source_concept_id#263 AS Concept" . ### https://w3id.org/omop/ontology/has_specimen rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "specimens" ; rdfs:comment "reversed relation, For Specimen: The person from whom the specimen is collected."@en ; rdfs:label "Has specimen" ; "specimen.person_id#216 AS Person" . ### https://w3id.org/omop/ontology/has_sponsor rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "sponsor" ; rdfs:comment "For Payer Plan Period: This field represents the sponsor of the Plan who finances the Plan. This includes self-insured, small group health plan and large group health plan. Map the sponsor directly to a standard CONCEPT_ID with the domain_id of 'Sponsor' ([Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=)). This vocabulary is not exhaustive so if there is a value missing, please see the [custom concepts](https://ohdsi.github.io/CommonDataModel/customConcepts.html) page."@en ; rdfs:label "Has sponsor" ; "payer_plan_period.sponsor_concept_id#276 AS Concept" . ### https://w3id.org/omop/ontology/has_sponsor_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "sponsor_source" ; rdfs:comment "For Payer Plan Period: If the source data codes the sponsor in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has sponsor source" ; "payer_plan_period.sponsor_source_concept_id#278 AS Concept" . ### https://w3id.org/omop/ontology/has_status rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "status" ; rdfs:comment "For Condition Occurrence: This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others. Choose the Concept in the Condition Status domain that best represents the point during the visit when the diagnosis was given. These can include admitting diagnosis, principal diagnosis, and secondary diagnosis. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Condition+Status&standardConcept=Standard&page=1&pageSize=15&query=)."@en ; rdfs:label "Has status" ; "condition_occurrence.condition_status_concept_id#68 AS Concept" . ### https://w3id.org/omop/ontology/has_stop_reason_concept rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "stop_reason_concept" ; rdfs:comment "For Payer Plan Period: This field represents the reason the Person left the Plan, if known. Map the stop reason directly to a standard CONCEPT_ID with a domain of 'Plan Stop Reason' ([Accepted Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&standardConcept=Standard&page=1&pageSize=15&query=)). If one does not exist visit the [Custom Concepts](https://ohdsi.github.io/CommonDataModel/customConcepts.html) pate for more information."@en ; rdfs:label "Has stop reason concept" ; "payer_plan_period.stop_reason_concept_id#280 AS Concept" . ### https://w3id.org/omop/ontology/has_stop_reason_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "stop_reason_source" ; rdfs:comment "For Payer Plan Period: If the source data codes the stop reason in an OMOP supported vocabulary store the concept_id here."@en ; rdfs:label "Has stop reason source" ; "payer_plan_period.stop_reason_source_concept_id#282 AS Concept" . ### https://w3id.org/omop/ontology/has_subject rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; "subject" ; rdfs:comment "For Cohort Definition: This field contains a Concept that represents the domain of the subjects that are members of the cohort (e.g., Person, Provider, Visit)."@en ; rdfs:label "Has subject" ; "cohort.subject_id#407 AS Thing" , "cohort_definition.subject_concept_id#415 AS Concept" . ### https://w3id.org/omop/ontology/has_target rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "target" ; rdfs:comment "For Source To Concept Map: The target Concept to which the source code is being mapped."@en ; rdfs:label "Has target" ; "source_to_concept_map.target_concept_id#389 AS Concept" . ### https://w3id.org/omop/ontology/has_target_vocabulary rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "target_vocabulary" ; rdfs:comment "For Source To Concept Map: The Vocabulary of the target Concept."@en ; rdfs:label "Has target vocabulary" ; "source_to_concept_map.target_vocabulary_id#390 AS Vocabulary" . ### https://w3id.org/omop/ontology/has_type rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "type" ; rdfs:comment "For Condition Occurrence: This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources. Choose the CONDITION_TYPE_CONCEPT_ID that best represents the provenance of the record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Death: This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc. Use the type concept that reflects the source of the death record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Device Exposure: You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR. Choose the device_type_concept_id that best represents the provenance of the record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Drug Exposure: You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure, etc. Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Measurement: This field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources. Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Note: The provenance of the note. Most likely this will be EHR. Put the source system of the note, as in EHR record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Observation: This field can be used to determine the provenance of the Observation record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources. Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Procedure Occurrence: This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources. Choose the PROCEDURE_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. If a procedure is recorded as an EHR encounter, the PROCEDURE_TYPE_CONCEPT would be 'EHR encounter record'. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Specimen: Put the source of the specimen record, as in an EHR system. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Visit Detail: Use this field to understand the provenance of the visit detail record, or where the record comes from. Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en , "For Visit Occurrence: Use this field to understand the provenance of the visit record, or where the record comes from. Populate this field based on the provenance of the visit record, as in whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT)."@en ; rdfs:label "Has type" ; "condition_occurrence.condition_type_concept_id#67 AS Concept" , "cost.cost_type_concept_id#286 AS Concept" , "death.death_type_concept_id#181 AS Concept" , "device_exposure.device_type_concept_id#122 AS Concept" , "drug_exposure.drug_type_concept_id#84 AS Concept" , "measurement.measurement_type_concept_id#140 AS Concept" , "metadata.metadata_type_concept_id#327 AS Concept" , "note.note_type_concept_id#189 AS Concept" , "observation.observation_type_concept_id#162 AS Concept" , "procedure_occurrence.procedure_type_concept_id#106 AS Concept" , "specimen.specimen_type_concept_id#218 AS Concept" , "visit_detail.visit_detail_type_concept_id#48 AS Concept" , "visit_occurrence.visit_type_concept_id#31 AS Concept" . ### https://w3id.org/omop/ontology/has_unique_device rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; "unique_device" ; rdfs:comment "For Device Exposure: This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given. For medical devices that are regulated by the FDA, a Unique Device Identification (UDI) is provided if available in the data source and is recorded in the UNIQUE_DEVICE_ID field."@en ; rdfs:label "Has unique device" ; "device_exposure.unique_device_id#123 AS Thing" . ### https://w3id.org/omop/ontology/has_unit rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "unit" ; rdfs:comment "For Device Exposure: UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data. There is no standardization requirement for units associated with DEVICE_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit. If the source unit is NULL (applicable to cases when there's no numerical value or when it doesn't require a unit), keep unit_concept_id NULL as well. If there's no mapping of a source unit, populate unit_concept_id with 0."@en , "For Dose Era: The Concept Id representing the unit of the specific drug ingredient."@en , "For Measurement: At present, there isn't a prescribed unit for individual measurements, such as Hemoglobin A1C, meaning it's not obligatory to express these measurements as a percentage. UNIT_SOURCE_VALUES should be linked to a Standard Concept within the Unit domain that most accurately reflects the unit provided in the source data. If the source data does not include units, set UNIT_CONCEPT_ID to NULL. If units are provided but not mapped, set UNIT_CONCEPT_ID to 0. Otherwise, map the units to a CONCEPT_ID. Remember that units are case-sensitive in vocabulary."@en , "For Observation: There is currently no recommended unit for individual observation concepts. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data. There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit. If the source unit is NULL (applicable to cases when there's no numerical value or when it doesn't require a unit), keep unit_concept_id NULL as well. If there's no mapping of a source unit, populate unit_concept_id with 0."@en , "For Specimen: The unit for the quantity of the specimen. Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Unit&standardConcept=Standard&page=1&pageSize=15&query=). If the source unit is NULL (applicable to cases when there's no numerical value or when it doesn't require a unit), keep unit_concept_id NULL as well. If there's no mapping of a source unit, populate unit_concept_id with 0."@en ; rdfs:label "Has unit" ; "device_exposure.unit_concept_id#131 AS Concept" , "dose_era.unit_concept_id#315 AS Concept" , "measurement.unit_concept_id#144 AS Concept" , "observation.unit_concept_id#167 AS Concept" , "specimen.unit_concept_id#222 AS Concept" . ### https://w3id.org/omop/ontology/has_unit_source rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "unit_source" ; rdfs:comment "For Device Exposure: This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network. If the UNIT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en , "For Measurement: \"This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.\" If the UNIT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here."@en ; rdfs:label "Has unit source" ; "device_exposure.unit_source_concept_id#133 AS Concept" , "measurement.unit_source_concept_id#153 AS Concept" . ### https://w3id.org/omop/ontology/has_value_as_concept rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "value_as_concept" ; rdfs:comment "For Measurement: If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the 'Meas Value' domain. If there is no categorial result in the source data, set VALUE_AS_CONCEPT_ID to NULL, if there is a categorial result in a source data but without mapping, set VALUE_AS_CONCEPT_ID to 0, else map to a CONCEPT_ID."@en , "For Observation: It is possible that some records destined for the Observation table have two clinical ideas represented in one source code. This is common with ICD10 codes that describe a family history of some Condition, for example. In OMOP the Vocabulary breaks these two clinical ideas into two codes; one becomes the OBSERVATION_CONCEPT_ID and the other becomes the VALUE_AS_CONCEPT_ID. It is important when using the Observation table to keep this possibility in mind and to examine the VALUE_AS_CONCEPT_ID field for relevant information. Note that the value of VALUE_AS_CONCEPT_ID may be provided through mapping from a source Concept which contains the content of the Observation. In those situations, the CONCEPT_RELATIONSHIP table in addition to the 'Maps to' record contains a second record with the relationship_id set to 'Maps to value'. For example, ICD10 [Z82.4](https://athena.ohdsi.org/search-terms/terms/45581076) 'Family history of ischaemic heart disease and other diseases of the circulatory system' has a 'Maps to' relationship to [4167217](https://athena.ohdsi.org/search-terms/terms/4167217) 'Family history of clinical finding' as well as a 'Maps to value' record to [134057](https://athena.ohdsi.org/search-terms/terms/134057) 'Disorder of cardiovascular system'. If there's no categorial result in a source_data, set value_as_concept_id to NULL, if there is a categorial result in a source_data but without mapping, set value_as_concept_id to 0."@en ; rdfs:label "Has value as concept" ; "measurement.value_as_concept_id#143 AS Concept" , "metadata.value_as_concept_id#330 AS Concept" , "observation.value_as_concept_id#165 AS Concept" . ### https://w3id.org/omop/ontology/has_visit_detail rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; "visit_details" ; rdfs:comment "reversed relation, For Visit Detail: Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE. Put the VISIT_OCCURRENCE_ID that subsumes the VISIT_DETAIL record here."@en ; rdfs:label "Has visit detail" ; "visit_detail.person_id#42 AS Person" , "visit_detail.visit_occurrence_id#59 AS VisitOccurrence" . ### https://w3id.org/omop/ontology/has_visit_occurrence rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; "visit_occurrences" ; rdfs:label "Has visit occurrence" ; "visit_occurrence.person_id#25 AS Person" . ### https://w3id.org/omop/ontology/has_vocabulary rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; "vocabulary" ; rdfs:comment "For Concept: A foreign key to the [VOCABULARY](https://ohdsi.github.io/CommonDataModel/cdm54.html#vocabulary) table indicating from which source the Concept has been adapted."@en ; rdfs:label "Has vocabulary" ; "concept.vocabulary_id#348 AS Vocabulary" . ################################################################# # Data properties ################################################################# ### https://w3id.org/omop/ontology/abbreviation rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: The abbreviation of the CDM instance."@en ; rdfs:label "Abbreviation" ; "cdm_source.cdm_source_abbreviation#335 AS str" . ### https://w3id.org/omop/ontology/address_1 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Location: This is the first line of the address."@en ; rdfs:label "Address 1" ; "location.address_1#236 AS str" . ### https://w3id.org/omop/ontology/address_2 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Location: This is the second line of the address"@en ; rdfs:label "Address 2" ; "location.address_2#237 AS str" . ### https://w3id.org/omop/ontology/admitted_from_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Visit Detail: This information may be called something different in the source data but the field is meant to contain a value indicating where a person was admitted from. Typically this applies only to visits that have a length of stay, like inpatient visits or long-term care visits."@en , "For Visit Occurrence: This information may be called something different in the source data but the field is meant to contain a value indicating where a person was admitted from. Typically this applies only to visits that have a length of stay, like inpatient visits or long-term care visits."@en ; rdfs:label "Admitted from source value" ; "visit_detail.admitted_from_source_value#54 AS str" , "visit_occurrence.admitted_from_source_value#37 AS str" . ### https://w3id.org/omop/ontology/amount_allowed rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Amount allowed" ; "cost.amount_allowed#300 AS float" . ### https://w3id.org/omop/ontology/amount_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Drug Strength: The numeric value or the amount of active ingredient contained within the drug product."@en ; rdfs:label "Amount value" ; "drug_strength.amount_value#396 AS float" . ### https://w3id.org/omop/ontology/anatomic_site_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Specimen: This is the site on the body where the specimen was taken from, as represented in the source."@en ; rdfs:label "Anatomic site source value" ; "specimen.anatomic_site_source_value#228 AS str" . ### https://w3id.org/omop/ontology/birth_datetime rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "For Person: This field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. For more information on how to populate this field, please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/person.html)."@en ; rdfs:label "Birth datetime" ; "person.birth_datetime#6 AS datetime" . ### https://w3id.org/omop/ontology/box_size rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Drug Strength: The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient."@en ; rdfs:label "Box size" ; "drug_strength.box_size#402 AS int" . ### https://w3id.org/omop/ontology/cause_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Death: If available, put the source code representing the cause of death here."@en ; rdfs:label "Cause source value" ; "death.cause_source_value#183 AS str" . ### https://w3id.org/omop/ontology/cdm_etl_reference rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: Version of the ETL script used. e.g. link to the Git release"@en ; rdfs:label "Cdm etl reference" ; "cdm_source.cdm_etl_reference#339 AS str" . ### https://w3id.org/omop/ontology/cdm_holder rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: The holder of the CDM instance."@en ; rdfs:label "Cdm holder" ; "cdm_source.cdm_holder#336 AS str" . ### https://w3id.org/omop/ontology/cdm_release_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Cdm Source: The date the ETL script was completed. Typically this is after the source_release_date."@en ; rdfs:label "Cdm release date" ; "cdm_source.cdm_release_date#341 AS date" . ### https://w3id.org/omop/ontology/cdm_version rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: Version of the OMOP CDM used as string. e.g. v5.4"@en ; rdfs:label "Cdm version" ; "cdm_source.cdm_version#342 AS str" . ### https://w3id.org/omop/ontology/city rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "City" ; "location.city#238 AS str" . ### https://w3id.org/omop/ontology/code rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Concept: The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies."@en ; rdfs:label "Code" ; "concept.concept_code#351 AS str" . ### https://w3id.org/omop/ontology/cohort_initiation_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Cohort Definition: A date to indicate when the Cohort was initiated in the COHORT table."@en ; rdfs:label "Cohort initiation date" ; "cohort_definition.cohort_initiation_date#416 AS date" . ### https://w3id.org/omop/ontology/concept_id_1 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Concept id 1" ; "concept_relationship.concept_id_1#366 AS int" . ### https://w3id.org/omop/ontology/concept_id_2 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Concept id 2" ; "concept_relationship.concept_id_2#367 AS int" . ### https://w3id.org/omop/ontology/country_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Location: The name of the country."@en ; rdfs:label "Country source value" ; "location.country_source_value#244 AS str" . ### https://w3id.org/omop/ontology/county rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "County" ; "location.county#241 AS str" . ### https://w3id.org/omop/ontology/date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Death: The date the person was deceased. If the precise date include day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day. For additional conventions related to this field, please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/tag_death_date.html). "@en , "For Measurement: Use this date to determine the date of the measurement. If there are multiple dates in the source data associated with a record such as order_date, draw_date, and result_date, choose the one that is closest to the date the sample was drawn from the patient."@en , "For Note Nlp: The date of the note processing."@en , "For Note: The date the note was recorded."@en , "For Observation: The date of when the Observation was obtained. Depending on what the Observation represents this could be the date of a lab test, the date of a survey, or the date a patient's family history was taken. For some observations the ETL may need to make a choice as to which date to choose."@en , "For Procedure Occurrence: Use this date to determine the date the procedure started. This is meant to be the **start date** of the procedure. It will be renamed in a future version to **PROCEDURE_START_DATE**."@en , "For Specimen: The date the specimen was collected."@en ; rdfs:label "Date" ; "death.death_date#179 AS date" , "measurement.measurement_date#137 AS date" , "metadata.metadata_date#332 AS date" , "note.note_date#187 AS date" , "note_nlp.nlp_date#210 AS date" , "observation.observation_date#160 AS date" , "procedure_occurrence.procedure_date#102 AS date" , "specimen.specimen_date#219 AS date" . ### https://w3id.org/omop/ontology/datetime rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "For Death: If you have date and time of death, populate death_datetime, otherwise leave NULL"@en , "For Measurement: This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Note Nlp: The date and time of the note processing."@en , "For Note: If time is not given set the time to midnight."@en , "For Observation: If no time is given set to midnight (00:00:00)."@en , "For Procedure Occurrence: If the procedure has a start time in the native date, use this field to house that information. This will be renamed in a future version to **PROCEDURE_START_DATETIME**."@en ; rdfs:label "Datetime" ; "death.death_datetime#180 AS datetime" , "measurement.measurement_datetime#138 AS datetime" , "metadata.metadata_datetime#333 AS datetime" , "note.note_datetime#188 AS datetime" , "note_nlp.nlp_datetime#211 AS datetime" , "observation.observation_datetime#161 AS datetime" , "procedure_occurrence.procedure_datetime#103 AS datetime" , "specimen.specimen_datetime#220 AS datetime" . ### https://w3id.org/omop/ontology/day_of_birth rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Person: For data sources that provide the precise date of birth, the day should be extracted and stored in this field."@en ; rdfs:label "Day of birth" ; "person.day_of_birth#5 AS int" . ### https://w3id.org/omop/ontology/days_supply rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Drug Exposure: The number of days of supply of the medication as recorded in the original prescription or dispensing record. Days supply can differ from actual drug duration (i.e. prescribed days supply vs actual exposure).\",\"The field should be left empty if the source data does not contain a verbatim days_supply, and should not be calculated from other fields.

Negative values are not allowed. If the source has negative days supply the record should be dropped as it is unknown if the patient actually took the drug. Several actions are possible: 1) record is not trustworthy and we remove the record entirely. 2) we trust the record and leave days_supply empty or 3) record needs to be combined with other record (e.g. reversal of prescription). High values (>365 days) should be investigated. If considered an error in the source data (e.g. typo), the value needs to be excluded to prevent creation of unrealistic long eras."@en ; rdfs:label "Days supply" ; "drug_exposure.days_supply#88 AS int" . ### https://w3id.org/omop/ontology/dea rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Provider: This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances."@en ; rdfs:label "Dea" ; "provider.dea#256 AS str" . ### https://w3id.org/omop/ontology/defines_ancestry rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Relationship: Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0."@en ; rdfs:label "Defines ancestry" ; "relationship.defines_ancestry#375 AS str" . ### https://w3id.org/omop/ontology/denominator_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Drug Strength: The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.)."@en ; rdfs:label "Denominator value" ; "drug_strength.denominator_value#400 AS float" . ### https://w3id.org/omop/ontology/description rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cohort Definition: A complete description of the cohort."@en ; rdfs:label "Description" ; "cohort_definition.cohort_definition_description#412 AS str" . ### https://w3id.org/omop/ontology/discharged_to_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Visit Detail: This information may be called something different in the source data but the field is meant to contain a value indicating where a person was discharged to after a visit, as in they went home or were moved to long-term care. Typically this applies only to visits that have a length of stay of a day or more."@en , "For Visit Occurrence: This information may be called something different in the source data but the field is meant to contain a value indicating where a person was discharged to after a visit, as in they went home or were moved to long-term care. Typically this applies only to visits that have a length of stay of a day or more."@en ; rdfs:label "Discharged to source value" ; "visit_detail.discharged_to_source_value#55 AS str" , "visit_occurrence.discharged_to_source_value#39 AS str" . ### https://w3id.org/omop/ontology/disease_status_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "Disease status source value" ; "specimen.disease_status_source_value#229 AS str" . ### https://w3id.org/omop/ontology/domain_concept_id_1 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Domain concept id 1" ; "fact_relationship.domain_concept_id_1#230 AS int" . ### https://w3id.org/omop/ontology/domain_concept_id_2 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Domain concept id 2" ; "fact_relationship.domain_concept_id_2#232 AS int" . ### https://w3id.org/omop/ontology/dose_unit_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Drug Exposure: This field houses the verbatim value from the source data representing the dose unit of the drug given. This information may be called something different in the source data but the field is meant to contain a value indicating the unit of dosage of drug given to the patient. **This is an older column and will be deprecated in an upcoming version.**"@en ; rdfs:label "Dose unit source value" ; "drug_exposure.dose_unit_source_value#98 AS str" . ### https://w3id.org/omop/ontology/drg_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cost: Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups."@en ; rdfs:label "Drg source value" ; "cost.drg_source_value#304 AS str" . ### https://w3id.org/omop/ontology/end_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Condition Era: The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition."@en , "For Condition Occurrence: Use this date to determine the end date of the condition Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE."@en , "For Device Exposure: The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given. Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable."@en , "For Dose Era: The date the Person was no longer exposed to the dosage of the specific drug ingredient. An era is ended if there are 31 days or more between dosage records."@en , "For Drug Era: The Drug Era End Date is the end date of the last Drug Exposure. The End Date of each Drug Exposure is either taken from the field drug_exposure_end_date or, as it is typically not available, inferred using the following rules: For pharmacy prescription data, the date when the drug was dispensed plus the number of days of supply are used to extrapolate the End Date for the Drug Exposure. Depending on the country-specific healthcare system, this supply information is either explicitly provided in the day_supply field or inferred from package size or similar information. For Procedure Drugs, usually the drug is administered on a single date (i.e., the administration date). A standard Persistence Window of 30 days (gap, slack) is permitted between two subsequent such extrapolated DRUG_EXPOSURE records to be considered to be merged into a single Drug Era."@en , "For Drug Exposure: The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient. If this information is not explicitly available in the data, infer the end date from start date and duration.
For detailed conventions for how to populate this field, please see the [THEMIS repository](https://ohdsi.github.io/Themis/tag_drug_exposure.html)."@en , "For Observation Period: Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded. It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer."@en , "For Payer Plan Period: End date of Plan coverage."@en , "For Procedure Occurrence: Use this field to house the date that the procedure ended. This is meant to be the end date of the procedure. It is not required and for most cases will be the same as the PROCEDURE_START_DATE."@en , "For Visit Detail: This the end date of the patient-provider interaction. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull. Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:
- Outpatient Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime - Emergency Room Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime - Inpatient Visit Detail: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs. - Non-hospital institution Visit Details: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.
For Inpatient Visit Details ongoing at the date of ETL, put date of processing the data into visit_detai_end_datetime and visit_detail_type_concept_id with 32220 \"Still patient\" to identify the visit as incomplete. All other Visits Details: visit_detail_end_datetime = visit_detail_start_datetime."@en , "For Visit Occurrence: For inpatient visits the end date is typically the discharge date. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull. Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them: - Outpatient Visit: visit_end_datetime = visit_start_datetime - Emergency Room Visit: visit_end_datetime = visit_start_datetime - Inpatient Visit: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs. - Non-hospital institution Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 \"Still patient\" to identify the visit as incomplete. - All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date."@en ; rdfs:label "End date" ; "cohort.cohort_end_date#409 AS date" , "condition_era.condition_era_end_date#323 AS date" , "condition_occurrence.condition_end_date#65 AS date" , "device_exposure.device_exposure_end_date#120 AS date" , "dose_era.dose_era_end_date#318 AS date" , "drug_era.drug_era_end_date#309 AS date" , "drug_exposure.drug_exposure_end_date#81 AS date" , "observation_period.observation_period_end_date#22 AS date" , "payer_plan_period.payer_plan_period_end_date#269 AS date" , "procedure_occurrence.procedure_end_date#104 AS date" , "visit_detail.visit_detail_end_date#46 AS date" , "visit_occurrence.visit_end_date#29 AS date" . ### https://w3id.org/omop/ontology/end_datetime rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "For Condition Occurrence: If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Device Exposure: If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Drug Exposure: This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Procedure Occurrence: Use this field to house the datetime that the procedure ended. This is meant to house the end datetime of the procedure and will most often be used in conjunction with the procedure_start_datetime to determine the length of the procedure."@en , "For Visit Detail: If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull. If no time is given for the end date of a visit, set it to midnight (00:00:0000)."@en , "For Visit Occurrence: If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull. If no time is given for the end date of a visit, set it to midnight (00:00:0000)."@en ; rdfs:label "End datetime" ; "condition_occurrence.condition_end_datetime#66 AS datetime" , "device_exposure.device_exposure_end_datetime#121 AS datetime" , "drug_exposure.drug_exposure_end_datetime#82 AS datetime" , "procedure_occurrence.procedure_end_datetime#105 AS datetime" , "visit_detail.visit_detail_end_datetime#47 AS datetime" , "visit_occurrence.visit_end_datetime#30 AS datetime" . ### https://w3id.org/omop/ontology/ethnicity_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Person: This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only. If the person has an ethnicity other than the OMB standard of \"Hispanic\" or \"Not Hispanic\" store that value from the source data here."@en ; rdfs:label "Ethnicity source value" ; "person.ethnicity_source_value#17 AS str" . ### https://w3id.org/omop/ontology/exposure_count rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Drug Era: The count of grouped DRUG_EXPOSURE records that were included in the DRUG_ERA row"@en ; rdfs:label "Exposure count" ; "drug_era.drug_exposure_count#310 AS int" . ### https://w3id.org/omop/ontology/fact_id_1 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Fact id 1" ; "fact_relationship.fact_id_1#231 AS int" . ### https://w3id.org/omop/ontology/fact_id_2 rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "Fact id 2" ; "fact_relationship.fact_id_2#233 AS int" . ### https://w3id.org/omop/ontology/family_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Payer Plan Period: The common identifier for all people (often a family) that covered by the same policy. Often these are the common digits of the enrollment id of the policy members."@en ; rdfs:label "Family source value" ; "payer_plan_period.family_source_value#279 AS str" . ### https://w3id.org/omop/ontology/gap_days rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Drug Era: The Gap Days determine how many total drug-free days are observed between all Drug Exposure events that contribute to a DRUG_ERA record. It is assumed that the drugs are \"not stockpiled\" by the patient, i.e. that if a new drug prescription or refill is observed (a new DRUG_EXPOSURE record is written), the remaining supply from the previous events is abandoned. The difference between Persistence Window and Gap Days is that the former is the maximum drug-free time allowed between two subsequent DRUG_EXPOSURE records, while the latter is the sum of actual drug-free days for the given Drug Era under the above assumption of non-stockpiling."@en ; rdfs:label "Gap days" ; "drug_era.gap_days#311 AS int" . ### https://w3id.org/omop/ontology/gender_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Person: This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only. Put the assigned sex at birth of the person as it appears in the source data."@en , "For Provider: This is provider's gender as it appears in the source data. Put the provider's gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value."@en ; rdfs:label "Gender source value" ; "person.gender_source_value#13 AS str" , "provider.gender_source_value#264 AS str" . ### https://w3id.org/omop/ontology/id rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range [ rdf:type rdfs:Datatype ; owl:unionOf ( xsd:integer xsd:string ) ] ; rdfs:comment "For Care Site: Assign an ID to each combination of a location and nature of the site - the latter could be the Place of Service, name or another characteristic in your source data."@en , "For Cohort Definition: This is the identifier given to the cohort, usually by the ATLAS application"@en , "For Concept Class: A unique key for each class."@en , "For Concept: A unique identifier for each Concept across all domains."@en , "For Condition Occurrence: The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled. Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled."@en , "For Device Exposure: The unique key given to records a person's exposure to a foreign physical object or instrument. Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key."@en , "For Domain: A unique key for each domain."@en , "For Drug Exposure: The unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled. Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled."@en , "For Location: The unique key given to a unique Location. Each instance of a Location in the source data should be assigned this unique key."@en , "For Measurement: The unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled. Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled."@en , "For Metadata: The unique key given to a Metadata record. Attribute value is auto-generated"@en , "For Note Nlp: A unique identifier for the NLP record."@en , "For Note: A unique identifier for each note."@en , "For Observation Period: A Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id. Assign a unique observation_period_id to each discrete Observation Period for a Person."@en , "For Observation: The unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled. Each instance of an observation present in the source data should be assigned this unique key."@en , "For Payer Plan Period: A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time."@en , "For Person: It is assumed that every person with a different unique identifier is in fact a different person and should be treated independently. Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number."@en , "For Procedure Occurrence: The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled. Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled."@en , "For Provider: It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently. This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number."@en , "For Relationship: The type of relationship captured by the relationship record."@en , "For Specimen: Unique identifier for each specimen."@en , "For Visit Detail: Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail. This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time."@en , "For Visit Occurrence: Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit. This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time."@en , "For Vocabulary: A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit."@en ; rdfs:label "Id" ; "care_site.care_site_id#247 AS int|str" , "cohort_definition.cohort_definition_id#410 AS int|str" , "concept.concept_id#345 AS int|str" , "concept_class.concept_class_id#363 AS int|str" , "condition_era.condition_era_id#319 AS int|str" , "condition_occurrence.condition_occurrence_id#60 AS int|str" , "cost.cost_id#283 AS int|str" , "device_exposure.device_exposure_id#115 AS int|str" , "domain.domain_id#360 AS int|str" , "dose_era.dose_era_id#312 AS int|str" , "drug_era.drug_era_id#305 AS int|str" , "drug_exposure.drug_exposure_id#76 AS int|str" , "location.location_id#235 AS int|str" , "measurement.measurement_id#134 AS int|str" , "metadata.metadata_id#325 AS int|str" , "note.note_id#185 AS int|str" , "note_nlp.note_nlp_id#201 AS int|str" , "observation.observation_id#157 AS int|str" , "observation_period.observation_period_id#19 AS int|str" , "payer_plan_period.payer_plan_period_id#266 AS int|str" , "person.person_id#1 AS int|str" , "procedure_occurrence.procedure_occurrence_id#99 AS int|str" , "provider.provider_id#253 AS int|str" , "relationship.relationship_id#372 AS int|str" , "specimen.specimen_id#215 AS int|str" , "visit_detail.visit_detail_id#41 AS int|str" , "visit_occurrence.visit_occurrence_id#24 AS int|str" , "vocabulary.vocabulary_id#355 AS int|str" . ### https://w3id.org/omop/ontology/invalid_reason rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Concept Relationship: Reason the relationship was invalidated. Possible values are 'D' (deleted), 'U' (updated) or NULL."@en , "For Concept: Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value."@en , "For Drug Strength: Reason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value."@en , "For Source To Concept Map: Reason the mapping instance was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value."@en ; rdfs:label "Invalid reason" ; "concept.invalid_reason#354 AS str" , "concept_relationship.invalid_reason#371 AS str" , "drug_strength.invalid_reason#405 AS str" , "source_to_concept_map.invalid_reason#393 AS str" . ### https://w3id.org/omop/ontology/is_hierarchical rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Relationship: Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not."@en ; rdfs:label "Is hierarchical" ; "relationship.is_hierarchical#374 AS str" . ### https://w3id.org/omop/ontology/latitude rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Location: Must be between -90 and 90."@en ; rdfs:label "Latitude" ; "location.latitude#245 AS float" . ### https://w3id.org/omop/ontology/lexical_variant rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: Raw text extracted from the NLP tool."@en ; rdfs:label "Lexical variant" ; "note_nlp.lexical_variant#206 AS str" . ### https://w3id.org/omop/ontology/longitude rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Location: Must be between -180 and 180."@en ; rdfs:label "Longitude" ; "location.longitude#246 AS float" . ### https://w3id.org/omop/ontology/lot_number rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "Lot number" ; "drug_exposure.lot_number#91 AS str" . ### https://w3id.org/omop/ontology/max_levels_of_separation rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Concept Ancestor: The maximum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis."@en ; rdfs:label "Max levels of separation" ; "concept_ancestor.max_levels_of_separation#384 AS int" . ### https://w3id.org/omop/ontology/min_levels_of_separation rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Concept Ancestor: The minimum separation in number of levels of hierarchy between ancestor and descendant concepts. This is an attribute that is used to simplify hierarchic analysis."@en ; rdfs:label "Min levels of separation" ; "concept_ancestor.min_levels_of_separation#383 AS int" . ### https://w3id.org/omop/ontology/modifier_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Procedure Occurrence: This field houses the verbatim value from the source data representing the modifier code for the procedure that occurred. The value stored here is mapped to a MODIFIER_CONCEPT_ID."@en ; rdfs:label "Modifier source value" ; "procedure_occurrence.modifier_source_value#114 AS str" . ### https://w3id.org/omop/ontology/month_of_birth rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Person: For data sources that provide the precise date of birth, the month should be extracted and stored in this field."@en ; rdfs:label "Month of birth" ; "person.month_of_birth#4 AS int" . ### https://w3id.org/omop/ontology/name rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Care Site: The name of the care_site as it appears in the source data"@en , "For Cdm Source: The name of the CDM instance."@en , "For Cohort Definition: A short description of the cohort"@en , "For Concept Class: The name describing the Concept Class, e.g. Clinical Finding, Ingredient, etc."@en , "For Concept: An unambiguous, meaningful and descriptive name for the Concept."@en , "For Domain: The name describing the Domain, e.g. Condition, Procedure, Measurement etc."@en , "For Provider: This field contains information that describes a healthcare provider. This field is not required for identifying the Provider's actual identity. Instead, its purpose is to uniquely and/or anonymously identify providers of care across the database."@en , "For Vocabulary: The name describing the vocabulary, for example, International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS) etc."@en ; rdfs:label "Name" ; "care_site.care_site_name#248 AS str" , "cdm_source.cdm_source_name#334 AS str" , "cohort_definition.cohort_definition_name#411 AS str" , "concept.concept_name#346 AS str" , "concept_class.concept_class_name#364 AS str" , "concept_synonym.concept_synonym_name#379 AS str" , "domain.domain_name#361 AS str" , "metadata.name#328 AS str" , "provider.provider_name#254 AS str" , "relationship.relationship_name#373 AS str" , "vocabulary.vocabulary_name#356 AS str" . ### https://w3id.org/omop/ontology/npi rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Provider: This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS)."@en ; rdfs:label "Npi" ; "provider.npi#255 AS str" . ### https://w3id.org/omop/ontology/numerator_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Drug Strength: The concentration of the active ingredient contained within the drug product."@en ; rdfs:label "Numerator value" ; "drug_strength.numerator_value#398 AS float" . ### https://w3id.org/omop/ontology/occurrence_count rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Condition Era: The number of individual Condition Occurrences used to construct the condition era."@en ; rdfs:label "Occurrence count" ; "condition_era.condition_occurrence_count#324 AS int" . ### https://w3id.org/omop/ontology/offset rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: Character offset of the extracted term in the input note"@en ; rdfs:label "Offset" ; "note_nlp.offset#205 AS str" . ### https://w3id.org/omop/ontology/paid_by_patient rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid by patient" ; "cost.paid_by_patient#292 AS float" . ### https://w3id.org/omop/ontology/paid_by_payer rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid by payer" ; "cost.paid_by_payer#291 AS float" . ### https://w3id.org/omop/ontology/paid_by_primary rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid by primary" ; "cost.paid_by_primary#296 AS float" . ### https://w3id.org/omop/ontology/paid_dispensing_fee rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid dispensing fee" ; "cost.paid_dispensing_fee#298 AS float" . ### https://w3id.org/omop/ontology/paid_ingredient_cost rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid ingredient cost" ; "cost.paid_ingredient_cost#297 AS float" . ### https://w3id.org/omop/ontology/paid_patient_coinsurance rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid patient coinsurance" ; "cost.paid_patient_coinsurance#294 AS float" . ### https://w3id.org/omop/ontology/paid_patient_copay rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid patient copay" ; "cost.paid_patient_copay#293 AS float" . ### https://w3id.org/omop/ontology/paid_patient_deductible rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Paid patient deductible" ; "cost.paid_patient_deductible#295 AS float" . ### https://w3id.org/omop/ontology/payer_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Payer Plan Period: This is the Payer as it appears in the source data."@en ; rdfs:label "Payer source value" ; "payer_plan_period.payer_source_value#271 AS str" . ### https://w3id.org/omop/ontology/place_of_service_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Care Site: Put the place of service of the care_site as it appears in the source data."@en ; rdfs:label "Place of service source value" ; "care_site.place_of_service_source_value#252 AS str" . ### https://w3id.org/omop/ontology/plan_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Payer Plan Period: This is the health benefit Plan of the Person as it appears in the source data."@en ; rdfs:label "Plan source value" ; "payer_plan_period.plan_source_value#274 AS str" . ### https://w3id.org/omop/ontology/qualifier_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Observation: This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference."@en ; rdfs:label "Qualifier source value" ; "observation.qualifier_source_value#174 AS str" . ### https://w3id.org/omop/ontology/quantity rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "For Device Exposure: If there is a record of device exposure in the source but no quantity value, then set to 1."@en , "For Drug Exposure: To find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is 'Has dose form'. If liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table. If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. For clinical drugs with fixed dose forms (tablets etc.) the quantity is the number of units/tablets/capsules prescribed or dispensed (can be partial, but then only 1/2 or 1/3, not 0.01). Clinical drugs with divisible dose forms (injections) the quantity is the amount of ingredient the patient got. For example, if the injection is 2mg/mL but the patient got 80mL then quantity is reported as 160. Quantified clinical drugs with divisible dose forms (prefilled syringes), the quantity is the amount of ingredient similar to clinical drugs. Please see [how to calculate drug dose](https://ohdsi.github.io/CommonDataModel/drug_dose.html) for more information. "@en , "For Procedure Occurrence: If the quantity value is omitted, a single procedure is assumed. If a Procedure has a quantity of '0' in the source, this should default to '1' in the ETL. If there is a record in the source it can be assumed the exposure occurred at least once"@en , "For Specimen: The amount of specimen collected from the person."@en ; rdfs:label "Quantity" ; "device_exposure.quantity#125 AS int" , "drug_exposure.quantity#87 AS float" , "procedure_occurrence.quantity#108 AS int" , "specimen.quantity#221 AS float" . ### https://w3id.org/omop/ontology/race_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Person: This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only. Put the race of the person as it appears in the source data."@en ; rdfs:label "Race source value" ; "person.race_source_value#15 AS str" . ### https://w3id.org/omop/ontology/range_high rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Measurement: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given. If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided."@en ; rdfs:label "Range high" ; "measurement.range_high#146 AS float" . ### https://w3id.org/omop/ontology/range_low rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Measurement: Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given. If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided."@en ; rdfs:label "Range low" ; "measurement.range_low#145 AS float" . ### https://w3id.org/omop/ontology/reference rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Vocabulary: External reference to documentation or available download of the about the vocabulary."@en ; rdfs:label "Reference" ; "vocabulary.vocabulary_reference#357 AS str" . ### https://w3id.org/omop/ontology/refills rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "For Drug Exposure: This is only filled in when the record is coming from a prescription written this field is meant to represent intended refills at time of the prescription."@en ; rdfs:label "Refills" ; "drug_exposure.refills#86 AS int" . ### https://w3id.org/omop/ontology/revenue_code_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cost: Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system."@en ; rdfs:label "Revenue code source value" ; "cost.revenue_code_source_value#302 AS str" . ### https://w3id.org/omop/ontology/route_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Drug Exposure: This field houses the verbatim value from the source data representing the drug route. This information may be called something different in the source data but the field is meant to contain a value indicating when and how a drug was given to a patient. This source value is mapped to a standard concept which is stored in the ROUTE_CONCEPT_ID field."@en ; rdfs:label "Route source value" ; "drug_exposure.route_source_value#97 AS str" . ### https://w3id.org/omop/ontology/sig rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Drug Exposure: This is the verbatim instruction for the drug as written by the provider. Put the written out instructions for the drug as it is verbatim in the source, if available."@en ; rdfs:label "Sig" ; "drug_exposure.sig#89 AS str" . ### https://w3id.org/omop/ontology/snippet rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: A small window of text surrounding the term"@en ; rdfs:label "Snippet" ; "note_nlp.snippet#204 AS str" . ### https://w3id.org/omop/ontology/source_code rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Source To Concept Map: The source code being translated into a Standard Concept."@en ; rdfs:label "Source code" ; "source_to_concept_map.source_code#385 AS str" . ### https://w3id.org/omop/ontology/source_code_description rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Source To Concept Map: An optional description for the source code. This is included as a convenience to compare the description of the source code to the name of the concept."@en ; rdfs:label "Source code description" ; "source_to_concept_map.source_code_description#388 AS str" . ### https://w3id.org/omop/ontology/source_description rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: The description of the CDM instance."@en ; rdfs:label "Source description" ; "cdm_source.source_description#337 AS str" . ### https://w3id.org/omop/ontology/source_documentation_reference rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: Refers to a publication or web resource describing the source data, e.g. a data dictionary."@en ; rdfs:label "Source documentation reference" ; "cdm_source.source_documentation_reference#338 AS str" . ### https://w3id.org/omop/ontology/source_release_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Cdm Source: The date the data was extracted from the source system. In some systems that is the same as the date the ETL was run. Typically the latest even date in the source is on the source_release_date."@en ; rdfs:label "Source release date" ; "cdm_source.source_release_date#340 AS date" . ### https://w3id.org/omop/ontology/source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Care Site: The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site."@en , "For Condition Occurrence: This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference."@en , "For Device Exposure: This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code. This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference."@en , "For Drug Exposure: This field houses the verbatim value from the source data representing the drug exposure that occurred. For example, this could be an NDC or Gemscript code. This code is mapped to a Standard Drug Concept in the Standardized Vocabularies and the original code is stored here for reference."@en , "For Location: Put the verbatim value for the location here, as it shows up in the source."@en , "For Measurement: This field contains the exact value from the source data that represents the measurement that occurred. This value corresponds to a standardized CONCEPT_ID found in MEASUREMENT_CONCEPT_ID and in the 'Measurement' domain within the Standardized Vocabularies. The original code is retained here for reference purposes."@en , "For Note: The source value mapped to the NOTE_CLASS_CONCEPT_ID."@en , "For Observation: This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code. This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference."@en , "For Person: Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic. Some use cases require the ability to link back to persons in the source data. This field allows for the storing of the person value as it appears in the source. This field is not required but strongly recommended."@en , "For Procedure Occurrence: This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code. Use this value to look up the source concept id and then map the source concept id to a standard concept id."@en , "For Provider: Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic. Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider identifier as it appears in the source."@en , "For Visit Detail: This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.) If there is information about the kind of visit detail in the source data that value should be stored here. If a visit is an amalgamation of visits from the source then use a hierarchy to choose the VISIT_DETAIL_SOURCE_VALUE, such as IP -> ER-> OP. This should line up with the logic chosen to determine how visits are created."@en , "For Visit Occurrence: This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.) If there is information about the kind of visit in the source data that value should be stored here. If a visit is an amalgamation of visits from the source then use a hierarchy to choose the visit source value, such as IP -> ER-> OP. This should line up with the logic chosen to determine how visits are created."@en ; rdfs:label "Source value" ; "care_site.care_site_source_value#251 AS str" , "condition_occurrence.condition_source_value#73 AS str" , "device_exposure.device_source_value#129 AS str" , "drug_exposure.drug_source_value#95 AS str" , "location.location_source_value#242 AS str" , "measurement.measurement_source_value#150 AS str" , "note.note_source_value#198 AS str" , "observation.observation_source_value#171 AS str" , "person.person_source_value#12 AS str" , "procedure_occurrence.procedure_source_value#112 AS str" , "provider.provider_source_value#261 AS str" , "specimen.specimen_source_value#226 AS str" , "visit_detail.visit_detail_source_value#51 AS str" , "visit_occurrence.visit_source_value#34 AS str" . ### https://w3id.org/omop/ontology/specialty_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Provider: This refers to the specific type of healthcare provider or field of expertise listed in the source data, encompassing physician specialties like internal medicine, emergency medicine, etc., as well as allied health professionals such as nurses, midwives, and pharmacists. It covers medical specialties like surgery, internal medicine, and radiology, while other services like prosthetics, acupuncture, and physical therapy fall under the domain of \"Service.\" The type of provider and their specialty should be entered as they appear in the source data. The decision to use either the coded value or the text description is left to the discretion of the ETL-er."@en ; rdfs:label "Specialty source value" ; "provider.specialty_source_value#262 AS str" . ### https://w3id.org/omop/ontology/sponsor_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Payer Plan Period: The Plan sponsor as it appears in the source data."@en ; rdfs:label "Sponsor source value" ; "payer_plan_period.sponsor_source_value#277 AS str" . ### https://w3id.org/omop/ontology/standard rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Concept: This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are 'S' (Standard Concept) and 'C' (Classification Concept), otherwise the content is NULL."@en ; rdfs:label "Standard" ; "concept.standard_concept#350 AS str" . ### https://w3id.org/omop/ontology/start_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Condition Era: The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition."@en , "For Condition Occurrence: Use this date to determine the start date of the condition Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE."@en , "For Device Exposure: Use this date to determine the start date of the device record. Valid entries include a start date of a procedure to implant a device, the date of a prescription for a device, or the date of device administration."@en , "For Dose Era: The date the Person started on the specific dosage, with at least 31 days since any prior exposure."@en , "For Drug Era: The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient, with at least 31 days since the previous exposure."@en , "For Drug Exposure: Use this date to determine the start date of the drug record. Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration was recorded. It is a valid ETL choice to use the date the drug was ordered as the DRUG_EXPOSURE_START_DATE."@en , "For Observation Period: Use this date to determine the start date of the Observation Period. It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_start_date can be inferred as the earliest Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer. If a Person switches plans but stays with the same payer, and therefore capturing of data continues, that change would be captured in [PAYER_PLAN_PERIOD](https://ohdsi.github.io/CommonDataModel/cdm54.html#payer_plan_period)."@en , "For Payer Plan Period: Start date of Plan coverage."@en , "For Visit Detail: This is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with. When populating VISIT_DETAIL_START_DATE, you should think about the patient experience to make decisions on how to define visits. Most likely this should be the date of the patient-provider interaction."@en , "For Visit Occurrence: For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same. When populating VISIT_START_DATE, you should think about the patient experience to make decisions on how to define visits. In the case of an inpatient visit this should be the date the patient was admitted to the hospital or institution. In all other cases this should be the date of the patient-provider interaction. If this information is not available the record should be dropped."@en ; rdfs:label "Start date" ; "cohort.cohort_start_date#408 AS date" , "condition_era.condition_era_start_date#322 AS date" , "condition_occurrence.condition_start_date#63 AS date" , "device_exposure.device_exposure_start_date#118 AS date" , "dose_era.dose_era_start_date#317 AS date" , "drug_era.drug_era_start_date#308 AS date" , "drug_exposure.drug_exposure_start_date#79 AS date" , "observation_period.observation_period_start_date#21 AS date" , "payer_plan_period.payer_plan_period_start_date#268 AS date" , "visit_detail.visit_detail_start_date#44 AS date" , "visit_occurrence.visit_start_date#27 AS date" . ### https://w3id.org/omop/ontology/start_datetime rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "For Condition Occurrence: If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Device Exposure: This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Drug Exposure: This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)"@en , "For Visit Detail: If no time is given for the start date of a visit, set it to midnight (00:00:0000)."@en , "For Visit Occurrence: If no time is given for the start date of a visit, set it to midnight (00:00:0000)."@en ; rdfs:label "Start datetime" ; "condition_occurrence.condition_start_datetime#64 AS datetime" , "device_exposure.device_exposure_start_datetime#119 AS datetime" , "drug_exposure.drug_exposure_start_datetime#80 AS datetime" , "visit_detail.visit_detail_start_datetime#45 AS datetime" , "visit_occurrence.visit_start_datetime#28 AS datetime" . ### https://w3id.org/omop/ontology/state rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "State" ; "location.state#239 AS str" . ### https://w3id.org/omop/ontology/status_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Condition Occurrence: This field houses the verbatim value from the source data representing the condition status. This information may be called something different in the source data but the field is meant to contain a value indicating when and how a diagnosis was given to a patient. This source value is mapped to a standard concept which is stored in the CONDITION_STATUS_CONCEPT_ID field."@en ; rdfs:label "Status source value" ; "condition_occurrence.condition_status_source_value#75 AS str" . ### https://w3id.org/omop/ontology/stop_reason rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Condition Occurrence: The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring. This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist."@en , "For Drug Exposure: The reason a person stopped a medication as it is represented in the source. Reasons include regimen completed, changed, removed, etc. This field will be retired in v6.0. This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist."@en ; rdfs:label "Stop reason" ; "condition_occurrence.stop_reason#69 AS str" , "drug_exposure.stop_reason#85 AS str" . ### https://w3id.org/omop/ontology/stop_reason_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Payer Plan Period: The Plan stop reason as it appears in the source data."@en ; rdfs:label "Stop reason source value" ; "payer_plan_period.stop_reason_source_value#281 AS str" . ### https://w3id.org/omop/ontology/syntax rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cohort Definition: Syntax or code to operationalize the Cohort Definition."@en ; rdfs:label "Syntax" ; "cohort_definition.cohort_definition_syntax#414 AS str" . ### https://w3id.org/omop/ontology/system rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: Name and version of the NLP system that extracted the term. Useful for data provenance."@en ; rdfs:label "System" ; "note_nlp.nlp_system#209 AS str" . ### https://w3id.org/omop/ontology/term_exists rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: Term_exists is defined as a flag that indicates if the patient actually has or had the condition. Any of the following modifiers would make Term_exists false: Negation = true Subject = [anything other than the patient] Conditional = true/li> Rule_out = true Uncertain = very low certainty or any lower certainties A complete lack of modifiers would make Term_exists true. "@en ; rdfs:label "Term exists" ; "note_nlp.term_exists#212 AS str" . ### https://w3id.org/omop/ontology/term_modifiers rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: For the modifiers that are there, they would have to have these values:

- Negation = false - Subject = patient - Conditional = false - Rule_out = false - Uncertain = true or high or moderate or even low (could argue about low). Term_modifiers will concatenate all modifiers for different types of entities (conditions, drugs, labs etc) into one string. Lab values will be saved as one of the modifiers."@en ; rdfs:label "Term modifiers" ; "note_nlp.term_modifiers#214 AS str" . ### https://w3id.org/omop/ontology/term_temporal rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note Nlp: Term_temporal is to indicate if a condition is present or just in the past. The following would be past:

- History = true - Concept_date = anything before the time of the report"@en ; rdfs:label "Term temporal" ; "note_nlp.term_temporal#213 AS str" . ### https://w3id.org/omop/ontology/text rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note: The content of the note."@en ; rdfs:label "Text" ; "note.note_text#192 AS str" . ### https://w3id.org/omop/ontology/time rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Measurement: This is present for backwards compatibility and will be deprecated in an upcoming version."@en ; rdfs:label "Time" ; "measurement.measurement_time#139 AS str" . ### https://w3id.org/omop/ontology/title rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Note: The title of the note."@en ; rdfs:label "Title" ; "note.note_title#191 AS str" . ### https://w3id.org/omop/ontology/total_charge rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Total charge" ; "cost.total_charge#288 AS float" . ### https://w3id.org/omop/ontology/total_cost rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Total cost" ; "cost.total_cost#289 AS float" . ### https://w3id.org/omop/ontology/total_paid rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:label "Total paid" ; "cost.total_paid#290 AS float" . ### https://w3id.org/omop/ontology/unit_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Device Exposure: This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference. Using the blood transfusion example, blood transfusion is represented by the DEVICE_CONCEPT_ID and the unit (mL) would be housed in the UNIT_SOURCE_VALUE and mapped to a standard concept in the unit domain."@en , "For Measurement: This field contains the exact value from the source data that represents the unit of measurement used. This value corresponds to a standardized CONCEPT_ID found in UNIT_CONCEPT_ID and in the 'Unit' domain within the Standardized Vocabularies. The original code is retained here for reference purposes."@en , "For Observation: This field houses the verbatim value from the source data representing the unit of the Observation that occurred. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference."@en , "For Specimen: This unit for the quantity of the specimen, as represented in the source."@en ; rdfs:label "Unit source value" ; "device_exposure.unit_source_value#132 AS str" , "measurement.unit_source_value#152 AS str" , "observation.unit_source_value#173 AS str" , "specimen.unit_source_value#227 AS str" . ### https://w3id.org/omop/ontology/valid_end_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:date ; rdfs:comment "For Concept Relationship: The date when the relationship is invalidated."@en , "For Concept: The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated."@en , "For Drug Strength: The date when then Concept became invalid."@en , "For Source To Concept Map: The date when the mapping instance became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099."@en ; rdfs:label "Valid end date" ; "concept.valid_end_date#353 AS date" , "concept_relationship.valid_end_date#370 AS date" , "drug_strength.valid_end_date#404 AS date" , "source_to_concept_map.valid_end_date#392 AS date" . ### https://w3id.org/omop/ontology/valid_start_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:date ; rdfs:comment "For Concept Relationship: The date when the relationship is first recorded."@en , "For Concept: The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception."@en , "For Drug Strength: The date when the Concept was first recorded. The default value is 1-Jan-1970."@en , "For Source To Concept Map: The date when the mapping instance was first recorded."@en ; rdfs:label "Valid start date" ; "concept.valid_start_date#352 AS date" , "concept_relationship.valid_start_date#369 AS date" , "drug_strength.valid_start_date#403 AS date" , "source_to_concept_map.valid_start_date#391 AS date" . ### https://w3id.org/omop/ontology/value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "For Dose Era: The numeric value of the dosage of the drug_ingredient."@en ; rdfs:label "Value" ; "dose_era.dose_value#316 AS float" . ### https://w3id.org/omop/ontology/value_as_number rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:decimal ; rdfs:comment "For Measurement: This is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic. [Convention for negative values](https://ohdsi.github.io/Themis/negative_value_as_number.html)"@en , "For Metadata: This is the numerical value of the result of the Metadata, if applicable and available. It is not expected that all Metadata will have numeric results, rather, this field is here to house values should they exist."@en , "For Observation: This is the numerical value of the Result of the Observation, if applicable and available. It is not expected that all Observations will have numeric results, rather, this field is here to house values should they exist."@en ; rdfs:label "Value as number" ; "measurement.value_as_number#142 AS float" , "metadata.value_as_number#331 AS float" , "observation.value_as_number#163 AS float" . ### https://w3id.org/omop/ontology/value_as_string rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Observation: This is the categorical value of the Result of the Observation, if applicable and available."@en ; rdfs:label "Value as string" ; "metadata.value_as_string#329 AS str" , "observation.value_as_string#164 AS str" . ### https://w3id.org/omop/ontology/value_source_value rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:string ; rdfs:comment "For Measurement: This field houses the verbatim result value of the Measurement from the source data . If both a continuous and categorical result are given in the source data such that both VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are both included, store the verbatim value that was mapped to VALUE_AS_CONCEPT_ID here."@en , "For Observation: This field houses the verbatim result value of the Observation from the source data. Do not get confused with the Observation_source_value which captures source value of the observation mapped to observation_concept_id. This field is the observation result value from the source. If the observation_source_value was a question, for example, or an observation that requires a result then this field is the answer/ result from the source data. Store the verbatim value that represents the result of the observation_source_value."@en ; rdfs:label "Value source value" ; "measurement.value_source_value#154 AS str" , "observation.value_source_value#175 AS str" . ### https://w3id.org/omop/ontology/verbatim_end_date rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "For Drug Exposure: This is the end date of the drug exposure as it appears in the source data, if it is given Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable."@en ; rdfs:label "Verbatim end date" ; "drug_exposure.verbatim_end_date#83 AS date" . ### https://w3id.org/omop/ontology/version rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Vocabulary: Version of the Vocabulary as indicated in the source."@en ; rdfs:label "Version" ; "vocabulary.vocabulary_version#358 AS str" . ### https://w3id.org/omop/ontology/vocabulary_version rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Cdm Source: Version of the OMOP standardised vocabularies loaded You can find the version of your Vocabulary using the query: `SELECT vocabulary_version from vocabulary where vocabulary_id = 'None'`"@en ; rdfs:label "Vocabulary version" ; "cdm_source.vocabulary_version#344 AS str" . ### https://w3id.org/omop/ontology/year_of_birth rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range xsd:integer ; rdfs:comment "For Person: Compute age using year_of_birth. For data sources with date of birth, the year should be extracted. If no year of birth is available all the person's data should be dropped from the CDM instance. For additional information on how to populate this field, please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/tag_year_of_birth.html)."@en ; rdfs:label "Year of birth" ; "person.year_of_birth#3 AS int" , "provider.year_of_birth#259 AS int" . ### https://w3id.org/omop/ontology/zip rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "For Location: Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply."@en ; rdfs:label "Zip" ; "location.zip#240 AS str" . ################################################################# # Classes ################################################################# ### https://w3id.org/omop/ontology/BasePerson rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:label "Base person" . ### https://w3id.org/omop/ontology/BaseVisit rdf:type owl:Class ; rdfs:subClassOf , , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:label "Base visit" . ### https://w3id.org/omop/ontology/CareSite rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.)."@en ; rdfs:label "Care site" ; "care_site" . ### https://w3id.org/omop/ontology/CdmSource rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The CDM_SOURCE table contains detail about the source database and the process used to transform the data into the OMOP Common Data Model."@en ; rdfs:label "Cdm source" ; "cdm_source" . ### https://w3id.org/omop/ontology/ClinicalElement rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Clinical element" . ### https://w3id.org/omop/ontology/Cohort rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] ; rdfs:comment "The subject of a cohort can have multiple, discrete records in the cohort table per cohort_definition_id, subject_id, and non-overlapping time periods. The definition of the cohort is contained within the COHORT_DEFINITION table. It is listed as part of the RESULTS schema because it is a table that users of the database as well as tools such as ATLAS need to be able to write to. The CDM and Vocabulary tables are all read-only so it is suggested that the COHORT and COHORT_DEFINTION tables are kept in a separate schema to alleviate confusion."@en ; rdfs:label "Cohort" ; "cohort" . ### https://w3id.org/omop/ontology/CohortDefinition rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The COHORT_DEFINITION table contains records defining a Cohort derived from the data through the associated description and syntax and upon instantiation (execution of the algorithm) placed into the COHORT table. Cohorts are a set of subjects that satisfy a given combination of inclusion criteria for a duration of time. The COHORT_DEFINITION table provides a standardized structure for maintaining the rules governing the inclusion of a subject into a cohort, and can store operational programming code to instantiate the cohort within the OMOP Common Data Model."@en ; rdfs:label "Cohort definition" ; "cohort_definition" . ### https://w3id.org/omop/ontology/Concept rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:comment "The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and standardized analytics. Each Standard Concept belongs to one Domain, which defines the location where the Concept would be expected to occur within the data tables of the CDM. Concepts can represent broad categories ('Cardiovascular disease'), detailed clinical elements ('Myocardial infarction of the anterolateral wall'), or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.). Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom OMOP Concepts defined to cover various aspects of observational data analysis."@en ; rdfs:label "Concept" ; "concept" . ### https://w3id.org/omop/ontology/ConceptAncestor rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "The CONCEPT_ANCESTOR table is designed to simplify observational analysis by providing the complete hierarchical relationships between Concepts. Only direct parent-child relationships between Concepts are stored in the CONCEPT_RELATIONSHIP table. To determine higher-level ancestry connections, all individual direct relationships would have to be navigated at analysis time. The CONCEPT_ANCESTOR table includes records for all parent-child relationships, as well as grandparent-grandchild relationships and those of any other level of lineage for Standard or Classification concepts. Using the CONCEPT_ANCESTOR table allows for querying for all descendants of a hierarchical concept, and the other way around. For example, drug ingredients and drug products, beneath them in the hierarchy, are all descendants of a drug class ancestor. This table is entirely derived from the CONCEPT, CONCEPT_RELATIONSHIP, and RELATIONSHIP tables."@en ; rdfs:label "Concept ancestor" ; "concept_ancestor" . ### https://w3id.org/omop/ontology/ConceptClass rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The CONCEPT_CLASS table includes semantic categories that reference the source structure of each Vocabulary. Concept Classes represent so-called horizontal (e.g. MedDRA, RxNorm) or vertical levels (e.g. SNOMED) of the vocabulary structure. Vocabularies without any Concept Classes, such as HCPCS, use the vocabulary_id as the Concept Class. This reference table is populated with a single record for each Concept Class, which includes a Concept Class ID and a fully specified Concept Class name. "@en ; rdfs:label "Concept class" ; "concept_class" . ### https://w3id.org/omop/ontology/ConceptRelationship rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:comment "The CONCEPT_RELATIONSHIP table contains records that define relationships between any two Concepts and the nature or type of the relationship. This table captures various types of relationships, including hierarchical, associative, and other semantic connections, enabling comprehensive analysis and interpretation of clinical concepts. Every kind of relationship is defined in the RELATIONSHIP table."@en ; rdfs:label "Concept relationship" ; "concept_relationship" . ### https://w3id.org/omop/ontology/ConceptSynonym rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The CONCEPT_SYNONYM table captures alternative terms, synonyms, and translations of Concept Name into various languages linked to specific concepts, providing users with a comprehensive view of how Concepts may be expressed or referenced."@en ; rdfs:label "Concept synonym" ; "concept_synonym" . ### https://w3id.org/omop/ontology/ConditionEra rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence and every Condition Occurrence record should be part of a Condition Era. Combining individual Condition Occurrences into a single Condition Era serves two purposes: - It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event. - It allows aggregation of multiple, closely timed doctor visits for the same Condition to avoid double-counting the Condition Occurrences. For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era."@en ; rdfs:label "Condition era" ; "condition_era" . ### https://w3id.org/omop/ontology/ConditionOccurrence rdf:type owl:Class ; rdfs:subClassOf , , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient."@en ; rdfs:label "Condition occurrence" ; "condition_occurrence" . ### https://w3id.org/omop/ontology/Cost rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] ; rdfs:comment "The COST table captures records containing the cost of any medical event recorded in one of the OMOP clinical event tables such as DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, VISIT_OCCURRENCE, VISIT_DETAIL, DEVICE_OCCURRENCE, OBSERVATION or MEASUREMENT. Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event."@en ; rdfs:label "Cost" ; "cost" . ### https://w3id.org/omop/ontology/DateDuration rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:label "Date duration" . ### https://w3id.org/omop/ontology/DatetimeDuration rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:dateTime ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:dateTime ] ; rdfs:label "Datetime duration" . ### https://w3id.org/omop/ontology/Death rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data."@en ; rdfs:label "Death" ; "death" . ### https://w3id.org/omop/ontology/DeviceExposure rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material)."@en ; rdfs:label "Device exposure" ; "device_exposure" . ### https://w3id.org/omop/ontology/Domain rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The DOMAIN table includes a list of OMOP-defined Domains to which the Concepts of the Standardized Vocabularies can belong. A Domain represents a clinical definition whereby we assign matching Concepts for the standardized fields in the CDM tables. For example, the Condition Domain contains Concepts that describe a patient condition, and these Concepts can only be used in the condition_concept_id field of the CONDITION_OCCURRENCE and CONDITION_ERA tables. This reference table is populated with a single record for each Domain, including a Domain ID and a descriptive name for every Domain."@en ; rdfs:label "Domain" ; "domain" . ### https://w3id.org/omop/ontology/DoseEra rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] ; rdfs:comment "A Dose Era is defined as a span of time when the Person is assumed to be exposed to a constant dose of a specific active ingredient."@en ; rdfs:label "Dose era" ; "dose_era" . ### https://w3id.org/omop/ontology/DrugEra rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras. Every record in the DRUG_EXPOSURE table should be part of a drug era based on the dates of exposure. "@en ; rdfs:label "Drug era" ; "drug_era" . ### https://w3id.org/omop/ontology/DrugExposure rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:comment "This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs."@en ; rdfs:label "Drug exposure" ; "drug_exposure" . ### https://w3id.org/omop/ontology/DrugStrength rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:comment "The DRUG_STRENGTH table contains structured content about the amount or concentration and associated units of a specific ingredient contained within a particular drug product. This table is supplemental information to support standardized analysis of drug utilization."@en ; rdfs:label "Drug strength" ; "drug_strength" . ### https://w3id.org/omop/ontology/Duration rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Duration" . ### https://w3id.org/omop/ontology/Era rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:label "Era" . ### https://w3id.org/omop/ontology/Event rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:dateTime ] ; rdfs:label "Event" . ### https://w3id.org/omop/ontology/Exposure rdf:type owl:Class ; rdfs:subClassOf , , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:label "Exposure" . ### https://w3id.org/omop/ontology/FactRelationship rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: [Person relationships](https://athena.ohdsi.org/search-terms/terms?domain=Relationship&standardConcept=Standard&page=2&pageSize=15&query=) (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen)."@en ; rdfs:label "Fact relationship" ; "fact_relationship" . ### https://w3id.org/omop/ontology/Location rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites."@en ; rdfs:label "Location" ; "location" . ### https://w3id.org/omop/ontology/Measurement rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured."@en ; rdfs:label "Measurement" ; "measurement" . ### https://w3id.org/omop/ontology/Metadata rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The METADATA table contains metadata information about a dataset that has been transformed to the OMOP Common Data Model."@en ; rdfs:label "Metadata" ; "metadata" . ### https://w3id.org/omop/ontology/Note rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The NOTE table captures unstructured information that was recorded by a provider about a patient in free text (in ASCII, or preferably in UTF8 format) notes on a given date. The type of note_text is CLOB or varchar(MAX) depending on RDBMS."@en ; rdfs:label "Note" ; "note" . ### https://w3id.org/omop/ontology/NoteNlp rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The NOTE_NLP table encodes all output of NLP on clinical notes. Each row represents a single extracted term from a note."@en ; rdfs:label "Note nlp" ; "note_nlp" . ### https://w3id.org/omop/ontology/Observation rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here."@en ; rdfs:label "Observation" ; "observation" . ### https://w3id.org/omop/ontology/ObservationPeriod rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "This table contains records which define spans of time during which two conditions are expected to hold: (i) Clinical Events that happened to the Person are recorded in the Event tables, and (ii) absence of records indicate such Events did not occur during this span of time."@en ; rdfs:label "Observation period" ; "observation_period" . ### https://w3id.org/omop/ontology/Occurrence rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Occurrence" . ### https://w3id.org/omop/ontology/OmopCDMThing rdf:type owl:Class ; rdfs:subClassOf owl:Thing , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom [ rdf:type rdfs:Datatype ; owl:unionOf ( xsd:integer xsd:string ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom [ rdf:type rdfs:Datatype ; owl:unionOf ( xsd:integer xsd:string ) ] ] ; rdfs:label "OMOP CDM thing" . ### https://w3id.org/omop/ontology/PayerPlanPeriod rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The PAYER_PLAN_PERIOD table captures details of the period of time that a Person is continuously enrolled under a specific health Plan benefit structure from a given Payer. Each Person receiving healthcare is typically covered by a health benefit plan, which pays for (fully or partially), or directly provides, the care. These benefit plans are provided by payers, such as health insurances or state or government agencies. In each plan the details of the health benefits are defined for the Person or her family, and the health benefit Plan might change over time typically with increasing utilization (reaching certain cost thresholds such as deductibles), plan availability and purchasing choices of the Person. The unique combinations of Payer organizations, health benefit Plans and time periods in which they are valid for a Person are recorded in this table."@en ; rdfs:label "Payer plan period" ; "payer_plan_period" . ### https://w3id.org/omop/ontology/Person rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:dateTime ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information."@en ; rdfs:label "Person" ; "person" . ### https://w3id.org/omop/ontology/ProcedureOccurrence rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose."@en ; rdfs:label "Procedure occurrence" ; "procedure_occurrence" . ### https://w3id.org/omop/ontology/Provider rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:integer ] ; rdfs:comment "The PROVIDER table contains a list of uniquely identified healthcare providers; duplication is not allowed. These are individuals providing hands-on healthcare to patients, such as physicians, nurses, midwives, physical therapists etc."@en ; rdfs:label "Provider" ; "provider" . ### https://w3id.org/omop/ontology/Relationship rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The RELATIONSHIP table provides a reference list of all types of relationships that can be used to associate any two Concepts in the CONCEPT_RELATIONSHIP table, the respective reverse relationships, and their hierarchical characteristics. Note, that Concepts representing relationships between the clinical facts, used for filling in the FACT_RELATIONSHIP table are stored in the CONCEPT table and belong to the Relationship Domain."@en ; rdfs:label "Relationship" ; "relationship" . ### https://w3id.org/omop/ontology/SourceToConceptMap rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:date ] ; rdfs:comment "The source to concept map table is recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a Standard Concept as target_concept_ids that can be used to populate the Common Data Model tables. The SOURCE_TO_CONCEPT_MAP table is no longer populated with content within the Standardized Vocabularies published to the OMOP community. **There are OHDSI tools to help you populate this table; [Usagi](https://github.com/OHDSI/Usagi) and [Perseus](https://github.com/ohdsi/Perseus). You can read more about OMOP vocabulary mapping in [The Book of OHDSI Chapter 6.3](https://ohdsi.github.io/TheBookOfOhdsi/ExtractTransformLoad.html#step-2-create-the-code-mappings).**"@en ; rdfs:label "Source to concept map" ; "source_to_concept_map" . ### https://w3id.org/omop/ontology/Specimen rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom owl:Thing ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The specimen domain contains the records identifying biological samples from a person."@en ; rdfs:label "Specimen" ; "specimen" . ### https://w3id.org/omop/ontology/SurveyConduct rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Survey conduct" ; "survey_conduct" . ### https://w3id.org/omop/ontology/VisitDetail rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain."@en ; rdfs:label "Visit detail" ; "visit_detail" . ### https://w3id.org/omop/ontology/VisitOccurrence rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called \"Encounters\". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed."@en ; rdfs:label "Visit occurrence" ; "visit_occurrence" . ### https://w3id.org/omop/ontology/Vocabulary rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom xsd:string ] ; rdfs:comment "The VOCABULARY table includes a list of the Vocabularies integrated from various sources or created de novo in OMOP CDM. This reference table contains a single record for each Vocabulary and includes a descriptive name and other associated attributes for the Vocabulary."@en ; rdfs:label "Vocabulary" ; "vocabulary" . ### Generated by the OWL API (version 5.1.18) https://github.com/owlcs/owlapi/