Hi all (@dorrd, @yguilarte, @Jes_Rhodes, @jon_duke, @DTorok )
I investigated with Epic about how we could share ETL scripts among Epic users last year. Because the Epic db are proprietary, we cannot post ETL scripts in a public open repository, but we can post them in Epic's repository on the UserWeb. As @DTorok stated, this is only available to Epic Users with an account, and not consultants, and consultants may not want their work posted. If Epic users do start to post their ETL scripts, it would be nice to have a convention for naming the files it should include OMOP (so users can find it with the search), the extraction db and version and the OMOP db version. It would also be helpful to include a README to provide any details about the progress of the work, considerations, etc- if that is possible. i2b2 users post information in this same place.
Here is the recommendation from Steven Van Manen at Epic late last year (which I thought I had posted already, but I did not)
The best place to start would be to upload the ETL Scripts to the Report Repository in the Data Handbook, look for the upload report button. This will allow you to have the most control over what is getting uploaded, and allows
other Epic organizations to search for and use the scripts as well. Like you
mentioned this is where a few customers have also uploaded there i2b2
scripts as well.
Steven Van Manen
| Software Developer | Research