2024-03-07 Meeting notes
Date
Mar 7, 2024
Attendees
Xavier Gansel
Marti James
Hubert W Vesper
Gyan Penrose-Kafka
Rebecca McNall
Yue Jin
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
| Review the slide deck for All SHIELD call update | Yue/Everyone |
|
Review recommended update to SHIELD Roadmap per ONC feedback on IVD Data Hub | Yue | The WG will review and add comments offline |
Action items
The IVD and Clinical Information System (CIS) industries strive to meet the needs of customers and promote the healthcare of the population through the provision of safe and effective products. Addressing the barriers to laboratory interoperability such as lack of standardization by enabling semantic harmonization and standardization will have a profoundly will have a significant positive impact on clinical laboratory operations, as it will significantly reduce the time and cost involved with deploying, connecting, and updating instruments in the laboratory. Such standardization will reduce the need for vendor-customized connectivity implementations and serve as a catalyst and common incentive for stakeholders across the ecosystem to promote interoperability of laboratory data. As such, SHIELD endeavors to promote the use of high-quality data for secondary use purposes. One practical use case would be the establishment of a tool or data system that serves as an IVD Data Hub to facilitate the use of RWD for the purposes of supporting regulatory decision making, improving public health reporting, and development of future innovation. This will eliminate the need for vendor-customized connectivity implementations and favor vendors that adopt the specifications and pass the savings on to their customers. The creation of an IVD data hub provides an incentive for the IVD industry by providing a pathway for using RWE to support regulatory decision making.
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.