Merge pull request #159 from OHDSI/cdm_v5.3.-bugfix.2

closes #140, #144, #135

BigQuery/OMOP CDM bigquery ddl.txt

@@ -578,7 +578,7 @@ create table cost
   payer_plan_period_id			integer			null ,
   amount_allowed		        float			  null ,
   revenue_code_concept_id		integer			null ,
-  reveue_code_source_value  varchar(50) null,
+  revenue_code_source_value  varchar(50) null,
   drg_concept_id			      integer		  null,
   drg_source_value			    varchar(3)	null
 )

Documentation/CommonDataModel_Wiki_Files/StandardizedVocabularies/COHORT_DEFINITION.md

@@ -8,7 +8,7 @@ Field|Required|Type|Description
 |definition_type_concept_id|Yes|integer|Type defining what kind of Cohort Definition the record represents and how the syntax may be executed|
 |cohort_definition_syntax|No|varchar(MAX)|Syntax or code to operationalize the Cohort definition|
 |subject_concept_id|Yes|integer|A foreign key to the Concept to which defines the domain of subjects that are members of the cohort (e.g., Person, Provider, Visit).|
-|cohort_instantiation_date|No|Date|A date to indicate when the Cohort was instantiated in the COHORT table|
+|cohort_initiation_date|No|Date|A date to indicate when the Cohort was instantiated in the COHORT table|
 
 ### Conventions
   * The cohort_definition_syntax does not prescribe any specific syntax or programming language. Typically, it would be any flavor SQL, a cohort definition language, or a free-text description of the algorithm. 

Documentation/CommonDataModel_Wiki_Files/StandardizedVocabularies/CONCEPT_SYNONYM.md

@@ -8,6 +8,6 @@ The CONCEPT_SYNONYM table is used to store alternate names and descriptions for
 
 ### Conventions
 
-  * The concept_name field contains a valid Synonym of a concept, including the description in the concept_name itself. I.e. each Concept has at least one Synonym in the CONCEPT_SYNONYM table. As an example, for a SNOMED-CT Concept, if the fully specified name is stored as the concept_name of the CONCEPT table, then the Preferred Term and Synonyms associated with the Concept are stored in the CONCEPT_SYNONYM table. 
+  * The concept_synonym_name field contains a valid Synonym of a concept, including the description in the concept_name itself. I.e. each Concept has at least one Synonym in the CONCEPT_SYNONYM table. As an example, for a SNOMED-CT Concept, if the fully specified name is stored as the concept_name of the CONCEPT table, then the Preferred Term and Synonyms associated with the Concept are stored in the CONCEPT_SYNONYM table. 
   * Only Synonyms that are active and current are stored in the CONCEPT_SYNONYM table. Tracking synonym/description history and mapping of obsolete synonyms to current Concepts/Synonyms is out of scope for the Standard Vocabularies.
   * Currently, only English Synonyms are included.

Impala/OMOP CDM impala ddl.txt

@@ -1187,7 +1187,7 @@ CREATE TABLE cost
 
     revenue_code_concept_id INTEGER,
 
-    reveue_code_source_value VARCHAR(50),
+    revenue_code_source_value VARCHAR(50),
 
     drg_concept_id INTEGER,
 

Netezza/OMOP CDM netezza ddl.txt

@@ -695,7 +695,7 @@ CREATE TABLE cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        REAL			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )

Oracle/OMOP CDM oracle ddl.txt

@@ -650,7 +650,7 @@ CREATE TABLE cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        FLOAT			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )

ParallelDataWarehouse/OMOP CDM pdw ddl.txt

@@ -616,7 +616,7 @@ IF XACT_STATE() = 1 COMMIT; CREATE TABLE  cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        FLOAT			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )

PostgreSQL/OMOP CDM postgresql ddl.txt

@@ -650,7 +650,7 @@ CREATE TABLE cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        NUMERIC			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )

Redshift/OMOP CDM redshift ddl.txt

@@ -616,7 +616,7 @@ CREATE TABLE cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        FLOAT			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )

Sql Server/OMOP CDM sql server ddl.txt

@@ -650,7 +650,7 @@ CREATE TABLE cost
   payer_plan_period_id			INTEGER			NULL ,
   amount_allowed		        FLOAT			  NULL ,
   revenue_code_concept_id		INTEGER			NULL ,
-  reveue_code_source_value  VARCHAR(50) NULL,
+  revenue_code_source_value  VARCHAR(50) NULL,
   drg_concept_id			      INTEGER		  NULL,
   drg_source_value			    VARCHAR(3)	NULL
 )