Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Topic

Notes

Call Schedule

send OOO via chat or email

 LIDR White Paper Review

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

Discussion:

Added Title

replaced “class” of LOINCs with set of LOINCs

talked about the EBV study - cited was done on LDTs, while follow up done on FDA approved tests found less variations, decided to keep older reference in, but adjust sentence to include the newer study - talked about the fact that since we know of the vairation most organizations have policy to not merge results form different labs

Update figure 6 to differentiate between kind (LIDR) and instnadce data going from labs to all its users = add box for LIS/LIMS in Clinical Laboratory boc and make different style arrows out of that to EHR-s and make research and PH systems instead of organizations

add a bi-directional arrow between LDIR and Trusted Certification body to allow updates to LIDR based on lab LOINC coding observed during certification, that is deemed allowable - example would be timed tests that may not be in the manufacturer provided LIDR input

Open To Dos:

  • Update reference style to use the numbers with reference Section (Riki has that prepped)

  • Reviewed comments on introduction - Still need to check for best place to talk about CLSI AUTO-16/IHE LAW (question: has anyone implemented in the US in production?)

  • Andrea to write up her sentences as per comments

GOAL: Get to SC for their 12/3 call!!!

Review examples of merged cell LIVD file entries

https://aphlinformatics.atlassian.net/wiki/download/attachments/1938718763/Copy-HIV-Diagnostic-LOINC-Map_v5.xlsx?api=v2

essentially the repeating cells were merged for readability, they all would be separate LIVD file entries with the same UDI

Reviewing minutes from the last call - Action Item Follow up

ACTION ITEMS

Next call

Monday 12/02/2024 9:05 - 9:55 AM ET

Adjourned

9:?? 53 AM ET

Action items

  •  

Quick decisions not requiring context or tracking

...