Medical necessity, clinical documentation, authorization, coverage, and payment are connected but separate. The treating provider determines the diagnosis, treatment plan, and clinical rationale. The payer applies the member's plan and review criteria. Administrative teams coordinate accurate records without making either party's decision.
For a direct comparison, read medical necessity versus coverage versus prior authorization. For practical documentation workflow, read how to document medical necessity for dental-to-medical claims.
Medical necessity
Definition: Medical necessity is a clinical and benefit concept used to evaluate whether a service is appropriate for diagnosing or treating a condition under applicable professional and plan criteria.
Real-life example: An oral surgeon documents the condition, functional effects, examination findings, proposed service, and rationale; the payer separately reviews the request under the plan.
Why it matters and what it does: It connects the patient's condition to the proposed care, but it does not itself guarantee authorization, coverage, or payment. The provider owns the clinical opinion; the payer controls its benefit determination.
Diagnosis
Definition: A diagnosis is the provider's identification of a disease, disorder, injury, or condition based on professional evaluation.
Real-life example: The provider records a diagnosed jaw condition after history, examination, and appropriate testing.
Why it matters and what it does: The diagnosis explains what condition is being treated. A code or administrative label cannot replace the provider's authentic diagnostic record.
Clinical indication
Definition: A clinical indication is the patient-specific reason a provider considers an examination, test, medication, or treatment appropriate.
Real-life example: Documented functional limitation prompts the provider to order imaging relevant to the treatment plan.
Why it matters and what it does: The indication links an action to the patient's condition. It should be recorded before an administrative team organizes support for payer review.
Functional impairment
Definition: Functional impairment is a documented limitation in how a person performs an activity, such as biting, chewing, speaking, breathing, swallowing, or opening the jaw.
Real-life example: The patient reports difficulty chewing, and the provider documents the history and objective examination findings.
Why it matters and what it does: Functional effects may help explain clinical significance. A patient statement alone or an image alone may be incomplete; the provider decides what evidence is relevant.
Symptom and objective finding
Definition: A symptom is an experience reported by the patient. An objective finding is something the provider observes, measures, or documents through examination or appropriate testing.
Real-life example: Pain is the symptom; measured limited opening is an objective finding.
Why it matters and what it does: Both can be important, but they are not interchangeable. Clear attribution helps the record remain accurate and auditable.
Treatment plan
Definition: A treatment plan is the provider's documented clinical plan for the patient's care, including proposed services and relevant alternatives or stages.
Real-life example: The provider identifies the planned procedure, expected units, timing, setting, and clinical goals.
Why it matters and what it does: Authorization and agreements must match what is actually planned. Administrative staff should not revise the treatment plan to fit payer preferences.
Clinical note
Definition: A clinical note records the provider's patient-specific history, examination, assessment, plan, and related care information.
Real-life example: The note describes the complaint, relevant findings, diagnosis, recommendation, and discussion with the patient.
Why it matters and what it does: The note is primary clinical evidence. Templates can help completeness but should not add facts that were not observed or discussed.
Supporting documentation
Definition: Supporting documentation is authentic information relevant to the request, such as notes, reports, images, test results, prior treatment records, or a provider statement.
Real-life example: The provider selects an examination note, imaging report, and prior treatment history that support the proposed oral-surgery request.
Why it matters and what it does: Relevant support can help a payer understand the case and may reduce avoidable requests. More pages are not automatically better; accuracy, relevance, legibility, authorization, and privacy still matter.
Imaging and imaging report
Definition: Imaging is a diagnostic tool selected by the provider when clinically appropriate. The imaging report is the qualified interpretation of the study.
Real-life example: A provider orders a panoramic radiograph because it is relevant to diagnosis and treatment planning, then includes the report when needed.
Why it matters and what it does: Images can demonstrate anatomy or pathology but do not speak for themselves. Not every patient needs imaging, and the provider must balance clinical benefit and radiation exposure. See the dental imaging glossary.
Letter of medical necessity
Definition: A letter of medical necessity, or LMN, is a provider-authored or provider-approved explanation connecting the patient's documented condition and functional needs to the proposed service.
Real-life example: The treating clinician explains diagnosis, prior care, objective findings, functional effects, proposed treatment, and why it is appropriate.
Why it matters and what it does: The letter can organize the clinical rationale, but it must agree with the underlying chart. An administrator may format or assemble the packet under provider direction but should not invent, certify, or sign clinical conclusions.
Payer medical or dental policy
Definition: A payer policy states criteria or administrative guidance the payer may use when reviewing a service. It operates within the member's plan and applicable law.
Real-life example: A policy lists documentation the payer wants for a jaw-surgery review.
Why it matters and what it does: The current version and effective date matter. A policy does not rewrite the patient's contract or replace professional judgment, and meeting criteria does not always guarantee benefits.
Coverage criteria
Definition: Coverage criteria are conditions the payer applies to determine whether a service qualifies for benefits under the plan.
Real-life example: The plan requires a covered diagnosis, documented functional impairment, and an authorized provider setting.
Why it matters and what it does: Criteria guide the payer's decision. The provider should document truthful clinical facts rather than “write to the criteria” when those facts are absent.
Prior authorization
Definition: Prior authorization is the payer's advance review of a proposed service under plan rules.
Real-life example: Before treatment, the practice submits provider-approved records and the payer responds with approved services, units, dates, or a denial.
Why it matters and what it does: The exact scope matters. A general approval may not cover every unit, date, setting, or provider. Prior authorization does not replace a separate SCA or guarantee claim payment.
Predetermination
Definition: Predetermination is a pre-service estimate or review of anticipated benefits, commonly used in dental plans. Its meaning varies by payer.
Real-life example: A dental payer returns estimated benefit amounts for a proposed treatment plan.
Why it matters and what it does: Predetermination can aid planning but may change with eligibility, annual maximum usage, coordination, or claim facts. It is not a clinical treatment decision.
Precertification
Definition: Precertification is a payer-used term for an advance eligibility or review requirement. Some payers use it similarly to authorization; others do not.
Real-life example: The plan requires a precertification number before scheduling a facility service.
Why it matters and what it does: Staff should ask what the returned number confirms and what it does not. Labels are less important than written scope and conditions.
Request for additional information
Definition: A request for additional information asks the provider or member to supply specific material needed for review.
Real-life example: The payer asks for an imaging report and detailed treatment history by a stated date.
Why it matters and what it does: The request should be assigned to the correct clinical or administrative owner. Only authentic, relevant, authorized records should be sent through the approved secure channel.
Urgent or expedited review
Definition: An urgent or expedited review is a faster payer process available when defined clinical or plan conditions are met.
Real-life example: The treating provider documents why delay may seriously affect the patient's health or function and requests the payer's urgent pathway.
Why it matters and what it does: Marking a case “urgent” is not enough. The request must be supported by provider-determined medical facts and must meet the plan or legal standard; otherwise it may be denied or routed normally.
Peer-to-peer review
Definition: Peer-to-peer review is a clinician-to-clinician discussion offered by some payers about the documented case.
Real-life example: The treating surgeon speaks with the payer's reviewing clinician about the proposed service and submitted evidence.
Why it matters and what it does: It can clarify clinical information, but administrative staff should not perform the clinical discussion. The provider should document what was reviewed and the resulting decision or next step.
Appeal and reconsideration
Definition: An appeal is a formal request to review an adverse decision. Reconsideration may be an informal or separate re-review, depending on the payer.
Real-life example: The provider submits additional authentic records and identifies why the denial should be reviewed.
Why it matters and what it does: These processes can correct errors or consider additional support. They do not guarantee approval and may have different deadlines and authority requirements.
Clinical decision, benefit decision, and payment decision
Definition: The provider makes the clinical decision. The payer makes the benefit decision under the plan. The claim and agreement process determines the payment result.
Real-life example: A provider recommends surgery, the payer authorizes only specified units, and the practice pauses to resolve scope and payment terms before nonurgent treatment.
Why it matters and what it does: Keeping these decisions separate prevents the plan from being presented as the treating clinician and prevents the administrator from being presented as the payer or provider.
What makes a documentation packet useful?
It is patient-specific, internally consistent, provider-owned, relevant to the requested service, dated, legible, securely transmitted, and matched to the payer's current request. It distinguishes patient reports from provider findings and never treats generated training illustrations as real patient evidence.
The HealthCare.gov medically necessary definition provides a general federal Marketplace description. A treating provider's clinical judgment and a payer's plan-specific coverage determination remain separate.
This glossary is general educational information, not medical, dental, legal, coding, utilization-review, privacy, or coverage advice. Administrative teams do not diagnose, determine medical necessity, select treatment, or guarantee payer decisions.
