White Paper: The NDC-12 Revenue Risk

Executive Summary

The Problem

Most NDC-12 discussions are happening in regulatory affairs and labeling. Commercial leadership has been largely absent from that conversation. That absence has a cost.

The Risk

The FDA's March 7, 2026, final rule mandating a uniform 12-digit National Drug Code (NDC) — effective March 7, 2033, with a three-year hybrid transition through 2036 — introduces revenue, patient access and market intelligence risks that will appear in quarterly business reviews, not system error logs.^1-5

The Zero-Prefix Collision Probability Model (ZCPM) identifies approximately 4,088 collision pairs in the current FDA NDC Directory — instances where automated zero-padding generates identical 12-digit strings for different drug products, approximately 270 of which involve Institute for Safe Medication Practices (ISMP) high-alert medications.⁶ In practice, this means rejected claims, broken patient program enrollments, corrupted IQVIA and Symphony Health data, specialty pharmacy handoff failures and a competitor's product occupying your product's identifier space in pharmacy systems.

The Action

The window to prevent these consequences is 2026-2030. Commercial teams that act now will launch faster, protect market share data integrity and maintain patient access without interruption. Those that defer will spend 2034 explaining to leadership why revenue recognition is delayed, why patient program enrollments are breaking and why market share reports no longer reconcile with sellout data.

Analytical Approach

A brief note on how this analysis was constructed — and why it should be trusted.

This paper combines three analytical threads. The first is statistical modeling: The ZCPM evaluates all existing NDC configurations in the FDA NDC Directory and simulates zero-padding transformation across the three legacy 10-digit formats: 5-4-1, 5-3-2 and 4-4-2. By mapping every possible conversion outcome across all active NDC records and identifying cases where different products generate the same 12-digit string under automated padding, the model arrives at a quantified collision risk count — approximately 4,088 pairs — rather than a theoretical estimate.⁶

The second thread is scenario-based modeling of commercial workflows: The reimbursement, hub service, patient access and market intelligence scenarios in this paper are constructed from the actual operational architecture of specialty pharmaceutical commercialization, not hypothetical abstractions. The failure modes described are traceable to documented system behaviors.

The third thread is a comparative analysis of prior industry transitions. DSCSA serialization — which ran from 2013 through full enforcement in 2023 — produced a well-documented record of what happens when identifier architecture decisions are deferred to the compliance deadline. That record informs the urgency of the timeline in this paper.

The objective is straightforward: translate identifier-level risk into measurable commercial impact across reimbursement, patient access and market intelligence systems — and give commercial leaders the framing they need to act early.

1. The Commercial Absence Problem

Commercial organizations are not in this conversation. That is the risk this paper is written to address.

I have watched commercial leadership absent itself from technical transitions before. The pattern is consistent: they re-enter the room when the first QBR shows numbers they cannot explain. The NDC-12 transition will follow that same arc — unless something changes now.

Every year, the U.S. pharmaceutical industry processes an estimated 5.8 billion prescription drug transactions — and every single one carries NDC as its primary drug identifier.⁷ Reimbursement depends on it. Patient access depends on it. Market intelligence depends on it. Brand integrity depends on it. That NDC is about to change format, and the people responsible for protecting all four of those things are not yet in the conversation.

The industry's response to the NDC-12 transition is being led by regulatory affairs, IT and labeling teams. These are exactly the right functions to lead the technical conversion. They are not, however, the functions that will feel the revenue consequences when something goes wrong — when a claim bounces for a drug that was correctly dispensed, when a patient calls their specialty pharmacy confused about a bill they thought was covered, when a quarterly market share report doesn't reconcile with sellout data and nobody can explain why.

The DSCSA experience from 2023 to 2025 is instructive. By mid-2023, only 35% of manufacturers were successfully transmitting serialized data to distribution partners — despite years of preparation.⁸ But the most important lesson from DSCSA wasn't technical. It was organizational: The hardest problems were not about systems — they were about coordination, data ownership and late integration. Functions that understood their stake in the outcome early moved through the transition with manageable friction. Those that waited discovered their dependencies at the worst possible moment.

