Barcodes in Pharma: From DSCSA to FMD in Practice

What the 2‑D barcode and seal on your medicine mean, how pharmacists scan packs, and why these checks stop fake medicines reaching you.

Barcodes in Pharma: From DSCSA to FMD in Practice
Written by TechnoLynx Published on 25 Sep 2025

Why barcodes still matter in modern pharma

Barcodes sit at the centre of medicine identity, traceability, and release. Teams across manufacturing, wholesale, and pharmacy use them every day to keep the supply chain safe and efficient. The European Union’s safety‑feature regime and the United States Drug Supply Chain Security Act (DSCSA) both depend on machine readable identifiers on each pack. These systems cut falsification risk, speed recalls, and reduce rework during audits (European Commission, n.d.; FDA, 2021).

Policy also sets a public‑health context. The World Health Organization links better identification to its medication safety drive, which aims to reduce avoidable harm from medicines across the health care system. Safer labelling and clearer product information support that goal (WHO, 2017).

Two regulatory anchors: EU safety features and US DSCSA

EU: unique identifier + anti‑tamper. In Europe, most prescription packs carry two “safety features”: a unique identifier in a 2D code and an anti‑tampering device. Manufacturers upload each pack’s encoded information to a secure repository before release. Pharmacies then scan the code and check the seal at supply, which both verifies authenticity and “decommissions” the serial so no one can reuse it (European Commission, n.d.; MHRA, 2019).

US: DSCSA product identifier. In the United States, DSCSA requires a 2D Data Matrix on packages that carries the GTIN, serial number, expiry, and lot. Systems use those data to support interoperable tracing at the package level across trading partners. FDA guidance describes the data elements, the code format, and the relationship to older linear barcodes that still meet 21 CFR 201.25 in specific contexts (FDA, 2021; CDC, 2023).

Both frameworks point in the same direction. Teams must scan, record, and act in near real time. Teams must also prove the link from the package in hand to the digital record, and then to the decision that followed (European Commission, n.d.; FDA, 2021).

Read more: Pharma’s EU AI Act Playbook: GxP‑Ready Steps

What to put on pack: symbologies and data

Types of barcodes fall into two broad families that pharma teams meet every day.

1D (one‑dimensional) formats. These include linear barcodes such as EAN‑13, Code 128 (GS1‑128), and the UPC barcode common at retail. These codes excel at point‑of‑sale and some warehouse tasks. They carry short identifiers, scan fast, and suit legacy scanners in North America and elsewhere (GS1 US, n.d.).

2D (two‑dimensional) formats. These include GS1 DataMatrix and QR codes with GS1 Digital Link. They carry more encoded information in a small space and work well on tiny vials or syringes. They also support direct links to up‑to‑date product information on a website when teams scan with a modern device (GS1, 2025; GS1, n.d.).

If you need a quick map for your packaging brief, use this simple pair:

  • DataMatrix for serialised identifiers at the unit‑of‑use (EU FMD, US DSCSA, hospital inventory).

  • Linear (EAN/UPC or GS1‑128) for outer packs, pallet labels, and retail settings where systems still expect 1D (GS1 US, n.d.; GS1, 2025).

  • GS1 calls these rules “General Specifications”. The document defines types of barcodes, the type of 2D barcodes that fit healthcare, and the application identifiers that make the data unambiguous across markets (GS1, 2025).

Read more: Cell Painting: Fixing Batch Effects for Reliable HCS

How scanning works in the pharmacy and the warehouse

A European pharmacy follows a straight path. Staff scan the machine readable code. The system checks the serial against the repository. The system also prompts a quick seal check.

If the scan passes and the seal looks intact, the record changes state and the pack leaves under “decommissioned” status. If the scan raises an alert, staff hold the pack and follow a clear procedure (European Commission, n.d.; MHRA, 2019).

In the United States, DSCSA pushes for “traceability by design”. A wholesaler scans on receipt and on ship. A dispenser scans at hand‑off to the patient. Partners exchange interoperable data so investigators can follow a pack’s trail within hours, not weeks (FDA, 2021).

