Versions Compared

Key

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

Date

...

Item

Notes

Quorum evaluation (two-thirds (2/3) of the Voting Representatives shall be necessary to constitute a quorum for the transaction of business)

Currently we have 19 named members, so 2/3 = 12 (excluding chair and government members).

 

Open Meeting

 12:09 PM ET - no quorum

Collaborative Community Panel Presentation

Request to participate in Panel on December 17, 2024 3:50 - 4:20 PM ET - these would be the questions; Riki would attend, Andrea would join if she can.

  • Question 1: Please briefly refresh the audience regarding the vision, objectives, key participants, and scope of activities in your Collaborative Community, including highlights of recent and ongoing activities and upcoming milestones or events. [3-5 minutes]

  • Question 2: What have been the biggest challenges or barriers to achieving standardized methodology and data structures (interoperability) across variety of data-generating devices, lab tests, and organizations?

  • Question 3 [back-up, time-permitting]: How has your CC sought to balance the competing needs for both innovation & standardization?

Conferences

ASCLS got submitted - waiting for response

ADLM got submitted - waiting for response

Review Working Groups progress

Setting milestones for deliverables should be NEXT for WGs: they will be captured here: SHIELD WG Deliverables and Milestone Grid

Lab LOINC Committee question

Question: Should LOINC support IFCC methods (as part of harmonization of tests) or should this be covered by the yet to created harmonization indicator?

only 2 LOINCs with IFCC as method: Hemoglobin A1C, https://loinc.org/91671-8

Could have a result with IFCC method and without.

Over 100 tests that are aligend with IFCC method - should more LOINCs be created?

Compinatorial explosion is not good, but we don’t currenlty have HL7 place for the harmonization indicator, but if we can create specific method codes that could cover that and we have had OBX-17 for a long time (some LIS/EHR-s may not support that field yet)

SNOMED CT collaboration on LOINC parts modeling around methods

Sometimes method is in the lab testname, but even then the LOINC chosen may be a methodless code (on the lab side, but also on the EHR-s side)

Method axis in LOINC supports multiple - example would be toxicology testing - SAMSHA drug testing requires different methods based on screening / confirmatory test type / cut-off based / detection limit

Sequoia IG Update - still working on addressing comments - suring a call a newer clinician participating also requested this harmonization indicator to help idetify results that can be merged

Administrative things

Review SC Composition, terms and requirements for re-voting:

  • Representative first 3 year terms expire 12/20/2025

  • Chair and Vice Chair 2 year terms expire 3/14/2025

    • 90 days would be 12/14/2024 for call for nominations for Chair and Vice-Chair, so folks, start thinking about who might want to take the reins (smile)

    • email Andrea and Riki with any nominations

  • Steering Committee attendance review:

  • Consider changing timeslot - what are some options?

Roadmap section updates in response to ONC comments on the SHIELD roadmap

  1. The roadmap mission section describes a broad vision of lab interoperability. However, the roadmap proposed solution is limited to the FDA use cases around In-vitro diagnostics (IVD) data, specifically populating the IVD data hub.  ONC suggests clearly describing the roadmap scope so the proposed solutions can be discussed within that context.

Updated language draft:Roadmap update: ONC Feedback

maybe add one more sentence or add a reference to the key consideration number for the IVD Datahub (Consideration 4) into these sentences. (change approved in principle.)

Discussion:

  • Updated roadmap:

    View file
    nameDRAFT_SHIELD_Community Roadmap_11_4_2024_Latest_Version.docx

  • Also need to remove the duplicate words “for the” in the last sentence

  • Anything else needed on this one?

  1. The roadmap identifies training and education needs around using LOINC as a barrier to interoperability. ONC suggests clarifying how the roadmap addresses this barrier. ONC recognizes that terminologies require training and education, and replacing LOINC with another standard will not address the barrier.

