From df8226bcf9db02f1b0dbca5c570c33a5f0e76b6d Mon Sep 17 00:00:00 2001 From: Elizabeth Betts <76218284+lizb101@users.noreply.github.com> Date: Wed, 18 Aug 2021 18:49:31 +0100 Subject: [PATCH] Update OMOP_CDMv5.4_Field_Level.csv Updated Location table with Robert Miller's suggestions in forum post : https://forums.ohdsi.org/t/themis-topic-location-table-non-u-s-address-locations/3828/3 --- inst/csv/OMOP_CDMv5.4_Field_Level.csv | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/inst/csv/OMOP_CDMv5.4_Field_Level.csv b/inst/csv/OMOP_CDMv5.4_Field_Level.csv index e5cc7dd..4004fcc 100644 --- a/inst/csv/OMOP_CDMv5.4_Field_Level.csv +++ b/inst/csv/OMOP_CDMv5.4_Field_Level.csv @@ -254,18 +254,16 @@ FACT_RELATIONSHIP,fact_id_1,Yes,integer,,,No,No,,,,, FACT_RELATIONSHIP,domain_concept_id_2,Yes,integer,,,No,Yes,CONCEPT,CONCEPT_ID,,, FACT_RELATIONSHIP,fact_id_2,Yes,integer,,,No,No,,,,, FACT_RELATIONSHIP,relationship_concept_id,Yes,integer,,,No,Yes,CONCEPT,CONCEPT_ID,,, -LOCATION,location_id,Yes,integer,The unique key given to a unique Location.,Each instance of a Location in the source data should be assigned this unique key.,Yes,No,,,,, -LOCATION,address_1,No,varchar(50),This is the first line of the address.,,No,No,,,,, -LOCATION,address_2,No,varchar(50),This is the second line of the address,,No,No,,,,, -LOCATION,city,No,varchar(50),,,No,No,,,,, -LOCATION,state,No,varchar(2),,,No,No,,,,, -LOCATION,zip,No,varchar(9),,"Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.",No,No,,,,, -LOCATION,county,No,varchar(20),,,No,No,,,,, -LOCATION,location_source_value,No,varchar(50),,"Put the verbatim value for the location here, as it shows up in the source. ",No,No,,,,, -LOCATION,country_concept_id,No,integer,The Concept Id representing the country. Values should conform to the [Geography](https://athena.ohdsi.org/search-terms/terms?domain=Geography&standardConcept=Standard&page=1&pageSize=15&query=&boosts) domain. ,,,,,,,, -LOCATION,country_source_value,No,varchar(80),The name of the country.,,,,,,,, -LOCATION,latitude,No,float,,Must be between -90 and 90.,,,,,,, -LOCATION,longitude,No,float,,Must be between -180 and 180.,,,,,,, +LOCATION,location_id,Yes,integer,A unique identifier for each geographic location,Each instance of a Location in the source data should be assigned this unique key.,Yes,No,,,,, +LOCATION,address_1,No,varchar(50),"The address field 1, typically used for the street address, as it appears in the source data",,No,No,,,,, +LOCATION,address_2,No,varchar(50),"The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data",,No,No,,,,, +LOCATION,city,No,varchar(50),The city field as it appears in the source data,,No,No,,,,, +LOCATION,district,No,varchar(50),The district field as it appears in the source data,,No,No,,,,, +LOCATION,postal_area,No,varchar(9),The zip or postal code,"Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.",No,No,,,,, +LOCATION,country,No,varchar(50),The country as it appears in the source data,,No,No,,,,, +LOCATION,latitude,No,numeric,,Must be between -90 and 90.,No,No,,,,, +LOCATION,longitude,No,numeric,,Must be between -180 and 180.,No,No,,,,, +LOCATION,location_source_value,No,varchar(50),The verbatim information that is used to uniquely identify the location as it appears in the source data,"Put the verbatim value for the location here, as it shows up in the source. ",No,No,,,,, CARE_SITE,care_site_id,Yes,integer,,Assign an id to each unique combination of location_id and place_of_service_source_value,Yes,No,,,,, CARE_SITE,care_site_name,No,varchar(255),The name of the care_site as it appears in the source data,,No,No,,,,, CARE_SITE,place_of_service_concept_id,No,integer,"This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.","Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=2&pageSize=15&query=).",No,Yes,CONCEPT,CONCEPT_ID,,,