Id leaf node

@prefix omop: <https://w3id.org/omop/ontology/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

omop:id a owl:DatatypeProperty,
        owl:FunctionalProperty ;
    rdfs:label "Id"^^xsd:string ;
    rdfs:comment "For Care Site: Assign an id to each unique combination of location_id and place_of_service_source_value."@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 Cost: A unique identifier for each COST record."@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 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 Specimen: Unique identifier for each specimen."@en,
        """For Survey Conduct: Unique identifier for each completed survey.
For each instance of a survey completion create a unique identifier."""@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:domain omop:OmopCDMThing ;
    rdfs:range [ a rdfs:Datatype ;
            owl:unionOf ( xsd:integer xsd:string ) ] ;
    omop:omop_cdm_name "care_site.care_site_id#267 AS int|str"^^xsd:string,
        "cohort_definition.cohort_definition_id#427 AS int|str"^^xsd:string,
        "concept.concept_id#362 AS int|str"^^xsd:string,
        "concept_class.concept_class_id#380 AS int|str"^^xsd:string,
        "condition_era.condition_era_id#339 AS int|str"^^xsd:string,
        "condition_occurrence.condition_occurrence_id#61 AS int|str"^^xsd:string,
        "cost.cost_id#307 AS int|str"^^xsd:string,
        "device_exposure.device_exposure_id#114 AS int|str"^^xsd:string,
        "domain.domain_id#377 AS int|str"^^xsd:string,
        "dose_era.dose_era_id#332 AS int|str"^^xsd:string,
        "drug_era.drug_era_id#325 AS int|str"^^xsd:string,
        "drug_exposure.drug_exposure_id#77 AS int|str"^^xsd:string,
        "location.location_id#251 AS int|str"^^xsd:string,
        "measurement.measurement_id#129 AS int|str"^^xsd:string,
        "note.note_id#177 AS int|str"^^xsd:string,
        "note_nlp.note_nlp_id#193 AS int|str"^^xsd:string,
        "observation.observation_id#149 AS int|str"^^xsd:string,
        "observation_period.observation_period_id#20 AS int|str"^^xsd:string,
        "payer_plan_period.payer_plan_period_id#286 AS int|str"^^xsd:string,
        "person.person_id#1 AS int|str"^^xsd:string,
        "procedure_occurrence.procedure_occurrence_id#100 AS int|str"^^xsd:string,
        "provider.provider_id#273 AS int|str"^^xsd:string,
        "relationship.relationship_id#389 AS int|str"^^xsd:string,
        "specimen.specimen_id#207 AS int|str"^^xsd:string,
        "survey_conduct.survey_conduct_id#227 AS int|str"^^xsd:string,
        "visit_detail.visit_detail_id#42 AS int|str"^^xsd:string,
        "visit_occurrence.visit_occurrence_id#25 AS int|str"^^xsd:string,
        "vocabulary.vocabulary_id#372 AS int|str"^^xsd:string .