Differences

This shows you the differences between two versions of the page.

--- documentation:next_cdm:place_of_service_source_concept_id [2017/03/14 14:06] – gowtham_rao
+++ documentation:next_cdm:place_of_service_source_concept_id [2017/03/14 17:49] (current) – gowtham_rao
@@ Line 23: / Line 23: @@
 **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_".
+**What is a place**
+The word 'place of service' is interpreted differently by different people. Which one is more important - 'place' or 'service' in place of service. In this proposal, we interpret place as a **place 'type'** e.g. it is a ward-unit within a location, or an operating room or icu. Source data may have non-standard source code value for it such as medical icu, or surgical icu, or Gold-wing, Red-wing, Blue-wing etc to represent local hospital vocabulary for 'places' within the location. These are "settings" or "operational units" within a location where service is provided. In United States claims, CMS defines "Place of Service Codes" as //"two-digit codes placed on health care professional claims to indicate the **setting** in which a service was provided."// It does not represent the actual service provided. In-fact the type of service and level/intensity of service may be independent of the "place of service" e.g. a patients with medical complication such as sepsis who needs ICU care, may be temporarily managed in surgical ICU, pending availability of beds in medical icu (place of service)