This page is part of the Loinc/IVD Mapping FHIR IG (v1.0.0-ballot: STU1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

LIVD Introduction

Official URL: http://hl7.org/fhir/uv/livd/ImplementationGuide/hl7.fhir.uv.livd				Version: 1.0.0-ballot
Active as of 2023-12-21				Computable Name: LoincIvdTestCodeMapping

This specification is the is the third STU ballot, which represents the updates since the second ballot (December 2020). It temporarily removes updates that were made in the 0.3.0 (December 2020) version which were intended to support the addition of Result Value mapping guidance. These updates for supporting Result Value mapping are expected to be brought back and further developed in a subsequent version. The intent is to publish LIVD STU R1 version upon completing the reconciliation for this current January 2024 ballot.

Feedback is welcome and may be submitted through the FHIR Jira tracker

Background

The objective of this implementation guide is to define an In Vitro Diagnostic (IVD) industry format to facilitate the publication and exchange of suggested LOINC codes for vendor IVD test assays, based on either vendor IVD test transmission codes or manual test identification, for use by laboratory personnel or laboratory applications. It is not intended to cover information for other related activities, such as purchasing tests from a vendor. Expected systems using the format include Laboratory Information Systems (LIS), clinical middleware applications, databases, and terminology servers.

This implementation guide defines a digital format that can be easily:

• Used as-is by IVD software systems to guide the mapping between vendor IVD test transmission codes and LOINC codes.
• Transformed into an alternate format, such as an Excel spreadsheet, to support the manual selection of LOINC codes for results produced by vendor IVD tests used by the laboratory.

Both vendor-defined IVD tests performed by a vendor IVD instrument and vendor-defined manual IVD tests are in scope.

The content uses FHIR resource profiles that can be expressed in either JSON or XML, where JSON is the minimum required format to conform to this guide. That can then in turn be expressed for a user in a table format, such as Microsoft Excel, that further simplifies its use within a laboratory setting, or consumed into the device configurator’s workbench that is part of an Laboratory Information System (LIS) or other middleware connecting devices to LIS.

By voluntarily adopting the format described here as an industry convention, IVD vendors will understand what data and in what format they should provide when publishing suggested LOINC codes for their IVD Tests. By doing so, this work will significantly reduce the variability of the content and format of the multiple publications received by laboratory environments, further reducing the time and effort required by laboratories to review and integrate this information into their laboratory software systems. The format includes additional vendor information, such as a description of the result, used to easily discriminate between multiple LOINC codes for the same IVD Test.

Ideally it is envisioned that the LOINC codes selected by manufacturers would be reviewed by a common party (e.g. Regenstrief) for correctness and consistency across vendors, and also that the industry would establish conventions for the storage and access of the IVD vendor LOINC publications. The effort required for these objectives will also be reduced by having this standard publication format and associated content.

Scope

In Scope

The initial scope of this implemnentation guide R1 is to support the IICC LIVD 2.0 specification and Excel format described here.

Out of Scope

The following topics are out of scope of this initial, first version R1:

• The mapping of IVD Test Orders, which requires additional data and alignment on a standardized coding system for orders. Although IVD Test Orders and IVD Test Results are related, information required for IVD Test Order mapping should be provided by a separate mapping table.
• The mapping of result values to LOINC answer codes and/or SNOMED.
• Any long-term or common storage locations vendors may agree upon to host the published LOINC codes or regulatory impacts of vendors providing LOINC codes for their IVD tests.
• The definition of the specific protocols or technologies that could be used to transmit the industry-defined digital content between IVD and LIS or other systems.
• Transmitting LOINC codes directly from IVD instruments, leaving that content to be represented by vendor-defined codes due to issues in achieving one-to-one appropriate LOINC codes, as discussed in the Data Definition section.
• Which LOINC codes vendors should choose for their tests, or what content is needed to make this decision. It only addresses the format used to publish these associations, for use by laboratory personnel or laboratory applications.
• What information is required to automatically set up a configuration between an IVD instrument and an IVD software system.