Patient Access
Medicare Secondary Payer: An Intake Workflow
A Medicare Secondary Payer intake workflow asks a consistent set of coverage, employment, accident, and liability questions, records the patient’s answers and source, and routes possible primary coverage to billing for verification. Intake staff collect facts and payer-order clues. They do not make legal coverage determinations or promise which payer will pay.
Last Updated: September 20, 2026
Medicare Secondary Payer, or MSP, applies when another entity may have payment responsibility before Medicare. A useful clinic workflow starts with structured questions, not an assumption that Medicare is always primary or always secondary.
The operational goal is modest and important: capture enough current facts for the practice’s qualified billing personnel to investigate payer order, submit claims correctly, and preserve the evidence used. CMS describes MSP as situations in which Medicare does not have primary payment responsibility and outlines separate provider responsibilities on its Medicare Secondary Payer overview. Contract terms, current CMS instructions, payer responses, and advice from the practice’s counsel control each case.
Use one questionnaire, then preserve the answers
Build the questionnaire into registration for new patients and into a defined update cadence for returning patients. Ask the patient or authorized representative, rather than inferring answers from age, an old scan, or the coverage already listed in the EHR. Record who answered, the date, the channel, and any documents reviewed. If the person cannot answer, mark the item unresolved and create follow-up work rather than selecting a convenient response.
The CMS MSP Manual, Chapter 3 includes model admission questions and provider billing requirements. A physician practice should adapt its script to its setting and current requirements, with billing and compliance approval. Do not shorten the workflow to “Do you have other insurance?” That question misses why coverage exists and whether an accident, employment relationship, or other circumstance needs review.
Use the same fields across phone, portal, and in-person intake. A virtual specialist may ask approved questions and enter answers with role-based access and designated exception owners. The patient intake forms workflow offers a broader queue design.
Collect facts that can signal another payer
The script should address current coverage through the patient’s or spouse’s employment, retirement status when relevant, disability or end-stage renal disease circumstances identified by the approved questionnaire, and whether the service relates to an accident, workers’ compensation matter, no-fault coverage, or liability claim. Ask for plan or claim identifiers, employer or insurer contacts, incident date, and representative details only when the answer makes them relevant.
These are clues, not conclusions. A commercial card does not prove that plan is primary, and retirement alone does not settle payer order. Intake staff should preserve the patient’s answer rather than turn uncertainty into a definitive category.
| Intake finding | Staff action | Exception owner |
|---|---|---|
| Employment-linked coverage reported | Capture subscriber, employer, plan, and effective-date facts | Billing verifies current payer order |
| Visit may relate to an accident or work injury | Capture incident and claim details; flag the encounter | Billing or designated workers’ compensation lead |
| Patient cannot answer a required question | Mark unresolved and schedule follow-up | Registrar lead or billing |
| Information conflicts with the record | Preserve both sources; do not overwrite silently | Billing resolves before claim submission |
Separate intake completion from payer verification
A completed questionnaire means the questions were answered or explicitly marked unresolved. It does not mean payer order is verified. Create a separate billing task whenever answers suggest possible primary coverage, conflict with existing coordination-of-benefits data, or lack a necessary identifier. Include the encounter, source answers, documents, and deadline so billing does not have to reconstruct the intake call.
Billing personnel review current information and determine the claim path under practice policy. Legal interpretation, disputes, or recovery questions escalate to the practice owner, compliance lead, payer, or counsel. Administrative staff must not promise that Medicare is secondary or that another carrier will pay.
Apply minimum-necessary access and documented handoffs. The role-based HIPAA staffing guide explains how to bound remote administrative work without giving every user broad record access.
Create explicit stops and escalation routes
Stop routine claim preparation when a likely primary payer has not been identified, a claim or policy number is missing, the patient gives conflicting employment dates, an accident-related visit lacks routing instructions, or a payer response contradicts the record. Define who may clear each stop and where that clearance is documented.
Follow the practice’s clinical access, emergency, financial, and legal policies. Qualified clinicians decide care; qualified practice personnel decide coverage handling and financial communication. Staff should document payer-order challenges and arrange the approved handoff.
Run a bounded daily MSP work queue
Limit the intake queue to sending the questionnaire, documenting responses, requesting missing details, and routing exceptions. Billing owns verification, payer-order resolution, claim preparation, and corrections. Only the authorized billing or financial team explains the practice’s conclusion.
A practical checklist is: confirm identity and authority to answer; complete every applicable question; record answer source and date; upload relevant cards or notices; compare responses with existing coverage data; open an exception when facts conflict; assign a named owner and due date; and document final billing disposition separately. Supervisors should sample records for skipped questions and unsupported conclusions, not merely count completed forms.
A hypothetical implementation example
Consider a hypothetical four-provider clinic that receives Medicare registrations through phone, portal, and walk-in channels. The manager creates one EHR questionnaire, an “MSP review needed” flag, and a billing work queue. Intake staff use the script and may request missing card images. They cannot change payer order. One senior biller reviews flagged visits each afternoon, and the practice administrator handles disputes or sends questions to counsel.
For the first month, the clinic samples questionnaire completion, unresolved items, pre-claim reviews, and coordination-of-benefits rework. These are implementation measures, not promised results. The manager uses patterns to adjust training or form logic without claiming guaranteed payment.
Measure reliability without rewarding guesses
Use a balanced scorecard: percentage of applicable encounters with a dated questionnaire; percentage with a named answer source; age of unresolved exceptions; percentage of flagged cases reviewed before claim release; and coordination-of-benefits rework by root cause. Review trends by intake channel and location. A fast completion rate is harmful if staff select “no” to move ahead.
Sample charts for accurate patient statements, traceable billing decisions, and old coverage carried forward without confirmation. The denial management playbook can categorize downstream rework; current contracts and policies determine corrective action.
Sources and review notes
Primary references reviewed for this workflow were the CMS Medicare Secondary Payer overview and MSP Manual, Chapter 3. CMS materials contain setting-specific instructions and exceptions, so this operational framework should be checked against the rules that apply to the practice and encounter.
This is administrative guidance, not legal advice or a payer-order determination. Practice leadership should approve the questionnaire, escalation path, and patient language with qualified personnel.
Frequently Asked Questions
Related reading
Patient Portal Proxy Access: A Practice Workflow
Build a safer portal proxy process for caregivers, legal representatives, minors, identity checks, access changes, and revocation.
Read articleMedical Records Requests: A Release-of-Information Workflow
Build a controlled medical records workflow that separates patient access from third-party releases, verifies authority, and escalates exceptions.
Read articleMedicare ABNs: An Administrative Workflow for Clinics
Create a controlled ABN workflow for Original Medicare, with case-specific approval, current CMS forms, patient choices, and clear handoffs.
Read articleRelated specialties
