Page Comparison

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

• Review LIDR Use Cases and sign up to lead one of these - prioritize these use cases, so that we can finalize the requirements for the first phase of LIDR

• 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?

Call Schedule

send OOO via chat or email

 LIDR White Paper Review

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

Reference range when it is dependent on specific characteristic to establish the reference range for each patient - each lab determines that for its population, so LIDR may only be able to indicate the items the reference range depends on - so this might be problematic on how to put this in LIDR right now - s so say outside of MVP and put into parking lot

PARKING LOT: for data exchange need to review how reference ranges are/shoudl should be reported -

Describing anticipated workflow - would be nice to have a diagram of how new codes are getting into LIDR / LIVD.

maybe include differnet different paths - new code needed (TINKAR is working on creating temporary code - those should not be called LOINC codes - we need to align this process with what we are doing) - once package insert content is available, who will extract the data

would be good to have the code creation be handled by the manufacturer

mPox is having new tests coming to market, but if there is time delay, how would all information be available to create codes during the EUA process - RIki to make drawing, Stan to convert to digial digital version

Regenstrief commited to make codes within days (max length is 2 weeks), so we should make that part of the process

Discouraged codes - strike the sentence to that; we may need ot work with Regenstrief when we see discouraged codes to have reasoning is to why

Requirement is software alerts for human to take action

Versioning - track each change - in LIVD file we have publication dates and the change log

need to track for each map which version of LOINC it came from

how do we know when LIDR has a new version

Currently the CDC LIVD files are published every 2 weeks, when changes are there

each entry in LIDR will have the metadata

should LIDR allow subscriptions to updates - maybe use CDX hooks - topic = manufacturer name or analyte

Request need to support query for new content since date 'X'

Add a paragraph that describes the difference between LIVD and LIDR and describe the ideal set up in the future - RIki to write and propose place in the white paper to put that

Pick up at Requirement #10

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 8/12/2024 9:05 - 9:55 AM ET

Adjourned

AM ET