Payer strategy · Medicare Fee-for-Service
Choose the CMS enrollment scenario before opening PECOS.
Medicare enrollment depends on whether the work is an initial enrollment, change, reassignment, organization record, location update, revalidation, or another CMS-855 scenario. The assigned MAC and provider type determine the supporting path.
Photo: Unsplash
Operational distinctions · reviewed 2026-08-09
What to separate in a Medicare Fee-for-Service workflow
CMS, PECOS, the assigned Medicare Administrative Contractor, and current enrollment forms control the process. Printed paper-form dates and MAC instructions must be reviewed immediately before use.
Classify the transaction
Initial enrollment, revalidation, reassignment, organization enrollment, location changes, and ownership changes are not interchangeable.
Use the assigned MAC
The provider type and practice jurisdiction determine the Medicare Administrative Contractor that processes the record.
Prefer current electronic guidance
PECOS is the primary electronic workflow where supported; paper forms require a current form and scenario-specific confirmation.
Enrollment is not the last step
PTAN, effective date, reassignment, EDI, ERA/EFT, ordering/referring status, and first-claim behavior may each need validation.
Evidence worth retaining
A durable record makes it possible to see which checkpoint is complete and which one still blocks payment.
Scenario
CMS-855 transaction type, provider/entity relationship, locations, reassignment, and MAC jurisdiction.
Application
PECOS tracking, signature, supporting documents, fee or screening evidence when applicable, and development responses.
Approval
Written determination, PTAN, effective date, specialty, locations, and reassignment status.
Transactions
EDI authorization, remittance and payment enrollment, claim identifiers, and a controlled first-claim review.
Public guidance boundary
This page is not the payer's contract or an enrollment determination.
The payer's current documentation, written correspondence, executed agreement, and applicable law control. OneSource does not guarantee network need, acceptance, processing time, effective date, reimbursement, or continued availability of a workflow.
- Verify the source immediately before use
- Keep provider, entity, product, and location scope explicit
- Do not submit claims until the practice has the required participation and billing evidence
Review a Medicare Fee-for-Service workflow in practice context.
Include provider type, state, product, locations, current evidence, and the first unresolved transaction. Do not send PHI.