LOINC - IVD Test Code (LIVD) Mapping

Laboratories are challenged to accurately and consistently map local and LOINC testing codes to the corresponding IVD test/analyte codes used in the various IVD devices. Due to widely varying requirements and capabilities, IVD devices can be configured in many different ways and use code systems unique to their capabilities. However, upon transmitting the results from the device to the LIS and onwards, these IVD test/analyte codes need to be translated to the appropriate LOINC codes. Ultimately that is the laboratory’s responsibility.

Establishing accurate mappings requires skill and experience to understand when to use a particular LOINC code. To date, laboratories have no specific guidance and need to rely mostly on institutional expertise.

The industry is interested in having device manufacturers provide suggested/recommended mappings that laboratories can use as a starting point, thereby substantially reducing effort and increasing consistency across the industry where those devices are used. Ultimately, final mappings remain the responsibility of the laboratories to accommodate local variations.

To communicate these mappings, IICC has endeavored to define a minimum data set and parameters that need to be provided and has agreed to an initial format using JSON. While that provides a machine-readable format that enables parties to consistently exchange and interpret, this format is not using the FHIR resources to define that format. The introduction of FHIR would maintain the consistency as desired of the mapping definitions itself. Also, it would provide an initial stepping stone to introduce FHIR into the full loop of laboratory test ordering and result reporting where next steps can be built on common definitions, as well as deploy a format that is starting to be widely adopted in the industry.