Both flows place people at the centre. Healthcare professionals want fast, clear signals. Systems must show “what this pack is”, “where it came from”, and “what to do now” without friction. That design supports safe medication management and reduces waste during audits and recalls (European Commission, n.d.; WHO, 2017).

Data you actually need inside the code

At minimum, a serialised pack needs:

  • A product identifier (GTIN or national code mapped to a GTIN).

  • A unique serial number.

  • Expiry date.

  • Batch or lot number.

DSCSA spells out the four DSCSA fields in the package Data Matrix and clarifies where teams still need a separate linear code to meet legacy label rules. The guidance also answers common change‑control questions when you update labels (FDA, 2021).

EU safety features rely on the same set, with a strong focus on verification at supply and on the long term integrity of the repository. Those checks stop recycled serials and highlight suspicious events early (European Commission, n.d.).

Read more: Explainable Digital Pathology: QC that Scales

Choosing the right code for tough real‑world contexts

Tiny primary containers. Use a compact DataMatrix with the smallest module size your vision system can read across your types of barcodes. Test under glare, curved glass, and high‑speed rotation. Always print a human‑readable string nearby for manual rescue (GS1, 2025).

Cartons at retail. Keep a UPC barcode or EAN for tills that still sit on 1D. Add the 2D code for serialisation and rich data. Configure scanners to read both, with a priority rule that meets your site’s need (GS1 US, n.d.).

Hospital stores and kits. Pack kits with a DataMatrix on each component and a GS1‑128 on the kit label. That mix helps central stores manage picks while theatres scan small units into their inventory management and medication management systems (GS1, 2025).

Barcodes and better medication safety

Better identification reduces selection errors and supports clean recalls. The World Health Organization set a global goal to cut severe, avoidable medication harm. Clearer labels, consistent barcodes, and fast digital checks help teams meet that goal in every health care system (WHO, 2017).

This is not only a European story. Hospitals across North America now scan QR codes or DataMatrix symbols on vaccines and high‑risk products. The CDC encourages 2D barcodes on vaccine packs to improve record quality and cut transcription errors during clinic sessions (CDC, 2023).

Read more: Validation‑Ready AI for GxP Operations in Pharma

Data quality: the part that breaks most projects

Bad data ruins good codes. Teams often ship packs with the wrong encoded information, stale product information, or mis‑mapped AIs.

Avoid that trap. Keep one product master. Assign an owner. Tie print files and repository uploads to that single source. Run pre‑flight checks before every production release (GS1, 2025).

When packs cross borders, expect small differences. Some markets still ask for local pharmacode formats or extra strings that sit next to the ISO date. Keep those extras out of the DataMatrix unless local rules say otherwise. Protect global consistency first, then add local fields visually (GS1, 2025).

Interoperability: from factory to last mile

A strong supply chain view needs more than a pack code. Warehouses need SSCC pallet labels. Shippers need EDI or API feeds.

Dispensers need clean look‑ups for price, shortage flags, and clinical notes. GS1 standards cover these flows and keep the machine readable elements consistent end to end (GS1, 2025; GS1 US, n.d.).

That same design helps investigations. When a regulator asks for a trail, your team can pull the scans by serial, show the status changes, and attach the relevant batch decisions in minutes, not days (European Commission, n.d.; FDA, 2021).

Read more: Edge Imaging for Reliable Cell and Gene Therapy

United States vs EU: what differs and what aligns

  • Repository vs interoperability. EU safety features centre on a verification repository and decommissioning at supply. DSCSA centres on interoperable exchange and unit‑level tracing. Both aim at the same outcome: a safe supply chain and clear accountability for each box (European Commission, n.d.; FDA, 2021).

  • Symbology. Both use DataMatrix for units, with support for linear barcodes where legacy systems still need them (UPC barcode at retail, GS1‑128 in logistics). That mix supports backward compatibility while teams modernise (GS1 US, n.d.; FDA, 2021).

  • People and process. Both expect trained staff, clean SOPs, and audit‑ready records. Both expect fast responses to alerts. Both view falsification and diversion as ongoing risks that demand long term vigilance (European Commission, n.d.; FDA, 2021).

