swap_callsWorkflows

EnrollNow Data Journey

edit_noteIn Progress: Workflow documentation being finalized by Lasso.

This workflow creates a central participant record from screening and consent information collected in EnrollNow. The ETL retrieves and validates the required registration metadata, applies privacy transformations, and transmits the resulting payload to Lasso Data Share.

At A Glance#

1
Screen & consent

Site staff screen and consent participants in EnrollNow, which generates the Lasso Participant ID.

2
Extract & validate

The ETL retrieves registration data and checks that required fields are complete and valid.

3
Apply privacy transformations

The ETL replaces the true date of birth with a jittered date, shifted by up to ±7 days.

4
Create participant record

The Lasso Data Share receives the transformed registration payload and creates the central participant record.

Workflow Safeguards#

  • Data Minimization: Only fields required for participant registration and cohort assignment are transmitted.
  • Early De-identification: Privacy-preserving transformations occur before data enter the central platform.
  • Clear System Boundaries: Identifiable data (EnrollNow PII) is restricted to the site level, intentionally separated from EDC/study data (Lasso) to limit exposure if either system is compromised, and supports HIPAA, SOC 2, and VPAT compliance. Lasso operates only on de-identified or transformed fields.
  • Auditability: All transformations and data handoffs are logged to support traceability and compliance.

Systems & Data Handoffs#

Data move through three systems. EnrollNow supports screening and consent, the ETL validates and transforms registration data, and Lasso Data Share creates the central participant record. The ETL performs both Steps 2 and 3 below.

EnrollNow

Participant registration

  • Participant profile created
  • Screening and consent

ETL Process

Pull & transform data

  • Pull data from EnrollNow
  • Transform and deidentify data
  • Push to Secure Environment

Lasso Data Share

Create participant record

  • Receive transformed payload
  • Create participant record

Workflow Details#

Site staff use EnrollNow to manage participant creation, including initial eligibility screening, informed consents, and scheduling. Upon participant creation, EnrollNow generates a Lasso Participant ID used as the primary key for all downstream data coordination activities. At this stage, no clinical, assessment, or derived data are transferred, only registration metadata required to establish the participant record centrally. The process will not move forward if the participant is not deemed to be eligible.

STEP 2 - ETL Process#

Once screened and consented, the data is pulled from EnrollNow on a fixed schedule (every 5 minutes via the Adapter). The data is screened for new participants/visits and the createParticipant and createVisit endpoints are called on "lasso-secure". Lasso secure de-identifies participant creation by jittering the DOB and triggers workflows associated with participant and/or visit creation.

STEP 3 - Privacy Transformations#

To reduce re-identification risk prior to central registration, the DOB is jittered by up to ±7 days in either direction, replacing the original DOB in all downstream systems (which remains available only within EnrollNow at the site level). This transformation occurs before the participant record is created in Lasso Data Share, ensuring that Lasso never receives the true date of birth. An internal audit log is generated by the ETL to capture Participant ID, transformation applied, and timestamp of the event.

STEP 4 - Participant Creation in Lasso Data Share#

The transformed payload is transmitted from the ETL to Lasso Data Share. Lasso Data Share uses the Lasso Participant ID as the primary identifier and creates a new participant record. At this point, the participant exists in the central system and is ready for downstream data ingestion, quality control workflows, and governed access. No raw identifiers (e.g., true DOB) are stored in the Lasso Data Share.