Seven years can sound like plenty of time to prepare for a regulatory change. When that change affects an identifier embedded across pharmacy, medical claims, reimbursement, contracting, clinical workflows, supply chain operations, and healthcare technology, seven years starts to look considerably shorter. I’m getting a headache just thinking about how a simple change to a 12-digit NDC would ripple across every healthcare stakeholder and system, but it’s more complicated than a single transition to a 12-digit code. Let’s get into it.

On March 5, 2026, the U.S. Food and Drug Administration (FDA) published its final rule establishing a uniform 12-digit National Drug Code (NDC). Beginning March 7, 2033, FDA-assigned NDCs will use a consistent 6-4-2 format: six digits for the labeler code, four for the product code, and two for the package code. Existing FDA-assigned 10-digit NDCs will also be converted to the new format by adding leading zeros where necessary. A three-year transition period, through March 6, 2036, will allow existing product labeling to work its way through the supply chain.

Read the FDA's National Drug Code Format guidance

Adding digits to the NDC creates a complex, industry-wide implementation challenge.

The NDC has become deeply embedded in healthcare processes well beyond its original role as an FDA drug identifier. Payers, PBMs, pharmacies, manufacturers, wholesalers, providers and technology vendors use NDCs throughout their systems and transactions, creating a data and interoperability challenge that requires coordination across organizations that may transition at different times.

Separate FDA and HIPAA Timelines Add Complexity

The FDA’s move to a 12-digit NDC does not update the HIPAA standard used for reimbursement at the same time, creating a more complex transition across the healthcare ecosystem.

Because HIPAA transactions currently use an 11-digit NDC that cannot accommodate the new FDA format, healthcare organizations must prepare for overlapping formats, conversion requirements, and dependencies. FDA expects a compatible HIPAA standard to be implemented before its rule takes effect, but the two changes are proceeding on separate regulatory timelines.

For some time, organizations may need to recognize, translate, and reconcile different representations of the same drug identifier across FDA data, existing reimbursement transactions, historical records, product labeling, and trading-partner systems.

FDA will continue assigning the existing 10-digit formats until March 7, 2033. During the 2033–2036 labeling transition, FDA also intends to publish both 10- and 12-digit NDCs for products that had previously been assigned 10-digit NDCs.

Organizations must reliably link 10-, 11-, and 12-digit representations to the same drug product without creating duplicate or mismatched records.

Health Plans and PBMs Must Assess NDC Use Across Operations

Health plans and PBMs should assess NDC impacts across claims and all other operations that rely on the identifier.

NDCs can appear throughout payer and PBM operations, including formulary and benefit management, pharmacy claims, medical benefit drug billing and NDC crosswalks, prior authorization, rebates and contracting, analytics, quality measurement and other downstream processes.

Every one of those uses raises questions worth answering early:

Where is the NDC stored? Is its length hard-coded? Is it being converted between formats? Is an NDC used as a key to connect datasets? What happens to historical data? What happens when a trading partner sends a different representation than the receiving system expects?

The interoperability implications deserve equal attention. Drug identifiers flow through terminology services, clinical data exchanges, APIs, and other integrations. Payers investing heavily in FHIR infrastructure to meet CMS interoperability requirements should incorporate NDC 12 into their broader terminology and data-governance planning.

These dependencies make end-to-end testing essential: a system may accept a 12-digit value while still producing errors in mapping, validation, downstream processing, or partner exchanges.

Pharmacies and Health Systems: Follow the NDC Through the Clinical Workflow

For pharmacies and health systems, the impact extends from the prescription and dispensing workflow to billing and medication administration.

Pharmacy management systems, EHRs, inventory applications, automated dispensing technology, barcode medication administration, and claims infrastructure can all touch the NDC. A change at one point in that chain can affect other parts of the process.

Barcode technology introduces additional considerations.

Because a 12-digit NDC can no longer be embedded in the existing GTIN-12 or GTIN-14 structure, technology and middleware that currently derive an NDC by parsing it from a GTIN will need a different approach. GS1 has created Application Identifier AI (715) to carry the U.S. NDC in GS1 DataMatrix and certain linear barcode formats, including GS1-128 and GS1 DataBar.

Review the GS1 specification for AI (715)

For organizations already managing Drug Supply Chain Security Act (DSCSA) requirements, this also creates an intersection between NDC transition planning, serialization, scanning technology and supply chain infrastructure.

