Attendees:

Slides:

Recording:


From Chat:

·       Riki Merrick 12:10 PM

o   Feel free to post questions here for us to discuss

·       Jim Case  to  Everyone 12:11 PM

o   I can try to answer questions in real time as they are posted

·       SZARFMAN  to  Everyone 12:15 PM

o   Hi @Stan Huff: have you also tackled the many-to-many mapping problem in LOINC?

·       Jim Case 12:15 PM

o   Ana, that is out of scope for this project

·       John Snyder (NLM) 12:31 PM

o   Has a decision been made regarding how to represent the binding strength between the answer list and the observable or is that still on the "to-do" list?

·       Jim Case 12:34 PM

o   We have talked about that, but have not made a final decision as these types of metadata are not definitional for a LOINC concept meaning

·       Cholan, Raja 12:42 PM

o   Are there artifacts from the collaboration that are posted online or available for public review? (Joined late sorry if I missed)

·       Keith.Campbell@fda.hhs.gov 12:43 PM

o   https://loincsnomed.org/

·       Jim Case  to  Everyone 12:43 PM

o   The preview browser is available at http://browser.loincsnomed.org

·       Andrea Pitkus  to  Everyone 12:44 PM

o   Sorry to be late.  Did you mention where a term meaning differs between the code systems, how those will be handled?  (i.e. blood in LOINC system covers whole blood, capillary blood, etc. such as CBC results.  SCT does not have that scope of meaning with "blood")

o   Similarly, how will XXX codes be handled?

·       Jim Case 12:45 PM

o   SNOMED and LOINC are collaborating to ensure that the part maps are semantically equivalent

·       Andrea Pitkus 12:45 PM

o   How do you plan to handle pathology terms where they are in SCT, but not LOINC?  Will content be created in LOINC?

·       Jim Case 12:45 PM

o   XXX is still on the list for final determination

·       Andrea Pitkus 12:45 PM

o   Thanks, Jim for the info!

·       Jim Case 12:46 PM

o   Andrea, the plan is to have a comprehensive set for both

·       Andrea Pitkus 12:49 PM

o   USCDI focuses on LOINC for orders and results for lab data.  For qualitative values, SCT is required

o   Regarding the question on LOINC answers.  CLIA indicates that the IVD result values are required

o   Deviations from vendor package inserts would make the test a LDT.

·       Real Time Questions:

o   LOINC answer lists have different binding strength

§  If normative list is usually because there is an outside authoritative group that publishes these – then you are not compliant with LOINC, if you are not using the corresponding LOINC answer content

o   For some programs we have normative codes that are needed for reporting – change requests ar required for any additions

o   For the required value sets the codes MUST meet the vendor package inserts – else they could be considered lab developed tests by CLIA , but several vendors are using the same LOINC code – so this will take time to align the more normative valuesets