Has source leaf node

@prefix omop: <https://w3id.org/omop/ontology/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix owlready: <http://www.lesfleursdunormal.fr/static/_downloads/owlready_ontology.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:has_source a owl:FunctionalProperty,
        owl:ObjectProperty ;
    rdfs:label "Has source"^^xsd:string ;
    owlready:python_name "source"^^xsd:string ;
    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:domain [ a owl:Class ;
            owl:unionOf ( omop:ProcedureOccurrence omop:BaseVisit omop:ConditionOccurrence omop:Exposure omop:Measurement omop:Observation omop:NoteNlp omop:Specimen omop:SourceToConceptMap ) ] ;
    omop:omop_cdm_name "condition_occurrence.condition_source_concept_id#74 AS Concept"^^xsd:string,
        "device_exposure.device_source_concept_id#130 AS Concept"^^xsd:string,
        "drug_exposure.drug_source_concept_id#96 AS Concept"^^xsd:string,
        "measurement.measurement_source_concept_id#151 AS Concept"^^xsd:string,
        "note_nlp.note_nlp_source_concept_id#208 AS Concept"^^xsd:string,
        "observation.observation_source_concept_id#172 AS Concept"^^xsd:string,
        "procedure_occurrence.procedure_source_concept_id#113 AS Concept"^^xsd:string,
        "source_to_concept_map.source_concept_id#386 AS Concept"^^xsd:string,
        "specimen.specimen_source_id#225 AS Thing"^^xsd:string,
        "visit_detail.visit_detail_source_concept_id#52 AS Concept"^^xsd:string,
        "visit_occurrence.visit_source_concept_id#35 AS Concept"^^xsd:string .