Barcode encyclopedia : Symbology hibc
Health Industry Bar Code
Basic information about HIBC as Health care code ....
Barcode in Health Care
- Developed in year 1984 in USA as a solution for world product tracking. In Europe uses 1987...
- Developed from Code39, coding numeric and alphanumeric data, but for some problems was developed HIBC...
- HIBC as a data structure is still valid without any change still offering the features of capatibility,safety, compactness.
- used in medical devices, pharmaceutical products...
- from year 1987
- compressed data structure, unique data structure
- Symbology independent ...
- Capable for users product alpha numeric codes up to 13 characters.
- Maintained by EHIBCC Technical Committee and its industries memebers
- Used in several market segments, Health Care, Precision Machanics&Optical Industries,Chemical Industry,Electronic Industry, .... etc...
- variable lenght, alphanumeric
- Not discrete, no space between cahrs....
- Optimization is offered by HIBC only by data compression which is a condensed representation of the data.
- HIBC is best system for product marking, in the reason, the HIBC is the best system for unique product marking.
- 2 dimensional barcodes can be used for small or smallest labels ...
- error free, correct and safe
- marked products is identified quickly and clearly anytime and anywhere.
- Barcode meets all marking requirements resulting from legal regulations in the health sector,including expiry dates.Finally, in using this barcode it is possible to integrate using serial number in the product marking.
- correct and error free data recording
- direct communication between electronic unit and medium...
- real time reaction
- batch steering
- steering of transport units
- control of expiry dates
- easy control of incoming and outgouing materials
- steering of return shipments
- alpha-numeric structure
- different part number system can be accomodated
- computer based connection of primary and secondary code
- optimal use of space because of different code designs
- international explicitness
Distribution and tradeAutomatic indentifiocation of :
- packaging unit
- handling unit consisting of different, sometimes individually marked products
- dispatch unit
- In future: sense for the dental dealers which have guaraantee trouble-free order processing.
- for dental dealers: start examining the possible symbologies and data structure or the barcode early.
HIBC, also offers valuable support in buildingup a quality management system. Since dental dealers are becoming more interested in systematic qualitymanagenent systems, the corresponding goals wll be easier to reach with an automatic marking system.
Main goals are:
- Increasing the reliability of deliveries
- reducingtransport and delivery times
- eliminating mistakes
- high transparency of current status of goods
- fast processing of complaints
HIBC Technical partThe Technical part of the HIBC is targetting to the HIBC Data Structure for product marking. It contains variable selection criteria for symbologies. IMHO very good.
- Data strucure is developed for product marking
- contain variable selection criteria for symbologies
- Contains also "Multi Industry Trasport Label"
- most flexible, compatible and secure
- compacr data structure,combining Product code with Manufacturer identification,Charge/Serial refference, Expiration date, ....
- defines "primary code" and "secondary code".Primary code contain LIC (Labeler Identification Code) and the product code. Secondary part contain data as Serial number, Expiration date ...
- HIBC data structure is symnbology independend. Recommended for full capacity, spacea and safety.
- Developed on code39, but for better numeric compression is used Code128, because Code 128 compress two digits into one symbol. Chars no, for digital code is Code128 better...
- if you have some troubles with capacity, you can use CodablockF, small packagesa without problems.
|ID Mark for HIBC Standard||The plus sign "+"|
|Labeler/location identification code||4 digit, a/n, issued by EHIBCC|
|Product/Article code||variable 1 to 13 digit , a/n, issued by the supplier|
|Unit of measure||1 digit numeric|
|Quantity||optional 2 or 5 numeric|
|Expiration date||YYMM, .... etc.|
|Charge/Serial number||variable 0 to 13 digit|
|Check digit||1 digit modlulo 43|
|Link character||1 digit modulo 43 for conecting connecting primary and secondary code properly|
|Data concatenation||COBABLOCK structure to concatenate separated barcode rows for space optimization reasons.|
The HIBC standard recognizes the integration of UCC/EAN product codes.
HIBC barcode in detailHIBC = primary segment and secondary segment. Allways primary segment begin with sign "+". This is recognized identifier for this baqcode type.
HIBC Primary data structure
- labeler of the ihem
- the item
- packanging number
|+||HIBC Supplier Labeling Flag Character|
|I||Labeler Identification Code (LIC) is alphanumeric and the first character is allways the alphabetic character.|
|P||Labelers Product of Catalog Numberaplhabetic data.|
|U||Unit of Measure ID 0 though 9, where 0 is for unit-of-use-items, 1 to 8 are used to inidicate different packages levels...above the unit-of-use|
9 is used for variable quantity informtation is encoded optiobnlally with the secondary symbol.
|L||Check and link character L. Applies only if secondary data segment is encoded in a separate symbol. Calculated from the above characters according the standard Code39 modulo 43 check digit calculation.|
HIBC Secondary data structure
The secondary code might be printed separately of the primary data Can be connected with character "L" or one barcode following in the primary segment.
The secondary data segment is variable and flexible, allowing recognition of manufacturers codification mechanismsl.
|Field Descriptor||Field legth||Filed descripion|
|+||1||HIBC Supplier labelng flag character"+" is applied, if the secondary data segment is printed with a separate barcode, but not is use primary and secondary barcode is contatenated as one.|
|R||1,2 or 5||Quality/Date/Refernce identifier|
Of the character in the secondary segment is "R", than R is fixed digit Julian date. No Quantiy/Lot/Batch/Serial is no present.
"$" : if the irst character is "$" and the second character is alphanumeric, than the quantity and date fields are not used.
"$$" : If the two characters are "$$" then the next digit specifies quantity and date format
|Q||0,3 or 6||Quantity field format indicator followed by two or five digit quantity.Use after the "$$"|
|D||0 or 5-9||Date fields, for use after the "$$", (includes data format field identificaor0|
|B||0-13||Charge/Serisl (Batch) number field|
Duplication of the last character from primary data element.Primary data elements "L" apply only if the secondary data element is printed as a separate barcode symbol. "L" is does not appear, if the Primary and Secondary fields are printed as one barcode symbol.
Calculated from above characters according the standard Code39 Modulo 43 check digit calculation. The check calculations includes the primary data segment, if encoded with the same symbolas one barcode as linear or 2D barcode.
Complete barcode and separated into parts : +E234MEDIX12Y0/9901510X3C
|HIBCsupplier labeling Flag character "+"||Labeler identification code||Product of Catalog Number||Units of measure||Separator between Primary and Secondary field||Date, option Julian calendar 5 digits YYJJJJ||Charge/Serial number||Check chraracter|
For large sized barcodes is used 2D code CodablockF.
Barcode symbologiesThe HIBC data structure is build to be symbology independent to by carried by a selection of barcodes.
Suitable are alphanumeric symbologies :Code 39, Code128, Ean 13, Ean 128, stacked barcode CodablockF, 2D barcode Matrix.
- Code 128 : all ASCII characters, if three or more digits is in one section, compression is starting. Two digits is coded as one symbol, compression 2:1.
If code is large, better is use 2D or stacked barcode.
- Code 39 : encoded only first 43 characters from alphabet, numeric and some special chars as $,+,/,...
Barcode width is not very good, Code128 is better, because use full ASCII table, use digital compression ...
- CodablockF is stacked symbology, use Code 128 in more rows to save space. One long Code128 is parsed to two or more smaller codes printed in one row, each parsed barcode have your own row number, check digit and is printed first under second, etc...
Standard scanners read it easy, reading no problem, because scanner complete barcode after reading and from row number complete this code to good sequention.
- Ean 13, UPC, ... is used in consumer products. Can contain two or five adiitional digits, used in periodical, books, music, ...
- Matrix code is pixel oriented 2D barcode, more data to small place :-)
- If used Code 39, is used checksum modulo 43. There is bad reading cca. 1:500.000
- By using Code 128 or CodablockF (this is 2 D version of Code128) , problem is smaller...
- Using Matrix or QR Code is no problem. This codes have implemented Reed Solomon error correction, your barcode can be destroyed from 5-95%, error correction solve this. But 95% level of error correction is small data size, 5% error correction = large data, but lowest secure :-) Bad reading is cca. 1:1.000.000.000
HIBC in production processAs a starting point typical references of data capture within the production flow might be selected and applied with the related ANSI/FACT identifiers.
|W||Work order number|
|1H||Employee Identification Code|
|1D...||Date ... YYMMDD, etc...|
|1P||Item ID Code assigned by the supplier|
|1T||Charge/Serial number-Traceability code|