Skip to content

Commit c3e4afa

Browse files
Merge pull request #507 from OHDSI/cdmRequestProcess-email
Fix broken email link in cdmRequestProcess
2 parents 9ae24a6 + d255229 commit c3e4afa

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

rmd/cdmRequestProcess.Rmd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Once a group or organization has decided on the update they would like made to t
2929
2. A clearly defined use case noting why the latest version of the OMOP CDM fails to adequately address said use case. This should include describing what you have already tried with the latest version of the OMOP CDM and why it does not meet your needs.
3030
3. An example of how the requested change or addition will be used in practice. This can be in the form of sample data, SQL code, a diagram, or text. The proposal can optionally include suggestions as to how other OHDSI tools (Achilles, DataQualityDashboard, Atlas, etc.) should work with your change or addition.
3131

32-
Once the document is ready to submit, please email [CDM Proposals - Workgroup - Common Data Model](a58abde7.ohdsi.org@amer.teams.ms). This will go directly to a separate channel in the OHDSI Teams environment that is available to all members of the CDM Working Group.
32+
Once the document is ready to submit, please email [CDM Proposals - Workgroup - Common Data Model](mailto:a58abde7.ohdsi.org@amer.teams.ms). This will go directly to a separate channel in the OHDSI Teams environment that is available to all members of the CDM Working Group.
3333
After submitting your document with your proposal to email listed above, someone in the OMOP CDM Working Group will respond to you within 2 weeks. The potential outcomes are as follows:
3434

3535
- Proposal merits further review (move on to next steps)

0 commit comments

Comments
 (0)