Data Management with FHIR
0.1.0 - ci-build

Data Management with FHIR - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Logical Model: OMOPConditionEra - Detailed Descriptions

Draft as of 2025-10-23

Definitions for the OMOPConditionEra logical model.

- Key Elements Table
- Differential Elements Table
- Snapshot Elements Table

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConditionEra
Définition | A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence. Combining individual Condition Occurrences into a single Condition Era serves two purposes: It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event. It allows aggregation of multiple, closely timed doctor visits for the same Condition to avoid double-counting the Condition Occurrences. For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era.
Short | Condition Era 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. OMOPConditionEra.condition-era-id
Définition | Condition Era Identifier
Short | Condition Era Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionEra.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionEra.condition-concept-id
Définition | The Concept Id representing the Condition.
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionEra.condition-era-start-date
Définition | The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very firstchronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
Short | Condition Era Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionEra.condition-era-end-date
Définition | The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
Short | Condition Era End Date
Control | 1..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionEra.condition-occurrence-count
Définition | The number of individual Condition Occurrences used to construct the condition era.
Short | Condition Occurence Count
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConditionEra
Définition | A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence. Combining individual Condition Occurrences into a single Condition Era serves two purposes: It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event. It allows aggregation of multiple, closely timed doctor visits for the same Condition to avoid double-counting the Condition Occurrences. For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era.
Short | Condition Era OMOP Table
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPConditionEra.condition-era-id
Définition | Condition Era Identifier
Short | Condition Era Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionEra.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionEra.condition-concept-id
Définition | The Concept Id representing the Condition.
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionEra.condition-era-start-date
Définition | The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very firstchronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
Short | Condition Era Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionEra.condition-era-end-date
Définition | The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
Short | Condition Era End Date
Control | 1..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionEra.condition-occurrence-count
Définition | The number of individual Condition Occurrences used to construct the condition era.
Short | Condition Occurence Count
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConditionEra
Définition | A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence. Combining individual Condition Occurrences into a single Condition Era serves two purposes: It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event. It allows aggregation of multiple, closely timed doctor visits for the same Condition to avoid double-counting the Condition Occurrences. For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era.
Short | Condition Era 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. OMOPConditionEra.condition-era-id
Définition | Condition Era Identifier
Short | Condition Era Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionEra.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionEra.condition-concept-id
Définition | The Concept Id representing the Condition.
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionEra.condition-era-start-date
Définition | The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very firstchronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
Short | Condition Era Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionEra.condition-era-end-date
Définition | The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
Short | Condition Era End Date
Control | 1..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionEra.condition-occurrence-count
Définition | The number of individual Condition Occurrences used to construct the condition era.
Short | Condition Occurence Count
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension