2025-01-13 LIDR Meeting Notes
Date
Jan 13, 2025
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 |
Carmen Pugh | CDC |
Christina Gallegos | APHL |
John Spinosa | Lantana |
Matthew Dietz | FDA |
Victoria Derbyshire | FDA |
Topic | Notes |
| Reviewing the comments on the LIDR White Paper = LIDR White Paper Discussion: 2 new additions under problem #3 Open To Dos:
|
Review examples of merged cell LIVD file entries | essentially the repeating cells were merged for readability, they all would be separate LIVD file entries with the same UDI - think of the excel as a viewing tool (but currently also it needs to be the source of truth) if you had LOINCs specific to Ser, that would be a separate LIDR entry, LOINC for Ser or Pl are mapped to acellular blood SCT (can/should add SCT for that) From LIDR perspective, every difference in a column produces a different LIDR entry (though not all of those would result in different mappings) not all elements in LIDR will be needed for mapping (and some should probably be usable to exclude from mapping for labs (entries that are speicifc ONLY for at-home tests for example) HIV file has 4 extra columns more that LIVD spec - those were requested by the CDC Epi folks:
For the SARS-COV-2 file APHL also has a file with additional columns, that CDC ReportStream is using for their data analysis / conversion to HL7 ELR from csv file - a few examples:
For the Reportable Conditions LIVD google sheet for crowdsourcing file we added some columns that would translate what is currently in the LIVD file to more detialed representations - example: Vendor Comments → Clinical Context needed for mapping; USe case Glucose Challenge testing the vendor provided LIVD file would indicate that the test can be used for Challenge testing, while in LIDR we would create separate entries with the respective proper CLinical Context for the different protocols that are available:
|
Reviewing minutes from the last call - Action Item Follow up |
|
Next call | ???? |
Adjourned | 9: AM ET |
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.