NDC-12 follows the same structural pattern — with one critical difference. The commercial consequences of NDC-12 failures will appear not in supply chain logs but in the metrics commercial organizations care about most: cash flow, patient access, brand performance and market intelligence accuracy.

The commercial teams that treat this as a back-office IT project will discover the damage in their quarterly business reviews. The ones that act early will launch faster, protect their brand's market share data integrity and enter the 2033 effective date with reimbursement infrastructure that works on day one.

2. The Collision Mechanism: What Every Commercial Leader Must Understand

2.1. A 50-Year Structural Flaw, Now Coming Due

The NDC was never standardized. It is about to be — and the process of standardization creates its own risk window.

The NDC has served as the foundational drug identifier across the U.S. pharmaceutical ecosystem since 1969. What was never resolved in those 50-plus years is a format fragmentation problem: Three distinct 10-digit configurations — 5-4-1, 5-3-2 and 4-4-2 — have coexisted under FDA assignment, with Health Insurance Portability and Accountability Act independently mandating an 11-digit format for electronic billing.^1,9 The result has been a system where the same drug can carry a different numeric string depending on which system is reading it and what conversion rule was applied.

The FDA's March 7, 2026, final rule establishes a uniform 12-digit format — 6-4-2 — effective March 7, 2033.¹ Existing 10-digit NDCs will be converted by adding leading zeros to the appropriate segment. The intent is to eliminate conversion errors permanently (Table 1). But the three-year hybrid period from 2033 to 2036, during which both 10-digit and 12-digit labels may circulate simultaneously, concentrates the very conversion risk the rule is designed to end into a finite, high-stakes window.

2.2. The Zero-Prefix Collision: A Plain-Language Explanation

This is the mechanism behind the revenue risk — and it is more intuitive than it first appears.

When a system converts a 10-digit NDC to 12 digits by inserting a leading zero, it must know which segment format the original NDC used — because the zero goes in a different position depending on whether the NDC is a 5-4-1, 5-3-2, or 4-4-2. Many older pharmacy management systems, pharmacy benefit manager claims engines and specialty pharmacy hub databases store NDCs as plain 10-digit numbers without format metadata — making it impossible to apply the correct conversion rule without an external lookup.

The ZCPM analysis of the full FDA NDC Directory identifies approximately 4,088 collision pairs — instances where two different drugs will generate the same 12-digit string when automated padding is applied without format-of-origin metadata.³ Approximately 270 of these involve ISMP-designated high-alert medications — drugs where an identifier error carries not just commercial consequence but direct patient safety risk.¹⁰ This is not a tail-risk scenario. It is a statistically quantified, analytically documented risk with a known effective date.

The Commercial Bottom Line on Zero-Prefix Collision

A collision means your product and a competitor's product share the same 12-digit identifier string in systems that did not preserve format-of-origin metadata. In practice, this shows up as: claims adjudicated against the wrong drug's benefit tier — your drug billed at a competitor's reimbursement rate, rebate contracts triggered by the wrong manufacturer's product, market share data assigning your dispensing to a competitor, patient support program eligibility evaluated against the wrong drug record, specialty pharmacy hub handoffs verified against the wrong product identifier and DSCSA serialization verification failures — a known failure mode from 2023 to 2025 now amplified by the format change.

None of these events generates an immediate visible error. They generate anomalous data that takes months to trace to its root cause.

2.3. The GTIN Cascade: A Broader Identifier Context

The NDC doesn't exist in isolation — it sits inside a broader product identification architecture, and that architecture is also shifting.

What makes this more complex is that the NDC is not an isolated identifier — it is embedded in broader product identification systems, most notably the Global Trade Item Number (GTIN) used in GS1 DataMatrix barcodes for DSCSA serialization. Currently, pharmaceutical manufacturers encode their 10-digit NDC within a GTIN-12, with a GS1 Company Prefix constructed from the two-digit prefix “03” followed by the FDA-assigned five-digit labeler code.

