Description

CARE_SITE

Table Description

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.).

ETL Conventions

Care site is a unique combination of location_id and place_of_service_source_value. 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. There can be 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.The relationships between Care Sites are defined in the FACT_RELATIONSHIP table.

CDM Field	User Guide	ETL Conventions	Datatype	Required	Primary Key	Foreign Key	FK Table
care_site_id		Assign an ID to each combination of a location and nature of the site - the latter could be the Place of Service, name or another characteristic in your source data.	integer	Yes	Yes	No
care_site_name	The name of the care_site as it appears in the source data		varchar(255)	No	No	No
place_of_service_concept_id	This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.	Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. Accepted Concepts.	integer	No	No	Yes	CONCEPT
location_id	The location_id from the LOCATION table representing the physical location of the care_site.		integer	No	No	Yes	LOCATION
care_site_source_value	The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site.		varchar(50)	No	No	No
place_of_service_source_value		Put the place of service of the care_site as it appears in the source data.	varchar(50)	No	No	No

Primary Key Constraint Name

xpk_care_site

Unlogged

false



Name	Begin	End

fpk_person_care_site_id : Relationship	care_site : Entity	person : Entity
fpk_provider_care_site_id : Relationship	care_site : Entity	provider : Entity
fpk_visit_detail_care_site_id : Relationship	care_site : Entity	visit_detail : Entity
fpk_visit_occurrence_care_site_id : Relationship	care_site : Entity	visit_occurrence : Entity
fpk_care_site_place_of_service_concept_id : Relationship	concept : Entity	care_site : Entity
: Relationship	location : Entity	care_site : Entity



	Name		Value

	Name		location_id
	Type		int4
	Nullable		false
	Unique		false
	Primary Key		true
	Index		false
	Length		0
	Scale		0
	Id Generator		native
	Foreign Key		true
	Generated		Unspecified
	Sync To Attribute		Yes



	Name		Value

	Name		care_site_id
	Type		int4
	Nullable		false
	Unique		false
	Primary Key		true
	Index		false
	Length		0
	Scale		0
	Id Generator		native
	Foreign Key		false
	Generated		Unspecified
	Sync To Attribute		Yes



	Name		Value

	Name		place_of_service_concept_id
	Type		int4
	Nullable		false
	Unique		false
	Primary Key		true
	Index		false
	Length		0
	Scale		0
	Id Generator		native
	Foreign Key		true
	Generated		Unspecified
	Sync To Attribute		Yes



	Name		Value

	Name		care_site_name
	Type		varchar
	Nullable		true
	Unique		false
	Primary Key		false
	Index		false
	Type Name		varchar
	Length		255
	Scale		0
	Id Generator		native
	Foreign Key		false
	Generated		Unspecified
	Sync To Attribute		Yes



Column Name	Data Type	PK / FK	Nullable	Description

location_id	int4	PK / FK	No
care_site_id	int4	PK	No
place_of_service_concept_id	int4	PK / FK	No
care_site_name	varchar(255)		Yes
care_site_source_value	varchar(50)		Yes
place_of_service_source_value	varchar(50)		Yes



	Diagram

	Standardized_Tables : Entity Relationship Diagram
	Vocabulary_With_Standard : Entity Relationship Diagram