HIBC

The Health Industry Number (HIN), Labeler Identification Code (LIC), and Universal Product Number (UPN) data systems that are monitored by the Health Industry Business Communications Council (HIBCC) can be encoded by several symbologies, in accordance with the Health Industry Bar Code (HIBC) application standard. The choice of which symbology to use is left to the labeler.

These symbologies and their implementations are as follows:

  • Code 128: When Code 128 is used, HIBC primary and secondary data should be encoded in separate symbols but may be concatenated if space allows. Code 128 is recommended over Code 39 due to its higher density and its ability to be decoded when printed sideways ("ladder" style).

  • Code 39 - Regular: When Code 39 is used, HIBC primary and secondary data should be encoded in separate symbols but may be concatenated if space allows. The Code 39 - Regular format (not Full ASCII) should be used, and the Full ASCII function in the barcode reader must be turned off. The wide-to-narrow ratio should be 3:1, the intercharacter gap should be equal to the X dimension, and the modulo 43 check character is used.

  • Aztec Code: When Aztec Code is used, all HIBC data should be encoded in a single symbol. This symbology is recommended for use in patient identification (multiple symbols can be printed side by side on patient wristbands), in drug identification, and on curved surfaces, such as intravenous (IV) bags.

  • Data Matrix ECC 200: When Data Matrix ECC 200 is used, all HIBC data should be encoded in a single symbol. This symbology is recommended for use on employee badges, in patient identification, and in drug identification.

  • MicroPDF417: When MicroPDF417 is used, all HIBC data should be encoded in a single symbol. This symbology is recommended for use on employee badges.

  • QR Code 2005: When QR Code 2005 is used, all HIBC data should be encoded in a single symbol.

When a two-dimensional (2-D) symbol is used, a single 2-D code should be used to carry all primary HIBC data. If both primary and secondary data (and optional supplemental data) are required, they should all be concatenated into a single 2-D code. The slash mark (/) is used as a concatenation character in the data stream.

The HIBC implementation of these symbology standards is defined in ANSI/HIBC 5.0 The Health Industry Bar Code (HIBC) Syntax Standard and ANSI/HIBC 2.6 The Health Industry Supplier Labeling Standard for Patient Safety and Unique Device Identification (UDI).