Location
The LOCATION table represents a generic way to capture physical location or address information of PERSON and CARE_SITE records.
| Field | Required | Type | FK Table | Description |
|---|---|---|---|---|
| location_id | Yes | bigint | A unique identifier for each geographic location. | |
| address_1 | No | varchar(50) | Address line 1. | |
| address_2 | No | varchar(50) | Address line 2. | |
| city | No | varchar(50) | City. | |
| state | No | varchar(50) | Country (nation state). Note that this field has been widened from standard OMOP. | |
| zip | No | varchar(9) | Postcode. | |
| county | No | varchar(20) | County. | |
| location_source_value | No | varchar(50) | The verbatim information that is used to uniquely identify the location as it appears in the source data. | |
| last_updated_datetime | Yes | datetime | Initially this is the time the row was written to OMOP. If the row is subsequently updated, it then becomes the most recent update time. | |
| deleted_datetime | No | datetime | NULL
initially. Set to the time when the row was marked for deletion. A value in this column sent to the central data source will result in this row being deleted from the combined dataset. |
Conventions
- Each address or Location is unique and is present only once in the table.
- Postcodes are stored without whitespace (i.e. “NW12BU”, not “NW1 2BU”).