Welcome! Is the controlled substance log barcode failing audit-scanning?

Joe B.

Reviewed for technical accuracy

Specialities: Pharmacy IT, Barcode systems, GS1/UDI, Rx inventory, Omnicell/Pyxis, Compliance (DEA/State Board)

Fix failed barcode scans on controlled substance logs — NDC/GTIN mismatch, GS1-128/Code 128, DataMatrix, scanner setup

Technician

Welcome! We’ll get the controlled substance log barcode to pass audit-scanning and record correctly in your perpetual inventory.
A few quick questions so I target the fix: Are auditors or staff failing to scan a printed log label from your system, or the manufacturer’s barcode on the bottle/box? Which symbology do you expect — GS1-128 (Code 128), GS1 DataMatrix (2D), or UPC-A? And what’s the system capturing — NDC (11-digit), GTIN (AI 01), plus Lot (AI 10) / Expiry (AI 17) / Serial (AI 21)?

Customer

Auditors couldn’t scan our log labels. Our scanners beep but data is wrong — the NDC posts without leading zero and the Lot + Expiry don’t populate. We use handhelds set to keyboard wedge/HID. System expects 11-digit NDC and MM/YY expiry.

Technician

Got it. Audit failures usually come from three buckets:
1) NDC formatting — converting 10-digit patterns (5-3-2, 4-4-2, 5-4-1) to 11-digit without proper zero-padding.
2) GS1 parsing — scanners not sending Application Identifiers (AI 01, 10, 17, 21) or dropping the FNC1 separator, so your Rx system can’t split GTIN/Lot/Expiry/Serial.
3) Label/print quality — low contrast, glossy lamination, 200–300 DPI thermal settings, tiny x-dimension, or wrong Code 128 subset.
Plan: fix the label data structure, correct scanner configuration (prefix/suffix/FNC1), and apply print specs so the controlled substance log scans cleanly during DEA/state board audits.

Customer

We print labels from our pharmacy system. The barcode type shows “Code 128.” Auditors asked for GS1-128 with GTIN (01), Lot (10), and Expiry (17). Our scanner sends all digits in one blob.

Technician

Step 1 — Output GS1-compliant data (GS1-128)
• Encode GTIN (AI 01) not raw NDC; convert NDC→GTIN: add labeler zeros + check digit via Mod-10.
• Append Lot (AI 10) and Expiry (AI 17) as variable/ fixed-length fields, using the FNC1 as separator after the GTIN and after Lot when followed by Expiry/Serial.
• Example data string: (01)00312345678905(17)2609(10)ABC123. Your software should render that as GS1-128 (Code 128 with AIs), not plain Code 128.
This lets the auditor’s system and your perpetual inventory parse fields reliably.

Customer

Our scanners are Zebra and Honeywell. They’re in HID mode. How do we make them send AIs and separators the way the log expects?

Technician

Step 2 — Configure scanners for GS1 parsing
• Enable GS1-128 and GS1 DataMatrix decode; turn on “Transmit AIs” and “Send FNC1 as Group Separator”.
• Set suffix to CR (Enter) and optional TAB if your log form advances between NDC/GTIN, Lot, Expiry fields.
• Disable Code 39/Interleaved 2 of 5 if false reads occur on outer cartons.
• For Honeywell, enable “Format for NDC/GTIN” or create a data template; for Zebra, use 123Scan to push a Data Formatting Rule that inserts separators where your Rx app expects them.

Customer

Labels sometimes scan on the bottle but not on our printed log. Auditors flagged “low grade” and “quiet zone” issues.

Technician

Step 3 — Meet print specs for audit-grade barcodes
• Thermal printer: 300–600 DPI, darkness 18–24 (avoid overheat/bleed); ribbon/label matched (wax-resin on semi-gloss).
• Quiet zone: ≥ 10× module width left/right; x-dimension 0.33–0.5 mm for GS1-128, height ≥ 25 mm.
• Contrast (PCS) ≥ 0.7; avoid glossy laminate and tight curvature on tiny vials; print at 0° or 90° only.
• Verify with ISO/IEC 15416/15415; aim for grade ≥ C. Reprint any label below C to avoid audit scanning failures.

