documentation:cdm:care_site
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
documentation:cdm:care_site [2014/12/05 21:03] cgreich |
documentation:cdm:care_site [2017/03/14 01:49] gowtham_rao |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== CARE_SITE ===== | + | ===== CARE_SITE table ===== |
| The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.). | The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.). | ||
| + | |||
| ^Field^Required^Type^Description^ | ^Field^Required^Type^Description^ | ||
| |care_site_id|Yes|integer|A unique identifier for each Care Site.| | |care_site_id|Yes|integer|A unique identifier for each Care Site.| | ||
| - | |care_site_name|No|varchar(255)|The description or name of the 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.| | |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 of the Care Site in the LOCATION table, where the detailed address information is stored.| | + | |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.| | |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_value|No|varchar(50)|The source code for the Place of Service as it appears in the source data, stored here for reference.| | |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.| | ||
| ==== Conventions ==== | ==== Conventions ==== | ||
| - | * Many sources do not make a distinction between individual and institutional providers. The CARE_SITE table contains the institutional providers. | + | * Care site is a unique combination of location_id and place_of_service_source_value. |
| + | * Every record in the visit_occurrence table may have only one care site | ||
| + | * Care site does not take into account the provider (human) information such a specialty. | ||
| + | * Many source data do not make a distinction between individual and institutional providers. The CARE_SITE table contains the institutional providers. | ||
| * If the source, instead of uniquely identifying individual Care Sites, only provides limited information such as Place of Service, generic or "pooled" Care Site records are listed in the CARE_SITE table. | * If the source, instead of uniquely identifying individual Care Sites, only provides limited information such as Place of Service, generic or "pooled" Care Site records are listed in the CARE_SITE table. | ||
| * There are hierarchical and business relationships between Care Sites. For example,wards can belong to clinics or departments, which can in turn belong to hospitals, which in turn can belong to hospital systems, which in turn can belong to HMOs. | * There are hierarchical and business relationships between Care Sites. For example,wards can belong to clinics or departments, which can in turn belong to hospitals, which in turn can belong to hospital systems, which in turn can belong to HMOs. | ||
documentation/cdm/care_site.txt · Last modified: 2017/09/25 15:08 by clairblacketer
Page Tools
