Guide d'implémentation du GT Standards et Interopérabilité pour les EDS
0.1.0 - ci-build
Guide d'implémentation du GT Standards et Interopérabilité pour les EDS - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Draft as of 2024-10-08 |
Definitions for the OMOPEpisode logical model.
Guidance on how to interpret the contents of this table can be found here
0. OMOPEpisode | |
Definition | 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. |
Short | Episode OMOP Table |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPEpisode.episode-id | |
Definition | Episode Identifier |
Short | Episode Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPEpisode.person-id | |
Definition | The PERSON_ID of the PERSON for whom the episode is recorded. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPEpisode.episode-concept-id | |
Definition | The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment. |
Short | Episode |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPEpisode.episode-start-date | |
Definition | The date when the Episode beings. |
Short | Episode Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPEpisode.episode-start-datetime | |
Definition | The date and time when the Episode beings. |
Short | Episode Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPEpisode.episode-end-date | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Episode End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPEpisode.episode-end-datetime | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Epsisode End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPEpisode.episode-parent-id | |
Definition | 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. |
Short | Episode Parent |
Control | 0..1 |
Type | Reference(Episode OMOP Table) |
18. OMOPEpisode.episode-number | |
Definition | For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here. |
Short | Episode Number |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
20. OMOPEpisode.episode-object-concept-id | |
Definition | 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. |
Short | Episode Object |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
22. OMOPEpisode.episode-type-concept-id | |
Definition | 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. |
Short | Episode Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
24. OMOPEpisode.episode-source-value | |
Definition | 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. |
Short | Episode Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
26. OMOPEpisode.episode-source-concept-id | |
Definition | A foreign key to a Episode Concept that refers to the code used in the source. |
Short | Episode Source |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
Guidance on how to interpret the contents of this table can be found here
0. OMOPEpisode | |
Definition | 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. |
Short | Episode OMOP Table |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPEpisode.episode-id | |
Definition | Episode Identifier |
Short | Episode Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPEpisode.person-id | |
Definition | The PERSON_ID of the PERSON for whom the episode is recorded. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPEpisode.episode-concept-id | |
Definition | The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment. |
Short | Episode |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPEpisode.episode-start-date | |
Definition | The date when the Episode beings. |
Short | Episode Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPEpisode.episode-start-datetime | |
Definition | The date and time when the Episode beings. |
Short | Episode Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPEpisode.episode-end-date | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Episode End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPEpisode.episode-end-datetime | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Epsisode End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPEpisode.episode-parent-id | |
Definition | 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. |
Short | Episode Parent |
Control | 0..1 |
Type | Reference(Episode OMOP Table) |
18. OMOPEpisode.episode-number | |
Definition | For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here. |
Short | Episode Number |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
20. OMOPEpisode.episode-object-concept-id | |
Definition | 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. |
Short | Episode Object |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
22. OMOPEpisode.episode-type-concept-id | |
Definition | 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. |
Short | Episode Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
24. OMOPEpisode.episode-source-value | |
Definition | 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. |
Short | Episode Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
26. OMOPEpisode.episode-source-concept-id | |
Definition | A foreign key to a Episode Concept that refers to the code used in the source. |
Short | Episode Source |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
Guidance on how to interpret the contents of this table can be found here
0. OMOPEpisode | |
Definition | 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. |
Short | Episode OMOP Table |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPEpisode.episode-id | |
Definition | Episode Identifier |
Short | Episode Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPEpisode.person-id | |
Definition | The PERSON_ID of the PERSON for whom the episode is recorded. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPEpisode.episode-concept-id | |
Definition | The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment. |
Short | Episode |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPEpisode.episode-start-date | |
Definition | The date when the Episode beings. |
Short | Episode Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPEpisode.episode-start-datetime | |
Definition | The date and time when the Episode beings. |
Short | Episode Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPEpisode.episode-end-date | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Episode End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPEpisode.episode-end-datetime | |
Definition | The date when the instance of the Episode is considered to have ended. |
Short | Epsisode End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPEpisode.episode-parent-id | |
Definition | 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. |
Short | Episode Parent |
Control | 0..1 |
Type | Reference(Episode OMOP Table) |
18. OMOPEpisode.episode-number | |
Definition | For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here. |
Short | Episode Number |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
20. OMOPEpisode.episode-object-concept-id | |
Definition | 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. |
Short | Episode Object |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
22. OMOPEpisode.episode-type-concept-id | |
Definition | 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. |
Short | Episode Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
24. OMOPEpisode.episode-source-value | |
Definition | 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. |
Short | Episode Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
26. OMOPEpisode.episode-source-concept-id | |
Definition | A foreign key to a Episode Concept that refers to the code used in the source. |
Short | Episode Source |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |