Tomorrow we have a CDM workgroup meeting at 9am eastern where we will be discussing the PROVIDER table. The Skype meeting link can be found on our homepage https://ohdsi.github.io/CommonDataModel/index.html and the straw-man description of the PROVIDER table is below. Please review and come ready to discuss.
|provider_id||It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently.||Any person linkage that needs to occur to uniquely identify Providers ought to be done prior to writing this table. This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number.|
|npi||This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS)|
|dea||This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances.|
|specialty_concept_id||This field represents the most common specialty that occurs in the data, should the provider have more than one.||If a Provider has more than one Specialty, the main or most often exerted specialty should be recorded.|
|care_site_id||This is the CARE_SITE_ID for the location that the provider primarily practices in.||If a Provider has more than one Care Site, the main or most often exerted specialty should be recorded.|
|provider_source_value||Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic.||Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider value as it appears in the source.|
|specialty_source_concept_id||This is often zero as many sites use propietary codes to store physician speciality||If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here.|