Date

Oct 25, 2023

Attendees


  • Nick Decker

  • Yue Jin

  • Marti Velezis

  • Rob Rae

  • Hubert Vesper

  • Xavier Gansel

Goals


  • Discuss objectives of this IVD Data Hub team for remainder of 2023 and 2024

  • Review, finalize proposed white paper outline

Discussion topics

Time

Item

Presenter

Notes


Update on discussion with K.Campbell

Nick

  • Discussed feedback from K.Campbell on IVD Data Hub considerations. FDA SHIELD Program is heavily focused on data quality as a foundational element which will enable other uses of collected data

  • Team discussed at length “Cart before the horse” thought of IVD Data Hub: agreed that the requirements for an IVD Data Hub must be considered in the development of Knowledge Mgmt tools (e.g. LIDR, etc). White Paper outline was updated accordingly. See below


White Paper Next Steps

All

Intro (what is SHIELD, how did we get here)
<Use intro from Community Roadmap executive summary)

IVD Data Hub Vision (What is it? why does it matter? why now?) (Nick & Hubert)

  • Research other repositories (e.g. Cancer Registries)

  • Highlight efforts ex-US (e.g. UK, Israel, EHDS, …)


Envisioned baseline requirements (Xavier & Marti)

  • improved data quality from knowledge mgmt tools (e.g. delivery of LIDR, etc)

  • Robust / appropriate standardization for things like UDI format for transmission from Mfg Instrument to LIS

  • Additional standards, solutions needed from HL7

  • Others…

Envisioned use cases for IVD Data Hub (Expanded upon by those who offered the proposals)

  • Broaden description beyond EUA transitions (Gyan)

  • Instrumentation and Ancillaries (Gyan)

  • Public Health Reporting (Rob)

  • Research & Innovation

  • infrastructure

Dependencies (Yue & Rob) → Xavier / Marti will provide input based on requirements

Action items


Nick will distribute minutes
Sub-teams (as assigned) will move into research between now and end of 2023. Drafting to start in 2024


Quick decisions not requiring context or tracking

For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.



Decisions requiring context or tracking

For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.

Create from Template