Differences

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

--- documentation:next_cdm:country [2016/03/03 15:13] – created cgreich
+++ documentation:next_cdm:country [2017/08/02 13:46] (current) – clairblacketer
@@ Line 1: / Line 1: @@
 ===== Add country field in LOCATION table =====
+===Proposals are now housed on github===
+[[https://github.com/OHDSI/CommonDataModel/issues/91|link to github issue]]
   * Requester: Ajit Londhe
@@ Line 6: / Line 9: @@
 ----
 === Proposal ===
-The CDM’s Location table includes physical location fields such as street address, state, zip code, and county. However, there is no field for capturing the country.
+The CDM’s Location table includes physical location fields such as street address, state, zip code, and county. However, there is no field for capturing the country of the subjects.
 == LOCATION Table ==
-The Cost Table will house all cost information from source data.  Any information reporting money or currency amounts will be stored in this table.  We distinguish three types of cost data: 1) paid or reimbursed amounts, 2) charges or list prices, and 3) costs or expenses incurred by the provider.
+The Country field will be based on the ISO's 3166-1 vocabulary (https://www.iso.org/obp/ui/#search), which officially designates 2- and 3-character codes for 249 countries. The alpha-3 set, which uses 3-characters, is the suggested version. Assuming alpha-3, then the Country field would only need to be a nullable varchar(3).
-^Field^Required^Type^Description^
-|||||
 ----
 === Use Cases ===
-Find use cases [[http://www.ohdsi.org/wp-content/uploads/2015/04/CDM-Cost-Table-Proposal_outins_JDuryea.pdf|here]].
+For data sets with patient records originating from multiple countries, there is no way to represent this difference in country; you could not stratify an analysis on country or include country as a covariate. We do not have a real-world use case at this time.