Survey conduct leaf node

OMOP CDM thing
- Survey conduct

URI

https://w3id.org/omop/ontology/SurveyConduct

Label

Survey conduct

Description

The SURVEY_CONDUCT table is used to store an instance of a completed survey or questionnaire.

Superclasses (1)

OMOP CDM thing

Usage

Instances of Survey conduct can have the following properties:

PROPERTY	TYPE	DESCRIPTION	RANGE
From class Survey conduct
Assisted source value	owl:DatatypeProperty	For Survey Conduct: Source value representing whether patient required assistance to complete the survey. Example: 'Completed without assistance', 'Completed with assistance'.	string
Collection method source value	owl:DatatypeProperty	For Survey Conduct: The collection method as it appears in the source data.	string
Respondent type source value	owl:DatatypeProperty	For Survey Conduct: Source code representing role of person who completed the survey.	string
Survey end date	owl:DatatypeProperty	For Survey Conduct: Date on which the survey was completed.	date
Survey end datetime	owl:DatatypeProperty	For Survey Conduct: If no time given, set to midnight.	dateTime
Survey source identifier	owl:DatatypeProperty	For Survey Conduct: Unique identifier for each completed survey in source system.	string
Survey source value	owl:DatatypeProperty	For Survey Conduct: The survey name as it appears in the source data.	string
Survey start date	owl:DatatypeProperty	For Survey Conduct: Date on which the survey was started.	date
Survey start datetime	owl:DatatypeProperty	For Survey Conduct: If no time given, set to midnight.	dateTime
Survey version number	owl:DatatypeProperty	For Survey Conduct: Version number of the questionnaire or survey used.	string
Timing source value	owl:DatatypeProperty	For Survey Conduct: Text string representing the timing of the survey. Example: Baseline, 6-month follow-up.	string
Validated survey source value	owl:DatatypeProperty	For Survey Conduct: Source value representing the validation status of the survey.	integer
Has assisted	owl:FunctionalProperty	For Survey Conduct: This is a Concept that represents whether the survey was completed with assistance or independently. There is no specific domain or class for this field, just choose the one that best represents the value given in the source.	Concept
Has collection method	owl:FunctionalProperty	For Survey Conduct: This Concept represents how the responses were collected. Use the concepts that have the relationship 'Has Answer' with the CONCEPT_ID [42529316](https://athena.ohdsi.org/search-terms/terms/42529316).	Concept
Has respondent type	owl:FunctionalProperty	For Survey Conduct: This is a Concept that represents who actually recorded the answers to the survey. For example, this could be the patient or a research associate. There is no specific domain or class for this field, just choose the one that best represents the value given in the source.	Concept
Has response visit occurrence	owl:FunctionalProperty	For Survey Conduct: The Visit during which any treatment related to the Survey was carried out.	Visit occurrence
Has survey	owl:FunctionalProperty	For Survey Conduct: This is the Concept that represents the survey that was completed. Put the CONCEPT_ID that identifies the survey that the Person completed. There is no specified domain for this table but the concept class 'staging/scales' contains many common surveys. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&conceptClass=Staging+%2F+Scales&page=5&pageSize=15&query=).	Concept
Has survey source	owl:FunctionalProperty	For Survey Conduct: If unavailable, set to 0.	Concept
Has timing	owl:FunctionalProperty	For Survey Conduct: This is a Concept that represents the timing of the survey. For example this could be the 3-month follow-up appointment. There is no specific domain or class for this field, just choose the one that best represents the value given in the source.	Concept
Has validated survey	owl:FunctionalProperty	For Survey Conduct: If unavailable, set to 0.	Concept
From class OMOP CDM thing
Id	owl:DatatypeProperty	For Note: A unique identifier for each note. - For Vocabulary: A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit. - 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. - For Note Nlp: A unique identifier for the NLP record. - 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. - 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. - For Specimen: Unique identifier for each specimen. - 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. - For Cohort Definition: This is the identifier given to the cohort, usually by the ATLAS application - For Concept Class: A unique key for each class. - 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. - 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. - For Cost: A unique identifier for each COST record. - For Domain: A unique key for each domain. - For Survey Conduct: Unique identifier for each completed survey. For each instance of a survey completion create a unique identifier. - 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. - For Care Site: Assign an id to each unique combination of location_id and place_of_service_source_value. - For Concept: A unique identifier for each Concept across all domains. - 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. - 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. - 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. - 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. - 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. - For Payer Plan Period: A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time.	owl:Thing
From class Thing
OMOP CDM name	owl:AnnotationProperty		owl:Thing

Implementation

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

omop:SurveyConduct a owl:Class ;
    rdfs:label "Survey conduct"^^xsd:string ;
    rdfs:comment "The SURVEY_CONDUCT table is used to store an instance of a completed survey or questionnaire."@en ;
    rdfs:subClassOf [ a owl:Restriction ;
            owl:onProperty [ owl:inverseOf omop:has_survey_conduct ] ;
            owl:someValuesFrom omop:Person ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_survey ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_survey ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:date ;
            owl:onProperty omop:survey_start_date ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:dateTime ;
            owl:onProperty omop:survey_start_datetime ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:date ;
            owl:onProperty omop:survey_end_date ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:dateTime ;
            owl:onProperty omop:survey_end_datetime ],
        [ a owl:Restriction ;
            owl:onProperty omop:survey_end_datetime ;
            owl:someValuesFrom xsd:dateTime ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_assisted ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_assisted ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_respondent_type ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_respondent_type ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_timing ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_timing ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_collection_method ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_collection_method ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:assisted_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:respondent_type_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:timing_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:collection_method_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:survey_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_survey_source ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_survey_source ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:survey_source_identifier ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Concept ;
            owl:onProperty omop:has_validated_survey ],
        [ a owl:Restriction ;
            owl:onProperty omop:has_validated_survey ;
            owl:someValuesFrom omop:Concept ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:integer ;
            owl:onProperty omop:validated_survey_source_value ],
        [ a owl:Restriction ;
            owl:allValuesFrom xsd:string ;
            owl:onProperty omop:survey_version_number ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:VisitOccurrence ;
            owl:onProperty omop:has_response_visit_occurrence ],
        [ a owl:Restriction ;
            owl:allValuesFrom omop:Provider ;
            owl:onProperty omop:has_provider ],
        omop:OmopCDMThing ;
    omop:omop_cdm_name "survey_conduct"^^xsd:string .