CoChat
Sign Up
Cited by 24,013Research Data Management PracticesScientific Computing and Data ManagementElectronic Health Records Systems

The REDCap consortium: building an international community of software platform partners

Open access
Harris, Paul A., Taylor, Robert, Minor, Brenda L., Elliott, Veida, Fernandez, Michelle, O'Neal, Lindsay, McLeod, Laura, Delacqua, Giovanni +3 more·2019·Journal of Biomedical Informatics
DOI 10.1016/j.jbi.2019.103208PMC PMC7254481
Open this paper in CoChat — free account

Abstract

The Research Electronic Data Capture (REDCap) data management platform was developed in 2004 to address an institutional need at Vanderbilt University, then shared with a limited number of adopting sites beginning in 2006. Given bi-directional benefit in early sharing experiments, we created a broader consortium sharing and support model for any academic, non-profit, or government partner wishing to adopt the software. Our sharing framework and consortium-based support model have evolved over time along with the size of the consortium (currently more than 3,200 REDCap partners across 128 countries). While the “REDCap Consortium” model represents only one example of how to build and disseminate a software platform, lessons learned from our approach may assist other research institutions seeking to build and disseminate innovative technologies.

AI snapshot

Written from the paper’s full text.

TL;DR

This paper describes how REDCap grew from a Vanderbilt-built data capture tool into an international consortium through phased sharing and support. It reports that by mid-December 2018 the consortium had more than 3,200 partners in 128 countries and argues that the staged model offers transferable lessons for disseminating research software.

Key findings

  • The consortium expanded from a single site in 2004–2005 to more than 3,207 partners across 128 countries by mid-December 2018; in 2018 alone it added 575 partners, with roughly 2.75 international requests for each U.S. request and more than 20% of partners in World Bank low- and middle-income countries.
  • Growth followed six phases: local development, three collaborating sites, 4–10 partners, about 50 national sites, about 500 sites, and then more than 500 sites globally, with changes in licensing, communication, support staffing, and feature priorities at each stage.
  • REDCap was cited in more than 6,000 journal articles between 2004 and 2018; early return-on-investment tracking at Vanderbilt in 2008–2009 cited REDCap’s value in securing 23 funded or awarded projects.
  • Lessons include starting with local needs, maintaining compatibility with existing projects, setting modest expectations and delivering more than promised, using simple communication tools, managing growth deliberately, and enabling flexible modules, APIs, and plug-ins.

Methods

  • Descriptive experience report tracing REDCap and the REDCap Consortium from 2004 through 2018, organized into six chronological phases.
  • Evidence includes consortium membership counts, partner distribution, publication citation counts, local return-on-investment examples, and narrative accounts of governance, licensing, support calls, conferences, and software features.
  • No formal hypothesis testing or controlled comparison; the analysis is a retrospective narrative synthesis of program metrics and lessons learned.

Limitations

  • Stated: the authors note that the REDCap Consortium is only one dissemination model and may not suit all groups; REDCap is not open source, eligibility is limited to non-profit or government institutions, the license restricts code sharing and reseller services, and Vanderbilt retains control over the development trajectory and funding-driven priorities.
  • Stated: growth reduced Vanderbilt’s ability to maintain close ties with every new partner; support is limited to partner informatics teams rather than end users, and many non-technical vendor requests were denied.
  • Evident: the metrics are program-reported and descriptive, with no independent or controlled evaluation; citation counts and return-on-investment examples are not adjusted for confounding, and the paper does not report systematic user outcomes or comparative performance against other platforms.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1016/j.jbi.2019.103208

Cites

57 of 57 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Claims the paper makes

