Instrument Manager uses mapping as a mechanism for translating information between the LIS and instruments. This mapping can apply to four types of data elements: fluid codes, test codes, error codes, and/or instrument IDs. Not every driver supports all four data elements, but test code mapping is typically supported. Here are some tips to help with mapping questions:

• To access mapping, find the name of the configuration you want to review and access it by selecting Configuration from the menu and selecting Configuration Editor on the configuration editor window. Select the configuration you wish to review and then select Properties. This will show you what mapping events are available for this specific driver.
• Test codes are an identifier or name for a test. Test code mapping is the process of associating instrument test codes with LIS test codes.
• Fluid codes refer to the specimen type (for example, Plasma, Serum, or Urine). Fluid code mapping is the process of associating instrument fluid codes with LIS fluid codes.
  • Not all instruments require fluid code mapping, but if available and part of your process, complete this mapping first. If fluid code mapping has not been completed for a specific test code, that test code mapping will not occur.
  • Instruments with fluid code mapping may or may not come with default mapping. Default mapping means that if the LIS fluid code is not correctly mapped or missing from the fluid code mapping, the driver will default to a particular fluid code for the rest of the mapping.
• IM Test Codes and Instrument Test Codes typically display as a one-to-one mapping when the instrument driver includes pre-defined test codes. For example, if an instrument test code is 300 and the driver has default test code mappings present, you will see IM Test Code 300 mapped to Instrument Test Code 300.
  • If 300 is not a code that your LIS would send for this specific orderable, you will need to map a different IM Test Code to the Instrument Test Code.
  • It is possible to have more than one LIS code mapped to the same instrument orderable code.
• Here is an example of why you might need to review your mappings:

The image below shows that the LIS has ordered test code LISSentTest. Instrument Manager reads that and determines from the mapping (shown in the upper right of the graphic) that IM Test Code LISSentTest is mapped to Instrument Test Code TEST. The instrument runs the test and sends the result TEST-R. The example originally had TEST-R mapped to TEST-R which the LIS does not recognize. By changing the mapping so that the Instrument test code TEST-R is mapped to the IM test code LISSentTest, a translation can occur so that the result is sent to the LIS in a way that the LIS will accept it.

For more information on mapping, please see the Getting Started User Guide chapter 6 titled “Mapping,” or contact the DI Support for your region.