swap_callsWorkflows

Questionnaire Intake, Build, & Deployment

edit_noteIn Progress: Workflow documentation is being finalized by Lasso.

This workflow describes how questionnaire specifications are reviewed, built in REDCap, tested in Lasso, and deployed in Lasso. It applies to participant-facing surveys and clinician- or research assistant (RA)-administered instruments. The primary artifacts produced are the REDCap questionnaire and a canonical data dictionary.

Overview#

The process begins when a Senior DCC Officer receives a questionnaire specification (not a completed form), such as a survey instrument or protocol-defined assessment. The workflow concludes after the questionnaire is deployed to Lasso production and a final sanity check is completed.

All work is tracked, with structured peer review, parallel artifact creation, and staged testing prior to production release.

The workflow emphasizes clear ownership, parallel work streams, and creation of durable artifacts to support downstream analytics, harmonization, and governance.

Workflow#

STEP 1 - Intake & Tracking - Senior DCC Officer#

The Senior DCC Officer receives a questionnaire specification (e.g. Participant survey, Clinician- or RA-administered instrument, Protocol appendix or assessment definition, etc.) and creates an item within the project management platform used by Lasso.

STEP 2 - Prepare REDCap Template - Data Analyst#

The Data Analyst translates the questionnaire specification into a REDCap questionnaire template and sends the template to the REDCap Engineer through Lasso's project management platform. REDCap questionnaire template options include:

  • Question text and ordering
  • Response options and encodings
  • Field types and validation
  • Required vs optional fields
  • Preliminary branching or skip logic (if specified)

STEP 3 - Build the Questionnaire in REDCap Development - REDCap Engineer#

  • Upload template from Data Analyst(s) to REDCap dev and prod
  • Turn on survey and attach to the appropriate events
  • Once questionnaire data is uploaded into REDCap, REDCap engineer to send over to PM.

STEP 4 - Create ticket in technical project management platform to add data dictionary to Lasso - Data Analyst#

The Data Analyst attaches the populated template to Lasso's project management platform and the technical project management platform tickets and assigns the project management platform ticket to a second Data Analyst for peer review by Team Charm.

STEP 5 - Peer Review of Questionnaire Specification - Second Data Analyst#

In parallel with Step 6, the Second Data Analyst reviews the populated REDCap template, requests revisions as needed, and reassigns the ticket to the REDCap Engineer once approved. The populated REDCap template is reviewed for:

  • Fidelity to the original questionnaire specification
  • Internal consistency and clarity
  • Alignment with study conventions and REDCap standards

STEP 6 - Canonical Data Dictionary Creation - Data Analyst#

In parallel with Step 5, the Data Analyst creates a canonical data dictionary as a separate Excel file, serving as the authoritative definition of questionnaire variables. The file is then attached or linked directly in the project management platform ticket, ensuring alignment between questionnaire specification, REDCap implementation, and downstream analytics and harmonization needs.

Example Elements Included in Canonical Data Dictionary
  • Canonical variable names
  • Source question text
  • Response options and coding
  • Data type and format
  • Missing value conventions
  • Notes on derivations, harmonization, or downstream expectations

STEP 7 - REDCap Questionnaire Implementation - REDCap Engineer#

  • Implements the questionnaire in REDCap, including Field configuration; Validation rules; Branching and conditional logic; Instrument settings appropriate for participant or clinician/RA administration.
  • Coordinates with the Data Analyst as needed to resolve discrepancies between the REDCap build and the canonical data dictionary.
  • Updates the project management platform ticket when implementation is complete.

STEP 8 - Staging Testing - Data Analysts → Senior DCC Officer → SMEs#

Data Analyst performs initial testing in Lasso staging to verify the following, then alerts the senior DCC officer that SME testing is ready:

  • Questionnaire behavior and flow
  • Response validation and required fields
  • Branching logic
  • Consistency with the canonical data dictionary

The SME then conducts secondary testing in Lasso staging to confirm:

  • Scientific and clinical intent is met
  • Usability for intended respondents
  • Data capture supports downstream analysis needs

STEP 9 - Production Deployment - Platform / Release Process#

Once approved by the SMEs, the questionnaire is promoted to Lasso production.

STEP 10 - Post-Release Sanity Check - Data Analyst#

The Data Analyst performs a final sanity check in production to confirm that (1) the correct questionnaire is live and (2) there are no configuration or deployment issues. Once verified, the project management platform ticket is closed.