12 of 20 cited sources checked · 4 supported · 0 flagged · accuracy not yet measured

  • Premisecitation

    REDCap is an example of a CTSA-funded clinical research software application that has grown beyond its single institutional use case to be shared with institutions across the world.

    “The Research Electronic Data Capture (REDCap) data management platform is an example of a CTSA-funded clinical research software application that has grown beyond its single institutional use case to be shared with institutions across the world [26].”
    Quote in the paperSubstantial claim1 of 1 sources checked
    • cites [26] Harris PA, Taylor R, Thielke R, Payne J, Gonzalez N, Conde JG, Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support, J. Biomed. Inform 42 (2009) 377– 381. doi: 10.1016/j.jbi.2008.08.010. 18929686 PMC2700030 source

      The Introduction says REDCap was initially developed at Vanderbilt, and Results IV.B reports that it was shared through a consortium of 26 domestic and one international partner. Results IV.A links REDCap to a CTSA organization, but the passages do not establish that CTSA funded the software. The reported international reach is also narrower than “institutions across the world” may suggest. (LLM, conf=0.86)

      Experimental — accuracy not yet measured
  • Premisecitation

    There remain significant barriers to sharing clinical research software applications.

    “there remain significant barriers to sharing clinical research software applications [19]”
    Quote in the paperSubstantial claim1 of 1 sources checked
    • cites [19] Reis SE, Berglund L, Bernard GR, Califf RM, Fitzgerald GA, Johnson PC, Reengineering the national clinical and translational research enterprise: the strategic plan of the National Clinical and Translational Science Awards Consortium, Acad. Med. J. Assoc. Am. Med. Coll 85 (2010) 463– 469. doi: 10.1097/ACM.0b013e3181ccc877. PMC2829722 20182119 source

      The Abstract (page not provided) describes barriers to collaboration in translational research, and Strategic Goal 3 proposes data-sharing mechanisms across the consortium. Neither passage identifies significant barriers to sharing clinical research software applications specifically. (LLM, conf=0.70)

      Experimental — accuracy not yet measured
  • Premisecitation

    Limited personnel and resources are stretched to support research needs, forcing sites to restrict programs and services and limit innovation.

    “limited personnel and resources are stretched to support research needs, forcing sites to restrict programs and services and limit innovation [6–9].”
    Quote in the paperSubstantial claim3 of 4 sources checked
    • cites [6] May L, Zatorski C, Vora D, The Role of Technology in Translational Science, World Med. Health Policy 5 (2013) 389– 394. doi: 10.1002/wmh3.69. source
    • cites [7] Fahy BG, Balke CW, Umberger GH, Talbert J, Canales DN, Steltenkamp CL, Conigliaro J, Crossing the chasm: information technology to biomedical informatics, J. Investig. Med. Off. Publ. Am. Fed. Clin. Res 59 (2011) 768– 779. doi: 10.231/JIM.0b013e31821452bf. PMC3137749 21383632 source

      The Discussion (Barriers; page unavailable) describes funding constraints, unevenly distributed resources, and reliance on IT personnel outside the program to meet research needs. It does not say these pressures forced sites to restrict programs or services or limited innovation; the program described instead obtained funding to expand its capabilities. (LLM, conf=0.83)

      Experimental — accuracy not yet measured
    • cites [8] Sheetz MP, Can small institutes address some problems facing biomedical researchers?, Mol. Biol. Cell 25 (2014) 3267– 3269. doi: 10.1091/mbc.E14-05-1017. 25360047 PMC4214771 source

      The Introduction describes funding difficulties and increasing regulatory demands, while “Funding of Small Institutes” says flexible funds are critical to innovative research. The paper does not say that limited personnel and resources force sites to restrict programs or services; its account instead focuses on how shared staff and facilities can support research. (LLM, conf=0.82)

      Experimental — accuracy not yet measured
    • cites [9] Etz RS, Hahn KA, Gonzalez MM, Crabtree BF, Stange KC, Practice-Based Innovations: More Relevant and Transportable Than NIH-funded Studies, J. Am. Board Fam. Med 27 (2014) 738– 739. doi: 10.3122/jabfm.2014.06.140053. 25381069 source

      The paper’s table (page not provided) says research grants often add responsibilities to existing jobs, and its discussion describes practices adapting to funding constraints. It does not say that supporting research forces sites to restrict programs or services, or that personnel demands limit innovation. (LLM, conf=0.81)

      Experimental — accuracy not yet measured
  • Findingown data

    Since its initial development at Vanderbilt University, REDCap has been adopted by more than 3,207 partners in 128 countries as of mid-December 2018.

    “Since its initial development at Vanderbilt University, REDCap has been adopted by more than 3,207 partners in 128 countries as of mid-December 2018 (Figures 1 and 2, Table 1).”
    Quote in the paperNot a substantial claim
  • Findingnone given

    The authors created a broader consortium sharing and support model for any academic, non-profit, or government partner wishing to adopt the software.

    “we created a broader consortium sharing and support model for any academic, non-profit, or government partner wishing to adopt the software”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. 42
  • May combine two claims. 25

  • Probably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing). May combine two claims.

    Premisecitation

    Clinical research informatics (CRI) is an evolving field widely recognized as crucial for transforming and reengineering the translational research enterprise.

    “Clinical research informatics (CRI) is an evolving field widely recognized as crucial for transforming and reengineering the translational research enterprise [1–3].”
    Quote in the paperNot a substantial claim3 of 3 sources checked
    • cites [1] Embi PJ, Clinical research informatics: survey of recent advances and trends in a maturing field, Yearb. Med. Inform 8 (2013) 178– 184. 23974569 source
    • cites [2] Embi PJ, Payne PRO, Advancing methodologies in Clinical Research Informatics (CRI): Foundational work for a maturing field, J. Biomed. Inform 52 (2014) 1– 3. doi: 10.1016/j.jbi.2014.10.007. 25484113 source

      The opening passage (page unavailable) describes CRI as an emergent field with growing activity in response to challenges in translational clinical research. Later passages say CRI methods can accelerate research and improve its conduct, but do not establish that CRI is widely recognized as crucial for transforming and reengineering the translational research enterprise. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
    • cites [3] Kahn MG, Weng C, Clinical research informatics: a conceptual perspective, J. Am. Med. Inform. Assoc 19 (2012) e36– e42. doi: 10.1136/amiajnl-2012-000968. 22523344 PMC3392857 source

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation

    REDCap has limited personnel requirements (one support person can easily manage hundreds of projects) but does require typical web infrastructure including one or more secure web servers running PHP, MySQL/MariaDB, and SMTP email services.

    “REDCap has limited personnel requirements (one support person can easily manage hundreds of projects [48]) but does require typical web infrastructure including one or more secure web servers running PHP, MySQL/MariaDB, and SMTP email services.”
    Quote in the paperNot a substantial claim1 of 1 sources checked
    • cites [48] Klipin M, Mare I, Hazelhurst S, Kramer B, The process of installing REDCap, a web based database supporting biomedical research: the first year, Appl. Clin. Inform 5 (2014) 916– 929. doi: 10.4338/ACI-2014-06-CR-0054. 25589907 PMC4287671 source

      The citation is attached to the personnel claim. The Methods section reports three staff with allocated REDCap time, and §4.2 reports 133 projects; these support modest staffing needs, but not the assertion that one support person can easily manage hundreds of projects. The subsequent infrastructure claim is outside the cited parenthetical. (LLM, conf=0.88)

      Experimental — accuracy not yet measured

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation

    Alternate software distribution models exist (e.g., i2b2, OpenMRS, Vivo).

    “Alternate software distribution models exist (e.g., i2b2 [61], OpenMRS [62], and Vivo [63])”
    Quote in the paperNot a substantial claim2 of 3 sources checked
    • cites [61] Natter MD, Quan J, Ortiz DM, Bousvaros A, Ilowite NT, Inman CJ, Marsolo K, McMurry AJ, Sandborg CI, Schanberg LE, Wallace CA, Warren RW, Weber GM, Mandl KD, An i2b2-based, generalizable, open source, self-scaling chronic disease registry, J. Am. Med. Inform. Assoc. JAMIA 20 (2013) 172– 179. doi: 10.1136/amiajnl-2012-001042. 22733975 PMC3555330 source
    • cites [62] Mohammed-Rajput NA, Smith DC, Mamlin B, Biondich P, Doebbeling BN, OpenMRS A Global Medical Records System Collaborative: Factors Influencing Successful Implementation, AMIA. Annu. Symp. Proc 2011 (2011) 960– 968. 22195155 PMC3243141
    • cites [63] Borner K, Ding Y, Conlon M, Corson-Rikert J, VIVO: A Semantic Approach to Scholarly Networking and Discovery, Morgan & Claypool Publishers, 2012. source

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation

    REDCap is a secure web application for building and managing online surveys and databases, designed to support data capture for research studies.

    “REDCap is a secure web application for building and managing online surveys and databases, designed to support data capture for research studies [26].”
    Quote in the paperNot a substantial claim1 of 1 sources checked
    • cites [26] Harris PA, Taylor R, Thielke R, Payne J, Gonzalez N, Conde JG, Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support, J. Biomed. Inform 42 (2009) 377– 381. doi: 10.1016/j.jbi.2008.08.010. 18929686 PMC2700030 source

      The Methods sections on study creation and the user interface describe REDCap as a secure, web-based application for creating study databases and collecting research data through electronic forms. The passages do not establish that it builds or manages online surveys specifically. (LLM, conf=0.85)

      Experimental — accuracy not yet measured

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    REDCap was developed in 2004 to address an institutional need at Vanderbilt University.

    “The Research Electronic Data Capture (REDCap) data management platform was developed in 2004 to address an institutional need at Vanderbilt University”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    REDCap was shared with a limited number of adopting sites beginning in 2006.

    “then shared with a limited number of adopting sites beginning in 2006”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    The sharing framework and consortium-based support model have evolved over time along with the size of the consortium.

    “Our sharing framework and consortium-based support model have evolved over time along with the size of the consortium”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    Currently more than 3,200 REDCap partners across 128 countries.

    “currently more than 3,200 REDCap partners across 128 countries”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingnone given

    The Vanderbilt team maintains control of the REDCap software development trajectory, although it frequently seeks input on features and prioritization from the Consortium.

    “The Vanderbilt team also maintains control of the REDCap software development trajectory, although we frequently seek input on features and prioritization from the Consortium.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    Vanderbilt's IRB system uses REDCap as a central component for protocol submissions.

    “Vanderbilt’s IRB system uses REDCap as a central component for protocol submissions”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning

    The Vanderbilt REDCap team expanded its staffing to five full-time developers and two dedicated community support people, with additional associated faculty and custom add-on developers from the Data Core.

    “the Vanderbilt REDCap team has expanded its staffing to five full-time developers and two dedicated community support people, with the addition of other associated faculty and custom add-on developers from the Data Core.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    A "zero-fee" REDCap Consortium membership meant we could only provide support to our partners' informatics teams, not their end users.

    “a “zero-fee” REDCap Consortium membership meant we could only provide support to our partners’ informatics teams, not their end users.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingreasoning

    By mid-2006, the three-site REDCap collaborative had proven so productive that we decided to establish a true consortium by expanding to ten sites.

    “By mid-2006, the three-site REDCap collaborative established in Phase 2 had proven so productive that we decided to establish a true consortium by expanding to ten sites.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    By the end of 2012, we were supporting more than 500 Consortium partners.

    “By the end of 2012, we were supporting more than 500 Consortium partners.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.

    Findingnone given

    Interest in REDCap spiked once approximately 50 partners had joined the Consortium and membership trended upwards in 2009.

    “Interest in REDCap spiked once approximately 50 partners had joined the Consortium and membership trended upwards in 2009.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingnone given

    Additional partners meant more time spent managing groups and less time working on needs specific to Vanderbilt research teams.

    “Additional partners meant more time spent managing groups and less time working on needs specific to Vanderbilt research teams.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    Funding support for REDCap has become increasingly diverse, including institutional sources, CTSA, Vanderbilt Data Core model, and other NIH-funded grants.

    “Funding support for REDCap has become increasingly diverse, including support from institutional sources, the CTSA, the Vanderbilt Data Core model, and other NIH-funded grants.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingnone given

    Consortium members continue to provide cross-institutional support through sharing resources, participating in formal presentations, and contributing to Consortium Committees.

    “Consortium members continue to provide cross-institutional support for one another through sharing resources (e.g., end-user local training material repository), participating in formal presentations (e.g., monthly REDCapU sessions design to support REDCap domain knowledge and career growth of local informatics champions), and contribution to Consortium Committees.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    Minor revisions to the REDCap EULA have clarified licensing for non-U.S. partners and cloud-based installations.

    “Minor revisions to the REDCap EULA have clarified licensing for non-U.S. partners and cloud-based installations.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    More than 20% of REDCap partners are located in countries designated as low-and middle-income by the World Bank.

    “More than 20% of REDCap partners are now located in countries designated as low-and middle-income by the World Bank.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    For-profit software vendors began to regard the REDCap community as a potential market, attempting to sell alternate software solutions.

    “For-profit software vendors also began to regard the REDCap community as a potential market, attempting to sell alternate software solutions.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Findingnone given

    By 2005, REDCap adoption had accelerated at Vanderbilt and we learned that other institutions faced the same challenge supporting their local research communities with centralized, HIPAA-compliant solutions for data planning, collection, and management.

    “By 2005, REDCap adoption had accelerated at Vanderbilt and we learned that other institutions faced the same challenge supporting their local research communities with centralized, HIPAA-compliant solutions for data planning, collection, and management.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    Vanderbilt's research data warehousing teams have built system exchange mechanisms allowing REDCap to serve as a final data delivery mechanism.

    “our research data warehousing teams have built system exchange mechanisms allowing REDCap to serve as a final data delivery mechanism.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning

    PCORI grant initiatives led to many features and functions necessary for participant engagement and patient reported data.

    “PCORI grant initiatives led to many features and functions necessary for participant engagement and patient reported data”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    New Committees have formed around shareable training materials, software plug-in development, and electronic health record systems integration.

    “New Committees have formed around shareable training materials, software plug-in development, and electronic health record systems integration.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given

    REDCap Consortium partner distribution tends to correlate with population density and regions of the world where biomedical research is supported.

    “In general, REDCap Consortium partner distribution tends to correlate with population density and regions of the world where biomedical research is supported.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingreasoning

    Vanderbilt resources were limited and the effort of supporting partner sites resulted in an overall slowdown of feature programming as well as local end-user training and promotion.

    “Vanderbilt resources were limited and the effort of supporting partner sites resulted in an overall slowdown of feature programming as well as local end-user training and promotion.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingnone given

    In 2018, 575 new REDCap partners were added, with approximately 2.75 international members for each U.S. request.

    “In 2018 alone, we added 575 new REDCap partners with approximately 2.75 international members for each U.S. request.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.

    Findingnone given

    REDCap partner institutions have gradually increased adoption of virtualized environments running REDCap, and more recently containerized solutions.

    “we have observed a gradual increase among REDCap partner institutions adopting virtualized environments running REDCap, and in more recent years, containerized solutions for supporting the software platform.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingreasoning

    Empowering local research teams to create and manage their own REDCap projects reduced per-project cost and ultimately allowed Vanderbilt to provide REDCap at no cost to any student, staff, or faculty member for any research project.

    “Empowering local research teams to create and manage their own REDCap projects reduced per-project cost and ultimately allowed Vanderbilt to provide REDCap at no cost to any student, staff, or faculty member for any research project.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Findingnone given

    The number of REDCap end users has grown proportionately, creating additional demand for generalized REDCap training.

    “The number of REDCap end users has grown proportionately, creating additional demand for generalized REDCap training.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning

    The paper EULA documents required signature by institutional officials on both sides, which introduced a two-to-three-week administrative turnaround time for joining the Consortium.

    “The paper EULA documents required signature by institutional officials on both sides, which introduced a two-to-three-week administrative turnaround time for joining the Consortium.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given

    Experts in various domains participate in the consortium and consult with the development team as needed.

    “Experts in informatics, biostatistics, data warehousing, clinical systems, trial operations, standards and ontologies, security methods, computer science, global health, mobile systems, library science, and other domains participate in the consortium and consult with the development team as needed.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S4 (based).

    Findingnone given

    Groups that were not proactive in their use of the Consortium mailing list were less likely to integrate with the existing community.

    “groups that were not proactive in their use of the Consortium mailing list were less likely to integrate with the existing community.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Findingnone given

    Organizations that adopted REDCap during Phase 4 were typically U.S.-based academic medical centers, though we also began working with a few highly motivated international partners from Japan, Singapore, and Canada.

    “Organizations that adopted REDCap during this Phase were typically U.S.-based academic medical centers, though we also began working with a few highly motivated international partners from Japan, Singapore, and Canada.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Findingreasoning

    The Core model enabled us to provide hosting services to users outside of Vanderbilt whose needs went beyond standard REDCap infrastructure, allowed diversification of our financial support model, and introduced the REDCap platform to more diverse users (including industry based research teams).

    “The Core model enabled us to provide hosting services to users outside of Vanderbilt whose needs went beyond standard REDCap infrastructure, allowed diversification of our financial support model, and introduced the REDCap platform to more diverse users (including industry based research teams).”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.

    Findingnone given

    During the 2014 Ebola outbreak, REDCap partner sites rapidly mobilized to share methods for surveillance data collection in academia and state governments, setting the stage for additional attention and adoption across U.S. state health departments, the U.S. Department of Veterans Affairs and other government agencies.

    “During the Ebola outbreak in 2014, we saw a rapid mobilization of REDCap partner sites sharing methods for surveillance data collection in both academia and state governments, setting the stage for additional attention and adoption across U.S. state health departments, the U.S. Department of Veterans Affairs and other government agencies.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S4 (based).

    Interpretationnone given

    Key features of the REDCap model have been early strategic partnering followed by managed growth and support of the community in stages.

    “Key features of the model have been early strategic partnering followed by managed growth and support of our community in stages.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Interpretationnone given

    New telephone and SMS-based survey features, offline functionality via the REDCap mobile application for coordinators, and MyCap for participants have enabled research data collection in settings unsuited to traditional web-based applications.

    “New telephone and SMS-based survey features, “offline” functionality via the REDCap mobile application for coordinators, and a separate mobile application (MyCap, https://www.projectmycap.org) for participants have enabled research data collection in settings unsuited to traditional web-based applications.”
    Quote in the paperNot a substantial claim

  • Classified as probably not a substantial claim.

    Interpretationreasoning

    Core components of the REDCap model may not be suited to all groups.

    “core components of our model may not be suited to all groups.”
    Quote in the paperSubstantial claim

  • May combine two claims.

    Premisenone given

    REDCap is available at no cost but is not open source software.

    “although REDCap is available at no cost, it is not open source software.”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisenone given

    REDCap's back-end architecture runs on open source components, is very flexible, and does not force strict requirements for general implementation.

    “REDCap’s back-end architecture, all of which runs on open source components, is very flexible and does not force strict requirements for general implementation.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Interpretationnone given

    The REDCap model has been successful to date, growing from a single site to a global consortium over approximately 13 years.

    “The REDCap model has been successful to date, growing from a single site to a global consortium over the course of approximately 13 years.”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Interpretationnone given

    Portability of project metadata across REDCap installations has allowed new types of sharing and collaboration.

    “Portability of project metadata across REDCap installations has allowed new types of sharing and collaboration.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).

    Interpretationreasoning

    As the Consortium has grown, the sophistication and influence of Consortium partners has increased.

    “As the Consortium has grown, so has the sophistication and influence of our Consortium partners.”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S2 (checkable), S4 (based).

    Interpretationnone given

    The REDCap Consortium has proven a successful model for software development and dissemination.

    “The REDCap Consortium has proven a successful model for software development and dissemination.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Interpretationreasoning

    By limiting Consortium membership to non-profit and government organizations, Vanderbilt reserved the right to market REDCap in the commercial space and to perform fee-based hosting for research teams in organizations not able or willing to join the REDCap consortium.

    “By limiting Consortium membership to non-profit and government organizations, Vanderbilt reserved the right to market REDCap in the commercial space and also to perform fee-based hosting for research teams in organizations not able or willing to join the REDCap consortium.”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Interpretationreasoning

    Recent work with major cloud vendors on deployment scripts and automated REDCap upgrade methods have created an opportunity for partners to set up REDCap installations in the cloud, eliminating the need for on-site hardware and reducing local systems administrator support.

    “Recent work with major cloud vendors on deployment scripts and automated REDCap upgrade methods have created an opportunity for partners to set up REDCap installations in the cloud, thereby eliminating the need for on-site hardware and reducing local systems administrator support.”
    Quote in the paperNot a substantial claim

  • Classified as probably not a substantial claim.

    Interpretationreasoning

    Software feature requests and guidance from active research teams have enabled the platform to grow from a rudimentary feature set to a rich set of modules capable of supporting diverse research operations on almost any scale.

    “Software feature requests and guidance from active research teams have enabled the platform to grow from a rudimentary feature set (data capture, data export, logging) to a rich set of modules capable of supporting diverse research operations on almost any scale.”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisereasoning

    REDCap can operate on-premise or on various cloud-based infrastructures (e.g., AWS, Azure, Google Cloud).

    “REDCap can operate “onpremise” (on the local institution’s hardware servers or virtualized servers) or on various cloud-based infrastructures (e.g., AWS, Azure, Google Cloud).”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisenone given

    The REDCap platform and Consortium represent only a single model in terms of software development and dissemination.

    “The REDCap platform and Consortium represent only a single model in terms of software development and dissemination.”
    Quote in the paperNot a substantial claim

  • May combine two claims.

    Premisereasoning

    Eligible REDCap partners must be non-profit or government institutions (not individuals), comply with U.S. export regulations, and agree to EULA terms including not sharing the codebase with third parties and not offering REDCap "reseller" services.

    “Eligible partners must be non-profit or government institutions (not individuals), comply with U.S. export regulations, and agree to the EULA terms, which include not sharing the codebase with third parties and not offering REDCap “reseller” services.”
    Quote in the paperSubstantial claim

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Interpretationnone given

    The REDCap software development and consortium growth model have been successful.

    “While the REDCap software development and consortium growth model have been successful”
    Quote in the paperNot a substantial claim

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Interpretationreasoning

    The iterative software design philosophy and incremental consortium growth fostered a collaborative spirit during REDCap's early days, which has been sustained through active participation of thousands of REDCap administrators.

    “The iterative software design philosophy and incremental consortium growth fostered a collaborative spirit during REDCap’s early days, which has been sustained through the active participation of thousands of REDCap administrators in REDCap calls, mailing lists, working groups, and conferences.”
    Quote in the paperNot a substantial claim
