What HIBC Aztec Code is
HIBC Aztec Code applies the Health Industry Bar Code (HIBC) Labeler Identification Code (LIC) standard's own 43-character charset and Modulo-43 check character on top of the general-purpose Aztec Code symbology. bwip-js builds the HIBC-specific validation layer itself, then delegates the actual symbol drawing to its Aztec Code encoder -- confirmed directly: bwipp_hibcazteccode computes/validates the HIBC check character, prepends the "+" flag character HIBC data always starts with (bwip-js adds this automatically -- do not include your own leading "+"), and calls bwipp_azteccode(). Unlike the separately-covered Compact Aztec Code capability, this bcid never forces a "format," so Aztec Code's own full "format"/"eclevel" choices remain real, live options.
Generate it now
Enter a value using digits, capital letters, spaces, or the symbols -. $/+% to see a live preview. Do not type a leading "+" -- bwip-js adds the required HIBC flag character automatically.
Valid input
The value must be non-empty and every character must come from HIBC's own 43-character set: digits, capital letters A-Z, and the symbols -. $/+% (bwipp.hibcazteccodeBadCharacter rejects anything else). bwip-js always computes a Modulo-43 check character from the data (the running sum starts at 41, the charset position of "+", accounting for the flag character it prepends) and appends it, unless validatecheck is turned on, in which case the input must already carry a correct trailing check character or the render is rejected (bwipp.hibcazteccodeBadCheckDigit).
Key options
Supported options include validatecheck (this bcid's own real option) plus format and eclevel (Aztec Code's own real options, genuinely reaching the underlying delegate because hibcazteccode forwards the caller's live options unchanged). Real, literal defaults: validatecheck false (a check character is computed and appended rather than verified), format "full", eclevel 23 (percent of the symbol reserved for error correction, 5-95).
Output and printing
Export SVG for vector-precise label artwork or PNG for a quick proof.
Common uses
HIBC Aztec Code is used for medical device and pharmaceutical unit-of-use labeling under the Health Industry Bar Code standard, where a small 2D symbol's higher data density suits compact device or vial labels better than a linear HIBC barcode would.
Example
See the live preview above, seeded with a bwip-js-verified valid value.
Size guidance
Choosing "compact" format produces a more compact symbol footprint for the same data than "full" format (at the cost of a lower maximum layer count); raising eclevel reserves more of the symbol for error correction, which can grow the symbol once the reserved space exceeds what the current layer count provides.
Troubleshooting
A rejected value usually means it contains a character outside HIBC's own 43-character set, or (with validatecheck on) that the trailing character is not the correct Modulo-43 check character for the preceding data. A value with a leading "+" already typed in will still render, but produces a real symbol with a doubled flag character -- do not include your own "+".
Related formats
Related formats: the separately-covered Aztec Code generator (the same underlying symbol drawing, with no HIBC charset/checksum layer) and Compact Aztec Code (a smaller, fixed-format variant of Aztec Code).
FAQ
Should I type the leading "+" myself?
No -- bwip-js always prepends the "+" HIBC flag character itself, regardless of what you type. Including your own leading "+" produces a real symbol with the flag character doubled, which is not correct HIBC data.
How is this different from the regular Aztec Code generator?
Both use the identical underlying Aztec Code encoder for the actual symbol; this generator additionally validates the payload against HIBC's own 43-character set and computes (or verifies) a Modulo-43 HIBC check character before delegating to Aztec Code's own drawing logic.