8/15/2023 TB ETOR Meeting notes

Kelly Wroblewski: --

Angela Starks: X

Zenda Berrada: --

Anne Gaynor: X

Lauren Cowan: X

Varvara Kozyreva: X

Laura Carlton: X

Joan Mangan: --

Mathew Sylvester:X

Sarah Buss: X

Stephanie Johnston: --

Steven Yu: X

Gretl Glick: X

Katelyn Chen: X

Welcome & Introductions

TB LWP Updates

• Proposed CDPH LWP TRF Updates (from PPT):

  • Add Whole Genome Sequencing options  (mDST and TB Genotyping)

  • PSQ will still be available for cultures until discontinued December 2023

  • Culture-based DST available

  • AOE question updates

  • tNGS will be available for sputum sediments; other sample types will be included in test validation depending on availability of remnant material. Additional sample types may be brought on as enough material are available (phased).

  • tNGS will replace PSQ as a test option.

• TB LWP Updates: Target timeline:

  • Expected targets:

  •  Resource Availability

Notes

• Potential update to TRF:

  • TB Genotype would be opt in

  • Genotyping would not be separate option

  • TRF updates:

    • tNGS would this be applied at same time as WGS updates in lwp

    • Potential to include molecular DST

    • Varvara: Would be logical to do WGS for culture

    • Test option:

  • Interim TRF: may not be feasible by end of September

  • Long-term: Would need to develop TRF by Dec 2023 when Pyrosequencing is removed

  • SY: Zenda wanted to provide PSQ for as long as possible; Would PSQ be hard stop after December?

    • VK: Yes, PSQ would not be offered after December

    • AS: Impacts on TAT will need to be communicated to submitters for WGS

  • VK: if this can be built by November, would it be available for ordering?

  • APHL: Interim solution would not be feasible by November, potentially develop updates for long-term solution which would remove PSQ but would add WGS

  • VK: Can test orders be manually mapped in SL if not mapped? SY: if test is not mapped, can potentially manually change in SL to correct test;

    • Would need to confirm with ICC

    • Would rely on manually update

    • KC: Once test is in pre-log, team can change it to other test in panel

    • Would need to verify results syncing

  • PSQ would be available through Dec; WGS would be available in Sep

  • SY: W/o PSQ option, would not be able to automate test ordering

  • KC: Remove PSQ from NEW TRF, and would only add PSQ manually

    • ADD: Sequence based DST performed

  • VK: Test released in Sept, but tNGS not yet ready?

    • tNGS should be ready ordering/in prod by Jan 1

    • WGS: October 1: Go live in SL

    • PSQ: Dec 31

  • AG: All isolates will be WGS for DST and genotyping, in addition to phenotypic

    • Are labs selecting WGS or is it default test by submitters in October?

    • VK: Always would add wgs

    • If WGS test is default happening (even if not ordered), would need to send results for reporting

  • SY: Would this be confusing for user in LWP? To be able to order WGS, but may need to provide guidance that WGS would be done if PSQ

  • Is there ever an instance where WGS is done by the time CDPH gets isolate? Unknown

  • Alternative workflow where sent to MI (low volume) --edge case

    • CDPH would need to re-do DST genosequencing if previously conducted by submitting lab

  • WGS would be performed for both clinical or surveillance? Yes, would be performed for both

  • ICC: Can one test be mapped to 2 different workflows? Conditional logic may need to be applied in LimsConnect

  • SY:

    • Potential phases: Complete TRF and PDF results report as Phase 1; phase 2: discrete results parsing

• Additional discussions/resources availability needed to determine project schedule

  • Determine Potential reporting options for WGS results Reporting on PDF Results Report (if it is added by CDPH staff as a test when it is ingested into SL; SY: Potential risk of confusion if submitter places order, but does not have WGS available for ordering

• VK: Genotyping: Interest in capturing information

  • Potential updates to AOE [current AOEs not stored discretely in SL; stored as a blob in questions/genotyping panel]

    • Potential data completeness/quality concerns by submitters

    • May be used by submitters, but not reviewed by CDPH/cdc

  • CDC: Have other submitters been asking for this optional fields? This has been available since 2016, so would submitters enter this data? This data could be entered post test in different system, so is this needed in ETOR?

    • Labs and programs may use AOE information differently

  • Potentially include opt-out for genotyping as a way to determine workflow

    • If genotyping is required, may be directed to MI for testing

  • If CDPH does genotyping, then would submitters have option to edit data? Yes

Next Steps & Action Items

• APHL: Confirm LWP functionality with ICC

  • If test ordered in LWP, can this trigger different workflows?

  • If WGS is added manually to test panel in StarLims by CDPH lab staff, will the results sync back to the LWP (e.g. be included on the PDF results report for review by submitter)?

• APHL: Assess ICC resource availability, determine development, deployment schedule

• CDPH: Provide updated Test Requisition Form for review to APHL/ICC