Update from Standards and Vocab WG about re-write of this section - from their March 18th call (notes here, recording here)

  1. Concepts around Healthcare IT (HIT) standards needs to be conveyed earlier in training for healthcare providers as use and application of standards in vended applications is the major gap.

  2. Decision making to use Health IT standards are less likely left up to IT analysts as they mainly follow the requirements and then they generally use vendor supplied implementation guidance. However, a vendor may not support functionality for standards or only partially support.

  3. Regulatory requirements (such as CLIA) may pose a hurdle to implementation of data standards.

  4. Implementation guidance is often not well read. Training resources may not be well publicized or readily available. Perhaps conformance testing tools need to be made more widely available?

  5. What might be helpful is to look at standards implementation from a data lifecycle standpoint across all users (end to end across ecosystem), rather than just training on a single standard for a single use case.

  6. Last paragraph on page 4 of the road map final version could be augmented with these points.

Discussion:

  • Need to find the exact space for these points, too

  1. There are several solutions proposed, including repositories and tools, which need to be further evaluated before ONC could fully support the roadmap.  ONC suggests the roadmap be updated to include details around feasibility, scalability and how the proposed changes can be integrated into the current laboratory ecosystem (e.g., regulation and industry).

Identify components that could improve the ecosystem infrastructure, and then highlight the places where these components can be advanced / sustained or made easier to implement. Would SHIELD be willing to consider to provide an example implementation - create the structures and bound terminologies to showcase how each element would be properly represented be working.

For each of the Consideration sections we could certainly add a section on feasibility / requirements (e.g. continued funding for LIDR, better describing the intended use of ANY data element added, overall goal of LIDR, clearly delineate what is commonly used and is minimum, provide best practice and alternatives (non-preferred) - example would be metadata around the value sets in VSAC (curation / usage etc) to be able to ascertain quality) and highlight that other mechanisms are needed to achieve for adoption.

ONC Annual Meeting

December 4-5, 2024
Omni Shoreham in
Washington, DC

https://www.astpannualmeeting.com/Agenda

This is in-person only, registration is open now - last year it filed up

no plans so far to have slides / recording available

December 5th 2:15 – 3:15 pm is Enhancing Laboratory Interoperability: Insights and a Path Forward - Sara can give update on January 14th call to SHIELD members

Also the report to congress wil be public one sent off

Antimicrobial result reporting

Placeholder to get back to later

Related work at HL7 Europe:

View file
nameEU coded value sets.xlsx

Next calls

All SHIELD Calls

  • November 26th

  • December 17th

General Updates: 2024 - WG Chairs please make sure we have material for updates (at least notes we can link to)

Special Topic:

  • December 10th - Clinical Architecture LOINC survey

  • January 14th - Update from ONC’s Annual Meeting / Enhancing Laboratory Interoperability: Insights and a Path Forward Panel

Steering Committee:

  • December 3rd

  • January 7th

Adjourned

 12 11: PM 54 AM ET

From Chat:

  • Jim Case 12:10 PM
    Yes, doodle poll is good for new time

    Andrea Pitkus 12:18 PM
    Would it be FHIR based or could HL7 support a non FHIR based solution?
    Nick Decker (Roche) 12:20 PM
    Truveta

    Nick Decker (Roche) to Everyone 12:20 PM
    https://www.truveta.com/truveta-data/regulatory-grade/

    Andrea Pitkus 12:21 PM
    They advertise supporting newborn screening panels ;)
    Julia Skapik 12:22 PM
    I'm still willing to help with standards and vocabulary but I can think of a couple of other folks who might be willing to help

    Eric Crugnale 12:23 PM
    SHIELD Membership Survey (https://airtable.com/appOlWUgNBTLteZAC/shrRB3rxwuF4ZAOLS)

    Nick Decker (Roche) 12:34 PM
    I need to run to this call with Truveta - thanks all

    Andrea Pitkus 12:51 PM
    IS this the detection limit LOINC, Riki? https://loinc.org/101128-7

...