The EPISODE table aggregates lower-level clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) into a higher-level abstraction representing clinically and analytically relevant disease phases,outcomes and treatments. The EPISODE_EVENT table connects qualifying clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) to the appropriate EPISODE entry. For example cancers including their development over time, their treatment, and final resolution.

Episode Identifier

The PERSON_ID of the PERSON for whom the episode is recorded.

The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment.

The date when the Episode beings.

The date and time when the Episode beings.

The date when the instance of the Episode is considered to have ended.

The date when the instance of the Episode is considered to have ended.

Use this field to find the Episode that subsumes the given Episode record. This is used in the case that an Episode are nested into each other.

For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here.

A Standard Concept representing the disease phase, outcome, or other abstraction of which the episode consists. For example, if the EPISODE_CONCEPT_ID is treatment regimen then the EPISODE_OBJECT_CONCEPT_ID should contain the chemotherapy regimen concept, like Afatinib monotherapy.

This field can be used to determine the provenance of the Episode record, as in whether the episode was from an EHR system, insurance claim, registry, or other sources.

The source code for the Episdoe as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.

A foreign key to a Episode Concept that refers to the code used in the source.

The EPISODE table aggregates lower-level clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) into a higher-level abstraction representing clinically and analytically relevant disease phases,outcomes and treatments. The EPISODE_EVENT table connects qualifying clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) to the appropriate EPISODE entry. For example cancers including their development over time, their treatment, and final resolution.

Episode Identifier

The PERSON_ID of the PERSON for whom the episode is recorded.

The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment.

The date when the Episode beings.

The date and time when the Episode beings.

The date when the instance of the Episode is considered to have ended.

The date when the instance of the Episode is considered to have ended.

Use this field to find the Episode that subsumes the given Episode record. This is used in the case that an Episode are nested into each other.

For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here.

A Standard Concept representing the disease phase, outcome, or other abstraction of which the episode consists. For example, if the EPISODE_CONCEPT_ID is treatment regimen then the EPISODE_OBJECT_CONCEPT_ID should contain the chemotherapy regimen concept, like Afatinib monotherapy.

This field can be used to determine the provenance of the Episode record, as in whether the episode was from an EHR system, insurance claim, registry, or other sources.

The source code for the Episdoe as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.

A foreign key to a Episode Concept that refers to the code used in the source.

The EPISODE table aggregates lower-level clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) into a higher-level abstraction representing clinically and analytically relevant disease phases,outcomes and treatments. The EPISODE_EVENT table connects qualifying clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) to the appropriate EPISODE entry. For example cancers including their development over time, their treatment, and final resolution.

Episode Identifier

The PERSON_ID of the PERSON for whom the episode is recorded.

The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment.

The date when the Episode beings.

The date and time when the Episode beings.

The date when the instance of the Episode is considered to have ended.

The date when the instance of the Episode is considered to have ended.

Use this field to find the Episode that subsumes the given Episode record. This is used in the case that an Episode are nested into each other.

For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here.

A Standard Concept representing the disease phase, outcome, or other abstraction of which the episode consists. For example, if the EPISODE_CONCEPT_ID is treatment regimen then the EPISODE_OBJECT_CONCEPT_ID should contain the chemotherapy regimen concept, like Afatinib monotherapy.

This field can be used to determine the provenance of the Episode record, as in whether the episode was from an EHR system, insurance claim, registry, or other sources.

The source code for the Episdoe as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.

A foreign key to a Episode Concept that refers to the code used in the source.