When the labeler code expands from five to six digits under the 12-digit NDC rule, this construction methodology breaks. GS1 US has confirmed that the 12-digit NDC format amplifies the need to associate an NDC with a GTIN for unique product identification at every packaging level — and the NDC can no longer be embedded directly in the product GTIN once the labeler code expands.^11,12 Every manufacturer that has built its GS1 Company Prefix around a five-digit labeler code will need to reassess its GTIN architecture. This is, in practical terms, a structural decoupling of the NDC from the GTIN — a break in the serialization model the industry has relied upon since DSCSA implementation.

The commercial implication is direct: If your GTIN architecture is not updated in advance, DSCSA serialization verification for your products will fail at the point of the labeler code change — independent of whether the NDC format conversion itself was handled correctly. That is two separate failure modes, hitting simultaneously, during the hybrid period.

3. Five Commercial Risk Domains: Where Revenue and Access Are Exposed

3.1. Reimbursement — Where Revenue Stops First

A claim rejection is straightforward to describe and genuinely difficult to trace in real time. The drug was manufactured. It was dispensed. The patient has it. The pharmacist scanned it correctly. The claim bounced — not because of a clinical problem, not because of a formulary issue — but because an identifier format mismatch generated a 12-digit code that the PBM adjudication engine could not match to a recognized drug record.

Insurance claims adjudication, Medicaid and Medicare billing, and pharmacy benefit management all use the NDC as the key identifier connecting a dispensed drug to its benefit tier, formulary status, prior authorization, and reimbursement rate.^13,14 During the 2033–2036 hybrid period, PBM systems must support both 10-digit and 12-digit NDC formats simultaneously. Systems that apply an incorrect padding rule and generate a mismatched 12-digit string will reject the claim.

For specialty drugs — oncology biologics, rare disease therapies, high-cost immunology agents — where a single claim can represent $30,000 to $100,000 or more in revenue, a collision-driven claim rejection is not a billing department problem. It is a revenue recognition event that shows up on the profit and loss.

The Medicaid Drug Rebate Program (MDRP) creates an additional layer of exposure. Average manufacturer price and best price submissions are keyed to NDC. A zero-prefix collision that causes Drug A's quarterly pricing submission to be logged against Drug B's MDRP record corrupts the rebate calculation for both drugs across all state Medicaid programs¹⁵ — potentially generating significant incorrect rebate obligations or underpayments, with OIG compliance consequences layered on top of the financial ones.

3.2. Specialty Pharmacy and Hub Networks — Patient Access at Every Handoff

A zero-prefix collision in a hub service platform doesn't just cause a billing problem. It can delay a patient getting a life-critical medication.

Specialty drugs move through complex hub-and-spoke architectures where NDC matching is critical at every point: manufacturer to specialty distributor, distributor to specialty pharmacy, specialty pharmacy to patient and back through the returns and destruction chain. Hub service platforms manage benefits verification, prior authorization, patient enrollment, copay assistance, clinical support and adherence programs — all indexed to the drug's NDC.

Here is the scenario that will play out if this is not addressed: A patient enrolled in a hub program for a specialty biologic before 2033. Their enrollment record carries the drug's legacy 10-digit NDC — because that was the format in the system when they enrolled. After March 7, 2033, the specialty pharmacy processes their next dispense with a 12-digit NDC on the label. The hub platform cannot resolve the two identifiers as the same drug. The patient's enrollment silently becomes unresolvable. Benefits verification fails. Prior authorization cannot be confirmed. The specialty pharmacy cannot process the order.

The patient calls their physician and says their medication has been denied. The commercial team gets a call about access failures that nobody can explain. Hours of manual investigation follow. All of this is traceable, in retrospect, to an identifier format resolution failure that a crosswalk update, deployed in 2028, would have stopped entirely.

This is not hypothetical. The DSCSA literature documents that verification failures at specialty pharmacy handoff points — driven by product identifier format mismatches — were among the most common stabilization-period problems encountered in 2023-2025.¹⁶ The NDC-12 transition creates an identical failure mode, at the same handoff points, with the same patients.

