/
SubmittedCohortDefinitions.Rmd
45 lines (37 loc) · 1.76 KB
/
SubmittedCohortDefinitions.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
---
title: "Submitted Cohort Definitions"
author: "Gowtham A. Rao"
date: "`r Sys.Date()`"
output:
html_document:
number_sections: no
toc: no
pdf_document:
toc: no
vignette: >
%\VignetteIndexEntry{Submitted Cohort Definitions}
%\VignetteEncoding{UTF-8}
%\VignetteEngine{knitr::rmarkdown}
---
```{r, echo = FALSE, message = FALSE}
knitr::opts_chunk$set(
cache = FALSE,
comment = "#>",
error = FALSE,
tidy = FALSE
)
```
[PhenotypeLibrary](https://github.com/OHDSI/PhenotypeLibrary) is part of [HADES](https://ohdsi.github.io/Hades/)
*This document is a DRAFT guidance.*
# Post submission
## Validity Checks
- All submissions get [validity Checks For CohortDefinitions](https://ohdsi.github.io/PhenotypeLibrary/articles/ValidityChecksForCohortDefinitions.html)
## Life cycle
- Cohort Definitions that have passed validity checks get put in the pipeline and will be available in the next release.
- If a cohort definition completes peer review, then the version number of the library when it was accepted becomes the *added version*.
## Assignment for Peer Review
- OHDSI will perform on optional open peer review through the OHDSI Phenotype Development and Evaluation workgroup.
- The peer review may be oral feedback (Recorded video sessions in the OHDSI Phenotype Development and Evaluation work group - archived in the workgroup) or written feedback - in forum.
- It is up-to the submitter to then consider the peer review recommendations, make changes, or not.
- Based on the decision of the peer reviewer(s) the cohort definition would be considered accepted.
- Once accepted, the cohort definitions will be made immutable and a version number will be assigned to it. Key peer review notes will usually be referenced (commonly to the forum post).