Submitting External Modules

Original Author: Mary Geda, December 6, 2021

The submission process and security requirements for External Modules (EMs) will vary depending upon where you plan to use your software. You should familiarize yourself with the relevant software development guidelines PRIOR to initiating work to avoid unnecessary refactoring. Remember to incorporate static code checks as described in Setting Up Your Environment to streamline the submission and approval process. You may wish to contact the appropriate REDCap team to obtain recommendations on which static analysis tool or tools to use.

1. Local Use- REDCap@Yale or YCCI/YNHH REDCap Local EMs typically involve custom programming (i.e. Custom EMs) that extend the functionality of REDCap for a specific purpose. These EMs are generally installed on one project that resides within a REDCap system managed by an Institution, University, or Health System. REDCap@Yale and YCCI/YNHH REDCap are hosted at Yale University and Yale New Haven Hospital respectively. The software guidelines for Custom EMs differ. Software developers that plan to submit an EM locally must follow guidelines issued by the respective institution.

2. Global Use- Vanderbilt/REDCap Consortium Global EM’s provide functionality that others may find useful. Global EMs are posted in the Vanderbilt repository and available for worldwide consortium members (i.e. local REDCap service-providers) to download and use on their local installation of REDCap. Software developers who plan to submit EMs to the REDCap Consortium must follow the guidelines issued by Vanderbilt.