FHIR to OMOP FHIR IG
1.0.0-ballot - INFORMATIVE 1 - Ballot
FHIR to OMOP FHIR IG
1.0.0-ballot - INFORMATIVE 1 - Ballot
This page is part of the Vulcan FHIR to OMOP FHIR Implementation Guide (v1.0.0-ballot: INFORMATIVE 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
| Page standards status: Informative | Maturity Level: 1 |
Definitions for the Death logical model.
Guidance on how to interpret the contents of this table can be foundhere
| 0. Death | |
| Definition | The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data. Base definition for all types defined in FHIR type system. |
| Short | Death OMOP TableBase for all types and resources |
| Control | 0..* |
| Is Modifier | false |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. Death.person-id | |
| Definition | Person |
| Short | Person |
| Control | 1..1 |
| Type | Reference(Person OMOP Table) |
| 4. Death.death-date | |
| Definition | The date the person was deceased. |
| Short | Death Date |
| Control | 1..1 |
| Type | date |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. Death.death-datetime | |
| Definition | Death Datetime |
| Short | Death Datetime |
| Control | 0..1 |
| Type | dateTime |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. Death.death-type-concept-id | |
| Definition | This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc. |
| Short | Death Type |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. Death.cause-concept-id | |
| Definition | This is the Standard Concept representing the Person's cause of death, if available. |
| Short | Cause |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. Death.cause-source-value | |
| Definition | Cause Source Value |
| Short | Cause Source Value |
| Control | 0..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 14. Death.cause-source-concept-id | |
| Definition | Cause Source |
| Short | Cause Source |
| Control | 0..1 |
| Type | code |
| 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. Death | |
| Definition | The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data. |
| Short | Death OMOP Table |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. Death.person-id | |
| Definition | Person |
| Short | Person |
| Control | 1..1 |
| Type | Reference(Person OMOP Table) |
| 4. Death.death-date | |
| Definition | The date the person was deceased. |
| Short | Death Date |
| Control | 1..1 |
| Type | date |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. Death.death-datetime | |
| Definition | Death Datetime |
| Short | Death Datetime |
| Control | 0..1 |
| Type | dateTime |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. Death.death-type-concept-id | |
| Definition | This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc. |
| Short | Death Type |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. Death.cause-concept-id | |
| Definition | This is the Standard Concept representing the Person's cause of death, if available. |
| Short | Cause |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. Death.cause-source-value | |
| Definition | Cause Source Value |
| Short | Cause Source Value |
| Control | 0..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 14. Death.cause-source-concept-id | |
| Definition | Cause Source |
| Short | Cause Source |
| Control | 0..1 |
| Type | code |
| 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. Death | |
| Definition | The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data. |
| Short | Death 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. Death.person-id | |
| Definition | Person |
| Short | Person |
| Control | 1..1 |
| Type | Reference(Person OMOP Table) |
| 4. Death.death-date | |
| Definition | The date the person was deceased. |
| Short | Death Date |
| Control | 1..1 |
| Type | date |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. Death.death-datetime | |
| Definition | Death Datetime |
| Short | Death Datetime |
| Control | 0..1 |
| Type | dateTime |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. Death.death-type-concept-id | |
| Definition | This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc. |
| Short | Death Type |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. Death.cause-concept-id | |
| Definition | This is the Standard Concept representing the Person's cause of death, if available. |
| Short | Cause |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. Death.cause-source-value | |
| Definition | Cause Source Value |
| Short | Cause Source Value |
| Control | 0..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 14. Death.cause-source-concept-id | |
| Definition | Cause Source |
| Short | Cause Source |
| Control | 0..1 |
| Type | code |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
IG © 2023+ HL7 International / Biomedical Research and Regulation. Package hl7.fhir.uv.omop#1.0.0-ballot based on FHIR 5.0.0. Generated 2025-07-29
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change