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. Also adding source_concept_id allows to have good data lineage and provenance to the source.
Backward compatibility: Yes
|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_”.
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)
Add the following to the descriptions in conventions: