Narratif généré : DéfinitionStructure OMOPDeviceExposure Nom Drapeaux Card. Type Description et contraintes <a href="StructureDefinition-OMOPDeviceExposure-definitions.html#OMOPDeviceExposure" title="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).).">OMOPDeviceExposure 0..* Base Device Exposure OMOP Table Instances of this logical model can be the target of a Reference #xD; device_exposure_id 1..1 integer Device Exposure Identifier #xD; person_id 1..1 Reference(Person OMOP Table) Person #xD; device_concept_id 1..1 Reference(Concept OMOP Table) Device #xD; device_exposure_start_date 1..1 date Device Exposure Start Date #xD; device_exposure_start_datetime 0..1 dateTime Device Exposure Start Datetime #xD; device_exposure_end_date 0..1 date Device Exposure End Date #xD; device_exposure_end_datetime 0..1 dateTime Device Exposure End Datetime #xD; device_type_concept_id 1..1 integer Device Type Concept Identifier #xD; unique_device_id 0..1 string Unique Device Identifier #xD; production_id 0..1 integer Production Identifier #xD; quantity 0..1 integer Quantity #xD; provider_id 0..1 Reference(Provider OMOP Table) Provider #xD; visit_occurrence_id 0..1 Reference(Visit Occurrence OMOP Table) Visit Occurence Identifier #xD; visit_detail_id 0..1 Reference(Visit Detail OMOP Table) Visit Detail Identifier #xD; device_source_value 0..1 string Device Source Value #xD; <a href="StructureDefinition-OMOPDeviceExposure-definitions.html#OMOPDeviceExposure.device-source-concept-id" title="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.">device_source_concept_id 0..1 Reference(Concept OMOP Table) Device Source #xD; unit_concept_id 0..1 Reference(Concept OMOP Table) Unit #xD; unit_source_value 0..1 string Unit Source Value #xD; <a href="StructureDefinition-OMOPDeviceExposure-definitions.html#OMOPDeviceExposure.unit-source-concept-id" title="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.">unit_source_concept_id 0..1 Reference(Concept OMOP Table) Unit Source #xD; Documentation for this format
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).).
The PERSON_ID of the PERSON for whom the condition is recorded.
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.
Use this date to determine the start date of the device record.
The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
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.
This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
The Visit during which the device was prescribed or given.
The Visit Detail during which the device was prescribed or given.
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.
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.
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.
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.
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.