OHDSI GIS WG

OMOP GIS Schema Extensions

location_history

Access DDL scripts here

Table Description

This table is a copy of the OMOP Location_History table.

User Guide

NA NA NA NA NA NA

ETL Conventions

NA NA NA NA NA NA

Gaia Field	User Guide	ETL Conventions	Datatype	Required	Primary Key	Foreign Key	FK Table	FK Domain
location_id			integer	Yes	No	Yes	location
relationship_type_concept_id			integer	Yes	No	Yes	concept
domain_id			integer	Yes	No	No
entity_id			integer	Yes	No	No
start_date			date	Yes	No	No
end_date			date	No	No	No

external_exposure

Access DDL scripts here

Table Description

This CDM Extension table is used to represent person-related transformations of data from Gaia and to interface with ATLAS and OHDSI tool stack from an OMOP CDM database.

User Guide

The unique key given to a social or environmental exposure for a Person The LOCATION_ID of the Person for whom the exposure is associated. The PERSON_ID of the Person for whom the exposure is associated. The EXPOSURE_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 value which represents a exposure. Use this date to determine the start date of the exposure. NA Use this date to determine the end date of the exposure. NA This field identifies the origin of the exposure record (e.g. Census, EHR, Environmental data, Geospatial data, Satellite imagery, GIS mapping, Sensor network, Mobile device geolocation, LiDAR) This field can be used to determine the spatiotemporal relationship between the source Exposure and the Person This field can be used to determine the original source of place-based exposure data This field houses the verbatim name of the original source of place-based exposure data. NA NA NA NA The meaning of Concept?4172703?for ?=? is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it?s important when devising analyses to not to forget testing for the content of this field for values different from =. This is the numerical value of the Exposure, if available. If the raw data gives a categorial result for exposures those values are captured and mapped to standard concepts in the ?Exposure Value? domain. 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.

ETL Conventions

Each derived instance of an exposure should be assigned this unique key. NA NA The CONCEPT_ID to which the source exposure is mapped. This mapping should be integrated into the variable_source record and automatically populated in this record. The date range of the exposure should represent the temporal overlap between the place-based exposure data point and the LOCATION_ID’s location_history record. NA The date range of the exposure should represent the temporal overlap between the place-based exposure data point and the LOCATION_ID’s location_history record. NA The CONCEPT_ID to which the exposure’s data source type is mapped. This mapping should be integrated into the data_source record and automatically populated in this record. The CONCEPT_ID to which the relationship between the Exposure and the Person is mapped. This mapping should be automatically populated in this record. The CONCEPT_ID to which the exposure’s data source is mapped. This mapping should be integrated into the data_source record and automatically populated in this record. This name is mapped to a Standard Exposure Source Concept and the original name is stored here for reference. NA NA NA NA NA This value should be integrated into the variable_source record and automatically populated in this record. This mapping should be integrated into the variable_source record and automatically populated in this record. This mapping should be integrated into the variable_source record and automatically populated in this record.

Gaia Field	User Guide	ETL Conventions	Datatype	Required	Primary Key	Foreign Key	FK Table	FK Domain
external_exposure_id	The unique key given to a social or environmental exposure for a Person	Each derived instance of an exposure should be assigned this unique key.	integer	Yes	Yes	No
location_id	The LOCATION_ID of the Person for whom the exposure is associated.		integer	Yes	No	Yes	location
person_id	The PERSON_ID of the Person for whom the exposure is associated.		integer	Yes	No	Yes	person
exposure_concept_id	The EXPOSURE_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 value which represents a exposure.	The CONCEPT_ID to which the source exposure is mapped. This mapping should be integrated into the variable_source record and automatically populated in this record.	integer	Yes	No	Yes	concept
exposure_start_date	Use this date to determine the start date of the exposure.	The date range of the exposure should represent the temporal overlap between the place-based exposure data point and the LOCATION_ID’s location_history record.	date	Yes	No	No
exposure_start_datetime			datetime	No	No	No
exposure_end_date	Use this date to determine the end date of the exposure.	The date range of the exposure should represent the temporal overlap between the place-based exposure data point and the LOCATION_ID’s location_history record.	date	Yes	No	No
exposure_end_datetime			datetime	No	No	No
exposure_type_concept_id	This field identifies the origin of the exposure record (e.g. Census, EHR, Environmental data, Geospatial data, Satellite imagery, GIS mapping, Sensor network, Mobile device geolocation, LiDAR)	The CONCEPT_ID to which the exposure’s data source type is mapped. This mapping should be integrated into the data_source record and automatically populated in this record.	integer	Yes	No	Yes	concept	Type Concept
exposure_relationship_concept_id	This field can be used to determine the spatiotemporal relationship between the source Exposure and the Person	The CONCEPT_ID to which the relationship between the Exposure and the Person is mapped. This mapping should be automatically populated in this record.	integer	Yes	No	Yes	concept
exposure_source_concept_id	This field can be used to determine the original source of place-based exposure data	The CONCEPT_ID to which the exposure’s data source is mapped. This mapping should be integrated into the data_source record and automatically populated in this record.	integer	No	No	Yes	concept
exposure_source_value	This field houses the verbatim name of the original source of place-based exposure data.	This name is mapped to a Standard Exposure Source Concept and the original name is stored here for reference.	varchar(50)	No	No	No
exposure_relationship_source_value			varchar(50)	No	No	No
dose_unit_source_value			varchar(50)	No	No	No
quantity			integer	No	No	No
modifier_source_value			varchar(50)	No	No	No
operator_concept_id	The meaning of Concept?4172703?for ?=? is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it?s important when devising analyses to not to forget testing for the content of this field for values different from =.		integer	No	No	Yes	concept
value_as_number	This is the numerical value of the Exposure, if available.	This value should be integrated into the variable_source record and automatically populated in this record.	float	No	No	No
value_as_concept_id	If the raw data gives a categorial result for exposures those values are captured and mapped to standard concepts in the ?Exposure Value? domain.	This mapping should be integrated into the variable_source record and automatically populated in this record.	integer	No	No	Yes	concept
unit_concept_id	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 mapping should be integrated into the variable_source record and automatically populated in this record.	integer	No	No	Yes	concept	Unit