swap_callsWorkflows

Wearable Sensors Data Journey

edit_noteIn Progress: Workflow being finalized by Lasso.

This workflow defines the end-to-end lifecycle for wearable device data from participant wear through cloud ingestion, quality control, standardization, and processing to generate derived metrics.

At A Glance#

1
Device registration & wear

Site staff register the device and link it to the participant. The participant wears the device for the prescribed period, and data upload to the vendor cloud.

2
Ingestion & secure routing

Retrieve vendor data, assess PII/PHI content, and route data to the appropriate environment.

3
Acquisition QC & follow-up

Extract metadata, validate completeness and coverage, notify sites of exceptions, and record the acquisition outcome.

4
Standardization & processing

Convert data to the required BIDS-compatible structure, run processing, and generate derived metrics.

Workflow Safeguards#

  • Participant–Device Linkage: Devices are tracked and linked to the correct participants.
  • Validated Wear Periods: Wear periods are checked against expected duration and completeness criteria.
  • Secure PII Handling: Data containing personally identifiable information are handled only in secure environments.
  • Automated Quality Control: Configurable rules evaluate wear duration, expected days, data gaps, and sampling consistency. Failures trigger site notifications that are logged for review.
  • Standardized, Reproducible Outputs: Processing produces consistent outputs that can be reliably reproduced.
  • End-to-End Traceability: Track each participant, device, serial number, wear period, ingestion event, QC decision, and derived output throughout the workflow.

Responsibilities & Data Handoffs#

Team or system Main responsibilities
Site staff & participants Register and assign devices, complete the wear period, document return, and respond to acquisition issues.
Vendor cloud Receive and retain device recordings for retrieval by Lasso, as applicable to the device.
Lasso Retrieve and route recordings, maintain participant–device linkage, run acquisition checks, and generate standardized and derived outputs.
SMEs Define QC criteria and review exceptions requiring scientific judgment.
  • LassoSAFE: Secure storage of raw wearable sensor recordings containing PHI/PII
  • Lasso Data Share: receives and stores stores non-identifying metadata and approved outputs only
  • External systems: Device-specific vendor cloud environments

Workflow Details#

STEP 1 - Device registration & wear#

When the participant arrives for an in-person visit, site staff complete an Equipment Inventory Form in Lasso, recording device type, serial number, and kit or asset ID. The wearable device is registered in Lasso and linked to the participant. The participant wears the device for the protocol-defined wear period and data is automatically uploaded to the vendor cloud environment.

STEP 2 - Ingestion & secure routing#

Lasso retrieves data from the vendor cloud to anonymize and convert to BIDS format. Raw data are routed to separate storage environments based on whether they PII/PHI:

  • Raw data containing PII → ingested into LassoSAFE
  • Raw data with no PII → ingested into standard Lasso storage

STEP 3 - Acquisition QC & follow-up#

In Lasso, non-identifying metadata are extracted (including file size, duration/days covered, and expected cadence) and registered in the Lasso Data Share. Validation is performed to confirm that that data size and coverage meet expectations. If validation fails, site staff are notified of insufficient or missing data to pursue optional remediation, including extended wear or re-sync of the data. If validation is successful, then wearable acquisition is marked COMPLETE in Lasso Launchpad.

STEP 4 - Standardization & processing#

The participant returns the device and site staff complete a Return of Equipment Form in Lasso, recording return date/time, device condition. Raw wearable data is converted to BIDS format and processed via a BIDS App pipeline to generate derived metrics (e.g., activity summaries).

Formats & Outputs#

Output category Contents
Administrative records Equipment registration, participant assignment, and return documentation
Source data Archived vendor exports
Acquisition QC Coverage/completeness results and documented exceptions
Standardized data BIDS-compatible wearable datasets
Derived data Processed wearable metrics