Creative Uses of Standard REDCap Functionality

Creative Uses of Standard REDCap Functionality

Bas de Veer (ITHS, University of Washington)

Jeff Hawley (Duke University)

JoinQA.com : Access Code 52408

Creative Uses of REDCap

Source: www.xkcd.com

Creative Uses of REDCap • Basic tricks

• AE’s, medication lists • Data dictionary tips • HTML

• Surveys • Randomization, different use cases

• Longitudinal • Landing page • Multiple arms, multiple workflows

Basic Tricks

Cascading medication lists • Need to design a maximum number • Takes up screen real estate

• Selector option • N+1 option

Example: Cascading medication list demo

Basic Tricks

Checkboxes • Follow up questions (e.g. “Other”) • Single Checkbox

• Multiple answers • Multiple Checkboxes

• Single answers

Example: Checkbox demo

Basic Tricks Dynamic SQL Lookup Tables

• Insert table in the backend database • Dynamic SQL fields

• Hide/Show based on Branching Logic • Pulls a drop down from table

• Unique values for options • Round up/down in calculation • Add .00001, .00002 etc etc

Example: D-SQL Lookup demo or Oncology adverse event demo

Basic Tricks Scoring tools

• Variety of uses • BMI, Scales, Validated tools

• Use for branching logic • Action Tags

• @HIDDEN • @READONLY

Example: Scoring tool demo

Basic Tricks

Data Dictionary

• Sequence variable • Inserts multiple fields

Sequence Variable

Sequence Variable

Sequence Variable

Sequence Variable

Sequence Variable

Sequence Variable

Sequence Variable

Sequence Variable

Basic Tricks

Attention grabbing descriptive fields

HTML is your friend!

Basic Tricks

Basic Tricks

Surveys Custom Invites

• Pipe in any information • Increases response rate • Think: name, topic, upcoming visit date

• Input form and a survey form • Included email in input form

• Track who filled out what

Example: Custom Invitations demo

Surveys Application – Review Surveys

• Gets around the single email restriction • Two surveys

• Linked by a Dynamic SQL • Shorten names ( Left() )

• Great for “lazy” users

Example: Application demo and Reviewer Demo

Surveys Point survey completion to a second survey to separate feedback from raffle drawings Location: Online Designer Survey Settings

Surveys Trigger Forms

• Used for triggering preset automatic invites • Useful for “fuzzy” intervals • Does require user intervention • Recommend a separate form • Simple variables

• Yes no questions • Single answer checkboxes

• Enrich the invitation by piping in values Example: Trigger form demo

Surveys Cascading triggers vs single triggers

• Cascading triggers • One survey triggers the next in line • Easy logic • One skipped survey breaks the chain

• Single triggers • One variable triggers all invites • Different time delays • Harder to add additional surveys

Surveys Survey Randomization

• Randomness based on the order of record creation • Works best with large numbers of participants • Public survey link

• Even distribution • Personal invitations

• Prevents spam • Uneven distribution

• Modulo Operator (%)

Example: Survey Randomization Demo

Longitudinal Multiple workflows/Multi-site

• Keeping everything in the same project • Reusing some of the same forms • Different workflows, different arms

• Create “Record ID form”

• See “Landing Page”

• Alternative: Use multiple projects

Example: Child Arm Demo or Parent Arm Demo

Longitudinal Landing Page

• Useful for creating the REDCap record ID • “Looks” professional • Use in combination with the survey queue • Add logo(s) • Add a generic welcome text

Example: Child Arm Demo or Parent Arm Demo

Longitudinal Enrollment Arm

• Unique Record ID’s • Technically possible, not advisable • Turn on auto-numbering, use 2nd ID

• Alternative: Enrollment project

• Use Dynamic SQL in main project to link back to the enrollment

Longitudinal D-SQL Example code

select a.value, concat_ws(', ',a.value,b.value) as label from (select record, value from redcap_data where project_id=948 and field_name=’record_id') a JOIN (select record, value from redcap_data where project_id=948 and field_name=’last_name') b ON a.record=b.record order by a.value