/
2025-04-01 LIDR Meeting Notes

2025-04-01 LIDR Meeting Notes

Date

Apr 1, 2025

Attendees

Bolded names indicates attendance

 Name

Organization

 Name

Organization

Hung Luu

Children’s

Riki Merrick

Vernetzt, APHL

Andrea Pitkus

UW

Xavier Gansel

Biomerieux

Pam Banning

3M - Solventum

Amy McCormick

Epic

Dan Rutz

Epic

Rob Rae

CAP

Rob Hausam

Hausam Consulting

Sandy Jones

CDC

Stan Huff - regrets

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

Russ Ott

FDA

Akila Namasivayam

FDA

Desiree Mustaquim

CDC

Carmen Pugh

long term lab professional

Christina Gallegos

APHL

John Spinosa

Lantana

Matthew Dietz

FDA

Logistics

  • Consider connectathon for LIDR - Dan will take a look - would need to know if we have material to actually ingest, probalby won’t develop against spreadsheet, FHIR LIVD IG format might be an option, which should be published soon

  • LIDR White Paper under SC review extended until April 16th

    • OPEN ACTIONS - no update on any of these:

      • Review again for making sure it doesn’t look like LOINC is a bad standard - we don't want to perpetuate inocrrect information - it is not a LOINC issue, it is trying to highlight the issue with modeling lab tests and how folks apply LOINC @Stan Huff

      • Review Figure 6 and associated text against Figure 8 and associtated text and combine / adjust as needed @riki.merrick

      • Add in Reference to AUTO 16 and provide the mapping between LIDR entries and instance data @Russell Ott to check for his version of the mapping file

      • Review the LIVD/LIDR requirements section to ensure we have the proper vendor view @Xavier Gansel and @Ed Heierman

Integrated Knowledge Management (IKM) development

Bringing Integrated Knowledge Management to Life | Integrated Knowledge Management

LIDR pilot participation - current focus is on SNOMED CT, still adding in support for LOINC and UCUM etc

Will get update on timeline to support other code systems next week

LIDR Googlesheet Potassium LIVD data

Blue column headers = LIVD file columns

Yellow column headers = additional meta data

Pink column header = codified information derived from LIVD columns

Reviewing the colored cells:

  • orange - some follow up needed - for rows 18/19 - only difference is method description in Vendor Analyte Name column and Vendor Analyte Code (marked yellow - why is 987 in both rows?) - using the same methodless LOINC

  • Timed urine as samples:

    • for 24 hr urine also include AOE for collection duration (need to add in LOINC info)

    • Collection Volume is determined by the lab, should be included, since needed for calculation

      • If IFU includes description of urine volume, why shouldn't vendors also include that information in their LIVD files?

    • Do we include XXX time LOINCs?

      • Many labs set this up to be more flexible, but then must include the “result” of the actual time - add column for “Implementation Notes”

      • Should we look at the most common timed urines and maybe include?

    • Check out Biomerieux LIVD file - any potassium tests?

    • Need to expand to some organism tests to see, if we can find patterns there that require additional columns

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”

      • Will look for a CLSI defintion

      • also check IFCC definition

Next call

Monday 4/15/2025 9:05 - 9:55 AM ET

Adjourned

9:54 AM ET

Chat

Action items

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.

 

Add label

Related content