{"id":4750,"date":"2026-04-08T09:07:46","date_gmt":"2026-04-08T13:07:46","guid":{"rendered":"https:\/\/health.uconn.edu\/clinical-research-center\/?page_id=4750"},"modified":"2026-04-08T14:42:35","modified_gmt":"2026-04-08T18:42:35","slug":"redcap-surveys-guide","status":"publish","type":"page","link":"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/redcap-surveys-guide\/","title":{"rendered":"REDCap Surveys Guide Hub"},"content":{"rendered":"<div class=\"in-page-tabs\"><ul id=\"menu-redcap\" class=\"menu nav nav-tabs\"><li id=\"menu-item-4436\" class=\"menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children dropdown\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/\" class=\"dropdown-toggle\" data-toggle=\"dropdown\">REDCap Usage<b class=\"caret\"><\/b><\/a>\n<ul class=\"dropdown-menu\">\n\t<li id=\"menu-item-4437\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/uch-redcap-user-agreement\/\">REDCap User Agreement<\/a><\/li>\t<li id=\"menu-item-4439\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-project-eligibility\/\">REDCap Usage &amp; Project Eligibility<\/a><\/li>\t<li id=\"menu-item-4440\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-user-eligibility\/\">REDCap User Eligibility<\/a><\/li>\t<li id=\"menu-item-4438\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/new-redcap-policy-and-fee-faq\/\">REDCap Usage Fees<\/a><\/li><!--.dropdown-->\n<\/ul>\n<\/li><li id=\"menu-item-4441\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-account-request\/\">REDCap Account Request<\/a><\/li><li id=\"menu-item-4446\" class=\"menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children dropdown\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/redcap-login-issues\/\" class=\"dropdown-toggle\" data-toggle=\"dropdown\">REDCap Login Issues<b class=\"caret\"><\/b><\/a>\n<ul class=\"dropdown-menu\">\n\t<li id=\"menu-item-4447\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-account-request\/uchc-user-login-issues\/\">UCHC User Login Issues<\/a><\/li>\t<li id=\"menu-item-4448\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-account-request\/login-issues\/\">UConn &amp; External Users Login Issues<\/a><\/li><!--.dropdown-->\n<\/ul>\n<\/li><li id=\"menu-item-4442\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-training\/\">REDCap Training<\/a><\/li><li id=\"menu-item-4443\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/\">REDCap Guides &amp; How-to<\/a><\/li><li id=\"menu-item-4449\" class=\"menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children dropdown\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/scheduled-maintenance\/\" class=\"dropdown-toggle\" data-toggle=\"dropdown\">REDCap Maintenance<b class=\"caret\"><\/b><\/a>\n<ul class=\"dropdown-menu\">\n\t<li id=\"menu-item-4678\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/scheduled-maintenance\/\">REDCap Maintenance<\/a><\/li>\t<li id=\"menu-item-4450\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/scheduled-maintenance\/new-features-improvements\/\">REDCap Upgrade Details<\/a><\/li><!--.dropdown-->\n<\/ul>\n<\/li><li id=\"menu-item-4451\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap-systems\/\">REDCap Systems<\/a><\/li><li id=\"menu-item-4452\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/using-redcap-for-nih-data-sharing\/\">Using REDCap for NIH Data Sharing<\/a><\/li><li id=\"menu-item-4453\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/citing-redcap\/\">Citing REDCap<\/a><\/li><li id=\"menu-item-4455\" class=\"menu-item menu-item-type-post_type menu-item-object-page\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/redcap_news\/\">REDCap News You Can Use<\/a><\/li><\/ul><\/div><div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<p style=\"font-size: 1.08em;margin-top: 0\"><strong>Planning, Building, Distributing, and Protecting Surveys in REDCap<\/strong><\/p>\n<p>REDCap offers several ways to build and distribute surveys, from a simple public survey link to more advanced workflows using the Participant List, Automated Survey Invitations, and Survey Queue. This guide is designed to help study teams choose the right approach, configure surveys intentionally, and avoid common setup mistakes.<\/p>\n<p>For a step-by-step walk through, check out the\u00a0<strong><span style=\"color: #0000ff\"><a href=\"https:\/\/uchredcap.uchc.edu\/redcap\/surveys\/?s=FMWYNLXXJXXDX494\" rel=\"\" style=\"color: #0000ff\">Survey Wizard: The Basics<\/a><\/span><\/strong><\/p>\n<p>For more advanced survey workflows, REDCap offers several automation tools that support how surveys are delivered, how participants move from one survey to the next, and how study teams are notified when specific conditions are met. Because these tools serve different purposes, it can be difficult to know which one to use. The <span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/redcap-surveys-guide\/redcap-survey-automation-overview\/\" rel=\"\" style=\"color: #0000ff\"><strong>Survey Automation Overview<\/strong><\/a><\/span> provides a clear, high-level guide to help you choose the right approach for your project.<\/p>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 14px 16px;margin: 22px 0;border-radius: 4px\"><strong>Core Principle:<\/strong> Decide <strong>before building<\/strong> whether your survey will be anonymous or identifiable, whether participants will complete one survey or multiple surveys, and whether invitations will be manual or automated.<\/div>\n<div style=\"background: #fef2f2;border-left: 6px solid #dc2626;padding: 14px 16px;margin: 22px 0;border-radius: 4px\"><strong>Important:<\/strong> Once you use participant email addresses, Participant List, designated email fields, or linked follow-up surveys, the workflow is no longer truly anonymous and must align with your IRB-approved plan.<\/div>\n<div style=\"background: #f0f9ff;border: 1px solid #bae6fd;padding: 16px 18px;margin: 24px 0;border-radius: 6px\">\n<h2 style=\"margin-top: 0;font-size: 1.2em\">On this page<\/h2>\n<ul style=\"margin: 0;padding-left: 20px\">\n<li><a href=\"#overview\">Survey Overview<\/a><\/li>\n<li><a href=\"#enable\">Enable and Build a Survey<\/a><\/li>\n<li><a href=\"#settings\">Survey Settings<\/a><\/li>\n<li><a href=\"#distribution\">Choose a Distribution Method<\/a><\/li>\n<li><a href=\"#public-link\">Public Survey Link<\/a><\/li>\n<li><a href=\"#participant-list\">Participant List &amp; Invitation Log<\/a><\/li>\n<li><a href=\"#automated\">Automated Survey Invitations (ASI)<\/a><\/li>\n<li><a href=\"#queue\">Survey Queue<\/a><\/li>\n<li><a href=\"#flow\">Survey Flow Controls<\/a><\/li>\n<li><a href=\"#longitudinal\">Multi-Survey and Longitudinal Workflows<\/a><\/li>\n<li><a href=\"#notifications\">Survey Notifications<\/a><\/li>\n<li><a href=\"#security\">Protecting Public Surveys<\/a><\/li>\n<li><a href=\"#best-practices\">Key Best Practices<\/a><\/li>\n<li><a href=\"#quick-start\">Quick Start Checklist<\/a><\/li>\n<\/ul>\n<\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"overview\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Survey Overview<\/h2>\n<p>Any data collection instrument in REDCap can be enabled as a survey, allowing participants to enter data without needing REDCap user access.<\/p>\n<p>Most survey workflows involve three key areas:<\/p>\n<ul style=\"padding-left: 20px\">\n<li><strong>Project Setup<\/strong> \u2013 enable surveys and project-level options<\/li>\n<li><strong>Online Designer<\/strong> \u2013 build the instrument, configure Survey Settings, and manage advanced survey features<\/li>\n<li><strong>Survey Distribution Tools<\/strong> \u2013 distribute survey links, manage participants, and review invitation activity<\/li>\n<\/ul>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> Think of survey setup as a workflow, not just a form. The build, invitation method, confidentiality model, and follow-up plan should all be decided together.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"enable\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Enable and Build a Survey<\/h2>\n<ol style=\"padding-left: 22px\">\n<li>Go to <strong>Project Setup<\/strong> and enable <strong>Use Surveys in this project<\/strong><\/li>\n<li>Go to <strong>Online Designer<\/strong><\/li>\n<li>Build or revise the instrument<\/li>\n<li>Click <strong>Enable<\/strong> to convert the instrument into a survey<\/li>\n<li>Open <strong>Survey Settings<\/strong> and save changes<\/li>\n<\/ol>\n<p>If you leave Survey Settings without saving, the instrument will remain a data entry form rather than a survey.<\/p>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> If a project is already in Production and surveys have not been enabled, that option may be locked and require administrator assistance.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"settings\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Survey Settings<\/h2>\n<h3>Basic Options<\/h3>\n<ul style=\"padding-left: 20px\">\n<li><strong>Survey Status<\/strong> \u2013 active or offline<\/li>\n<li><strong>Survey Title<\/strong> \u2013 can differ from the instrument name<\/li>\n<li><strong>Survey Instructions<\/strong> \u2013 text shown at the top of the survey<\/li>\n<\/ul>\n<h3>Design &amp; Display<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Logo, font, text size, and theme<\/li>\n<li>Question numbering<\/li>\n<li>All on one page vs. one section per page<\/li>\n<li>Enhanced radio buttons and checkboxes<\/li>\n<li>Text-to-speech and accessibility options<\/li>\n<\/ul>\n<h3>Access &amp; Response Controls<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Response limit<\/li>\n<li>Time limit for survey completion<\/li>\n<li>Survey expiration<\/li>\n<li>Save &amp; Return Later<\/li>\n<li>Allow returning to edit completed responses<\/li>\n<\/ul>\n<h3>Completion &amp; Termination<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Survey completion text<\/li>\n<li>Redirect to a URL<\/li>\n<li>Auto-continue to next survey<\/li>\n<li>Allow respondents to repeat the survey, when repeating instruments are enabled<\/li>\n<li>PDF Auto-Archiver<\/li>\n<li>Confirmation email<\/li>\n<\/ul>\n<h3>Special Use Cases<\/h3>\n<ul style=\"padding-left: 20px\">\n<li><strong>Save Survey PDF to File Upload field<\/strong> \u2013 useful when another form or user needs a snapshot of a completed survey<\/li>\n<li><strong>Survey-specific email invitation field<\/strong> \u2013 useful when different surveys in one project are completed by different people<\/li>\n<li><strong>e-Consent Framework<\/strong> \u2013 supports certification and archiving workflows for electronic consent<\/li>\n<\/ul>\n<div style=\"background: #fef2f2;border-left: 6px solid #dc2626;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> Confirmation emails and PDF attachments are generally not recommended for surveys containing identifying information or PHI, because email is not considered a secure communication channel.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> Keep Survey Settings as simple as possible. Most survey problems come from adding too many features without a clear workflow need.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"distribution\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Choose a Distribution Method<\/h2>\n<p>Most survey workflows fall into one of four categories:<\/p>\n<table style=\"width: 100%;border-collapse: collapse;margin: 20px 0\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Method<\/th>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Best For<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Public Survey Link<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Open-access or truly anonymous surveys<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Participant List<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Known participants, one-time links, reminders, response tracking<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Automated Survey Invitations<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Logic-based and scheduled invitation workflows<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Survey Queue<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Multiple surveys presented in sequence for the same record<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div style=\"background: #f8fafc;border: 1px solid #cbd5e1;padding: 16px 18px;margin: 24px 0;border-radius: 6px\">\n<h2 style=\"margin-top: 0;font-size: 1.15em\">Public Survey vs. Participant List (Invitations)<\/h2>\n<table style=\"width: 100%;border-collapse: collapse;margin-top: 12px\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Feature<\/th>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Public Survey Link<\/th>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Participant List \/ Invitations<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Main purpose<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Open access survey via a shared link<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Send individualized survey links via email<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Best for<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Anonymous or broad distribution<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Known participants and tracked responses<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Unique links per participant<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">No (same link for everyone)<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes (individualized survey links)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Tracks who responded<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">No (unless you collect identifiers)<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes (linked to record\/participant)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Email invitations<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Not built-in<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes (manual or automated)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Reminder capability<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">No<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes (via Invitation Log or ASIs)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Anonymous responses<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes (default use case)<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Optional (depends on configuration)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Typical use case<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Open survey posted online or shared broadly<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Send baseline + follow-up surveys to enrolled participants<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 12px 14px;margin: 16px 0 0 0;border-radius: 4px\"><strong>Simple rule:<\/strong> Use a <strong>Public Survey Link<\/strong> when you do not need to track who responded. Use the <strong>Participant List \/ Invitations<\/strong> when you need to send surveys to specific individuals and track responses.<\/div>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 12px 14px;margin: 12px 0 0 0;border-radius: 4px\"><strong>Important:<\/strong> If you collect email addresses or identifiers in a public survey to send follow-up surveys, the data is no longer truly anonymous and becomes linked to participant identity.<\/div>\n<\/div>\n<div style=\"background: #f8fafc;border: 1px solid #cbd5e1;padding: 16px 18px;margin: 24px 0;border-radius: 6px\">\n<h2 style=\"margin-top: 0;font-size: 1.15em\">Survey Queue vs. Automated Survey Invitations<\/h2>\n<table style=\"width: 100%;border-collapse: collapse;margin-top: 12px\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Feature<\/th>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">Survey Queue<\/th>\n<th style=\"border: 1px solid #d1d5db;padding: 10px;text-align: left;background: #f3f4f6\">ASI<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Main purpose<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Controls which survey a participant sees next<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Controls when a survey invitation is sent<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Best for<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Multi-survey navigation and sequencing<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Scheduled or logic-based invitation delivery<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Sends emails?<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">No<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Uses logic?<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes, to decide what appears next<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Yes, to decide when invitations are scheduled<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\"><strong>Typical use case<\/strong><\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Eligibility survey \u2192 consent \u2192 baseline survey<\/td>\n<td style=\"border: 1px solid #d1d5db;padding: 10px\">Send follow-up survey 7 days after baseline completion<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Simple rule:<\/strong> Use <strong>Survey Queue<\/strong> to guide participants through surveys. Use <strong>ASI<\/strong> to send surveys automatically.<\/div>\n<\/div>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 12px 14px;margin: 16px 0 0 0;border-radius: 4px\"><strong>Decision Tip:<\/strong> If you need broad anonymous access, start with Public Survey Link. If you know who your participants are and need tracking or reminders, use Participant List. If invitations should be triggered automatically, use ASI. If participants need to complete multiple surveys in sequence, consider Survey Queue.<\/div>\n<div><\/div>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"public-link\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Public Survey Link<\/h2>\n<p>The Public Survey Link is the simplest and fastest way to distribute a survey. It uses one shared link for all respondents.<\/p>\n<ul style=\"padding-left: 20px\">\n<li>Best for anonymous or open-access workflows<\/li>\n<li>No respondent-specific tracking<\/li>\n<li>Allows multiple submissions unless additional controls are added<\/li>\n<li>Only the first survey in a project has a public survey link<\/li>\n<\/ul>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> A public survey link can be shared, reposted, or reused. If the survey involves compensation, eligibility screening, or sensitive recruitment, a public link requires additional safeguards.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"participant-list\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Participant List &amp; Invitation Log<\/h2>\n<p>The Participant List allows you to send customized email invitations and track whether each person has responded.<\/p>\n<h3>What it does<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Add participants by email address<\/li>\n<li>Optionally add a Participant Identifier<\/li>\n<li>Send invitations immediately or schedule them<\/li>\n<li>Send reminders to non-responders<\/li>\n<li>Track no response, partial response, and completed response<\/li>\n<li>Review sent and scheduled invitations in the Survey Invitation Log<\/li>\n<\/ul>\n<h3>When to use it<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>You know participant email addresses in advance<\/li>\n<li>You want one-time unique survey links<\/li>\n<li>You want to track responders and non-responders<\/li>\n<li>You need reminders<\/li>\n<\/ul>\n<div style=\"background: #fef2f2;border-left: 6px solid #dc2626;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> If you enable <strong>Participant Identifier<\/strong>, the survey is no longer anonymous. If participants need to take the same survey more than once, they must be added to the Participant List multiple times so each invitation has its own unique link.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> Use the Survey Invitation Log when you need to verify what was sent, what is scheduled, what reminders exist, or whether an invitation failed.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"automated\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Automated Survey Invitations (ASI)<\/h2>\n<p>Automated Survey Invitations allow REDCap to schedule and send survey invitations automatically when specified conditions are met.<\/p>\n<h3>Requirements<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>A survey must already exist<\/li>\n<li>A valid email field must be designated at the project or survey level<\/li>\n<li>If the project is longitudinal, the correct event must be selected<\/li>\n<\/ul>\n<h3>ASI setup includes four parts<\/h3>\n<ol style=\"padding-left: 22px\">\n<li>Compose the message<\/li>\n<li>Define the trigger conditions<\/li>\n<li>Define when to send the invitation<\/li>\n<li>Activate the ASI<\/li>\n<\/ol>\n<h3>Good uses for ASI<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Follow-up surveys sent a set number of days after an earlier survey<\/li>\n<li>Event-based invitation workflows in longitudinal projects<\/li>\n<li>Conditional invitations that depend on data values<\/li>\n<li>Repeated reminder schedules for incomplete surveys<\/li>\n<\/ul>\n<p>Manual invitations and ASIs can coexist. If needed, scheduled invitations and reminders can be reviewed and deleted in the Survey Invitation Log.<\/p>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> ASIs do <strong>not<\/strong> work on projects enabled with repeating instruments\/events. Also, once an ASI has fired for a record, changing the logic later will not make it fire again for that same record automatically.<\/div>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Design Tip:<\/strong> Build an explicit \u201cstop emails\u201d or \u201cprevent surveys\u201d field into the project so invitation logic can be turned off for a participant when needed.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> Test ASI logic with test records and consider using a Data Quality rule or report logic first to confirm that the condition behaves as expected before activating invitations.<\/div>\n<\/div>\n<h3><strong><span style=\"color: #0000ff\"><br \/>\n<span style=\"color: #000000\">Click here to take a <\/span><\/span><span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/redcap-surveys-guide\/deep-dive-guide-for-scheduled-and-logic-based-survey-invitations\/\" rel=\"\" style=\"color: #0000ff\">Deeper-Dive into Scheduled and Logic-Based Survey Invitation<\/a><\/span><\/strong><\/h3>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"queue\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Survey Queue<\/h2>\n<p>The Survey Queue displays surveys for a participant on a single page, like a to-do list, and can control which surveys appear next based on completion status and logic.<\/p>\n<h3>Use Survey Queue when<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Participants need to complete multiple surveys in one workflow<\/li>\n<li>The next survey depends on prior answers or eligibility<\/li>\n<li>You want participants guided through a structured sequence<\/li>\n<\/ul>\n<h3>Key features<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Display logic based on survey completion and branching-like conditions<\/li>\n<li>Optional custom text at the top of the queue<\/li>\n<li><strong>Auto Start<\/strong> to immediately launch the next incomplete survey<\/li>\n<li>Option to keep the queue hidden from participants<\/li>\n<\/ul>\n<div style=\"background: #fef2f2;border-left: 6px solid #dc2626;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> Survey Queue logic is evaluated at the record level, not relative to the current event or repeating instance. Also, <strong>Auto-continue<\/strong> in Survey Settings can override Survey Queue behavior, so do not combine them casually.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> Use Survey Queue rather than Auto-continue when progression depends on conditions or eligibility. Use Auto-continue only for very simple same-event survey chains.<\/div>\n<\/div>\n<div><\/div>\n<h3>Click here to take a\u00a0<strong><span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/redcap-surveys-guide\/redcap-survey-queue\/\" rel=\"\" style=\"color: #0000ff\">Deeper-Dive into Multi-Survey Workflows and Participant Navigation<\/a><\/span><\/strong><\/h3>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div><\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"flow\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Survey Flow Controls<\/h2>\n<h3>Stop Action<\/h3>\n<p>Stop Action allows a survey to end when a participant selects a specific answer choice on supported field types such as dropdowns, radio buttons, checkboxes, Yes\/No, or True\/False.<\/p>\n<ul style=\"padding-left: 20px\">\n<li>Useful for ineligibility screening<\/li>\n<li>Useful when a survey should end early based on a response<\/li>\n<li>Can display alternate completion text for those who stop out<\/li>\n<\/ul>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> By default, when a survey ends via Stop Action, the partial response is saved and marked complete, even if required questions later in the survey were never answered.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> If Stop Action is being used for ineligibility screening, consider enabling the option to prevent responses from being saved when the survey ends through a Stop Action.<\/div>\n<h3>Repeat Survey Option<\/h3>\n<p>If an instrument is enabled as a repeating instrument, Survey Settings can display a button allowing the participant to repeat the survey. This is useful when one person may need to submit multiple similar entries in a single sitting.<\/p>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"longitudinal\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Multi-Survey and Longitudinal Workflows<\/h2>\n<p>When you need to send multiple surveys to the same participant over time, REDCap must have a way to tie those responses back to the same record.<\/p>\n<h3>Common approaches<\/h3>\n<ul style=\"padding-left: 20px\">\n<li><strong>Public Survey Link + designated email field<\/strong> \u2013 the first survey collects the participant\u2019s email, which populates the Participant List for later invitations<\/li>\n<li><strong>Participant List from the start<\/strong> \u2013 participants are invited using known email addresses, and follow-up surveys are sent through additional Participant List invitations or ASIs<\/li>\n<li><strong>Longitudinal project + ASIs<\/strong> \u2013 later surveys are triggered after completion of earlier event surveys<\/li>\n<\/ul>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> In a multi-survey workflow within one project, only participants who completed the earlier required survey and provided the needed linkage information will typically appear for the follow-up survey workflow.<\/div>\n<div style=\"background: #f0fdf4;border-left: 6px solid #16a34a;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Best Practice:<\/strong> If the workflow depends on the same person completing multiple linked surveys, design the linkage method at the beginning. Retrofitting email capture or participant matching later is messy and error-prone.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"notifications\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Survey Notifications<\/h2>\n<p>Survey Notifications send an email to selected project users whenever a survey is completed.<\/p>\n<ul style=\"padding-left: 20px\">\n<li>Configured from <strong>Online Designer \u2192 Survey Notifications<\/strong><\/li>\n<li>Useful when the study team needs prompt awareness of new survey responses<\/li>\n<li>The email includes a link to the response, not the survey data itself<\/li>\n<\/ul>\n<div style=\"background: #fff7ed;border-left: 6px solid #ea580c;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> Notifications can become overwhelming in higher-volume projects. In those cases, a report or alert-based workflow may be more manageable.<\/div>\n<\/div>\n<\/div>\n<div><\/div>\n<h3>Click here to take a\u00a0<strong><span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/services\/informatics-core\/redcap\/guides-how-tos\/redcap-surveys-guide\/redcap-alerts-notifications\/\" rel=\"\" style=\"color: #0000ff\">Deeper-Dive into Automated Notifications and Data-Triggered Messaging<\/a><\/span><\/strong><\/h3>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"security\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Protecting Public Surveys<\/h2>\n<p>Public survey links are useful, but they are also the most vulnerable to bots, invalid responses, repeat submissions, and compensation abuse.<\/p>\n<h3>Core safeguards<\/h3>\n<ul style=\"padding-left: 20px\">\n<li>Use CAPTCHA or other challenge-based access controls<\/li>\n<li>Consider a response limit to reduce exposure<\/li>\n<li>Add challenge or attention-check questions<\/li>\n<li>Use hidden honeypot fields to help identify bot activity<\/li>\n<li>Review timestamps, response patterns, and anomalous clusters<\/li>\n<li>Avoid fully automated compensation workflows<\/li>\n<li>Use targeted distribution instead of broad public posting when possible<\/li>\n<\/ul>\n<h3>CAPTCHA options<\/h3>\n<p>Depending on your instance, you may have built-in Google reCAPTCHA or an external module such as <strong>nedCAPTCHA<\/strong>, which can provide math, image, or custom challenge-response protections for public surveys.<\/p>\n<div style=\"background: #fef2f2;border-left: 6px solid #dc2626;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Important:<\/strong> CAPTCHA helps, but it is not enough by itself. Public surveys that include incentives or open recruitment need layered protections and active monitoring.<\/div>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Security Mindset:<\/strong> Treat a public survey as the front porch, not the whole house. Use the initial public survey to screen, verify, or triage respondents before moving them deeper into the study workflow.<\/div>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<h4><strong>For a deeper dive, check out:<\/strong><\/h4>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div>\n<ul>\n<li><span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/wp-content\/uploads\/sites\/50\/2024\/05\/Avoiding-and-Detecting-Bots-and-Fraud_REDCapSurveys_.pdf\" target=\"_blank\" rel=\"noopener\" style=\"color: #0000ff\"><strong>Detecting and Preventing BOT and Fraudulent Survey Responses<\/strong><\/a><\/span><\/li>\n<li><strong><span style=\"color: #0000ff\"><a href=\"https:\/\/health.uconn.edu\/clinical-research-center\/wp-content\/uploads\/sites\/50\/2024\/05\/nedCAPTCHA.docx\" target=\"_blank\" rel=\"noopener\" style=\"color: #0000ff\">CAPTCHA<\/a><\/span><\/strong><\/li>\n<\/ul>\n<\/div>\n<div id=\"top\" class=\"redcap-survey-hub-guide\" style=\"max-width: 1100px;margin: 0 auto;line-height: 1.7;color: #1f2937\">\n<div><\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"best-practices\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Key Best Practices<\/h2>\n<ul style=\"padding-left: 20px\">\n<li>Choose the survey distribution model before you start building<\/li>\n<li>Use Public Survey Link only when open access is truly appropriate<\/li>\n<li>Use Participant List when you need one-time links, reminders, or response tracking<\/li>\n<li>Use ASIs for automated follow-up, but test logic before activation<\/li>\n<li>Use Survey Queue for multi-survey workflows, especially when progression depends on conditions<\/li>\n<li>Use Stop Action thoughtfully and decide whether stop-out responses should be saved<\/li>\n<li>Protect public surveys with layered safeguards, not just a single setting<\/li>\n<li>Test every workflow with realistic test records before going live<\/li>\n<li>Move the project to Production before collecting real data<\/li>\n<li>Ensure survey design, identifiers, and communications align with the IRB-approved plan<\/li>\n<\/ul>\n<div style=\"background: #eff6ff;border-left: 6px solid #2563eb;padding: 14px 16px;margin: 20px 0;border-radius: 4px\"><strong>Final Takeaway:<\/strong> The best REDCap survey workflow is not the one with the most features. It is the one that clearly fits the study design, protects confidentiality, minimizes user confusion, and can be reliably managed by the study team.<\/div>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<\/div>\n<hr style=\"margin: 30px 0;border: 0;border-top: 1px solid #d1d5db\" \/>\n<h2 id=\"quick-start\" style=\"background: #329EB8;color: #ffffff;padding: 12px 16px;border-radius: 6px;margin-bottom: 16px\">Quick Start Checklist:<\/h2>\n<p>&#x2705; Enable Surveys at the project level<\/p>\n<p>&#x2705; Enable the instrument as a survey in Online Designer<\/p>\n<p>&#x2705; Review Survey Settings before sending any link<\/p>\n<p>&#x2705; Choose the correct distribution method<\/p>\n<p>&#x2705; Decide whether data will be anonymous, coded, or identifiable<\/p>\n<p>&#x2705; Test the full workflow from the participant perspective<\/p>\n<p>&#x2705; Move the project to Production before collecting real data<\/p>\n<div style=\"text-align: right;margin-top: 14px\"><a href=\"#top\" style=\"background: #eef6f8;color: #1f2937;padding: 6px 12px;text-decoration: none;border-radius: 20px;font-size: 0.95em\">Back to top \u2191<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>REDCap Usage REDCap User Agreement REDCap Usage &amp; Project Eligibility REDCap User Eligibility REDCap Usage Fees REDCap Account RequestREDCap Login Issues UCHC User Login Issues UConn &amp; External Users Login Issues REDCap TrainingREDCap Guides &amp; How-toREDCap Maintenance REDCap Maintenance REDCap Upgrade Details REDCap SystemsUsing REDCap for NIH Data SharingCiting REDCapREDCap News You Can Use Planning, [&hellip;]<\/p>\n","protected":false},"author":4679,"featured_media":0,"parent":2190,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"acf":[],"publishpress_future_action":{"enabled":false,"date":"2026-05-05 05:09:32","action":"change-status","newStatus":"draft","terms":[],"taxonomy":""},"_links":{"self":[{"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/pages\/4750"}],"collection":[{"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/users\/4679"}],"replies":[{"embeddable":true,"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/comments?post=4750"}],"version-history":[{"count":16,"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/pages\/4750\/revisions"}],"predecessor-version":[{"id":4776,"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/pages\/4750\/revisions\/4776"}],"up":[{"embeddable":true,"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/pages\/2190"}],"wp:attachment":[{"href":"https:\/\/health.uconn.edu\/clinical-research-center\/wp-json\/wp\/v2\/media?parent=4750"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}