Attendees
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 |
Christina Gallegos | APHL |
John Spinosa | Lantana |
Agenda and Notes
...
Topic
...
Notes
...
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 for June 3, 2024
...
Call Schedule
...
send OOO via chat or email
...
LIDR White Paper Review
...
Reviewing the comments on the LIDR White Paper = LIDR White Paper
Discussing the corect LOINC assignment section:
goal here is to say be as specific as need be - Serum/Plasma would be the most commonly used LOINC system here, though for the lab they will validate and set up either Serum or Plasma, but the test would have the same LOINC, since there are very few LOINCs that are only for Serum or only for Plasma
XXX LOINCs may be used when the lab sets these tests up in their system, even if they mostly test on serum, but can test other sample types - in this case the expectation is that they will send the sampletype in the data exchange - this is outside of LIDR
Updated the sentence
Stan’s comment mentions order codes:
are order codes in scope?
Stan was meaning the code that the provider is expecting as the performed test - the one that would include the clinical context - in the example we discussed 24 urine (which is how this test will be set up in the lab’s compendium) - which for the instrument is just urine
EHR-s to LIS order - 24 hr urine creatinine
LIS to instrument - vendor code for urine creatinine (may or may not use spot urine LOINC)
had discussion about use of LOINCs for orders - using LOINC only as order codes will not work, as they are often not specific enough as to the components of a panel
Ordering from the instrument will need to use the analyte code provided by the vendor, might get assigned a LOINC, but MUST be the vendor code
vendor codes may also be used to report the performed test
LIVD is for instrument to LIS, but if we want LIDR to support communications to/from EHR-s and LIS, then we may have to include a mapping to additional LOINCs that woudl not be provided by the manufacturers - that is the point Walter is trying to make here
Start back up here next week
...
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 7/22/2024 9 - 10 AM ET
...
Adjourned
...
Cancelled due to lack of quorum.