documentation:next_cdm:place_of_service_source_concept_id
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
documentation:next_cdm:place_of_service_source_concept_id [2017/03/14 01:28] gowtham_rao created |
documentation:next_cdm:place_of_service_source_concept_id [2017/03/14 14:06] gowtham_rao |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| **Proposal:** This is a small proposal to add place_of_service_source_concept_id. It is a general OMOP convention to represent X_source_value as X_source_concept_id and X_concept_id, where X_concept_id is always standard-vocabulary for the domain, and X_source_concept_id maybe standard/non-standard vocabulary that is an integer representation of X_source_value. We don't have X_source_concept_id in care_site and this proposal is to add it. | **Proposal:** This is a small proposal to add place_of_service_source_concept_id. It is a general OMOP convention to represent X_source_value as X_source_concept_id and X_concept_id, where X_concept_id is always standard-vocabulary for the domain, and X_source_concept_id maybe standard/non-standard vocabulary that is an integer representation of X_source_value. We don't have X_source_concept_id in care_site and this proposal is to add it. | ||
| - | **Use cases:** Many place of services such as Acquired immune deficiency syndrome clinic, Acute pain clinic, Bone marrow transplant clinic, Hospital-based outpatient emergency care center, Medical Intensive Care unit -- does not always have 1:1 mapping with standard-concept ids. We have use cases where we want to use local place of service vocabulary for analytics e.g. how many persons attended the Acute Pain Clinic on Saturday's vs Mondays. This cannot be addressed without adding the field place_of_service_source_concept_id | + | **Use cases:** Many place of services such as Acquired immune deficiency syndrome clinic, Acute pain clinic, Bone marrow transplant clinic, Hospital-based outpatient emergency care center, Medical Intensive Care unit -- does not always have 1:1 mapping with standard-concept ids. We have use cases where we want to use local place of service vocabulary for analytics e.g. how many persons attended the Acute Pain Clinic on Saturday's vs Mondays. This cannot be addressed without adding the field place_of_service_source_concept_id. Also adding source_concept_id allows to have good data lineage and provenance to the source. |
| **Discussion:** http://forums.ohdsi.org/t/proposal-add-place-of-service-concept-id-to-care-site-table/2404 | **Discussion:** http://forums.ohdsi.org/t/proposal-add-place-of-service-concept-id-to-care-site-table/2404 | ||
| **Backward compatibility:** Yes | **Backward compatibility:** Yes | ||
| + | |||
| + | |||
| + | ^Field^Required^Type^Description^ | ||
| + | |care_site_id|Yes|integer|A unique identifier for each Care Site.| | ||
| + | |care_site_name|No|varchar(255)|The verbatim description or name of the Care Site as in data source| | ||
| + | |place_of_service_concept_id|No|integer|A foreign key that refers to a Place of Service Concept ID in the Standardized Vocabularies.| | ||
| + | |location_id|No|integer|A foreign key to the geographic Location in the LOCATION table, where the detailed address information is stored.| | ||
| + | |care_site_source_value|No|varchar(50)|The identifier for the Care Site in the source data, stored here for reference.| | ||
| + | |place_of_service_source_concept_id|No|integer|A foreign key that refers to the Place of Service Concept Id refers to the code used in the source .| | ||
| + | |place_of_service_source_value|No|varchar(50)|The source code for the Place of Service as it appears in the source data, stored here for reference.| | ||
| + | |||
| + | |||
| + | **Other considerations:** | ||
| + | "Place_of_service_" is a long descriptor. "Place_of_service_source_concept_id" is very long and is more than 32 - breaks database column naming rules such as 32 character limit. To overcome, we will have to systematically replace "Place_of_service_" to "Place_". | ||
| + | |||
| + | |||
| + | **Add the following to the descriptions in conventions:** | ||
| + | |||
| + | * It represents the site information needed for use in visit_occurrence table. | ||
| + | * The care_site_source_value typically contains the name of the Care Site as used in source data e.g. Medical ICU or a hospital’s name. Care Site is source name for area where service was provided. | ||
| + | * The care site is the non-human or institutional entity where care was delivered. Care site is not based on provider (human) information such as physician who provided care | ||
| + | |||
| + | * Care site is a unique combination of location_id and place_of_service_source_value. | ||
| + | * Location_id (location table) is street address - and is self-explanatory | ||
| + | |||
| + | **Place_of_service_source_value** | ||
| + | * Place_of_service_source_value is a component of the care site | ||
| + | * It is a named entity within a location_id or street address | ||
| + | * In a hospital these are the named (noun) units or wards where beds are physically present. | ||
| + | * Examples are ER, ICU unit, med-surg beds, gold-service, red-service, rehab floor etc. | ||
| + | |||
| + | |||
documentation/next_cdm/place_of_service_source_concept_id.txt · Last modified: 2017/03/14 17:49 by gowtham_rao
Page Tools
