End date leaf node


URI

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

Label

End date

Description

For Visit Occurrence: For inpatient visits the end date is typically the discharge date.
Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:
Outpatient Visit: visit_end_datetime = visit_start_datetime
Emergency Room Visit: visit_end_datetime = visit_start_datetime
Inpatient Visit: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs.
Non-hospital institution Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.
For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 "Still patient" to identify the visit as incomplete.
All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date. - For Device Exposure: The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable. - For Condition Occurrence: Use this date to determine the end date of the condition
Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE. - For Visit Detail: This the end date of the patient-provider interaction.
Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:<br>
- Outpatient Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
- Emergency Room Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
- Inpatient Visit Detail: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs.
- Non-hospital institution Visit Details: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.<br>
For Inpatient Visit Details ongoing at the date of ETL, put date of processing the data into visit_detai_end_datetime and visit_detail_type_concept_id with 32220 "Still patient" to identify the visit as incomplete.
All other Visits Details: visit_detail_end_datetime = visit_detail_start_datetime. - For Payer Plan Period: End date of Plan coverage. - For Location History: The date the relationship ended - For Drug Exposure: The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.
If this information is not explicitly available in the data, infer the end date using the following methods:/n/n 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. [Examples by dose form](https://ohdsi.github.io/CommonDataModel/drug_dose.html) - For Observation Period: Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded.
It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer.

Usage

DOMAINPROPERTYRANGE
Date duration End date date

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:end_date a owl:DatatypeProperty,
        owl:FunctionalProperty ;
    rdfs:label "End date"^^xsd:string ;
    rdfs:comment """For Condition Occurrence: Use this date to determine the end date of the condition
Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE."""@en,
        """For Device Exposure: The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable."""@en,
        """For Drug Exposure: The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.
If this information is not explicitly available in the data, infer the end date using the following methods:/n/n 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. [Examples by dose form](https://ohdsi.github.io/CommonDataModel/drug_dose.html)"""@en,
        "For Location History: The date the relationship ended"@en,
        """For Observation Period: Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded.
It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer."""@en,
        "For Payer Plan Period: End date of Plan coverage."@en,
        """For Visit Detail: This the end date of the patient-provider interaction.
Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:<br>
- Outpatient Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
- Emergency Room Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
- Inpatient Visit Detail: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs.
- Non-hospital institution Visit Details: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.<br>
For Inpatient Visit Details ongoing at the date of ETL, put date of processing the data into visit_detai_end_datetime and visit_detail_type_concept_id with 32220 "Still patient" to identify the visit as incomplete.
All other Visits Details: visit_detail_end_datetime = visit_detail_start_datetime."""@en,
        """For Visit Occurrence: For inpatient visits the end date is typically the discharge date.
Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:
Outpatient Visit: visit_end_datetime = visit_start_datetime
Emergency Room Visit: visit_end_datetime = visit_start_datetime
Inpatient Visit: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs.
Non-hospital institution Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.
For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 "Still patient" to identify the visit as incomplete.
All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date."""@en ;
    rdfs:domain omop:DateDuration ;
    rdfs:range xsd:date ;
    omop:omop_cdm_name "cohort.cohort_end_date#426 AS date"^^xsd:string,
        "condition_occurrence.condition_end_date#66 AS date"^^xsd:string,
        "device_exposure.device_exposure_end_date#119 AS date"^^xsd:string,
        "drug_exposure.drug_exposure_end_date#82 AS date"^^xsd:string,
        "location_history.end_date#266 AS date"^^xsd:string,
        "observation_period.observation_period_end_date#23 AS date"^^xsd:string,
        "payer_plan_period.payer_plan_period_end_date#290 AS date"^^xsd:string,
        "visit_detail.visit_detail_end_date#47 AS date"^^xsd:string,
        "visit_occurrence.visit_end_date#30 AS date"^^xsd:string .