Differences

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

--- documentation:next_cdm:cdm_process [2016/02/02 04:56] – rimma_belenkaya
+++ documentation:next_cdm:cdm_process [2017/08/04 14:05] (current) – clairblacketer
@@ Line 1: / Line 1: @@
 ===== Process for adopting CDM/Vocabulary changes =====
-**Discussing proposals**
+===Discussing proposals==
-Proposals are discussed on the OHDSI Forum for CDM Builders at [[http://forums.ohdsi.org/c/cdm-builders/]]
+Proposals are discussed either:
+  - on the [[https://github.com/OHDSI/CommonDataModel/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3AProposal%20|github issue site]]
+  - during the [[http://www.ohdsi.org/web/wiki/doku.php?id=projects:workgroups:cdm-wg|workgroup meetings]]
+  - or on the [[http://forums.ohdsi.org/c/cdm-builders/|OHDSI Forum for CDM Builders]]
-**Submitting proposals**
+===Submitting proposals===
-Proposals are submitted at the [[documentation:next_cdm|CDM and Vocabulary Development]]
+Proposals were previously submitted at the [[documentation:next_cdm|CDM and Vocabulary Development]]. From **7/11/2017** forward they are submitted as issues on the CDM [[https://github.com/OHDSI/CommonDataModel/issues|github]]
 Every proposal needs:
@@ Line 17: / Line 20: @@
   * Consequences of doing it and not doing it including technical (e.g. implications on vocab, existing software), resources
+**Github issues are written in a form of markdown different from this wiki so please use {{:documentation:next_cdm:proposal_template.docx|this template}} as a guide.**
-**Vetting proposals**
+===Vetting proposals===
 Proposals are vetted by a group of experts.
@@ Line 31: / Line 35: @@
-**Accepting proposals**
+===Accepting proposals===
-  * At monthly meetings by a majority vote
+  * At [[http://www.ohdsi.org/web/wiki/doku.php?id=projects:workgroups:cdm-wg|workgroup meetings]] by a majority vote
   * Determine time of release
-**Implementation and release**
+===Implementation and release===
   * The change should be accompanied by documentation and conventions including use cases
   * The change should be demonstrated to the community