See the Aventi 340B Rebate Model Demo.
Aventi Health logo
Book a Demo
Effective November 15, 2026

Amgen's 340B encounter data requirement: what to do before November 15

Short answer

Starting November 15, 2026, covered entities that want Amgen's 340B pricing must also submit “standard healthcare visit and service claims data” (encounter data) for their 340B pharmacy and medical claims of Amgen drugs, through the 340B ESP platform. It is due within 45 days of dispense for pharmacy claims and 60 days of administration for medical claims. Amgen says failing to submit timely, complete and accurate data will be treated as rejecting its offer of 340B pricing. Amgen is the first manufacturer to require encounter-level data, even though HRSA does not allow encounter data in the 2027 rebate pilot.[1][2][3][7]

Get a 15-min data readiness check Jump to the checklist
What changes

From claims data to claims plus encounter data

Since June 1, 2026

  • Claims-level data for all 340B pharmacy and medical dispenses of all Amgen products, submitted to 340B ESP.[3]
  • No contract pharmacies for entities with an in-house pharmacy; others may designate one contract pharmacy within 40 miles of the parent or grantee site.[3]
  • Designations can change once every 12 months and take about 10 business days to take effect.[3]

Starting November 15, 2026

  • Standard visit and service claims data (encounter data) for applicable 340B pharmacy and medical claims, submitted through 340B ESP.[2][3]
  • Due within 45 days of dispense (pharmacy) or 60 days of administration (medical).[3]
  • 340B ESP supports Pharmacy + Encounter and Medical + Encounter submissions.[5]

Required encounter fields (Pharmacy + Encounter)

These are on top of the usual pharmacy claim fields such as 340B ID, date of service, NDC-11, quantity, Rx number and service provider ID. Supplemental diagnosis codes and HCPCS modifiers are optional.[4][6]

FieldWhat it is
Encounter billing service provider IDPublic ID of the entity that billed for the patient's visit
Encounter date of serviceDate the patient was seen and received a service
Encounter rendering physician IDPublic ID of the clinician who provided the service
Encounter HCPCS codeFive-digit HCPCS code for the service on the encounter claim
Primary encounter diagnosis codeICD-10 code assigned as the primary diagnosis
Encounter place of service codeTwo-digit code for the facility type where the visit happened

Field list as published by 340B ESP on August 27, 2026. Check 340B ESP for the current specification and the Medical + Encounter fields.

Before November 15

Six steps to get ready

  1. Step 1

    Confirm you're in scope

    The policy covers all Amgen products, for both pharmacy dispenses and medical (administered) claims. Check whether your state is one of the 12 listed as exempt for in-state contract pharmacy arrangements.[3]

  2. Step 2

    Check your 340B ESP account and Amgen designation

    You need a 340B ESP account (Entity Profile tab) to submit. If you have no in-house pharmacy, your single designated contract pharmacy must be registered in OPAIS, have a HIN, and be within 40 miles of your parent or grantee site unless none is available.[3]

  3. Step 3

    Map each encounter field to a system that has it

    Encounter dates, HCPCS codes, diagnosis codes, rendering provider and place of service usually live in your EHR or billing system, not on the prescription. NACHC told HRSA that standard EHR, pharmacy and TPA reports don't produce this combined dataset, so plan the data pull now.[4][6]

  4. Step 4

    Set up the submission calendar

    Pharmacy claims with encounter data are due within 45 days of dispense and medical claims within 60 days of administration. Missing or incomplete submissions can cost you Amgen's 340B price.[3]

  5. Step 5

    Do a privacy review

    Amgen describes the data as anonymized. Powers recommends checking whether it is de-identified enough for HIPAA and any state privacy laws, and NACHC raised the same concern with HRSA.[1][6]

  6. Step 6

    Keep your rebate pilot workflow separate

    Encounter data is not permitted in the HRSA rebate pilot. Don't build Amgen's encounter fields into your 2027 rebate claims process.[7][8]

How this fits with the HRSA rebate pilot

HRSA declined to let pilot manufacturers require encounter data, purchasing data, invoice-level information or patient-level clinical information, citing the burden on covered entities.[8] HRSA approved Amgen's separate rebate plan as one of the initial 10, and that plan doesn't mention encounter data. Amgen's requirement comes through its own 340B policy, and HRSA had not acted to stop it as of Powers' alert.[1]

Amgen policyHRSA rebate pilot
BasisAmgen's 340B Program Integrity PolicyHRSA 340B Rebate Model Pilot (from Jan 1, 2027)[3][7]
Encounter dataRequired from Nov 15, 2026Not permitted at this time[3][7]
Data allowedClaims fields plus encounter fields set by 340B ESPHRSA-approved standardized pharmacy and medical claims fields only[4][7]
Other uses of dataAmgen lists MFP deduplication, replenishment eligibility and site, coding and date checksData may not be used for purposes beyond those identified in the pilot[2][3][7]

Powers also notes that manufacturers have justified claims data as a way to prevent duplicate discounts, and that it's unclear how encounter data serves that purpose. It suggests Amgen may be checking patient eligibility, which it argues should go through a manufacturer audit and HRSA's dispute process instead.[1]

Timeline

