← Back to Resources

Employer benefits guidance · RxDC

RxDC reporting: Who’s filing for your health plan?

Your insurer, third-party administrator, and pharmacy benefit manager may each handle part of the annual Prescription Drug Data Collection report. Confirm who will submit each part and what each filer will provide as confirmation.

For: Employers and plan sponsorsScope: Filing coordinationSources reviewed: November 13, 2026

Start here

Which coverage arrangement are you coordinating?

Fully insured

Begin with the issuer’s written agreement and identify exactly which information the issuer agreed to report.

Self-funded

Map every assigned filer while keeping the plan’s responsibility visible for any required reporting a third party does not complete.

Mixed arrangement

Separate the insured and self-funded components, then map the responsible filer, period, input, and confirmation for each.

For every arrangement, ask: What will each filer submit, what employer input does it need, and what confirmation will it provide?

Keep the responsibility limits intact

  • If the issuer fails to report information it agreed in writing to report for the insured coverage it provides, the issuer is responsible for that failure for the information covered by the agreement.
  • For self-funded coverage, assigning work to a third party does not remove the plan’s responsibility if that party fails to report as required.
  • One filer generally cannot verify another filer’s submission. Obtain confirmation from each filer for its own work and track open items separately.

Before the annual filing

  1. Step 1: Confirm the reference year and current instructions. Check CMS filing resources for the instructions that apply to the year you’re reporting.
  2. Step 2: Map the parties and periods. Include vendor changes and any file or input without a confirmed owner.
  3. Step 3: Meet vendor input dates. Record each vendor’s due date for employer inputs. Vendor dates are separate from the federal filing deadline.
  4. Step 4: Track the federal deadline separately. The general deadline is June 1 following the reference year.
  5. Step 5: Collect filer-specific confirmation. Record what each filer says it submitted and when, then track rejects and corrections with that filer.

Suggested internal evidence packet

Keep applicable written agreements, the responsibility map, vendor input requests, filer-specific confirmations, rejected-file follow-up, correction records, and the coordination owner together. This is a suggested internal control packet—not required CMS documentation or proof that every reporting component was accepted.

Practical coordination aids

Three tools to build the working record

Privacy boundary

Do not enter member-level prescription, claims, health, or identifying information. These are Lvl Haus coordination aids—not CMS forms.

Resource in development

Responsibility Assignment Worksheet

Outcome: determine who owns each reporting component and period.

Example row: Insured medical component · issuer · full year · premium input due April 15 · issuer confirmation expected.

Resource in development

Filer Confirmation Log

Outcome: record what each filer says it submitted and whether follow-up remains.

Example entry: PBM · submission confirmed May 28 · identifier retained · no correction reported.

Resource in development

Vendor-Change and Correction Checklist

Outcome: prevent gaps during a vendor transition.

Example item: July 1 TPA change · predecessor period confirmed · successor input owner assigned · one reject remains open.

These cards will link to accessible webpage tools only after product, content, accessibility, privacy, and release approval. Printable formats may follow as secondary options.

Continue the work

Related employer guidance

Official sources and scope

CMS RxDC filing resources · 45 CFR § 149.720

This is an employer coordination guide, not a complete technical submission checklist. A vendor assignment alone is not proof of compliance.

This article is for general informational purposes only and does not constitute legal, tax, or benefits advice. Requirements may change. Employers should confirm current official guidance, governing agreements, and qualified-advisor input.