Practical tips for better scanning performance

  • Keep quiet zones and contrast within GS1 tolerances; adjust inks and boards for small‑module DataMatrix codes (GS1, 2025).

  • Test in motion with your actual cameras and optics; static checks hide motion blur.

  • Train healthcare professionals on “scan‑first” habits in stores and dispensaries; measure scan rates, not only stock accuracy.

  • When teams report false alerts, fix root causes quickly—duplicate serials, mis‑reads from poor print, or wrong GTIN mappings (MHRA, 2019; FDA, 2021).

Read more: AI in Genetic Variant Interpretation: From Data to Meaning

A note on data field names and odd imports

Some data feeds bundle both organisation type and country into a single field. You may even meet the string pharmacyunited states in legacy imports.

Clean that field on ingest. Split it into “site type” and “country”. Keep your repository free of such glue. Small hygiene wins like this protect analytics and compliance downstream.

Where standards go next

Standards continue to evolve. GS1 promotes broader QR codes adoption with GS1 Digital Link so smartphones can fetch current product information directly from a pack. Industry groups also discuss a retail “sunrise” for 2D in some sectors. Healthcare will move more slowly because patient risk sits higher, but the direction stays clear: compact machine readable codes with richer data, under one global standard (GS1, 2025; GS1 US, n.d.).

At the same time, large providers and payers in North America ask for tighter scan‑to‑record flows. They want fewer transcription steps and cleaner links from each medicine to the patient record. Those asks line up with the WHO challenge on medication safety and the broader goals of each international organization that pushes for safer systems (WHO, 2017).

Read more: AI Visual Inspection for Sterile Injectables


Read more: AI in Life Sciences

How TechnoLynx can help

TechnoLynx equips pharma, wholesale, and hospital teams with machine readable workflows that align with EU safety features and DSCSA. We deploy vision and barcodes pipelines on‑premise, tune codes for tough surfaces, and integrate scan events with your QMS and ERP.

We also build explainable dashboards that show serial status, scan quality, and recall reach within minutes. Our solutions keep product information current across sites and reduce noise from false alerts. We package everything with validation artefacts and change control that QA accepts on first pass. We support inventory management, pack design, and lane qualification with the same discipline that your auditors expect.

References

  • Centers for Disease Control and Prevention (2023) Drug Supply Chain Security Act and 2D vaccine barcodes. Available at: https://www.cdc.gov/vaccines/programs/iis/2d-barcodes/downloads/Drug-Supply-Chain-Security-Act-508.pdf

  • European Commission (n.d.) Falsified medicines. Available at: https://health.ec.europa.eu/medicinal-products/falsified-medicines_en

  • Food and Drug Administration (2021) Product identifiers under the Drug Supply Chain Security Act: Questions and answers—Guidance for industry. Available at: https://www.fda.gov/media/116304/download

  • GS1 (2025) GS1 General Specifications, Version 25.0. Available at: https://www.gs1.org/standards/barcodes-epcrfid-id-keys/gs1-general-specifications

  • GS1 (n.d.) General Specifications—overview and symbologies. Available at: https://gs1mu.org/standards-services/gs1-general-specifications (Accessed: 25 September 2025).

  • GS1 US (n.d.) Types of barcodes. Available at: https://www.gs1us.org/upcs-barcodes-prefixes/barcode-types

  • Medicines and Healthcare products Regulatory Agency (2019) Falsified Medicines Directive: Safety features. Available at: https://mhrainspectorate.blog.gov.uk/2019/02/08/falsified-medicines-directive-safety-features/

  • World Health Organization (2017) Medication Without Harm—Global Patient Safety Challenge. Available at: https://www.who.int/publications/i/item/WHO-HIS-SDS-2017.6

  • Image credits: Freepik

Cost, Efficiency, and Value Are Not the Same Metric

Cost, Efficiency, and Value Are Not the Same Metric

17/04/2026

Performance per dollar. Tokens per watt. Cost per request. These sound like the same thing said differently, but they measure genuinely different dimensions of AI infrastructure economics. Conflating them leads to infrastructure decisions that optimize for the wrong objective.
Precision Is an Economic Lever in Inference Systems