3.3. Patient Support Programs and Copay Assistance — the Orphaned Prescription

The most patient-facing risk has the quietest failure signature.

Manufacturer-sponsored patient support programs are among the highest-value commercial investments in specialty pharmaceutical portfolios. They are also completely NDC-dependent. Eligibility determination, enrollment verification, dispensing event matching, and program performance reporting all rely on the program platform's ability to match the dispensed drug's NDC to the enrolled patient's program record.

The Orphaned Prescription scenario unfolds this way: a patient enrolls in a co-pay assistance program in 2031. Their enrollment record carries the drug's 10-digit NDC. After 2033, their specialty pharmacy processes a dispense with the 12-digit NDC. The program platform cannot resolve the two as the same drug. The patient's enrollment silently breaks.

The patient does not receive an error message. They receive a copay bill for the full amount instead of their program benefit — a financial shock that, for therapies costing $8,000 per month, can cause immediate discontinuation. The commercial team receives access barrier reports weeks before the root cause is identified. The experience drives negative social media, potential congressional attention, and brand damage — all traceable, in retrospect, to a systems remediation project that was not prioritized in time.

3.4. 340B, Chargeback and Wholesaler Reconciliation — the Hidden Revenue Leak

Less visible than a claim rejection, but potentially just as costly.

The 340B Drug Pricing Program and the chargeback infrastructure supporting it add another dimension to NDC-12 commercial exposure that has received insufficient attention. Covered entity eligibility determination, chargeback submission, and wholesaler reconciliation are all keyed to the NDC. A zero-prefix collision that causes a 340B transaction to be matched to the wrong product record disrupts chargeback processing for both the covered entity and the manufacturer — generating leakage that may not surface in financial reporting until a quarter-end reconciliation.

Wholesaler reconciliation compounds this exposure. Wholesalers reconcile inventory against NDC-keyed product records. A format mismatch during the hybrid period — particularly for products moving through multiple distribution tiers — creates the conditions for wholesaler inventory miscounts, disputed chargebacks, and attribution errors that are difficult to resolve retroactively. These are not hypothetical edge cases; they are foreseeable consequences of an identifier architecture transition without adequate crosswalk infrastructure.

3.5. PDMP and Prescription Data Feeds — When Market Intelligence Goes Dark

A commercial team making multi-million-dollar decisions on corrupted analytics is not a system problem — it is a strategy problem.

Commercial organizations depend on prescription data — IQVIA MIDAS and National Prescription Audit, Symphony Health, PDMP feeds and specialty pharmacy dispense data — for sales analytics, market share tracking, promotional targeting, competitive intelligence and launch forecasting. Every data point in these systems is NDC keyed.^17,18 The integrity of commercial market intelligence depends entirely on the ability of these platforms to correctly join historical prescription records (10-digit NDC) to current dispensing events (12-digit NDC) as a continuous data series.

If that linkage breaks at the 2033 format boundary — and neither IQVIA nor Symphony Health has yet publicly committed to a crosswalk continuity plan — the market intelligence foundation for post-2033 commercial decisions becomes unreliable. A commercial organization that launches a product in 2034 and builds its market share baseline from a platform that has silently fragmented its historical data at the 2033 boundary will be making multimillion-dollar decisions on a corrupted analytical foundation.

Prescription Drug Monitoring Programs (PDMP) data create a specific controlled substance management dimension.^19,20 PDMPs use the NDC as the sole drug identifier — there is no RxNorm fallback. If historical PDMP dispensing records for opioids and controlled substances are stored under 10-digit NDCs and query infrastructure is updated to search by 12-digit NDC, historical controlled substance dispensing history becomes invisible to prescribers. This affects patient safety directly — and affects the commercial analytics that use PDMP feed data to understand controlled substance market dynamics.

3.6. Brand Protection — the Competitor Collision Risk

The most strategically significant risk — and the least discussed.

