1. REDCap Plugin Examples From VICTR Data Core Team
Kyle McGuffin
Senior Application Developer
Vanderbilt University Medical Center

2. Plugin Types
Hooks: Plugins that are run within existing REDCap pages. Can alter pages in almost any way.
Portals/Bookmarks: Pages outside of REDCap that connect to the same database. Provides completely customizable display/editing of REDCap data.
Triggers/Crons: Processes that run in the background to provide automation
External Plugins: Use REDCap API to access REDCap data from outside the REDCap server

3. PRO Employee Protection: Inventory Hook
Dynamic dropdowns, with ability to select multiple pieces of equipment for a single field. Also saves equipment and order quantities for each piece of equipment.

4. PRO Employee Protection : Inventory Hook
Inventory data is compressed down to one data field
Inventory fields can be added and removed using field annotations. This also allows multiple fields to feed the dynamic list of equipment types.

5. PRO Employee Protection : Respondent Matrix Hook
28 different fields are compressed into a matrix to make data entry more readable and to shrink the form length

6. AFFORD/RED-AF Risk Calculator: Survey Complete Portal
Survey results are sent to a calculator that displays a color-coded visual representation of future risk

7. Eskind Pediatric Diabetes Clinic: Patient Portal
Portal connects with clinic’s appointment scheduling service to pull a list of today’s patients meeting certain criteria. Patients (and their parents) are asked to give consent through the portal before they are sent on to a survey based on which criteria they meet.

8. Eskind Pediatric Diabetes Clinic: Patient Portal
Consent and inclusion pre-surveys

9. Eskind Pediatric Diabetes Clinic: Patient Portal
After completing screening, patients will be sent to a REDCap survey if they meet the survey’s criteria.

10. HIP Trial: Reporting bookmark
PI is given a customized monthly report showing number of patients enrolled by each participating clinic and number excluded for each reason

11. PROMIS Recruitment: Survey Dashboard
Custom dashboard was created to verify a random survey code and keep track of participant’s survey completion status, as well as show a visual representation of their scores on several metrics. Dashboard also ensured only the needed number of participants were allowed to complete the survey from each cohort.
After completing all surveys, patients were sent to a separate survey to input contact information. This setup allowed complete anonymization of survey respondents.

12. PRO Employee Protection: Quarterly Report Cron
Automated process sends an (above) to survey respondents at each participating hospital, showing them a full report of their hospital’s Ebola readiness status.

13. LIBR: Screening Information Trigger
A master project is configured to track participant enrollment in several studies along with various screening and demographic data.
After enrollment in a study, a copy of the screening data is sent to the study’s REDCap project and locked to prevent accidentally changing the patient’s information.
This allows PIs to only see data for patients enrolled in their study, but allows patients to be enrolled in multiple studies, which wouldn’t be possible with Data Access Groups.

14. LIBR: Screening Information Trigger
Screening project data is transferred to SimmonsNARSAD project form and locked.

15. Q & A