Precision Is an Economic Lever in Inference Systems

17/04/2026

Precision isn't just a numerical setting — it's an economic one. Choosing FP8 over BF16, or INT8 over FP16, changes throughput, latency, memory footprint, and power draw simultaneously. For inference at scale, these changes compound into significant cost differences.
Precision Choices Are Constrained by Hardware Architecture

Precision Choices Are Constrained by Hardware Architecture

17/04/2026

You can't run FP8 inference on hardware that doesn't have FP8 tensor cores. Precision format decisions are conditional on the accelerator's architecture — its tensor core generation, native format support, and the efficiency penalties for unsupported formats.
Steady-State Performance, Cost, and Capacity Planning

Steady-State Performance, Cost, and Capacity Planning

17/04/2026

Capacity planning built on peak performance numbers over-provisions or under-delivers. Real infrastructure sizing requires steady-state throughput — the predictable, sustained output the system actually delivers over hours and days, not the number it hit in the first five minutes.
How Benchmark Context Gets Lost in Procurement

How Benchmark Context Gets Lost in Procurement

16/04/2026

A benchmark result starts with full context — workload, software stack, measurement conditions. By the time it reaches a procurement deck, all that context is gone. The failure mode is not wrong benchmarks but context loss during propagation.
Building an Audit Trail: Benchmarks as Evidence for Governance and Risk

Building an Audit Trail: Benchmarks as Evidence for Governance and Risk

16/04/2026

High-value AI hardware decisions need traceable evidence, not slide-deck bullet points. When benchmarks are documented with methodology, assumptions, and limitations, they become auditable institutional evidence — defensible under scrutiny and revisitable when conditions change.
The Comparability Protocol: Why Benchmark Methodology Defines What You Can Compare

The Comparability Protocol: Why Benchmark Methodology Defines What You Can Compare

16/04/2026

Two benchmark scores can only be compared if they share a declared methodology — the same workload, precision, measurement protocol, and reporting conditions. Without that contract, the comparison is arithmetic on numbers of unknown provenance.
A Decision Framework for Choosing AI Hardware

A Decision Framework for Choosing AI Hardware

16/04/2026

Hardware selection is a multivariate decision under uncertainty — not a score comparison. This framework walks through the steps: defining the decision, matching evaluation to deployment, measuring what predicts production, preserving tradeoffs, and building a repeatable process.
How Benchmarks Shape Organizations Before Anyone Reads the Score

How Benchmarks Shape Organizations Before Anyone Reads the Score

16/04/2026

Before a benchmark score informs a purchase, it has already shaped what gets optimized, what gets reported, and what the organization considers important. Benchmarks function as decision infrastructure — and that influence deserves more scrutiny than the number itself.
Accuracy Loss from Lower Precision Is Task‑Dependent

Accuracy Loss from Lower Precision Is Task‑Dependent

16/04/2026

Reduced precision does not produce a uniform accuracy penalty. Sensitivity depends on the task, the metric, and the evaluation setup — and accuracy impact cannot be assumed without measurement.
Precision Is a Design Parameter, Not a Quality Compromise

Precision Is a Design Parameter, Not a Quality Compromise

16/04/2026

Numerical precision is an explicit design parameter in AI systems, not a moral downgrade in quality. This article reframes precision as a representation choice with intentional trade-offs, not a concession made reluctantly.
Mixed Precision Works by Exploiting Numerical Tolerance

Mixed Precision Works by Exploiting Numerical Tolerance

16/04/2026

Not every multiplication deserves 32 bits. Mixed precision works because neural network computations have uneven numerical sensitivity — some operations tolerate aggressive precision reduction, others don't — and the performance gains come from telling them apart.

Throughput vs Latency: Choosing the Wrong Optimization Target

16/04/2026

Throughput and latency are different objectives that often compete for the same resources. This article explains the trade-off, why batch size reshapes behavior, and why percentiles matter more than averages in latency-sensitive systems.

Quantization Is Controlled Approximation, Not Model Damage

16/04/2026