54 of 54

  • The paper relies on this without support.

    The core principles of the REDCap Consortium model are generalizable to other software development teams or sharing consortia.

    “we believe the core principles are generalizable and can benefit any software development team or sharing consortium.”
1 of 1

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • The randomization table will be generated by an external researcher, who will be the only one with access to the original randomization table; enrolment and the generation of the allocation code will be automatized via REDCap and cannot be influenced by any member of the research team.

    “The randomization table providing the basis for the computerized allocation in REDCap [182, 183] will be generated by an external researcher, who will be the only one with access to the original randomization table. Enrolment and the generation of the allocation code will be automatized via REDCap [182, 183] and hence cannot be influenced by any member of the research team.”

    From Efficacy of a transdiagnostic Internet prevention approach in adolescents (EMPATIA study): study protocol of a randomized controlled trial (2024) · cites this paper as [183]

    Split into 2 atoms — 1 confirmed, 1 partially supported, 0 disputed, 0 misattributed, 0 unverifiable. Expand the claim to see per-atom verdicts.

    Experimental — accuracy not yet measured

  • REDCap provides user-level access control, and changes with username, date, time, and modification are logged (audit trail) and can be controlled at any time.

    “REDCap [182, 183] will be used for data collection (interviews, online surveys). It provides user-level access control as it is only accessible to authorized personnel. To ensure traceability of relevant processing operations, changes with username, date, time, and modification are logged (audit trail) and can be controlled at any time.”

    From Efficacy of a transdiagnostic Internet prevention approach in adolescents (EMPATIA study): study protocol of a randomized controlled trial (2024) · cites this paper as [183]

    The Phase 1 section (page not provided) identifies user-rights functionality and extensive data and operations logging, supporting access control and a general audit trail. It does not specify that each change is logged with a username, date, time, and modification, or that the log can be checked at any time. (LLM, conf=0.88)

    Experimental — accuracy not yet measured

  • Randomization was conducted using REDCap's randomization function with a 1:1 allocation ratio to MB-P or usual prenatal care.

    “pregnant individuals were assigned using REDCap’s randomization function via a 1:1 allocation ratio to MB-P or usual prenatal care.”

    From Effects of a Personalized Stress Management Intervention on Maternal Mental Health: A Randomized Clinical Trial. (2025) · cites this paper as Harris et al. 2019

    The Phase 5 section (no page provided) says REDCap developed a participant-randomization module, supporting the reference to REDCap’s randomization function. It does not report the MB-P prenatal trial, its participants, or a 1:1 allocation to MB-P versus usual care. (LLM, conf=0.87)

    Experimental — accuracy not yet measured

  • The randomization sequence was created by a statistician unaffiliated with the study to ensure masking to the randomization scheme and was implemented by REDCAP's randomization software based on the participant's location.

    “This randomization sequence was created by a statistician unaffiliated with the study to ensure masking to the randomization scheme and was implemented by REDCAP’s randomization software based on the participant’s location52,53.”

    From Autonomous artificial intelligence increases screening and follow-up for diabetic retinopathy in youth: the ACCESS randomized control trial (2024) · cites this paper as [52]

    The Phase 5 section says REDCap added a participant-randomization module, supporting the identification of REDCap as randomization software. It does not describe this study’s sequence, an unaffiliated statistician, masking, or randomization based on participant location; searches for those details found no supporting passage. No page number is available in our copy. (LLM, conf=0.88)

    Experimental — accuracy not yet measured

  • 118 additional families completed a REDCap screening form but were not enrolled.

    “118 additional families completed a REDCap (Research Electronic Data Capture, [51,52]) screening form but were not enrolled.”

    From Tracking Acquisition of Language in Kids (TALK) study protocol: A longitudinal investigation of infants at high vs. low risk for atypical speech and language development (2026) · cites this paper as [52]

