LOINC – IVD Test Code (LIVD) Mapping, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/livd/ and changes regularly. See the Directory of published versions

LIVD Concepts

The basic structure that the LIVD Publication must support is based on the Digital Format for Publication of LOINC to Vendor IVD Test Results as published by IICC - IVD Industry Connectivity Consortium. It can be represented as follows:

The implementation guide supports the following mappings:

IVD Test Performed

• A publication is typically for one vendor's devices, but it is possible to combine information from multiple vendors into an aggregate publication.
• One IVD Test Performed to zero or many LOINCs
• Depending on the context of the result, specimen, or other qualification, the same IVD Test Performed can be mapped to different suggested LOINC codes as also shown in the example in Section 2.1 [general-summary.html#example-1-%E2%80%93-glucose] and 2.2 [general-summary.html#example-2-total-protein-csf-urine] . An example may be that an IVD Test Performed for serum glucose could map to one LOINC code considering a mass concentration (e.g. mg/dL) or another LOINC considering a substance concentration (e.g. mol/L). Or, a urine albumin could map to one LOINC code for a 24 hour excretion rate with units of mg/(24.h), versus another LOINC code for a random urine with unit of md/dL.
• It is also possible that a LOINC code is not yet known or available at the time of the LIVD Publication, thus it is possible to not indicate any mapping.
• One LOINC to zero or many vendor IVD Test Performed
• Having a LOINC code mapped to by multiple IVD Test Performed for a given device is less likely, but having the same LOINC code referenced by difference IVD Test Performed for different Vendor Equipment, certainly by different vendors, is very common.
• For example, an IVD instrument may distinguish stat tests from routine tests by the IVD Test Performed's vendor analyte code. In this case, the LOINC [13969-1] Creatine kinase.MB [Mass/volume] in Serum or Plasma is associated with two IVD Test Performed, depending if the test is routine or stat (prioritized).
• Or, consider a susceptibility test that has different IVD Test Performed IDs based on the original specimen source. In this case, the LOINC [6932-8] Penicillin [Susceptibility] by Minimum inhibitory concentration (MIC), which is named for testing on the isolate, could be associated with multiple IVD Test Performed for one IVD Instrument depending on the clinical context. For example, the break points are different for suspected meningitis versus blood infections and to date LOINC has only distinguished test codes by suspected source of infection for some antibiotic susceptibility codes.
• The IVD Test Map enable these many to many mappings, also considering that there may not be a suggested LOINC code for a particular IVD Test Performed, or clearly that not every LOINC code is related to an IVD Test Performed.

IVD Coded Result Values

• One vendor IVD Test Performed to zero or many IVD Coded Result Values.
• When an IVD Test Performed represents a non-quantititative test, then there would be one or more coded result values that are used to result on the test.
• One IVD Coded Result Value to zero or many LOINC or SNOMED codes
• The IVD Coded Result Value may have a corresponding LOINC and/or SNOMED code.
• While the IVD Coded Result Value could be represented in LOINC and SNOMED, the intent is not that a particular configuration mixes both coding approaches for the specific IVD Test's IVD Coded Result Values. Rather it should use one encoding or the other. The LIVD Publication allows for documenting both to enable the LIS to make that choice.