Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 2 Next »

Date

Attendees

(Bolded indicates presence at meeting)

Name

Organization

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

John Spinosa

Lantana

Agenda and Notes

Topic

Notes

Reviewing minutes from the last call - Action Item Follow up

Call Schedule

send OOO via chat or email

LIDR Elements Discussion

 Not today

Review LIDR White Paper

 Going through the comments:

  • LIDR roadmap

    • #1 LIVD on FHIR collection of currently available spreadsheets

    • #2 additional data elements and tool being build by Deloitte

    • Riki will draft something here before the next call

  • Stan’s comment on Walter’s section:

    • Labname not enough to decide what the test truly is - LOINC not designed to encode all of the details of a lab test - Stan will try to find a citation

    • LOINC also not being used by developers as described in the existing guidance documents - example is Apple using LOINC longname for display in health app - Andrea will work with Walter to provide references

    • This is not a problem of just LOINC - no single terminology can resolve - use of HL7 terminology in additon to SNOMED CT; UCUM for units of measure (though some are older than UCUM - how to convince labs to use something different - not a problem LIDR can solve)

    • Need to deal with legacy data - we can improve future coding - with some effort - this is what LIDR can help address - but need to also figure out how to deal with legacy data - how to intergrate the difference in accurcy/precision of legacy data and future data - this is not solvable by LIDR - do we need to add an OUT OF SCOPE section?

  • Intro section:

    • the impetus for this sentence was just that we have been working on lab data standardization for a long time - not sure we need to add updates since then…

    • replaced “accurate industrywide adoption” with “accurate adoption across the healthcare ecosystem”

    • will add the reference to AUTO 16

    • here is just an example - not focused just on AUTO16, so will leave as is

    • added question around why pointing to IHE here, too?

    • Raja will help update the sentence to make the point of the study a bit more clear than it currently is written

  • LIDR business case section

    • use of “local code set”

      • needed for CLIA to distinguish each test within each lab’s compendium

      • standard coding can be added

      • should not be understood to NOT send the local codes along

      • need to ensure folks understand that local codes should NOT be used to understand what they mean across different organizations

ACTION ITEMS

Please see the action items at top of this page - Next deliverable is White paper draft by end of this month

Next call

Monday 3/25/2024 9 - 10 AM ET

Adjourned

10:02 AM ET

Goals

Discussion topics

Time

Item

Presenter

Notes





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.