Request for additional information

An RFI leaves the underlying review open

The payer may need a missing form, provider detail, assessment, progress summary, plan, order, units calculation, record excerpt, or clarification. The request may relate to prior authorization, credentialing, claim review, audit, or another process.

Identify the underlying workflow first. A claim documentation request and a prior-authorization RFI can have different owners, rights, clocks, and submission routes.

Lock the exact request

Save the notice and delivery evidence. Record:

• payer, product, member, and request identifiers
• underlying service, claim, or review
• every requested item and date range
• stated reason and criteria when supplied
• issue, receipt, response, and decision dates
• whether the payer says the review clock changes
• destination, channel, file limits, and contact
• consequences stated for no response
• correction, review, or appeal rights

Do not rely on a paraphrased task if the original notice is available.

Assign each item to the right owner

Clinical facts, assessment interpretation, treatment rationale, goals, and permitted record amendments belong to appropriately qualified clinicians. Billing, credentialing, intake, contracting, and privacy teams answer within their domains.

Administrative staff can inventory items, route work, check consistency, and transmit the approved packet. They should not create clinical evidence or change a record to fit payer criteria.

Confirm disclosure authority and scope

Determine which privacy rule, consent, authorization, payer contract, or other authority permits disclosure. Use the approved secure channel and include purpose-needed material. Redact unrelated information when appropriate and permitted.

Record exactly what was sent, by whom, to which destination, and when. Keep the matched payer receipt. A request from an unverified email address should be authenticated before any protected information leaves the practice.

A fictional RFI cohort

Forest Lane, a fictional clinic, reviews 15 RFIs whose internal response date falls this week. Twelve have verified scope, assigned owners, complete source records, privacy clearance, and a prepared response. Readiness is 12 of 15, or 80%.

One awaits payer clarification because the date range predates care. One lacks a required clinician signature under the applicable rule. One was sent to an old payer contact and must be authenticated.

Ten of the 12 ready packets are submitted with matched receipt by the internal target. Submitted-ready completion is 10 of 12, or 83.3%; original-cohort completion is 10 of 15, or 66.7%.

Check consistency before transmission

Compare member and provider identifiers, service dates, codes, units, goals, baseline periods, progress dates, signatures, and requested remedy across the cover response, forms, and records. Explain valid differences rather than forcing numbers to match.

Use a final packet index. Lock the transmitted version so later staff can reproduce it. If the payer asks for another item, create a new request event instead of silently replacing history.

Respond to ambiguity before the deadline

An RFI can ask for “all progress notes,” “updated testing,” or another broad item without enough detail to identify the relevant period or purpose. Contact the payer through the verified route and ask which records, dates, providers, and decision criteria are in scope. Preserve the question and written response.

Continue preparing the portions that are clear while clarification is pending, unless the source requires another approach. Do not let uncertainty sit without an owner. If the payer does not respond, follow the documented escalation path and protect the stated deadline as far as possible.

When the requested item does not exist, state that fact accurately and explain the applicable record or workflow. Avoid creating a retrospective document that misrepresents when an assessment, service, signature, or clinical decision occurred.

Track the next payer state

Matched receipt does not establish approval, claim acceptance, adjudication, or payment. Follow the case until the payer issues a determination, another RFI, procedural closure, or other documented state.

Determine whether the RFI pauses, restarts, or leaves a decision clock unchanged under the actual source. Avoid inventing a clock rule from another payer.

Keep CMS policy in scope

The CMS final-rule page and two official Prior Authorization API FAQ routes describe federal interoperability requirements for impacted payers. They do not create one RFI deadline or guarantee approval for all plans.

Useful measures include RFIs authenticated, response scope verified, packets ready by target, matched receipts, repeat requests by reason, and open cases by age. Keep authorization, claim, audit, and credentialing RFIs in separate cohorts.

Age unresolved clarification requests separately.

Close an RFI event only when the response, matched receipt, transmitted packet, deadline evidence, and next payer state are linked. A repeated request for the same item should prompt comparison of the two requests and escalation of the receipt trail rather than indefinite record transmission.