2025-01-06 LIDR Meeting Notes

Hung Luu

Children’s

Riki Merrick

Vernetzt, APHL

Andrea Pitkus

UW

Pam Banning

3M - Solventum

Xavier Gansel

Biomerieux

Amy McCormick

Epic

Dan Rutz

Epic

Rob Rae

CAP

Rob Hausam

Hausam Consulting

Sandy Jones

CDC

Stan Huff

Graphite

Ed Heierman

Abbott / IICC

Andrew Quinn

Laurent Lardin

Biomerieux

Anthony Killeen

UMN

Craig Collom

Marti Velezis

 Sonrisa / FDA

Walter Sujansky

FDA

Susan Downer

JMC

Ralf Herzog

Roche

Cornelia Felder

Roche

Daniel Golson

JMC

Andrea Prada

JMC

Maria Sagat

CAP

Raja Cholan

FDA

Russ Ott

FDA

Akila Namasivayam

FDA

Desiree Mustaquim

CDC

Carmen Pugh

CDC

Christina Gallegos

APHL

John Spinosa

Lantana

Matthew Dietz

FDA

Logistics

• New call time?

  • Hung will send out doodle poll

• Consider connectathon for LIDR - Dan will take a look

Reviewing the comments on the LIDR White Paper = LIDR White Paper

Discussion:

• Historically, this has been sufficient when laboratory results have been primarily utilized within the context of a single health system and the laboratory(ies) to which they are contracted for testing. However, as laboratory data are exchanged more outside of these settings, context and meaning may be lost or not known by others

• Many LOINC codes, specifically those with nominal scale, e.g. for microbiology culture reporting, use a more general component compared to those where the LOINC component identifies the exact analyte tested.

Open To Dos:

• Update reference style to use the numbers with reference Section (Riki has that prepped)

• Still need to check for best place to talk about CLSI AUTO-16/IHE LAW (question: has anyone implemented in the US in production?)

Next Steps AFTER SC approval:

• Work with Communications WG to socialize / get the word out / journal article?

• Review where all LIDR elements are in the HL7 data exchange standards

  • example: screening or confirmation

    • not currenlty as an independent field, most commonly in the local test name

    • would the indication that this is the screen or confirmatory test come in with the order (this is not always the methodology, it often is the clinical context)

  • May be good to go through a few examples and identify all the elements that are not currently covered in data exchange standards / require changes in LIS set ups

  • Sometimes labs have to forward tests to other labs based on insurance or other rules

  • make sure any proposed new elements provide additional value for the labs (get the labs to understand why / how this will make the domain better)

Review examples of merged cell LIVD file entries

https://aphlinformatics.atlassian.net/wiki/download/attachments/1938718763/Copy-HIV-Diagnostic-LOINC-Map_v5.xlsx?api=v2

essentially the repeating cells were merged for readability, they all would be separate LIVD file entries with the same UDI

Reviewing minutes from the last call - Action Item Follow up

• Pull out the definitions from LIVD for test kit and equipment and put here: SHIELD Glossary

  • Review operational definition of “equivalence”

• Outreach to Dr. DeBaca

  • Hung will check for more info and maybe see, if she could participate in SHIELD

• Keep updating the googlesheet: Potassium LIVD data

• Shared Reportable Conditions LIVD google sheet for crowdsourcing with CSTE - added sign up sheet for PHAs to specific conditions and see how that develops

• Have LIVD File Repository Requirements

  Have draft budget (for setting up a web-based database and yearly maintenance): https://aphlinformatics.atlassian.net/wiki/download/attachments/915407143/LIDR - Budget.xlsx?api=v2

• Define next steps to migrate existing LIVD files into FHIR LIVD catalog format and find a FHIR server to host

• Marti can share the LIDR categorical data to instance data mapping for each element - DATE?

Next call

Monday 1/13/2025 9:05 - 9:55 AM ET

Adjourned

9:55 AM ET