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: OMOPDeviceExposure - Detailed Descriptions

Draft as of 2025-10-23

Definitions for the OMOPDeviceExposure 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. OMOPDeviceExposure
Définition | The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
Short | Device Exposure 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. OMOPDeviceExposure.device-exposure-id
Définition | Device Exposure Identifier
Short | Device Exposure Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPDeviceExposure.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPDeviceExposure.device-concept-id
Définition | The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
Short | Device
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPDeviceExposure.device-exposure-start-date
Définition | Use this date to determine the start date of the device record.
Short | Device Exposure Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPDeviceExposure.device-exposure-start-datetime
Définition | Device Exposure Start Datetime
Short | Device Exposure Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPDeviceExposure.device-exposure-end-date
Définition | The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
Short | Device Exposure End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPDeviceExposure.device-exposure-end-datetime
Définition | Device Exposure End Datetime
Short | Device Exposure End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPDeviceExposure.device-type-concept-id
Définition | You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
Short | Device Type Concept Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPDeviceExposure.unique-device-id
Définition | This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
Short | Unique Device Identifier
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPDeviceExposure.production-id
Définition | This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
Short | Production Identifier
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPDeviceExposure.quantity
Définition | Quantity
Short | Quantity
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPDeviceExposure.provider-id
Définition | The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
26. OMOPDeviceExposure.visit-occurrence-id
Définition | The Visit during which the device was prescribed or given.
Short | Visit Occurence Identifier
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
28. OMOPDeviceExposure.visit-detail-id
Définition | The Visit Detail during which the device was prescribed or given.
Short | Visit Detail Identifier
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
30. OMOPDeviceExposure.device-source-value
Définition | This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
Short | Device Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
32. OMOPDeviceExposure.device-source-concept-id
Définition | This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Device Source
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPDeviceExposure.unit-concept-id
Définition | UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
Short | Unit
Control | 0..1
Type | Reference(Concept OMOP Table)
36. OMOPDeviceExposure.unit-source-value
Définition | This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
Short | Unit Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
38. OMOPDeviceExposure.unit-source-concept-id
Définition | This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Unit Source
Control | 0..1
Type | Reference(Concept OMOP Table)

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

0. OMOPDeviceExposure
Définition | The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
Short | Device Exposure OMOP Table
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPDeviceExposure.device-exposure-id
Définition | Device Exposure Identifier
Short | Device Exposure Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPDeviceExposure.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPDeviceExposure.device-concept-id
Définition | The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
Short | Device
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPDeviceExposure.device-exposure-start-date
Définition | Use this date to determine the start date of the device record.
Short | Device Exposure Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPDeviceExposure.device-exposure-start-datetime
Définition | Device Exposure Start Datetime
Short | Device Exposure Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPDeviceExposure.device-exposure-end-date
Définition | The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
Short | Device Exposure End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPDeviceExposure.device-exposure-end-datetime
Définition | Device Exposure End Datetime
Short | Device Exposure End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPDeviceExposure.device-type-concept-id
Définition | You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
Short | Device Type Concept Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPDeviceExposure.unique-device-id
Définition | This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
Short | Unique Device Identifier
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPDeviceExposure.production-id
Définition | This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
Short | Production Identifier
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPDeviceExposure.quantity
Définition | Quantity
Short | Quantity
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPDeviceExposure.provider-id
Définition | The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
26. OMOPDeviceExposure.visit-occurrence-id
Définition | The Visit during which the device was prescribed or given.
Short | Visit Occurence Identifier
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
28. OMOPDeviceExposure.visit-detail-id
Définition | The Visit Detail during which the device was prescribed or given.
Short | Visit Detail Identifier
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
30. OMOPDeviceExposure.device-source-value
Définition | This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
Short | Device Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
32. OMOPDeviceExposure.device-source-concept-id
Définition | This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Device Source
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPDeviceExposure.unit-concept-id
Définition | UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
Short | Unit
Control | 0..1
Type | Reference(Concept OMOP Table)
36. OMOPDeviceExposure.unit-source-value
Définition | This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
Short | Unit Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
38. OMOPDeviceExposure.unit-source-concept-id
Définition | This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Unit Source
Control | 0..1
Type | Reference(Concept OMOP Table)

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

0. OMOPDeviceExposure
Définition | The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
Short | Device Exposure 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. OMOPDeviceExposure.device-exposure-id
Définition | Device Exposure Identifier
Short | Device Exposure Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPDeviceExposure.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPDeviceExposure.device-concept-id
Définition | The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
Short | Device
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPDeviceExposure.device-exposure-start-date
Définition | Use this date to determine the start date of the device record.
Short | Device Exposure Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPDeviceExposure.device-exposure-start-datetime
Définition | Device Exposure Start Datetime
Short | Device Exposure Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPDeviceExposure.device-exposure-end-date
Définition | The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
Short | Device Exposure End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPDeviceExposure.device-exposure-end-datetime
Définition | Device Exposure End Datetime
Short | Device Exposure End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPDeviceExposure.device-type-concept-id
Définition | You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
Short | Device Type Concept Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPDeviceExposure.unique-device-id
Définition | This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
Short | Unique Device Identifier
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPDeviceExposure.production-id
Définition | This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
Short | Production Identifier
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPDeviceExposure.quantity
Définition | Quantity
Short | Quantity
Control | 0..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPDeviceExposure.provider-id
Définition | The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
26. OMOPDeviceExposure.visit-occurrence-id
Définition | The Visit during which the device was prescribed or given.
Short | Visit Occurence Identifier
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
28. OMOPDeviceExposure.visit-detail-id
Définition | The Visit Detail during which the device was prescribed or given.
Short | Visit Detail Identifier
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
30. OMOPDeviceExposure.device-source-value
Définition | This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
Short | Device Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
32. OMOPDeviceExposure.device-source-concept-id
Définition | This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Device Source
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPDeviceExposure.unit-concept-id
Définition | UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
Short | Unit
Control | 0..1
Type | Reference(Concept OMOP Table)
36. OMOPDeviceExposure.unit-source-value
Définition | This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
Short | Unit Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
38. OMOPDeviceExposure.unit-source-concept-id
Définition | This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
Short | Unit Source
Control | 0..1
Type | Reference(Concept OMOP Table)