https://w3id.org/omop/ontology/has_parent
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.
DOMAIN | PROPERTY | RANGE |
---|---|---|
Visit detail | Has parent | Visit detail |
@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_parent a owl:FunctionalProperty,
owl:ObjectProperty ;
rdfs:label "Has parent"^^xsd:string ;
owlready:python_name "parent"^^xsd:string ;
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:domain omop:VisitDetail ;
rdfs:range omop:VisitDetail ;
omop:omop_cdm_name "visit_detail.visit_detail_parent_id#59 AS VisitDetail"^^xsd:string .