Skip to main content

A collection of tools to interact with the REDCap API

Project description

redcap-toolbox

Python package of REDCap tools

Background

The goal of redcap-toolbox is to provide researchers with the tools to download and upload data to existing REDCap builds. One key aspect of this toolbox is that the minimum number of changes needed to the records are calculated prior to importing data in to REDCap, thereby reducing the API load.

Installing REDCap Toolbox and Supported Versions

redcap-toolbox is available on PyPI:

$ pip install redcap-toolbox

redcap-toolbox officially supports Python 3.8+.

Getting started

redcap-toolbox relies on the environmental variables REDCAP_API_URL and REDCAP_API_TOKEN.

Downloading data

  • Download REDCap dataset using download_redcap and provide an output file name. By default, all forms are exported.
  • If you want to include survey timestamps, add the optional flag: --survey-fields
  • To download specific instrument forms, enter form names to export in a text file, one per line. If in the web UI, the form name has a space in it, replace the space with an underscore. Then, provide that file using the optional flag: --forms get_forms.csv

An example call might look like this:

download_redcap --survey-fields --forms get_forms.csv source_data/full_data.csv

which will download the data set with only the forms defined in the get_forms.csv with timestamps

Downloading reports

  • Reports can be downloaded using download_redcap_report with either a list of report IDs separated by commas or a file with list of report IDs, one per line.
  • Use the --prefix flag, to specify the prefix to be added for the filenames. Default is redcap.

An example call might look like this:

download_redcap_report --file report_ids.csv --prefix StudyName report_data

or

download_redcap_report --id 32001,32004 --prefix StudyName report_data

which will save all the reports for IDs listed in the report_ids.csv file in the report_data directory.

  • The output report filenames will look like this:
    report_data
    ├── StudyName__report_32001.csv
    └── StudyName__report_32004.csv
    

Splitting REDCap data into event files

  • Use split_redcap_data to split the REDCap CSV file into:

    • A file for each event
    • A file for repeated instruments in events where they happen
  • So, if your data has events 'scr', 'pre', and 'post', and 'pre' and 'post' each have a repeated instrument called 'meds', you can expect the output files to like this:

    ├── redcap__scr.csv
    ├── redcap__pre.csv
    ├── redcap__pre__meds.csv
    ├── redcap__post.csv
    ├── redcap__post.csv
    └── redcap__post__meds.csv
    
  • In addition, if you don't like the whole _arm_1 appended to your event names (who does like that?) or you're using events to denote arms and want all your event's data together, you can use the event_map file for this. That file should be a CSV file and contain the columns 'redcap_event' and 'filename_event'

    • Example event maps might look like:
      scr__all_arm_1,scr
      pre__control_arm_1,pre
      pre__intervention_arm_1,pre
      

An example call might look like this:

split_redcap_data --event-map=event_map.csv --prefix StudyName --no-condense source_data/full_data.csv source_data

where the split event files will be saved in the source_data directory as well with the prefix StudyName added to them.

source_data
├── full_data.csv
├── StudyName__scr.csv
├── StudyName__pre.csv
├── StudyName__pre_meds.csv
├── StudyName__post.csv
└── StudyName__post_meds.csv

Update records in REDCap

  • Update the REDCap database with the minimum changes needed to make the system in sync.
  • It is important that the updated data file has the same number of rows and columns as the original data file.
  • This functionality is especially useful when updating the record information for Tracking purposes.

An example call might look like this:

update_redcap_diff StudyName__scr.csv StudyName__scr_cache.csv

where the _cache.csv file contains the changes made to the original data file.

Credits

redcap-toolbox was written by Nate Vack njvack@wisc.edu, with features added by Nicholas Vanhaute nvanhaute@wisc.edu and Stuti Shrivastava sshrivastav6@wisc.edu. redcap-toolbox is copyright 2023 by the Boards of Regents of the University of Wisconsin System.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

redcap_toolbox-2025.7.29.tar.gz (50.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

redcap_toolbox-2025.7.29-py3-none-any.whl (12.0 kB view details)

Uploaded Python 3

File details

Details for the file redcap_toolbox-2025.7.29.tar.gz.

File metadata

  • Download URL: redcap_toolbox-2025.7.29.tar.gz
  • Upload date:
  • Size: 50.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.7.3

File hashes

Hashes for redcap_toolbox-2025.7.29.tar.gz
Algorithm Hash digest
SHA256 cf018d93920a4fbe23e6fc3b4b88c73d6e7093d85aa67d299adb7c555d29d6cb
MD5 1e89dccc8ff84e7f39162f6e3ef9ff58
BLAKE2b-256 e6665ef2b1e6eceb4504e157a6d45f5993043a8c7eb788477081019cf204ea40

See more details on using hashes here.

File details

Details for the file redcap_toolbox-2025.7.29-py3-none-any.whl.

File metadata

File hashes

Hashes for redcap_toolbox-2025.7.29-py3-none-any.whl
Algorithm Hash digest
SHA256 3ec869c41847ca8edf69b73d3d78ccc248c46221ec0a1faae568535e1a9412f5
MD5 41a99c84a9787ac59ca981c72082a865
BLAKE2b-256 f1a7cb19f372a207f1bc42ad0687433f4168850536b51d3eda2d88869c8740dc

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page