Cites

Flagged first, then by citations

6 of the 63 references couldn’t be matched to a known paper.

Research works printed but not linked: 2

  1. Committee to Review the Clinical and Translational Science Awards Program at the National Center for Advancing Translational Sciences, Board on Health Sciences Policy, Institute of Medicine, The CTSA Program at NIH: Opportunities for Advancing Clinical and Translational Research, National Academies Press (US), Washington (DC), 2013. http://www.ncbi.nlm.nih.gov/books/NBK144067/ (accessed December 10, 2014).
  2. Nadan, 2004, Software licensing in the 21st century: Are software licenses really sales, and how will the software industry respond, AIPLA Q. J., 32, 555

Cited by

Sorted by citations

Related

Authors
Harris, P. A., Taylor, R., Minor, B. L., Elliott, V., Fernandez, M., O'Neal, L., McLeod, L., Delacqua, G., Delacqua, F., Kirby, J., & Duda, S. N.
Affiliations
  • Vanderbilt University (US)
  • Vanderbilt University Medical Center (US)
Corresponding author
Harris, Paul A.
ORCID
Venue
Journal of Biomedical Informatics
Publisher
Elsevier BV
Published
2019-07
Volume
95
Pages
103208
ISSN
1532-0464 (ISSN-L)
DOI
10.1016/j.jbi.2019.103208
PMC
PMC7254481
OpenAlex
W2944434778
Semantic Scholar
aea266d1d66f01c9141385a7e1baf6d1599dcae9
Cited by
24,013
References
63
Citations by year
2026: 3706 · 2025: 4752 · 2024: 4657 · 2023: 3779 · 2022: 3249 · 2021: 2604 · 2020: 1153 · 2019: 70 · 2018: 2 · 2016: 1 · 2014: 1 · 2013: 1 · 2012: 3
FWCI
2198.23
Type
journal article
Language
en
Open access
Licence
Locations
  • Journal of Biomedical Informatics (publishedVersion)
  • PubMed (publishedVersion)
  • PubMed Central (acceptedVersion)
Funders
NIH/NCATS (UL1 TR002243)
Topics
  • Physical Sciences › Computer Science › Information Systems › Research Data Management Practices
  • Social Sciences › Decision Sciences › Information Systems and Management › Scientific Computing and Data Management
  • Health Sciences › Health Professions › Health Information Management › Electronic Health Records Systems
Keywords
REDCap, research data management tools, consortium model, software adoption
MeSH terms
Humans, Medical Informatics, Software, Information Dissemination, Biomedical Research, Internationality

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-15.

Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-15.

Cited sources are checked by gpt-6-sol.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review