swap_callsWorkflows

Questionnaire Scoring

edit_noteIn Progress: Workflow documentation is being finalized by Lasso.

This page describes the end-to-end workflow for implementing, validating, and deploying scoring logic for REDCap questionnaires in the Lasso platform.

Overview#

1

The Senior DCC Officer receives the scoring algorithm and creates a ticket within the project management platform used by Lasso.

2

The Data Analyst codes the scoring logic in R.

3

The Data Analyst versions and centralizes the scoring code and links in the project management platform ticket.

4

The Data Analyst adds the code links and implementation details to the ticket, then reassigns it to the Workflow Manager.

5

The Workflow Manager implements the scoring logic in the ETL.

6

The Data Analyst tests end-to-end form population and scoring in the Lasso staging environment.

7

The Working Group tests the scoring implementation in the Lasso staging environment.

8

The scoring implementation is approved and deployed to Lasso production.

Why This Workflow#

  • Transparent Implementation: Scoring algorithms are implemented in R using clear, reviewable logic.
  • Centralized Version Control: Scoring code is versioned and maintained in a centralized location.
  • End-to-End Testing: Form population and scoring are tested in the staging environment.
  • Validated Before Release: Scoring implementations are reviewed and approved before deployment to production.

Required Forms#

SME Measure Implementation Test Checklist SMEs complete this checklist to verify correct protocol implementation in Lasso. Testing includes review of question content, response options, ordering and branching logic, scoring, and value ranges. Only validated measures are included in release data.

Workflow#

The process begins when a data analyst receives a scoring algorithm associated with a questionnaire (e.g., total scores, subscales, derived variables). The workflow concludes when the scoring logic is successfully deployed to Lasso production after staged testing and SME approval. Lasso uses a project management platform that serves as the system of record for tracking work, linking to versioned code, and managing handoffs to the Workflow Manager.

STEP 1 - Scoring Algorithm Intake (Data Analyst)#

  • Receives the scoring algorithm, which may include:
  • Scoring rules defined in a protocol or publication
  • Subscale definitions
  • Handling of missing or partial responses
  • Transformations, cutoffs, or derived classifications
  • Confirms scope and applicability to the questionnaire and study.

STEP 2 - Scoring Code Development (R) (Data Analyst)#

  • Implements the scoring logic in R, ensuring:
  • Clear, readable, and modular code
  • Alignment with the defined scoring algorithm
  • Explicit handling of missing or invalid data
  • Initial development work is tracked via the project management platform used by Lasso.

STEP 3 - Versioning, Centralization, & Documentation (Data Analyst)#

  • Versions and centralizes the R scoring code in the approved repository or shared location.
  • Updates the project management platform ticket with:
  • Links to the versioned code (e.g., repository, commit, tag)
  • Any required run-time assumptions or dependencies
  • Notes relevant to ETL implementation
  • Reassigns the project management platform ticket to the Workflow Manager for ETL implementation.

STEP 4 - ETL Implementation (Workflow Manager)#

  • Integrates the versioned scoring code into the ETL workflow, ensuring:
  • Correct execution order relative to form ingestion
  • Consistent variable naming and outputs
  • Alignment with platform conventions
  • Updates the project management platform ticket once implementation is complete.

STEP 5 - End-to-End Staging Testing (Data Analyst)#

  • Tests the full pipeline in Lasso staging, including:
  • Questionnaire form population
  • Execution of scoring logic via the ETL
  • Verification of scored outputs against expected results
  • Confirms that scoring behaves correctly across:
  • Complete responses
  • Partial or missing data scenarios
  • Documents test results or issues in the project management platform ticket.

STEP 6 - SME Validation#

  • Performs secondary testing in Lasso staging to confirm:
  • Scientific and clinical correctness of scoring outputs
  • Alignment with study intent and documentation
  • Suitability of derived variables for downstream use
  • Approves or requests revisions as needed.

STEP 7 - Production Deployment#

  • Upon SME approval, the scoring logic is promoted to Lasso production as part of the ETL release.
  • Release status is recorded in the project management platform ticket.