Customer

Our system stores NDC, not GTIN. Can we still pass audits? We also track C-II waste and witness sign-off.

Technician

Step 4 — Map NDC↔GTIN and capture required fields
• Maintain a labeler-product-package map: 10-digit NDC → 11-digit NDC → GTIN-14 (pad labeler with leading zero, compute check digit).
• Store both NDC and GTIN so you can ingest either bottle barcode or your log label.
• Ensure log form captures: Lot, Expiration, Quantity dispensed/returned, Blind count, Chain-of-custody, Witness sign-off. These fields matter for DEA diversion controls and state inspections.
• For C-II: reconcile daily; for CIII-V: weekly cycle counts synced to your perpetual inventory.

Customer

We’re a hospital using Omnicell/Pyxis and a separate pharmacy system. VPN carts sometimes fail to scan or post duplicates. Any enterprise tips?

Technician

Yes — for enterprise/ADC environments:
• Standardize scanners (same firmware/profile); push configs via Zebra StageNow or Honeywell DME.
• Use GS1 parsing on the device and send fields via API/HL7/CSV instead of raw keystrokes when possible.
• Prevent duplicates: one source of truth for NDC/GTIN mapping; block non-GS1 symbologies; require FNC1.
• Over VPN/Wi-Fi, lock scanners to low-latency SSID; disable power-saving that drops HID sessions mid-scan; add debounce on your log form to avoid double posts.

Customer

After changes, our labels scan. Auditors return next week. Any last checks so we pass?

Technician

Final checks for audit-scanning:
• Re-verify sample labels with an ISO verifier (grade ≥ C), confirm quiet zones, and print density.
• Test scans in your controlled substance log workflow: Bottle → Log label → Return/waste record → Reconciliation report — ensure Lot/Expiry persist across steps.
• Freeze the scanner profile through the audit window; keep backup pre-printed labels; document your GS1/NDC mapping and FNC1 policy for the auditor packet.

Customer

Perfect — test run passes and fields map correctly. We’re ready for the audit. Thanks!

Technician

Summary: To fix controlled substance log barcode failing audit-scanning, output GS1-compliant data (GTIN with AIs 01/10/17/21), configure scanners to transmit AIs + FNC1, and meet print quality specs. Map NDC↔GTIN, capture Lot/Expiry/Quantity/Witness, and standardize profiles across devices (Omnicell/Pyxis). Need help applying templates or scanner rules? Open the chat.

Quick answer: the accepted fix

Accepted fix when a controlled substance log barcode fails audit-scanning: output GS1-128/DataMatrix with GTIN (AI 01), Lot (10), Expiry (17); configure scanners to send AIs and FNC1; meet ISO print quality (quiet zone, x-dimension, contrast). Map NDC→GTIN, then test end-to-end so your perpetual inventory reconciles for DEA/state board.

FAQ

Step-by-step (rapid remediation)

1. Change label template to GS1-128 (or GS1 DataMatrix) with GTIN (01), Lot (10), Expiry (17).
2. Enable scanner options: Transmit AIs, Send FNC1, suffix CR (and TAB if needed).
3. Normalize NDC↔GTIN mapping (compute check digit, pad to 11 digits).
4. Set printer to 300–600 DPI, correct darkness; enforce quiet zones; verify ISO grade ≥ C.

Note for mixed environments (ADC, carts, macOS)

1. On carts/ADCs (Omnicell/Pyxis), push a single standardized scanner profile with GS1 parsing on.
2. macOS/HID: ensure input method doesn’t swallow TAB/CR; test with both 1D and 2D symbols.

Sources

• GS1 — Barcodes & Application Identifiers
• FDA — National Drug Code (NDC) basics
• ISO/IEC 15416/15415 — Barcode print quality (1D/2D)

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Send Message →

4 Tech Support Specialists are online right now.