OHDSI / Themis

Repository for OMOP CDM conventions as defined by THEMIS. These can be reference lists of concepts, pieces of standardized code for data generation or quality certification, and debates.
Apache License 2.0
27 stars 8 forks source link

Multiple Addresses per Provider #107

Closed haydenbspence closed 5 months ago

haydenbspence commented 5 months ago

Multiple Addresses per Provider

CDM or THEMIS convention?

THEMIS

Is this a general convention?

YES. Impacts location, provider, and visit_occurrence tables.

Summary of issues

A provider may have multiple addresses through work at multiple facilities. This can result in multiple locations associated with care (e.g. provider address and provider location). ^2

Summary of answer

"The CDM allows us to capture location of visits, so knowing where a patient was treated is quantified in the CDM. If a provider has multiple addresses the ETL should just choose one as it is unknown what the analytical use case for storing multiple addresses per provider.

The question of how to handle a situation where the billing address differs from where the patient received care is already handled in the CDM. The VISIT_OCCURRENCE table has a separate PROVIDER_ID and CARE_SITE_ID for expressly this purpose. This is already handled with Convention 8 on the VISIT_OCCURRENCE page" ^1

Related links

Other comments/notes

clairblacketer commented 5 months ago

Issue # and location

Issue summary

A provider may have multiple addresses through work at multiple facilities. This can result in multiple locations associated with care (e.g. provider address and provider location).

Convention type

Global

CDM table

NA

CDM field

NA

Links to issue discussion

Provenance of data

General, any database with provider location information

The ratified convention

The CDM allows us to capture location of visits, so knowing where a patient was treated is quantified in the CDM. If a provider has multiple addresses the ETL should just choose one to associate with the provider in the PROVIDER table as the analytical use case for storing multiple addresses per provider is unknown.

The question of how to handle a situation where the billing address differs from where the patient received care is already handled in the CDM. The VISIT_OCCURRENCE table has a separate PROVIDER_ID and CARE_SITE_ID for expressly this purpose.

Date of ratification/published

Nov 27, 2018

Downstream implications

No

Link to DQD check

No. The isPrimaryKey check will make sure the provider ids are not duplicated in the PROVIDER table but there is no explicit check for the same provider_source_value and different location_ids

Related conventions/further information

NA

#Tags provider, location, care_site

clairblacketer commented 5 months ago

opened PR #118