Practice Academy / Revenue cycle / Before the visit
“Insurance verified”
is not the whole answer.
Eligibility, benefits, participation, and prior authorization are different questions. Build a workflow that keeps them separate.
General physician business education • Prepared November 15, 2026
Executive summary
Before a scheduled service, a practice needs several distinct answers: Is coverage active for the relevant date? What benefits and limitations apply? Does the provider’s participation match the patient’s plan and location? Is prior authorization required, and what decision has actually been received? These checkpoints reduce uncertainty, but none should be mistaken for a guarantee that a future claim will be paid. A useful workflow preserves the source, date, scope, unresolved questions, and accountable owner for each check. Administrative staff organize the evidence; clinicians retain decisions about care and urgency. The goal is not to delay care automatically whenever a field is incomplete. It is to identify uncertainty early, escalate it appropriately, and communicate accurately with the patient.
Learning outcomes
- Explain what an eligibility response establishes and what it leaves open.
- Distinguish authorization requirements, submission, receipt, and a decision.
- Design a documented escalation pathway without delegating clinical judgment to a checklist.
Where this fits: Read the complete revenue-cycle system first. For the practice’s own payer setup, use enrollment readiness. This lesson focuses on the patient-service workflow, not credentialing the practice.
Separate checkpoints • Not universal permissions
Ask the question the evidence can answer.
For whom and which date?
For which service and conditions?
For which clinician, entity, and plan?
Required, submitted, or decided?
Later claim adjudication is a separate event. The practice still needs to submit the actual service accurately and interpret the payer’s response. Do not convert a pre-visit status into a promise of payment.
CMS states that Medicare HETS eligibility information reflects the transaction time, is not a comprehensive list of every benefit, and is not a payment guarantee. Benefits remain subject to applicable terms, conditions, limitations, exclusions, and eligibility when services occur (Centers for Medicare & Medicaid Services [CMS], 2026a). This is specifically a Medicare HETS source, not a specification for every commercial portal.
Read the boundaries of the response
Preserve the source, inquiry date, patient and plan match, relevant service date, and what was actually checked. If the response does not answer a service-specific question, record the gap and obtain the appropriate clarification. An empty field should not silently become “not required,” and a general coverage indicator should not silently become service-specific approval.
Also distinguish an estimate from final patient responsibility. Staff should explain known information and uncertainty without promising that an estimate is the final balance or that a signature removes applicable patient protections.
Track the decision, not the upload
Authorization is a workflow with distinct states.
A requirement check identifies what may need authorization and supporting documentation. It does not prove that the request was submitted or approved. In its guidance for impacted payers and the Prior Authorization API, CMS explains that a Coverage Requirements Discovery response alone neither submits an authorization request nor begins the decision clock (CMS, 2026b).
| State | Evidence to retain | Question still open |
|---|---|---|
| Requirement identified | Applicable payer, product, service, rule source, and date checked | Does this pathway apply to the actual planned service? |
| Request prepared | Required information and responsible preparer | Is the material complete and appropriately authorized for disclosure? |
| Submitted and received | Receipt, reference number, timestamp, and status source | What review deadline and escalation process actually apply? |
| Decision received | Decision, scope, conditions, dates or units when applicable | Does it match the intended clinician, location, and service? |
| Service or circumstances change | Documented change and verified follow-up requirement | Does the previous decision still apply? |
This table is an illustrative operational design, not a universal payer protocol. In Medicare initiatives described by CMS, prior authorization occurs before services, whereas pre-claim review occurs before claim submission and may follow services. Moving review earlier does not eliminate applicable medical-necessity or documentation requirements (CMS, 2025).
A dated policy example: why one universal authorization clock is unsafe
CMS’s October 14, 2026 FAQ describes maximum decision timeframes generally of 72 hours for expedited requests and seven calendar days for standard requests for affected payers under CMS-0057-F, with earlier decisions when warranted by the patient’s condition. These particular changes exclude drugs and federally facilitated Exchange QHP issuers; program-specific extensions may apply. The FAQ distinguishes Medicaid fee-for-service expedited requests from the categories eligible for an extension of up to 14 calendar days. These are calendar-time limits measured from receipt, not business-hour limits or API-only deadlines. Additional-document requests do not automatically restart the clock; verify any permitted extension under the actual program. Verify the controlling rule for the actual program rather than applying these numbers to every plan (CMS, 2026b).
Fictional case • No patient data
The appointment is approaching. The status says “uploaded.”
Coverage appears active. The portal indicates that authorization is required. Staff upload supporting documents, but the record contains neither a receipt nor a decision. The appointment is two days away.
Established: a coverage response and an identified authorization requirement.
Not established: confirmed receipt, current review status, an applicable decision deadline, or an authorization decision.
The next action is a coordinated escalation
Administrative staff verify receipt and status using the payer’s supported pathway, retain the reference, identify missing information, and notify the accountable practice lead. The treating clinician evaluates clinical urgency and care implications. Appropriate staff communicate the unresolved financial or administrative questions to the patient using the practice’s approved process. Legal or reimbursement questions go to qualified advisors when needed.
This case does not establish an automatic cancellation rule. Nor does it authorize nonclinical staff to decide medical necessity, urgency, or the patient’s legal financial obligation.
Knowledge check: is the uploaded document proof of authorization?
No. An upload, receipt, and decision are different evidence. Confirm the current state, applicable requirements, and next action. Do not promise approval or payment while the decision remains unverified.
Say what is known
An illustrative communication: “We have checked the coverage information currently available. We are still confirming the authorization status for this service. We will explain what remains unresolved and any available estimate. The final claim decision may differ.” Adapt the wording to the actual facts, clinical needs, payer rules, and applicable patient protections.
Close the loop
Make recurring exceptions visible.
After the service, compare the actual claim and payer response with the information the team relied on. A mismatch may involve changed service details, an inaccurate identifier, a missing condition, or another cause. Investigate rather than assuming every denial is an authorization failure.
- Define the population: which scheduled services require this specific check?
- Measure timeliness: how many required checks were complete by the practice’s defined review point?
- Measure unresolved work: how old are open items, who owns them, and what blocks resolution?
- Measure outcomes separately: distinguish missing evidence, authorization mismatches, claim rejection, adjudicated denial, and actual cash.
For example, 180 checks completed by the review point out of 200 checks required equals 90% timely completion. It is not a 90% authorization approval rate or payment rate. The fictional calculation teaches denominator discipline; it does not propose a national target.
MedCBO’s role in coordination, reporting, or separately scoped execution depends on the signed engagement. Clinicians retain clinical decisions, and payer requirements must be verified for the actual situation. Continue with vendor handoffs and the complete RCM system.
References & source notes
Centers for Medicare & Medicaid Services. (2025, September 15). Prior authorization and pre-claim review initiatives. CMS program overview.
Centers for Medicare & Medicaid Services. (2026a, May). HETS 270/271 5010 companion guide (Version 15-1). Official guide.
Centers for Medicare & Medicaid Services. (2026b, October 14). Improving prior authorization processes. CMS frequently asked questions.
Sources checked November 15, 2026. Workflow, cases, and metric examples are educational synthesis, not a validated protocol or empirical performance claim. Requirements differ by state, payer, program, product, service, and facts. General education only; not clinical, legal, coding, or reimbursement advice.