If a competitor's product and your product are a collision pair in the converted code space, their product's 12-digit NDC string is identical to yours in systems that did not correctly resolve the collision. Your product may be substituted for theirs — or theirs for yours — in pharmacy dispensing systems that match by NDC string. Your product may be miscounted in wholesaler inventory audits. Your market share data may include dispensing of a competitor's product misidentified as yours. A recall action for a competitor's product may be falsely matched to your product identifier and create supply disruptions for your brand.

For branded specialty products in competitive therapeutic categories — where the difference between 47% and 52% market share is measured in hundreds of millions of dollars — this level of data contamination represents a material strategic risk. And it is fully preventable if the commercial organization engages with this problem before 2030.

4. Commercial Risk Dashboard: What to Track and When

Every risk domain described in this paper has an observable indicator that will appear in standard commercial reporting within the first year of the hybrid period — for organizations without adequate NDC-12 preparation.

5- The Commercial Action Plan: What to Do and When

Seven years sounds generous. It isn't — once validation, vendor engagement, crosswalk development, and testing are mapped against actual calendar availability.

The DSCSA implementation experience taught the industry a painful lesson about compressed timelines: validation requirements for GMP and claims systems create bottlenecks that cannot be accelerated past a certain point.⁸ A seven-year runway sounds generous. It is not, once system inventory, vendor engagement, crosswalk development, staging, parallel testing, and validation are mapped against actual calendar availability.

Phase 1: 2026–2028 — Foundation

The first priority is not system remediation. It is system inventory. Commercial teams routinely underestimate how many of their systems store, process, or transmit NDCs. The inventory should cover PBM claims processing and formulary management systems, hub service platform and specialty pharmacy network NDC resolution logic, patient support program and co-pay assistance platforms, contract pricing systems (WAC, GPO, government pricing, chargebacks, rebates), commercial data analytics platforms with specific attention to how each handles the historical-to-current NDC join, PDMP and controlled substance reporting systems, specialty pharmacy dispense confirmation systems, and DSCSA serialization EPCIS records — confirming that the NDC/GTIN decoupling is addressed in the product identifier architecture.

In parallel, zero-prefix collision pairs for your product portfolio should be identified against the full FDA NDC Directory. Collision pairs that involve products in the same therapeutic category — particularly where both products are commercially active — represent the highest-priority brand protection risk and should be escalated immediately. PBM and payer trading partners should be engaged formally on dual-format readiness, and IQVIA and Symphony Health should receive written NDC-12 continuity inquiries this year.

Phase 2: 2028–2030 — Development

Once the inventory is complete, the development priority is building crosswalk infrastructure that prevents commercial revenue and market intelligence disruption. Every commercial system must maintain a crosswalk mapping each legacy 10-digit NDC to its canonical 12-digit equivalent, with the format-of-origin metadata needed to apply the correct conversion rule. Hub service platforms and patient support program platforms must correctly resolve a 10-digit enrollment record against a 12-digit dispense event post-2033 — and this resolution must be tested, not assumed.

This phase also covers chargeback and rebate system NDC field handling, MDRP/AMP/Best Price submission crosswalk mappings, and co-pay program platform updates with pre/post-2033 enrollment scenario testing. 340B program identifier governance — specifically, how covered entity eligibility will be validated against post-2033 NDCs — should be confirmed with program administrators.

Phase 3: 2030–2033 — Readiness and Validation

For commercial organizations supporting products in active launch or growth phase during the 2033–2036 hybrid period, the final preparatory phase is validation of dual-format operating capability across all commercial systems. This means running parallel claims test scenarios — submitting the same claim with 10-digit and 12-digit NDC variants — and confirming that hub service platforms can process both formats in the same dispense workflow.

Patient support program platforms deserve specific pre-validation attention. The program team should confirm exactly how a legacy patient enrollment record will be matched to a post-2033 dispense event, and what the patient-facing outcome is if the match fails. This scenario must be tested in a staging environment before the effective date. Discovering it in production — for a patient trying to access a therapy costing $8,000 per month — is not a manageable risk.

