Has place of service 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 rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

omop:has_place_of_service a owl:FunctionalProperty,
        owl:ObjectProperty ;
    rdfs:label "Has place of service"^^xsd:string ;
    owlready:python_name "place_of_service"^^xsd:string ;
    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. If this information is not available then set to 0. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=2&pageSize=15&query=)."""@en ;
    rdfs:domain omop:CareSite ;
    rdfs:range omop:Concept ;
    omop:omop_cdm_name "care_site.place_of_service_concept_id#269 AS Concept"^^xsd:string .