https://w3id.org/omop/ontology/has_observation
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. - reversed relation, For Observation: The PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code. - 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.
| DOMAIN | PROPERTY | RANGE |
|---|---|---|
| Blank node (see implementation) | Has observation | Observation |
@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_observation a owl:ObjectProperty ;
rdfs:label "Has observation"^^xsd:string ;
owlready:python_name "observations"^^xsd:string ;
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:domain [ a owl:Class ;
owl:unionOf ( omop:BaseVisit omop:Person ) ] ;
rdfs:range omop:Observation ;
omop:omop_cdm_name "observation.person_id#150 AS Person"^^xsd:string,
"observation.visit_detail_id#162 AS VisitDetail"^^xsd:string,
"observation.visit_occurrence_id#161 AS VisitOccurrence"^^xsd:string .