Phase 4: 2033–2036 — Hybrid Period Management

During the hybrid period, commercial organizations should monitor claim reject codes for NDC-resolution-related patterns in real time. Market intelligence continuity protocols should be activated — with crosswalk logic maintaining historical data series across the 2033 format boundary. Any brand protection anomalies should be escalated immediately to Commercial Operations. Patient support program helplines should be briefed on NDC transition-related inquiry handling. Commercial leadership should receive quarterly hybrid-period performance reports with specific metrics for claim rejection rates, hub enrollment resolution, and market data continuity.

6- Governance: Who Owns The Risk?

The organizational problem that compounds every technical risk in this paper: no function sees NDC-12 clearly as theirs — until it is too late.

The NDC-12 transition has no natural commercial owner. Regulatory affairs sees a compliance project. IT sees a data infrastructure project. Commercial leadership sees someone else's problem — until the quarterly business review tells a story nobody can explain. That gap in ownership is not neutral. It is where the risk described in this paper actually lives.

Best practice: elevate NDC-12 transition oversight to the Commercial Operations leadership team — the same governance tier that owns DSCSA compliance and serialization for commercial distribution. Designate a Commercial NDC-12 Program Lead with authority across Market Access, Patient Services, Trade, and Analytics. Ensure IT resources for commercial system updates are budgeted separately from routine IT capital — because the validation requirements for changes to claims adjudication and reimbursement systems make this a multi-year program, not a sprint.

The organizations that will navigate this most effectively are those that treat NDC-12 not as a compliance exercise but as what the companion ZCPM white paper correctly identifies as an architectural reset — the first time the pharmaceutical industry is being forced to answer what actually defines a drug product consistently across systems, use cases, and time. Organizations that unify their product identity infrastructure in response to NDC-12 will be better positioned commercially than those that only convert it.

7. Conclusion: The Revenue Risk Is Preventable — but Not if You Wait

The NDC-12 transition is being managed as a regulatory compliance project. The commercial risk embedded in it is not a compliance risk. It is a revenue continuity risk, a patient access risk, and a market intelligence risk — and it will show up in the places commercial organizations monitor most closely, not in system error logs.

Organizations that launch products between now and 2033 will build their commercial infrastructure on NDCs that will change format during the active growth phase of those products. Organizations with established brands will navigate the hybrid period with patient support programs, hub service platforms, and market data subscriptions designed for a 10-digit world.

None of the commercial consequences described in this paper are inevitable. They are all preventable — with early system inventory, crosswalk infrastructure investment, vendor engagement on data continuity, and patient program platform validation. The window to do this work correctly is 2026–2030.

The commercial teams that act early will launch faster, protect their brand's market share data integrity, maintain patient access without interruption, and enter the 2033 effective date with reimbursement infrastructure that works on day one. The ones that defer will spend 2034 explaining to their leadership why revenue recognition is delayed, why a patient support program has unexplained enrollment breaks, and why their market share report does not reconcile with their sell-out data.

Disclosure: No financial conflicts of interest. No external funding. This paper does not represent the position of the FDA or any regulatory agency.

Manish Garg is the associate director of IT applications, serialization, track & trace, at Hikma.

References

