One of the most common—and most consequential—questions in 340B operations is deceptively simple: how do you identify a 340B claim? The answer determines whether a prescription or administration can be replenished at 340B pricing, whether savings are captured correctly, and whether the organization can defend its decisions during an audit.
Identifying a 340B claim is not about a single flag or code. It is the result of a multi-step eligibility determination that pulls together encounter data, provider relationships, site-of-service rules, patient status, payer considerations, and documentation standards. When any part of that chain breaks, claims may be incorrectly included or excluded—creating compliance risk or financial leakage.
This article explains how to identify a 340B claim in practice, what systems and controls are required, and where organizations most often go wrong.
Need help validating your 340B claim identification logic?
Contact Cooper Strategy
What a 340B Claim Is—and Is Not
Defining a 340B Claim
A 340B claim is a prescription or drug administration that meets all 340B eligibility requirements and is therefore eligible for replenishment using 340B-priced drugs. The claim itself does not “become” 340B at the pharmacy counter or point of care. Instead, it is identified as 340B after eligibility validation through internal systems or a third-party administrator.
What Does Not Make a Claim 340B
A claim is not 340B simply because:
- The patient is uninsured or underinsured
- The drug is expensive
- The prescription was written by a hospital-affiliated provider
- The drug was dispensed at a contract pharmacy
Eligibility must be proven, not assumed.
The Core Elements Used to Identify a 340B Claim
Patient Eligibility Under the 340B Patient Definition
To identify a 340B claim, the covered entity must confirm that:
- The covered entity provided a healthcare service to the patient
- The service resulted in the prescription or administration of the drug
- The covered entity maintains the medical record
- The patient was not an inpatient at the time the drug was ordered or administered
This encounter-level validation is the foundation of claim identification.
Outpatient Status Verification
Only outpatient drugs qualify for 340B. Systems must accurately distinguish:
- Outpatient visits
- Observation stays
- Emergency department encounters
- Same-day admissions that convert to inpatient
Misclassification is one of the most common causes of incorrect claim identification.
Site-of-Service Eligibility
The location where care occurred must be:
- Registered in HRSA’s database as an eligible outpatient site
- Aligned with the most recently filed cost report (for hospitals)
- Properly mapped in EHR, billing, and TPA systems
Claims tied to unregistered sites cannot be identified as 340B.
Provider Eligibility and Attribution
The prescribing or rendering provider must be:
- Employed by or contracted with the covered entity
- Acting within the scope of services
- Properly mapped in eligibility systems
Incorrect provider attribution invalidates otherwise eligible claims.
How Systems Identify a 340B Claim
Role of the EHR
The EHR captures the encounter that establishes eligibility. Key data elements include:
- Visit type
- Provider identity
- Location of service
- Clinical documentation
- Order details
Incomplete or inconsistent EHR data undermines claim identification.
Role of the TPA or Split-Billing System
The TPA applies eligibility logic by:
- Linking encounters to prescriptions or administrations
- Applying patient definition rules
- Validating outpatient status
- Excluding ineligible claims
- Accumulating eligible usage
The TPA does not create eligibility—it evaluates it.
Role of Pharmacy Systems
Pharmacy systems provide:
- NDC-level detail
- Dispense quantities
- Fill dates
- Pharmacy identifiers
This data must align precisely with eligibility determinations.
Identifying 340B Claims in Different Settings
In-House Pharmacy Claims
For in-house dispensing, 340B claims are identified through:
- Internal eligibility logic
- Virtual inventory accumulation
- Replenishment reporting
Daily reconciliation is essential.
Contract Pharmacy Claims
Contract pharmacy claims are identified through:
- Prescription-level eligibility evaluation
- Prescriber attribution logic
- Duplicate discount prevention controls
- Claim routing rules
Contract pharmacy claims receive heightened scrutiny.
Outpatient Infusion and Clinic Administrations
For administered drugs, identification depends on:
- Accurate charge capture
- Correct HCPCS-to-NDC mapping
- Encounter documentation
- Split-billing configuration
Errors here often result in lost savings or diversion findings.
Duplicate Discount Considerations
Medicaid and Managed Care
A claim may meet all other eligibility criteria but still be excluded if:
- It creates a duplicate discount
- Medicaid carve-in or carve-out logic is misapplied
- Managed Medicaid identifiers are incorrect
Duplicate discount prevention is a mandatory step in claim identification.
Common Errors in Identifying 340B Claims
Assuming Eligibility Without Documentation
Claims cannot be identified as 340B without documented encounters.
Relying Solely on Prescriber Affiliation
Provider employment alone does not establish eligibility.
Ignoring Site Registration Changes
New or moved clinics must be registered before claims qualify.
Poor Data Integration
Misaligned systems result in false inclusions or exclusions.
Overreliance on Vendor Determinations
Covered entities are ultimately responsible for claim identification accuracy.
Best Practices for Accurate 340B Claim Identification
Standardize Eligibility Rules
Eligibility logic should be clearly documented and consistently applied.
Perform Routine Claim Sampling
Sampling verifies that identified 340B claims meet requirements.
Monitor Exception Reports Daily
Exception reports highlight:
- Missing encounters
- Unmapped providers
- Site mismatches
- Eligibility conflicts
Maintain Audit-Ready Documentation
Each identified 340B claim should be defensible through data and records.
Cooper Strategy helps organizations validate and strengthen 340B claim identification processes.
Contact us to learn more
Conclusion
Identifying a 340B claim is a data-driven, documentation-dependent process—not a simple label. Accurate claim identification protects compliance, ensures appropriate savings capture, and strengthens audit readiness.
Organizations that invest in clear eligibility logic, strong system integration, and continuous monitoring are best positioned to identify 340B claims correctly and defend those decisions under scrutiny.
Frequently Asked Questions About How to Identify a 340B Claim
Is there a specific code that identifies a 340B claim?
No. There is no universal billing code that automatically identifies a 340B claim. Instead, claims are identified through eligibility logic applied after the fact using encounter data, provider information, site registration status, and patient definition criteria. Some systems use internal indicators or modifiers, but these are the result of eligibility determination—not the cause of it.
Can a commercially insured prescription be a 340B claim?
Yes. Insurance type does not determine 340B eligibility. A commercially insured prescription can qualify if all patient definition, outpatient status, provider, and site-of-service requirements are met and no duplicate discount occurs. Many high-value 340B claims involve commercial insurance.
How do audits verify whether a claim was correctly identified as 340B?
Auditors review encounter documentation, provider attribution, site registration, and system logic used to identify the claim. They expect covered entities to reproduce eligibility determinations using data and documentation. Claims identified as 340B without supporting evidence are at high risk for findings.
Why do organizations miss eligible 340B claims?
Missed claims often result from incomplete documentation, unmapped providers, incorrect site registration, or integration failures between systems. Referral-based claims and specialty prescriptions are particularly vulnerable to being missed if workflows are not designed intentionally.
How can Cooper Strategy help improve 340B claim identification?
Cooper Strategy evaluates eligibility logic, audits claim identification processes, reviews system integration, and helps organizations correct gaps that lead to missed savings or compliance risk. We help translate regulatory requirements into operational controls that teams can manage confidently.