This repository provides documentation on the processes for contributing data to the CHoRUS consortium. Content is written in Markdown, which is then converted to HTML with Docusaurus.
Online documentation SOP site.
The following SOPs are under development:
SOP Title | Lead | Status | Provisional Created | Draft Due Date | Notes |
---|---|---|---|---|---|
Structured EHR data | @jshoughtaling | In Progress | 21 Feb | Supporting the time committed for cloud | |
Flowsheet data | @jshoughtaling | In Progress | 21 Feb | Supporting the time committed for cloud | |
Waveform | @briangow | In Review | Yes | 31 Jan | Finalize |
Imaging | @edilbertoamorim | In Progress | 7 March | Considering current testing ongoing | |
2nd Data Request/re-upload | @clermontg | In Review | 7 Feb | Updating to add more technical information and need timeline for first data quality requirements | |
Free-Text data | @hol7001 (Hongfang) | In Progress | 7 Feb | ||
Data update | @tcpan | In Progress | Yes | 31 Jan | Finalize the process and get reviewed |
Central Processing | @rkamaleswaran | In Progress | 31 Mar | Taking longer as figures are being created and detailed outline of architexture being created | |
Azure Roles | Pending (Sara helping create) | In Progress | 14 Mar | Have defined the roles, but outlining what each can do | |
Privacy/Safe Harboring | Xiaoqian (need GitHub handle) | In Review | Yes | 31 Jan | Checklist created, need to confirm if that is enough |
Common data elements | Eric (need GitHub handle) | In Progress | Yes | 31 Jan | Initial delphi list created, but need specific list of elements we will review for in each upload |
Date Shifting SOP | @clermontg (Should this be Gilles?) | In Progress | 31 Jan | We should have good idea of what we should be doing for date shifting, but need to put down on virtual paper | |
Annotations/Chart Review | Joo (need GitHub handle) | In Progress | 21 Feb | ||
Cultures/organism reporting used in ICU | Standards Team | In progress | TBD | ||
OMOP extension for waveform acquisition parameters & derived features | Standards Team | TBD | |||
Data provenance & institution specific data generation | Standards Team | TBD | |||
SDoH Data | Standards Team | TBD | collaborate with UF team | ||
Amendment to Linkage SOP | Standards Team | TBD | ICU representation and procedure ID representation |
To add or update the guidelines, you will need to edit the relevant markdown files. The easiest way to do this is to find the relevant file on GitHub, click "edit", and then follow the steps to create a "pull request". You can navigate to the relevant markdown file on GitHub from the website by clicking the Edit this page
button at the bottom. Alternatively, if you are familiar with git, you can submit a pull request in the usual way.
Once a pull request is opened it will be reviewed by CHoRUS colleagues. After the pull is request is approved, you may merge it into the repository by clicking "Merge". Merging a pull request will trigger a rebuild of the website.
If you would like to add topics that are not yet represented, please add your request to issues
.