1. US Food and Drug Administration. Revising the National Drug Code format and drug label barcode requirements. Fed Regist. 2026;91(43):10749. https://www.federalregister.gov/documents/2026/03/05/2026-04368
2. FDA finalizes rule requiring 12-digit National Drug Code (NDC). Faegre Drinker Biddle & Reath LLP. March 2026. Accessed March 25, 2026. https://www.faegredrinker.com/en/insights/publications/2026/3/fda-finalizes-rule-requiring-12-digit-national-drug-code-ndc
3. 12-digit NDC format: FDA final rule timeline (2026-2033). Systech. March 2026. Accessed March 25, 2026. https://www.systechone.com/blog/fda-finalizes-12-digit-ndc-format-what-it-means-for-the-pharma-supply-chain/
4. FDA just finalized the biggest change to NDCs in decades. TrackTraceRX. March 2026. Accessed March 25, 2026. https://www.tracktracerx.com/post/fda-finalized-biggest-change-to-ndcs-in-decades
5. FDA final rule: preparing for the transition to a 12-digit NDC. LexisNexis Reed Tech. March 2026. Accessed March 25, 2026. https://www.reedtech.com/knowledge-center/fda-12-digit-ndc-final-rule/
6. Chaudhary M. The zero-prefix collision: a statistical risk model for medication errors in NDC 10/12-digit hybrid environments. Pharmatech Regulatory Intelligence Series. 2026;1.
7. Understanding the use of medicines in the U.S. 2025. IQVIA Institute for Human Data Science. May 2025. Accessed March 25, 2026. https://www.iqvia.com/insights/the-iqvia-institute/reports-and-publications/reports/understanding-the-use-of-medicines-in-the-us-2025
8. DSCSA serialization: the road to compliance. Supply Chain Brain. 2024. Accessed March 25, 2026. https://www.supplychainbrain.com/articles/39196-dscsa-serialization-the-road-to-compliance
9. FDA proposes switch to uniform, 12-digit National Drug Code format. Arnold & Porter. August 2022. Accessed March 25, 2026. https://www.arnoldporter.com/en/perspectives/advisories/2022/08/fda-proposes-switch-to-uniform-12-digit-ndc-format
10. ISMP list of high-alert medications in acute care settings. Institute for Safe Medication Practices. 2024. Accessed March 25, 2026. https://www.ismp.org/sites/default/files/attachments/2018-08/highalert2018-%20Acute%20Care.pdf
11. Drug Supply Chain Security Act (DSCSA): GTIN and NDC relationship under 12-digit transition. GS1 US. 2026. Accessed March 25, 2026. https://www.gs1us.org/industries-and-insights/by-industry/healthcare/dscsa
12. FDA introduces 12-digit NDC format: operational and serialization implications. SoftGroup. March 2026. Accessed March 25, 2026. https://www.softgroup.eu/fda-introduces-12-digit-ndc-format-operational-and-serialization-implications/
13. Formatting of NDC codes in medical and pharmacy claims. Healthcare Data Insight. June 2023. Accessed March 25, 2026. https://datainsight.health/formatting-of-ndc-codes-in-medical-and-pharmacy-claims/
14. Drug & infusion billing errors in 2026: J-codes, modifiers & ASP-NDC mismatches. 24/7 Medical Billing Services. February 2026. Accessed March 25, 2026. https://www.247medicalbillingservices.com/blog/drug-infusion-billing-errors-in-2026/
15. Medicaid Drug Rebate Program. Centers for Medicare & Medicaid Services. Updated 2026. Accessed March 25, 2026. https://www.medicaid.gov/medicaid/prescription-drugs/medicaid-drug-rebate-program/index.html
16. DSCSA compliance: milestones, more deadlines — and the road ahead. Pharmaceutical Commerce. 2026. Accessed March 25, 2026. https://www.pharmaceuticalcommerce.com/view/dscsa-compliance-milestones-more-deadlines-and-the-road-ahead
17. National Prescription Audit and Xponent: prescription information, United States. IQVIA. 2026. Accessed March 25, 2026. https://www.iqvia.com/solutions/life-sciences/information-solutions/essential-information/prescription-information
18. . Healthcare data providers: overview of Symphony Health, IQVIA, First Databank. Vega Economics. 2026. Accessed March 25, 2026. https://vegaeconomics.com/healthcare-data-providers
19. Prescription drug monitoring program. In: StatPearls. StatPearls Publishing; 2024. Accessed March 25, 2026. https://www.ncbi.nlm.nih.gov/books/NBK532299/
20. Dowell D, Ragan KR, Jones CM, Baldwin GT, Chou R. CDC clinical practice guideline for prescribing opioids for pain — United States, 2022. MMWR Recomm Rep. 2022;71(3):1-95. doi:10.15585/mmwr.rr7103a1