When someone says 'quantize the model,' the instinct is to hear 'degrade the model.' That framing is wrong. Quantization is controlled numerical approximation — a deliberate engineering trade-off with bounded, measurable error characteristics — not an act of destruction.

GPU Utilization Is Not Performance

15/04/2026

The utilization percentage in nvidia-smi reports kernel scheduling activity, not efficiency or throughput. This article explains the metric's exact definition, why it routinely misleads in both directions, and what to pair it with for accurate performance reads.

FP8, FP16, and BF16 Represent Different Operating Regimes

15/04/2026

FP8 is not just 'half of FP16.' Each numerical format encodes a different set of assumptions about range, precision, and risk tolerance. Choosing between them means choosing operating regimes — different trade-offs between throughput, numerical stability, and what the hardware can actually accelerate.

Peak Performance vs Steady‑State Performance in AI

15/04/2026

AI systems rarely operate at peak. This article defines the peak vs. steady-state distinction, explains when each regime applies, and shows why evaluations that capture only peak conditions mischaracterize real-world throughput.

The Software Stack Is a First‑Class Performance Component

15/04/2026

Drivers, runtimes, frameworks, and libraries define the execution path that determines GPU throughput. This article traces how each software layer introduces real performance ceilings and why version-level detail must be explicit in any credible comparison.

The Mythology of 100% GPU Utilization

15/04/2026

Is 100% GPU utilization bad? Will it damage the hardware? Should you be worried? For datacenter AI workloads, sustained high utilization is normal — and the anxiety around it usually reflects gaming-era intuitions that don't apply.

Why Benchmarks Fail to Match Real AI Workloads

15/04/2026

The word 'realistic' gets attached to benchmarks freely, but real AI workloads have properties that synthetic benchmarks structurally omit: variable request patterns, queuing dynamics, mixed operations, and workload shapes that change the hardware's operating regime.

Why Identical GPUs Often Perform Differently

15/04/2026

'Same GPU' does not imply the same performance. This article explains why system configuration, software versions, and execution context routinely outweigh nominal hardware identity.

Training and Inference Are Fundamentally Different Workloads

15/04/2026

A GPU that excels at training may disappoint at inference, and vice versa. Training and inference stress different system components, follow different scaling rules, and demand different optimization strategies. Treating them as interchangeable is a design error.

Performance Ownership Spans Hardware and Software Teams

15/04/2026

When an AI workload underperforms, attribution is the first casualty. Hardware blames software. Software blames hardware. The actual problem lives in the gap between them — and no single team owns that gap.

Performance Emerges from the Hardware × Software Stack

15/04/2026

AI performance is an emergent property of hardware, software, and workload operating together. This article explains why outcomes cannot be attributed to hardware alone and why the stack is the true unit of performance.

Power, Thermals, and the Hidden Governors of Performance

14/04/2026

Every GPU has a physical ceiling that sits below its theoretical peak. Power limits, thermal throttling, and transient boost clocks mean that the performance you read on the spec sheet is not the performance the hardware sustains. The physics always wins.

Why AI Performance Changes Over Time

14/04/2026

That impressive throughput number from the first five minutes of a training run? It probably won't hold. AI workload performance shifts over time due to warmup effects, thermal dynamics, scheduling changes, and memory pressure. Understanding why is the first step toward trustworthy measurement.

CUDA, Frameworks, and Ecosystem Lock-In

14/04/2026

Why is it so hard to switch away from CUDA? Because the lock-in isn't in the API — it's in the ecosystem. Libraries, tooling, community knowledge, and years of optimization create switching costs that no hardware swap alone can overcome.

GPUs Are Part of a Larger System

14/04/2026

CPU overhead, memory bandwidth, PCIe topology, and host-side scheduling routinely limit what a GPU can deliver — even when the accelerator itself has headroom. This article maps the non-GPU bottlenecks that determine real AI throughput.

Why AI Performance Must Be Measured Under Representative Workloads

14/04/2026

Spec sheets, leaderboards, and vendor numbers cannot substitute for empirical measurement under your own workload and stack. Defensible performance conclusions require representative execution — not estimates, not extrapolations.

Low GPU Utilization: Where the Real Bottlenecks Hide

