A payer-ready case file puts all key records in one clear order. A reviewer should be able to trace the case from start to close.
The file does not make support for a claim. It keeps what took place and flags what is missing. It also keeps office work apart from the provider's clinical role. A neat folder does not prove coverage or prior approval. It does not prove claim receipt or payment.
What should define the case file before records are collected?
Set the scope first. Name the patient, plan, provider, care event, and file use.
Start with a copyable index. Use a fixed file name such as section, source date, and version. Keep the true source name when policy requires it.
| Section | Source and date or version | Owner | Status and open item |
|---|---|---|---|
| Case cover | Approved index and current version. | Case owner. | Scope, status, and open questions. |
| Provider record | Chart, report, or order and source date. | Provider or record owner. | Complete, pending, or in conflict. |
| Payer evidence | Full payer reply and reply date. | Benefit or approval owner. | Scope and requested item. |
| Claim | Claim version and send proof. | Billing owner. | Sent, accepted, rejected, or pending. |
| Remittance and payment | Payer reply and deposit reference. | Posting owner. | Matched, unmatched, or under review. |
| Close or reopen | Close version, date, and later evidence. | Case owner. | Closed, open, or reopened with reason. |
Do not turn an unsure fact into a set fact. The index should point to the true source, not replace it.
The dental-to-medical record checklist gives a sound start. The real payer request and case facts still control each file.
Which provider records belong in the file?
Use only relevant records from the provider's normal chart process.
The file may hold the provider's signed or done chart note. It may hold orders, reports, images, care plans, and referrals. Add only items tied to the case use. The right set will vary by care and payer request. Office staff must not make missing care facts. They must not pick a health finding or rewrite the provider's reason.
CMS says providers are responsible for documenting each encounter completely, accurately, and on time. See its Documentation Matters toolkit. That guidance supports careful documentation and file order. It does not say one record set will meet a commercial plan's needs.
Send a missing or clashing record to the right source owner. Keep any valid fix or added note under the practice's chart rules.
How should payer and authorization evidence be organized?
File payer proof by event, source, date, and scope.
Keep plan status and benefit replies apart from prior approval replies. Save the full request and proof of send. Keep payer receipts, record requests, sent replies, the final choice, call numbers, and call logs. Store any signed network or case terms on their own. Do not treat them as the same as prior approval.
The file should make these distinctions visible:
- Eligibility reports plan status for a set time.
- Coverage rests on plan terms and case facts.
- Prior approval covers only its written scope.
- Network terms cover provider and pay ties.
- Payment follows claim review and account checks.
- The patient amount needs its own review.
The care need, coverage, and prior approval guide helps staff keep these choices apart.
How should claim versions and status records be maintained?
Link each claim version to its source, send event, and payer reply.
Label the first, fixed, replaced, or new claim. Do not erase its past. Keep the build and send dates, route, receipt, vendor report, payer status, claim reply, and related notes. A status note must name its source. It must not turn a pending reply into a yes or no.
If a claim changes, note what changed and why. Name who approved the office step. Link the change to its true source. Never change a chart just to match a claim. The claim status guide shows why status, claim review, and payment are distinct.
How should the file track ownership and deadlines?
Give each open item an owner, next step, source, and due date.
A work log can track missing records and payer questions. It can also track approval updates, claim follow-up, payer reply review, a second claim, and account holds. Get due dates from current plan files, payer steps, signed terms, or other valid rules. The right owner should check them.
Access by role helps stop unapproved change. The file should show who added, read, sent, or fixed an item. A shared folder needs clear names and version rules. It also needs a change log. Without them, staff may not be able to trace the case.
What does a payer-ready file look like in practice?
A clear file lets another reviewer trace the case without memory.
Hypothetical scenario: A payer asks a dental practice for more claim records. The case index lists the provider chart and first approval request. It also lists the written reply, filed claim, payer request, and due date. The due date comes from the payer notice.
Staff check the request against the file list. One requested chart item is not there. They do not make it or describe it from memory. They send the question to the provider. The provider decides what the chart supports. Staff then send the approved records. They keep proof of send and update the work log.
Later, the payer sends a claim reply. The practice matches it to the claim and payment. It does this before case close. The file keeps the result and any open items.
Close-or-reopen check: Confirm the final claim version and send proof. Match the remittance to that claim. Match the payment to its deposit. Route any adjustment, other payer, patient balance, or open item to its owner. Save the close date, reviewer, status, and evidence links. If a later reply, reversal, corrected claim, or new record changes the account, keep the first close record and add a dated reopen event.
Frequently asked questions
Should every record in the patient chart be sent to the payer?
No. Follow the real request, written approval, data rules, and skilled advice. Send only records that fit the request and have proper approval.
Can a case file prove that a claim will be paid?
No. Good order helps staff review and reply. It does not prove plan status, coverage, prior approval, network terms, payment, or the patient share.
This guide is general administrative information, not legal, medical, clinical, dental, coding, documentation, privacy, security, contract, accounting, financial, patient-billing, or coverage advice, and not a statement that any workflow, record, request, response, claim, payment, adjustment, deadline, decision, or outcome is accurate, complete, compliant, authorized, covered, or payable. Requirements and outcomes vary by payer, program, plan, patient, provider, service, record, agreement, system, jurisdiction, and date.