How we got here

  • May 15, 2026

    Amgen announces an update to its 340B Program Integrity Policy.[3]

  • June 1, 2026

    Claims-level data for all 340B pharmacy and medical dispenses of Amgen products becomes a condition of 340B pricing. Entities with an in-house pharmacy can no longer use contract pharmacies for Amgen drugs. Entities without one may designate a single contract pharmacy.[2][3]

  • Aug 3, 2026

    HRSA's rebate pilot notice limits manufacturer data requests to standardized claims fields and declines to require encounter data.[8]

  • Aug 26–27, 2026

    Amgen reissues its letter to covered entities with the November 15 encounter data requirement, and 340B ESP publishes its Pharmacy + Encounter field list.[3][4]

  • Oct 1, 2026

    340B ESP releases Pharmacy + Encounter and Medical + Encounter submission modules.[5]

  • Oct 6, 2026

    NACHC asks HRSA to suspend Amgen's November 15 requirements pending federal review.[6]

  • Nov 15, 2026

    Encounter data required with applicable Amgen 340B pharmacy and medical claims.[2][3]

  • Jan 1, 2027

    HRSA's 340B Rebate Model Pilot starts. Amgen's rebate plan is one of the 10 HRSA approved.[1][7]

How Aventi helps

Know your gaps before the deadline

Data readiness check

In 15 minutes we'll go through which encounter fields your EHR, billing and pharmacy systems already produce, and where the gaps are.

ESP and Beacon in one place

Aventi is an independent 340B TPA working with 300 covered entities, 24 of them hospitals. Our platform covers claims management, reporting and ESP/Beacon workflows. Read about Beacon and 340B ESP.

Ready for 2027 rebates

The rebate module is included for Aventi TPA clients. See the 340B rebate model guide and why rebates get denied.

Contract pharmacy setup

Amgen's single-pharmacy rule makes your designation matter. See how contract pharmacy setup works with a TPA.

Talk to us before November 15

Book a 15-minute call to check your Amgen encounter data readiness and your 2027 rebate plan.

Book a 15-min walkthrough Watch the rebate demo
FAQ

Amgen 340B encounter data: common questions

Beginning November 15, 2026, covered entities that want to accept Amgen's offer of 340B pricing must submit standard healthcare visit and service claims data for applicable 340B pharmacy and medical claims through 340B ESP. Amgen describes it as standard, anonymized information about the provider interaction that led to the dispense or administration.[2][3]

Covered entities that dispense or administer Amgen's 340B drugs, for both pharmacy and medical claims. Amgen's policy does not apply to in-state contract pharmacy arrangements in Arkansas, Hawaii, Louisiana, Maryland, Minnesota, Mississippi, Missouri, Nebraska, Oregon, South Dakota, Tennessee and Vermont. Amgen says covered entities in those states do not need to submit claims-level data for their in-house or contract pharmacies there.[1][3]

Claims-level data with encounter information must be submitted within 45 days of dispense for pharmacy claims and within 60 days of administration for medical claims.[3]

Amgen's FAQ says failure to submit timely, complete and accurate data will be considered a rejection of Amgen's offer of 340B pricing.[3]

Amgen says the data may help determine whether the visit took place in an eligible 340B setting, whether accurate billing and diagnosis codes were used, and whether the date of service lines up with the dispense. Its FAQ also says claims-level data is used to deduplicate Maximum Fair Price discounts and to determine eligibility for certain replenishment orders.[2][3]

Within the pilot, yes. HRSA limits pilot submissions to a set of standardized pharmacy and medical claims fields and says purchasing data and encounter-level data are not permitted as part of the pilot at this time. Amgen's requirement is part of its separate 340B Program Integrity Policy, not its rebate plan, and Powers notes HRSA had not acted to stop it.[1][7]

NACHC wrote to HRSA on October 6, 2026, asking it to suspend Amgen's November 15 requirements pending federal review, to evaluate the data elements under HIPAA with the HHS Office for Civil Rights, and to act if Amgen denies 340B pricing to entities that can't comply. Check for updates before November 15.[6]

No. This page summarizes public sources. Talk to your counsel about whether and how to submit.

Related pages

Sources

  1. Powers Pyles Sutter & Verville, Amgen Establishes Encounter Data Submission Requirement (Oct. 19, 2026, updated Oct. 29, 2026) — https://www.powerslaw.com/amgen-340b-encounter-data-requirements/
  2. Amgen, 340B Program Integrity Policy Update (company statement) — https://www.amgen.com/newsroom/company-statements/340b-program-integrity-policy-update
  3. Amgen USA, letter to covered entities and FAQ, modified August 26, 2026 (USA-CBU-82780), via 340B ESP — https://340besp.com/resources/amgen/all_claims/Amgen%2520340B_Covered%2520Entities%2520Letter_Aug%252026%25202026.pdf.pdf
  4. 340B ESP Help Center, Pharmacy + Encounter Data Submissions Requirements — https://help.340besp.com/en/articles/16560061-pharmacy-encounter-data-submissions-requirements
  5. 340B ESP Help Center, October 1, 2026 Release: New Submission Experience, Encounter Data Modules & Navigation Updates — https://help.340besp.com/en/articles/17272500-october-1-2026-release-new-submission-experience-encounter-data-modules-navigation-updates
  6. NACHC, letter to HRSA Administrator Thomas J. Engels on Amgen's expanded 340B claims and encounter data requirements (Oct. 6, 2026) — https://www.nachc.org/wp-content/uploads/2026-10-26-10-6-NACHC-Letter-to-HRSA-on-Amgen_7189.pdf
  7. HRSA, 340B Rebate Model Pilot Program — https://www.hrsa.gov/opa/340b-model-pilot-program
  8. Federal Register, Notice Regarding 340B Rebate Model Pilot Program (Aug. 3, 2026) — https://www.federalregister.gov/documents/2026-08-03/2026-15633/notice-regarding-340b-rebate-model-pilot-program

Last updated November 11, 2026. This page is general information, not legal advice. Amgen may change its policy; check 340B ESP and Amgen's current notices.