Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

🗞 Headlines

Our goal for the Mobile Toolbox Platform is to provide a complete end-to-end solution for the use of remotely-administered cognitive and other tests by researcher teams, without the need for any study-specific technology development. A complete solution must cover scenarios across the complete lifecycle of a study, and support research teams in: 

  • Delivering timely, reliable, high-fidelity data to researchers

  • Providing well documented validated measures.

  • Learning about available mobile cognitive measures and designing appropriate digital research protocols.

  • Managing collection of data from study participants, including support for enrollment, aggregate/high-level adherence tracking, and participant communications. 

  • Providing secure transfer of de-identified data to analysts.

  • Disseminating data, results, and other findings from completed studies for forms that encourage reuse by other research teams, subject to FAIR principles.


Identified the last long tail issue
Tip

Highlights -

May 2023
  • Got ICAR study launch to the finish line with intense coordination and entirely new schemas, ETL and scoring

  • DCCS and Flanker final resolution

  • Data state API completed in Bridge.

  • June 2023

    1. MyCogMobile initial incorporation into production app

    2. Long tail of missing parquet data (underscore file name ) of missing parquet data

    3. no new issues from live studies

    4. adherence report had first-look and feedback from coordinators

    5. Additional feature squeezed in to incled ‘not completed status’issue) final resolution for live studies and construct validation

    6. Resolution of missing startdate and enddate metadata

    7. Operationalization of scoring code is in progress

    8. Progress on manuscripts

    9. Improved documentation of Bridge Downstream setup processes

    Warning

    Lowlights -

    May

    June 2023

    1. Reprocessing of data with ‘underscore’ issue led to a broader error that broke completion.csv process

    2. Unexpected metadata change caused missing startdate and enddateGlue bug continues to produce unpredictable results, slowing down data analysis and start for ICAR

    3. Data export delays due to sluggish queues

    4. new issue reported with long session window schedule delivery

    5. Did not get to Jira service desk metrics

    6. Did not get joint sprint planning cadence on the schedule

    Note

    Risks

    • Compressed timeline allows for minimal data QA for ICAR study

    • Need to define QA and work plan for upcoming MyCogMobile study in mid-JulyPersonnel and function transitions with departure of Larsson

    • Summer schedules and temporary leave

    • Need better process to validate schemas

    Info

    Other updates

    • Progress on Completed PoC of Monash binaries to get builds into sample appsproduction app


    📈 Monthly summary


    Where can I find information about…

    *reach out to Sonia or Ann if you can’t access links

    Release Calendar

    Release Notes

    Issue Tracker

    Issue Prioritization rubric

    Data completion dashboard

    Data completion downloadable .csv

    Jira Service Desk bug template - in progress

    Jira Metrics - in progress

    Jira Incident Manager - not started

    Jira projects, backlogs, boards

    Synapse Mobile Toolbox parent project

    What are we working on?

    June

    July 2023 our focus is on….

    Description

    Type

    Expected output for end of month

    Future work

    Compute scores for DCCS (shape-color sorting) based on inferred Response Time for Android users where direct collection of RT is missing. This is to recover from a bug where RT was not collected from Android users prior to build 26.

    User facing

    • DCCS scores updated in daily .csv provided to collaborators - on track for 6/1 completion

    • item-level response times provided to NU for QA

    • provide item-level response times persistent for users, prior to public release of data

    • maintenance of computation in future scoring code

    Support for myCog ‘grouped’ assessment

    Planning

    Confirm and implement any support requirements

    Implement solution to mitigate ‘Glue bug’ to unblock ICAR and future studies

    User facing

    • Analysts don’t have unpredictable columns (_double and _int) appearing in parquet, or NaNs or unexpected zero values in scores .csv

    • define monitoring/validation tests

    Scoring code operationalization

    Infrastructure

    • Automation of completion dashboard and .csv to refresh every 24hrs

    • Create mapping of which version of scoring code is running by setting up release process for scoring code to tag to Docker container.

    • optimize EC2 compute instance

    • write back data completion state to Bridge

    iOS support for MyCogMobile ‘grouped’ assessment

    User facing

    • Study launch in mid-July

    • respond to bug fixes

    none

    Define data processing states for internal and external exposure. Researchers will be able to see assessment level data status of completed on device, data processing, and data ready for analysis. Internal tools can see additional states (validation fail, parquet complete etc.)

    Planning

    • Requirements Final requirements document for data states

    • Implement writing to API and exposing states in UI

    • persist scores completion state for Bridge - API complete

    • provide status of data as ‘in progress’ or ‘ready for analysis’ in Researcher Portal UI

    Define process and tools for more efficient schema validation

    Planning

    Work plan to prepare for upcoming schema refresh of core measures

    Implementation of process and toolsDetailed adherence report visible in the Researcher Portal UI that shows each assessment completion status, skipped status, and completion timestamp

    User facing

    • Expand beta to UCSF and UCSD - completed

    • provide status of data as ‘in progress’ or ‘ready for analysis’ in Researcher Portal UI

    Jira Service Desk

    Process

    Mechanism for internal and external collaborators to file bugs in a template that propagates through to staging for triage

    • respond to feedback

    • setup cloning to Jira project space

    Data re-processing of data ‘stuck’ in parquet queue

    Issue resolution

    • resolution of ~1% null value validation fails due to weather data

    • resolution of UCSD failures

    investigate taskdata validation fails due to null value and finalize plan for go-forwardData re-processing of data ‘stuck’ in parquet queue

    Issue resolution

    • resolution of ~1-2% ‘underscore file name’

    Re-process data

    Implement next phases of background recorder shutdown

    User facing

    • Live studies - completed

    • Rollback App implementation with E2E QA plan for metadata/schema validation

    • Future studies - remove from Researcher Portal UIPlan to rollback App implementation and metadata/schema validation

    • Rollback App implementation with extensive QA

    Implement logout capability

    User facing

    • enabled in debug mode

    • QA started in Android and iOSQA complete in Android and iOS

    • available in participant app UI

    Create a way to expose/stage new assessments for specific studies

    Infrastructure

    Design complete for server implementation of study-level permissions

    Implement UI/API to designate permissions

    Alerting reqs for adherence

    User facing

    Validation of UI

    Define criteria for onboarding new studies

    Planning

    • External/internal studies

    • Understand timing

    • Infrastructural and process needs

    • Map to funding status

    • Evaluate results for GA

    Compute scores for DCCS (shape-color sorting) based on inferred Response Time for Android users where direct collection of RT is missing. This is to recover from a bug where RT was not collected from Android users prior to build 26.

    User facing

    • none

    • provide item-level response times persistent for users, prior to public release of data

    • maintenance of computation in future scoring code

    Communications


    📈 User facing feature requests


    Feature

    Description

    Complexity

    Priority

    Delivery forecast

    Upgrade and unify build processes for production app

    https://sagebionetworks.jira.com/l/cp/XnNugxp1

    medium

    TBD

    TBD

    Login/logout capability

    Allow participant and preview accounts to logout and login so that data state is retained and cache i s properly cleared without deleting and reinstalling the app. Supports preview and ‘recycled’ phone scenarios

    high

    1TBD

    August release 2023

    Turn off background recorders

    part 1: turn off capability for researchers to optionally turn on recorders and defalut all study configs to OFF

    part 2: excise the implementation of the recorders on both Android and iOS

    part 1 = low

    part 2 = high because of QA

    2

    Part 1 june July 2023

    Editable schedules

    Allow changes to a schedule after a study has been launched

    high

    2

    Post-renewal. Requires architectural overhaul. New studies can currently be manually constructed to have more flexibility. Existing studies will not be editable. New work will ensure that ALL new studies will automatically have more flexibility.

    Spanish language

    Provide app and assessments to run studies ALL in english or ALL in spanish

    medium

    2

    earliest Fall 2023

    Self-service account setup

    Allow public users to onboard to Mobile Toolbox to explore, and to launch studies with a verified identity

    high

    1

    target fall 2023

    Self-service access controls

    Allow Study Admins to invite users and have granular control over what team members can see and do with PII and study data

    high

    1

    target fall 2023

    Custom Survey Authoring

    Researchers can collaborate and construct custom survey questions that can be delivered to participants as part of their schedule of activities

    high

    2

    Deprioritized. Target beta in Q3/Q4

    Detailed Adherence completion reporting

    Study Coordinators can see the details of completion status and date for every assessment administered

    medium

    1

    April 2023 - completed

    Adherence Alerts page

    Study Coordinators can view alerts when participants fall below adherence thresholds or other events

    medium

    2

    Q2 2023

    Schema refresh

    Update the schemas of core assessments to optimize data processing

    medium

    2completed

    post-renewal

    Automated scoring

    Scores are automatically processed on-device or on a daily basis to keep up with ongoing data collection

    medium

    1

    V1 complete

    Public website updates

    Include suggested language for grant submissions, sample data, FAQs, About Us bios, more detailed assessment information

    medium

    2

    Q3 2023

    Customer support helpdesk

    Ticketing and tracking system and knowledge base to scale up responses to issues reported by coordinators

    high

    2

    Q3 2023

    Product documentation

    Update and publish product documentation

    medium

    3

    July oost-renewal October 2023

    Crashlytics tuning

    Improve crash and log collection from the mobile App to more quickly characterize and respond to bugs.

    medium

    2

    Q2 2023

    Data samples

    Provide data samples so potential users can demo the app and explore data output without having to launch a study

    low

    3

    Q2 2023

    Demographics upload UI

    Study Coordinators can upload demographics metadata so it can be automatically incorporated into data processing and analysis

    medium

    3

    TBD


    🎯 OKRs and supporting initiatives - Work in progress….


    <Objective 1>

    Status
    colourGreen
    titleon track
    /
    Status
    colourYellow
    titleat risk
    /
    Status
    colourRed
    titleOFF Track

    Key results

    (tick)

    (error)

    (warning)

    (info)

    Expand
    titleJira tickets

    <Objective 2>

    Status
    colourGreen
    titleon track
    /
    Status
    colourYellow
    titleat risk
    /
    Status
    colourRed
    titleOFF Track

    Key results

    (tick)

    (error)

    (warning)

    (info)

    Expand
    titleJira tickets

    <Objective 3>

    Status
    colourGreen
    titleon track
    /
    Status
    colourYellow
    titleat risk
    /
    Status
    colourRed
    titleOFF Track

    Key results

    (tick)

    (error)

    (warning)

    (info)

    Expand
    titleJira tickets


    (.) Other updates


    💚 Engineering/Operational Health

    (lightbulb) Customer insights

    📣 Marketing Highlights

    🎭 Competitor insights