Manufacturers, Wholesalers and Life Sciences Organizations Must Address Revenue and Contracting Impacts

Manufacturers have obvious responsibilities related to FDA listing, product labeling, packaging and barcodes, but the implications quickly extend into commercial operations.

NDCs support pricing, contracting, rebate administration, chargebacks, government pricing and reconciliation among manufacturers, wholesalers, health plans and other trading partners.

As Model N notes in its analysis of the new rule, inconsistencies between old and new formats could contribute to rebate discrepancies, contract misalignment, and compliance risks if systems and partners are not prepared to handle the transition.

That makes master data especially important.

Organizations should maintain reliable relationships among historical 10-digit, reimbursement-oriented 11-digit, and new 12-digit representations. This requires knowing which applications use NDCs as authoritative data, which consume or transform them, and which exchange them externally—without treating different representations as different products.

Manufacturers, wholesalers and life sciences organizations should also use the transition to replace accumulated mapping and master-data workarounds with governed crosswalks that downstream systems and trading partners can use consistently.

Health IT and EDI Vendors Must Assess Rules, Mappings and Interfaces

Technology vendors, clearinghouses, and integration partners have a significant role to play.

The biggest risks may be embedded in business rules, validation logic, databases, APIs, EDI mappings, crosswalks, reporting systems, and interfaces with external partners, as well as hard-coded field lengths.

During rulemaking, the FDA noted that databases, IT systems, electronic transactions, scanning hardware, labeling, and other infrastructure would be affected by the change. Industry comments characterized the scope as comparable to an industry-specific Y2K because of the sheer number of systems and interfaces involved.

The first step is a comprehensive inventory of every system, workflow, rule, mapping and external interface that creates, stores, transforms, transmits or consumes an NDC.

Preparation Must Begin Well Before the 2033 Deadline

The healthcare industry has until March 7, 2033, before FDA begins using the uniform 12-digit NDC, followed by the three-year labeling transition.

Successful implementation requires years of coordinated assessment, remediation and testing before 2033.

Organizations will need time to identify dependencies, monitor changes to standards, determine remediation strategies, coordinate with vendors and trading partners, build crosswalks, update master data, test interfaces, and validate that downstream workflows still produce the expected result.

A useful starting point is to ask:

• Where does NDC data live? Inventory systems, databases, applications, interfaces and workflows that create, store, transform, transmit or consume NDCs.
• How is it represented? Identify where systems expect 10, 11 or another fixed number of digits and where conversion logic is occurring.
• What depends on it? Look beyond claims to clinical workflows, formulary, prior authorization, contracting, rebates, analytics, reporting, supply chain, barcoding and interoperability.
• Who else needs to change? Identify dependencies on vendors, clearinghouses, trading partners, standards organizations and government requirements.
• How will coexistence work? Develop governance for mapping and maintaining multiple NDC representations while preserving historical data and avoiding duplicate or mismatched product records.
• What standards are still evolving? FDA does not control every standard in which the NDC is used. Organizations will need to monitor standards organizations and federal agencies as the broader ecosystem aligns around NDC 12.

FDA intentionally provided a long implementation runway because this is a significant industry transition. The agency has encouraged manufacturers, distributors, repackagers, relabelers, pharmacies, healthcare providers, payers, and other supply-chain participants to use the years before 2033 to update their systems, processes, and infrastructure.

FDB reaches a similar conclusion in its article, “The 12-Digit NDC Is Coming—Healthcare Readiness Starts Now,” describing the seven-year period as a long runway rather than a long wait and emphasizing the need to begin evaluating systems, standards, workflows, labeling, and barcode impacts now.

The organizations that use that runway to understand their dependencies now will be in a much better position than those that discover them during implementation.

Start Your NDC 12 Readiness Assessment Now

NDC 12 will affect regulatory compliance, pharmacy and payer operations, clinical workflows, supply chains, interoperability, and health IT. Most organizations need a cross-functional view to identify every system, process, and partner dependency.

Point-of-Care Partners (POCP) can help you assess where NDC 12 touches your organization, uncover gaps and dependencies, interpret evolving standards, and build a practical transition roadmap grounded in real-world technology, workflow, and business requirements.

Whether you are a health plan, PBM, pharmacy, health system, life sciences organization or technology vendor, POCP can help you turn a complex, industry-wide change into a coordinated plan for action.

Contact POCP to begin your NDC 12 readiness assessment and identify the steps your organization should take now.