14/04/2026

When GPU utilization drops below expectations, the cause usually isn't the GPU itself. This article traces common bottleneck patterns — host-side stalls, memory-bandwidth limits, pipeline bubbles — that create the illusion of idle hardware.

Why GPU Performance Is Not a Single Number

14/04/2026

AI GPU performance is multi-dimensional and workload-dependent. This article explains why scalar rankings collapse incompatible objectives and why 'best GPU' questions are structurally underspecified.

What a GPU Benchmark Actually Measures

14/04/2026

A benchmark result is not a hardware measurement — it is an execution measurement. The GPU, the software stack, and the workload all contribute to the number. Reading it correctly requires knowing which parts of the system shaped the outcome.

Why Spec‑Sheet Benchmarking Fails for AI

14/04/2026

GPU spec sheets describe theoretical limits. This article explains why real AI performance is an execution property shaped by workload, software, and sustained system behavior.

Visual Computing in Life Sciences: Real-Time Insights

6/11/2025

Learn how visual computing transforms life sciences with real-time analysis, improving research, diagnostics, and decision-making for faster, accurate outcomes.

AI-Driven Aseptic Operations: Eliminating Contamination

21/10/2025

Learn how AI-driven aseptic operations help pharmaceutical manufacturers reduce contamination, improve risk assessment, and meet FDA standards for safe, sterile products.

AI Visual Quality Control: Assuring Safe Pharma Packaging

20/10/2025

See how AI-powered visual quality control ensures safe, compliant, and high-quality pharmaceutical packaging across a wide range of products.

AI for Reliable and Efficient Pharmaceutical Manufacturing

15/10/2025

See how AI and generative AI help pharmaceutical companies optimise manufacturing processes, improve product quality, and ensure safety and efficacy.

Pharma’s EU AI Act Playbook: GxP‑Ready Steps

24/09/2025

A clear, GxP‑ready guide to the EU AI Act for pharma and medical devices: risk tiers, GPAI, codes of practice, governance, and audit‑ready execution.

Cell Painting: Fixing Batch Effects for Reliable HCS

23/09/2025

Reduce batch effects in Cell Painting. Standardise assays, adopt OME‑Zarr, and apply robust harmonisation to make high‑content screening reproducible.

Explainable Digital Pathology: QC that Scales

22/09/2025

Raise slide quality and trust in AI for digital pathology with robust WSI validation, automated QC, and explainable outputs that fit clinical workflows.

Validation‑Ready AI for GxP Operations in Pharma

19/09/2025

Make AI systems validation‑ready across GxP. GMP, GCP and GLP. Build secure, audit‑ready workflows for data integrity, manufacturing and clinical trials.

Edge Imaging for Reliable Cell and Gene Therapy

17/09/2025

Edge imaging transforms cell & gene therapy manufacturing with real‑time monitoring, risk‑based control and Annex 1 compliance for safer, faster production.

AI in Genetic Variant Interpretation: From Data to Meaning

15/09/2025

AI enhances genetic variant interpretation by analysing DNA sequences, de novo variants, and complex patterns in the human genome for clinical precision.

AI Visual Inspection for Sterile Injectables

11/09/2025

Improve quality and safety in sterile injectable manufacturing with AI‑driven visual inspection, real‑time control and cost‑effective compliance.

Predicting Clinical Trial Risks with AI in Real Time

5/09/2025

AI helps pharma teams predict clinical trial risks, side effects, and deviations in real time, improving decisions and protecting human subjects.

Generative AI in Pharma: Compliance and Innovation

1/09/2025

Generative AI transforms pharma by streamlining compliance, drug discovery, and documentation with AI models, GANs, and synthetic training data for safer innovation.

AI for Pharma Compliance: Smarter Quality, Safer Trials

27/08/2025

AI helps pharma teams improve compliance, reduce risk, and manage quality in clinical trials and manufacturing with real-time insights.

Markov Chains in Generative AI Explained

31/03/2025

Discover how Markov chains power Generative AI models, from text generation to computer vision and AR/VR/XR. Explore real-world applications!
Back See Blogs
arrow icon