3.2 Serialization, the Product Identifier & EDDS

The Product Identifier — Four Elements

At the heart of DSCSA's package-level tracing is the product identifier. For a covered prescription drug package, the product identifier must encode four specific data elements:

1. GTIN / NDC — the Global Trade Item Number, which in the U.S. incorporates the National Drug Code (NDC). The GTIN uniquely identifies the product, strength, and configuration.
2. Serial number — a unique numeric or alphanumeric string assigned to that individual package, making it distinguishable from every other package of the same product.
3. Lot number — the manufacturer's lot/batch identifier.
4. Expiration date — the product's expiry.

Together these four elements make each package uniquely and fully identifiable. A package without a valid product identifier (or with a mismatched identifier) is a red flag during receiving.

SGTIN — Serialized Global Trade Item Number

The standardized data construct that carries serial-level identity is the Serialized Global Trade Item Number (SGTIN). SGTIN builds on the GTIN by appending a serial number, so the package carries a globally unique identifier rather than just a product-level code. GS1 standards underpin SGTIN and the 2D Data Matrix carriers most commonly used to encode DSCSA product identifiers on packages. Packages may also carry the data in linear barcode and/or plain text form.

Aggregation and Inference

Scanning every individual package inside a sealed case or pallet is impractical at scale. DSCSA therefore relies on two supporting concepts:

• Aggregation — the documented relationship between a pallet, the cases on it, and the individual packages inside each case. When aggregation data is accurate, a trading partner can scan a case-level identifier and "know" which package-level identifiers are inside.
• Inference — the use of aggregation relationships to verify the presence and identity of inner packages without physically scanning each one. Inference allows a receiving pharmacy to verify a case by scanning the case and relying on the aggregation data for the inner packages, provided the aggregation relationship is intact and trusted.

Aggregation and inference are what make package-level tracing operationally feasible at pharmacy-receiving scale.

EDDS — Enhanced Drug Distribution Security

The Enhanced Drug Distribution Security (EDDS) requirements carry staggered compliance dates by trading-partner type — manufacturers and repackagers from May 27, 2025, wholesale distributors from August 27, 2025, dispensers with 26 or more full-time licensed pharmacists/qualified technicians from November 27, 2025, and small dispensers from November 27, 2026. Under EDDS, trading partners must use interoperable, electronic, package-level methods to exchange tracing data — replacing the earlier lot-level transaction-data approach with true package-level granularity.

Key features of EDDS:

• Package-level (not just lot-level) data exchange
• Electronic and interoperable systems using common standards (e.g., EPCIS, the Electronic Product Code Information Services standard)
• Verification at the package level — trading partners can look up a specific package's history through its SGTIN/product identifier
• Authorization verification — trading partners confirm that their counterparty is an authorized trading partner

Lot-Level vs Package-Level — Why the Distinction Matters

Before EDDS, DSCSA tracing was largely lot-level: trading partners passed transaction data keyed to lot numbers, so a pharmacy could know a lot came from a given wholesaler but could not distinguish one package from another within the same lot. EDDS moves tracing to the package level: each individual package has a unique serial number, so a single stolen package can be identified even when thousands of legitimate packages from the same lot remain in the supply chain. This package-level granularity is the central advance of EDDS and a common exam point.

What Interoperability Means

"Interoperable" is not the same as "using the same software." Interoperability means that different trading partners — a manufacturer using one serialization system and a wholesaler using another — can exchange and interpret package-level data because they adhere to common standards (GS1, EPCIS, and related data-exchange standards). This lets a dispenser verify a product's chain of custody even when the data originated in a different trading partner's system. When a trading partner needs to verify a specific package's legitimacy, it can query package-level data — sometimes through a Verification Router Service (VRS) — to confirm the package's identifier and history.

Worked Example — Receiving a Serialized Case

A technician receives a sealed case of a covered prescription product. The case label carries a GS1 2D Data Matrix encoding the case-level GTIN plus a case serial number. Using aggregation data, the case is associated with the 48 individual packages inside. The technician scans the case identifier; the inventory system uses inference to confirm the 48 inner package SGTINs without opening the case. If the aggregation relationship is intact and the wholesaler is an authorized trading partner, the receive is verified at the package level without unpacking — a core efficiency of the EDDS system.

Exam Tip

Memorize the four product-identifier elements as a set: GTIN/NDC + serial + lot + expiration. Any option that omits one of these (for example, "GTIN + lot + expiry" with no serial) is wrong on the exam — the serial number is what converts a product identifier into a package-level (serialized) identifier.