For radiation oncology authorization, patient-access, scheduling, clinical-operations, revenue-cycle, and practice leaders who are accountable for keeping an approved treatment course aligned as the plan changes.
Keep every authorized radiation treatment course aligned through the last fraction
Turn a scattered series of consultation, simulation, planning, image-guidance, delivery, fraction, and replanning authorizations into one source-linked course record—without letting software make a clinical, coding, coverage, or patient-liability decision.
Evaluate this workflow when staff can obtain an initial approval but still spend the treatment course reconciling component scope, approved technique, fraction count, date validity, plan versions, peer-review tasks, and payer responses. The buying question is not whether AI can send another form. It is whether your team can see exactly what was requested, submitted, authorized, changed, delivered, and still unresolved before a downstream handoff.
An approval can go stale while the treatment course is still moving
Radiation oncology prior authorization is not a single front-desk transaction. It can span consultation, simulation, dosimetry, treatment planning, image guidance, treatment delivery, and a payer-defined number of fractions, with pathology and imaging evidence feeding the request. In ASTRO's 2024 nationwide physician survey, 80% of respondents said prior authorization required staff-time reallocation, 64% said it required additional hiring, and respondents estimated that 73% of initially denied requests were later overturned on appeal. Those are survey findings—not QuickIntell outcomes—and the reviewed ASTRO source appears below.
One course is represented by several disconnected service components
The order, simulation record, planning work, dosimetry, image guidance, delivery services, and fraction schedule may live in different records and may not be described the same way in the request, payer response, scheduler, and billing work queue. A generic approved label can hide which component, technique, site, count, or date span the payer actually addressed.
Operational consequence
Staff repeatedly reopen portals, faxes, notes, and spreadsheets to answer basic scope questions. Scheduling may proceed on an assumption, billing may inherit an unverified mapping, and the team may discover a partial approval only when a deadline or treatment date is close.
The clinical plan changes, but the authorization record does not
When an authorized clinician creates a new treatment-plan version or directs replanning, the administrative effect is not self-evident. The technique description, planning or delivery components, fraction count, service dates, setting, or other payer-facing facts may stay the same, change, or remain uncertain until qualified staff compare the governing records and current payer instructions.
Operational consequence
An earlier payer response can be treated as if it automatically covers the revised course. Alternatively, staff may restart work that did not need to be reopened. Both paths consume time and can leave the next fraction, amendment, claim, or patient communication without a defensible source trail.
Validity is tracked as a date instead of a course ledger
An authorization response may contain dates, units, visits, fractions, technique language, provider or facility scope, and conditions that do not line up with the schedule. A date-only reminder cannot show whether scope was used, whether a missed or added visit changes the count, or whether a payer response belongs to the current request version.
Operational consequence
Renewal and amendment work starts late, authorized scope is difficult to reconcile, and staff cannot explain why a course was marked ready, held, or expired. Uncertainty is passed to therapists, schedulers, coders, financial counselors, and patients instead of being resolved by the right owner.
Peer review and appeal work depends on individual memory
A denial or partial approval can trigger a narrow scheduling window, a request for more information, a peer-to-peer discussion, a reconsideration, or an appeal. The response reason, current packet, plan version, contact attempt, deadline, and clinician availability are often maintained in separate queues with no shared chronology.
Operational consequence
Teams duplicate outreach, miss the response that governs, or ask clinicians to reconstruct the case under time pressure. A successful transmission may be mistaken for a completed review, and a later overturned denial can remain disconnected from the authorization and billing records it should update.
Pathology and imaging evidence is present but not decision-ready
A report may exist in the EHR, image repository, outside-record inbox, or scanned document store without being clearly linked to the current treatment-course request. Administrative software can confirm identity, provenance, date, document type, and requested criterion, but it cannot interpret findings or decide that the evidence establishes medical necessity.
Operational consequence
Staff either submit an oversized chart, send an incomplete packet, or wait without a named evidence owner. Reviewers spend time locating the relevant passage, while privacy and clinical risk increase when unrelated records move through payer channels.
A named agent team with visible decision boundaries
Each agent handles a defined part of the treatment-course authorization and change management workflow. Confidence signals and human escalation remain visible rather than being hidden behind an automation label.
Course Identity and Payer Path Agent
Creates the administrative identity for one radiation treatment course and keeps payer, plan, product, provider, facility, treatment-site description, and request-version context attached to every downstream task. It does not establish coverage, medical necessity, network status, or the clinically appropriate course.
Inputs
- Authenticated registration, coverage, ordering, provider, facility, and referral fields from buyer-designated systems
- Current consultation, simulation, and treatment-course order references with version timestamps
- Buyer-approved payer routing tables, delegate relationships, submission channels, and effective dates
- Existing request, response, and coordination-of-benefits records for the same administrative course
Checks
- Resolve duplicate or conflicting course identities before work is combined
- Confirm that payer, plan product, provider, facility, and requested service context belong to the same current request
- Separate Original Medicare, Medicare Advantage, Medicaid, commercial, and liability or workers' compensation paths
- Detect a coverage, provider, facility, or payer change that may invalidate downstream readiness
- Keep unknown eligibility, coordination, network, and delegate fields visible instead of inferring an answer
Outputs
- Versioned course cover record with source provenance
- Payer-path decision map with unresolved ownership
- Change alert when identity or coverage context makes prior work potentially stale
- Confidence method
- Confidence reflects agreement among authenticated sources, exact request-to-plan matching, source freshness, duplicate-resolution quality, and completion of buyer-defined identity fields. It measures administrative identity confidence only, not whether treatment is clinically appropriate or covered.
- Low-confidence action
- The agent keeps the course unmerged or on administrative hold, shows the conflicting source values, and assigns a verification task to patient access or authorization staff. It never chooses the most convenient payer path or carries an old approval into a new product or facility context.
- Human escalation
- Patient-access and authorization leaders resolve identity and coverage questions; contracting staff resolve network or delegate questions; qualified clinical staff resolve treatment-course identity conflicts; compliance or legal personnel handle disputed coordination and liability issues.
Clinical Evidence Retrieval Agent
Finds buyer-permitted consultation notes, pathology, imaging, prior-treatment history, orders, and other requested records, then maps them to the payer's stated evidence request. It identifies where information is documented but never interprets a finding, authors clinical rationale, or decides that a criterion is satisfied.
Inputs
- The current payer request, questionnaire, form, and evidence checklist from an approved source
- Authenticated EHR, pathology, imaging, document-management, and outside-record indexes exposed for the configured purpose
- Current treatment-course and plan-version references approved by the responsible clinical owner
- Organization rules for permitted disclosure, document freshness, and qualified review
Checks
- Match every requested item to a source document, precise passage, human response, or unresolved state
- Confirm that each record belongs to the current course, request version, service context, and approved disclosure purpose
- Distinguish a missing record from a record that exists but still requires clinical interpretation
- Flag conflicting dates, treatment-site descriptions, plan versions, or prior-therapy references
- Exclude unrelated material under the buyer's approved privacy and minimum-necessary policy where applicable
Outputs
- Requirement-to-source evidence map with provenance
- Focused retrieval queue with named record owners
- Human-review packet index that separates extracted facts from clinical judgment
- Confidence method
- Confidence combines document identity, provenance, readability, extraction quality, request-version match, required-field coverage, and reviewer acknowledgement. A complete document list does not create confidence in clinical meaning, medical necessity, or payer acceptance.
- Low-confidence action
- The agent withholds a complete status, displays the uncertain passage or missing source, and routes the item to the authorized clinician, imaging, pathology, or records team. It does not summarize an unreadable report, infer a diagnosis, or substitute a different document.
- Human escalation
- Radiation oncologists and other qualified clinicians interpret clinical evidence and approve rationale; pathology and imaging professionals control their reports; health-information and privacy staff resolve record access or disclosure questions; authorization staff control the administrative packet.
Component, Code, and Fraction Scope Agent
Builds a component ledger for consultation, simulation, dosimetry, treatment planning, image guidance, delivery, and payer-defined fractions or units. It compares explicit descriptions and code references across the request and response but never selects a code, technique, fractionation plan, dose, or billable service.
Inputs
- Current human-approved treatment-course description and plan-version metadata
- Buyer-maintained service catalog and current licensed code references available to authorized users
- Requested, submitted, and payer-returned component, technique, unit, visit, fraction, date, provider, and facility fields
- Qualified coding, revenue-integrity, and authorization decisions recorded for the course
Checks
- Keep consultation, simulation, planning, dosimetry, image guidance, delivery, and other configured components as separate states
- Compare requested, submitted, authorized, scheduled, delivered, and billed-preparation fields without collapsing them
- Show source-to-source differences in descriptors, code references, units, fractions, dates, provider, and facility
- Require effective-date and authoritative-code review when a descriptor or code set has changed
- Block arithmetic or scope conclusions when the payer's unit basis is absent or ambiguous
Outputs
- Source-linked component and fraction concordance ledger
- Mismatch queue for authorization, coding, scheduling, or payer clarification
- Human sign-off record for the administrative scope used downstream
- Confidence method
- Confidence is based on exact source agreement, current reference dates, complete component mapping, explicit unit labels, verified response scope, and qualified reviewer sign-off. It is not a coding opinion, clinical plan review, or prediction that a claim will pay.
- Low-confidence action
- The affected component remains unknown or on hold, with the source values displayed side by side for review. The agent does not choose a code that appears to fit, convert an unclear fraction basis, or change the clinical plan to match an authorization response.
- Human escalation
- Radiation oncologists retain treatment authority; dosimetrists, medical physicists, and therapists retain their professional responsibilities; qualified coders and revenue-integrity staff establish code treatment; payer representatives clarify authorized scope; operations leaders approve release rules.
Response and Course Ledger Agent
Captures payer acknowledgements and decisions as source artifacts, classifies only the scope they explicitly state, and tracks validity across the treatment course. It does not turn a portal success message, estimated turnaround, silence, or a partial response into an approval.
Inputs
- Responses received through buyer-approved portal, API, clearinghouse, fax, phone, or mail workflows
- The exact submitted packet version and acknowledgement history
- Payer-returned status, scope, limits, dates, fractions, units, provider, facility, and reason fields
- Verified scheduling and service events used only for administrative reconciliation
Checks
- Match each response to the correct payer, product, course, request version, provider, facility, and submission
- Distinguish approved, partially approved, denied, pending, more-information, cancelled, expired, and indeterminate states
- Preserve the response artifact and stated limitation instead of expanding scope through interpretation
- Reconcile date, fraction, unit, and component balances only from verified events
- Alert before buyer-defined deadlines while keeping unknown counters and dates visibly unknown
Outputs
- Current authorization ledger with requested, submitted, authorized, used, remaining, expired, and unknown scope
- Source-linked response record and downstream impact notice
- Role-owned queue for additional information, amendment, renewal, peer review, appeal, or clarification
- Confidence method
- Confidence reflects channel authentication, exact request-response matching, response completeness, event freshness, source agreement, and downstream acknowledgement. A copied status or portal banner without the governing response artifact is not treated as high confidence.
- Low-confidence action
- The last verified state remains in force, the uncertain response is marked pending, and authorized staff receive a reconciliation task through an approved channel. The agent never assumes approval from silence or declares unused scope from an unverified schedule event.
- Human escalation
- Authorization staff validate payer responses and next actions; schedulers and clinical operations confirm verified course events; payer representatives clarify determinations; coding and billing staff decide claim handling; financial counselors control patient-facing cost communication.
Replanning Change-Impact Agent
Detects a new treatment-plan or course version and compares its administrative attributes with the version tied to the payer response. It identifies potentially affected components and deadlines but does not decide why replanning is needed, whether the revised plan is safe, or whether payer notification is required.
Inputs
- Authenticated treatment-plan version events and human-approved administrative descriptors
- The version frozen at submission and the version linked to the current payer response
- Current component, technique, fraction, unit, date, provider, facility, and site fields available for comparison
- Verified payer change, amendment, notification, and retrospective-review instructions from approved sources
Checks
- Confirm that a version event is final enough under local policy to trigger administrative comparison
- Identify unchanged, changed, and unknown payer-facing attributes without interpreting clinical content
- Trace which packet, authorization, schedule, coding, financial, and billing records depend on the prior version
- Apply current payer-product and effective-date instructions rather than a universal replan rule
- Prevent an earlier ready state from surviving an unresolved material change
Outputs
- Before-and-after administrative change map with source lineage
- Affected-record and affected-owner queue
- Human-reviewable amendment, notification, new-request, or no-change work package
- Confidence method
- Confidence uses authenticated version lineage, exact field comparison, current payer-source matching, dependency completeness, and human confirmation of the administrative descriptors. It does not express confidence in the revised treatment plan or predict a payer's change decision.
- Low-confidence action
- The relevant course state moves to human review, prior approval remains historical evidence, and downstream readiness is paused according to buyer-defined risk rules. The agent does not label an unclear change immaterial or submit a retrospective request without authorized review.
- Human escalation
- The radiation oncologist, medical physicist, dosimetrist, and other qualified professionals control clinical replanning; authorization leadership decides the payer path; coding and revenue staff assess downstream handling; compliance or legal personnel review disputed retrospective or notice questions.
Peer Review and Appeal Orchestration Agent
Organizes a denial, partial approval, or more-information response into an accountable chronology; coordinates peer-review availability; and assembles the current source packet for reconsideration or appeal. It never impersonates a clinician, invents rationale, or promises that an adverse decision will be overturned.
Inputs
- The governing payer response, reason, scope, instructions, and deadlines
- Current submitted packet, treatment-course version, evidence map, and change history
- Approved clinician availability, payer contact channels, and buyer-defined escalation rules
- Human-authored clinical rationale, attestation, appeal decision, and submission approval
Checks
- Verify the response and deadline against the correct plan, product, request, course version, and appeal level
- Keep peer review, additional-information response, reconsideration, internal appeal, and external review as distinct paths
- Schedule only within approved calendars and channels, with acknowledgement and fallback ownership
- Require the appropriate qualified clinician for professional discussion and clinical statements
- Record every attempt, submitted version, receipt, decision, and downstream reconciliation event
Outputs
- Peer-review scheduling packet with availability and acknowledgement status
- Human-approved reconsideration or appeal packet and submission manifest
- Complete denial-to-disposition chronology with unresolved deadlines
- Confidence method
- Confidence combines response authenticity, deadline calculation, path and level matching, current evidence completeness, clinician authorization, schedule acknowledgement, and submission receipt. It does not estimate appeal success or the clinical merit of a request.
- Low-confidence action
- The deadline or path remains unconfirmed, a named human owner receives the source conflict, and no unsupported submission occurs. The agent does not select an appeal right, create clinical language, or treat an unacknowledged peer-review request as scheduled.
- Human escalation
- Qualified clinicians conduct peer discussions and approve clinical rationale; authorization and appeal specialists choose and submit the administrative path; payer personnel make coverage decisions; compliance, contracting, or legal staff interpret disputed rights, contracts, notices, and deadlines.
The operating sequence, evidence by evidence
The sequence separates agent work from accountable human checkpoints so teams can see what moves forward, what stays pending, and why.
Patient access and radiation oncology operations
Open one treatment-course record before collecting documents
The workflow first establishes the current course identity, coverage path, ordering context, provider and facility, service description, and plan-version reference. Existing requests and responses are linked as evidence rather than copied into a new unqualified approved status.
Agent actions
- Reconcile identity and payer-path fields across designated sources
- Attach prior request and response lineage to the current course
- Assign every conflict or missing field to a named role
Evidence produced
- Versioned course cover record
- Payer and delegate routing map
- Identity-conflict and coordination queue
Human checkpoint: Patient-access staff confirm the coverage and administrative identity; radiation oncology staff confirm which treatment-course record governs. This checkpoint does not establish clinical appropriateness, coverage, or authorization.
Authorization team and clinical evidence owners
Map payer requirements to current pathology, imaging, and clinical sources
The current payer request is decomposed into evidence items, questions, attestations, and administrative fields. Permitted records are retrieved with provenance and linked to the current course version, while interpretation and clinical conclusions remain with qualified people.
Agent actions
- Create a requirement-to-source matrix
- Retrieve only buyer-approved records for the configured purpose
- Separate present, missing, conflicting, stale, and human-judgment items
Evidence produced
- Source-linked evidence map
- Focused document-request queue
- Clinical-review and disclosure exceptions
Human checkpoint: The authorized clinician approves clinical statements and identifies the evidence that supports the request; privacy or health-information staff resolve disclosure questions; authorization staff accept the administrative completeness assessment.
Authorization, coding, and revenue integrity
Build and approve the component-level course request
Consultation, simulation, dosimetry, planning, image guidance, delivery, fraction, unit, date, provider, and facility fields are kept separate in the request ledger. The packet shows exactly which values came from which source and where qualified review is still required.
Agent actions
- Compare the clinical source description with configured administrative references
- Assemble a payer-specific packet and explicit component scope
- Run version, source, signature, channel, and disclosure checks
Evidence produced
- Human-reviewable course authorization packet
- Component and fraction concordance ledger
- Clinical, coding, and administrative approval record
Human checkpoint: The radiation oncologist controls treatment statements, qualified coding staff control code decisions, and authorized operations staff approve the submission. Software does not alter a course to fit payer criteria.
Authorization operations
Submit through a supervised channel and capture the governing response
An authorized person releases or supervises the exact approved version through a validated channel. The workflow retains the submission manifest, acknowledgements, requests for information, and governing payer response without treating transmission success as a decision.
Agent actions
- Prepare channel-specific work with explicit release authority
- Record acknowledgement and follow-up attempts
- Match the returned response to the submitted course version and scope
Evidence produced
- Submission manifest and receipt history
- Source-linked payer response
- Additional-information, partial-approval, denial, or clarification queue
Human checkpoint: Authorization staff inspect the source response and determine the operational next step. Payer personnel retain determination authority, and qualified clinicians answer clinical questions or participate in peer review.
Scheduling and radiation oncology operations
Reconcile the authorization with the scheduled course
Before the first and subsequent configured handoffs, the authorized component, technique, date, fraction, unit, provider, and facility scope is compared with the current schedule and course version. A single ready label cannot hide a partial, expired, or unknown field.
Agent actions
- Calculate administrative scope only from verified response and event records
- Expose scheduled-to-authorized differences and approaching validity limits
- Produce a ready, hold, unknown, or human-review explanation
Evidence produced
- Current course-authorization ledger
- Schedule-to-scope exception list
- Human release record and unresolved-condition list
Human checkpoint: Scheduling, clinical operations, authorization, and revenue-cycle owners decide whether their configured administrative conditions are met. The release is not a treatment decision, safety clearance, or guarantee of payment.
Radiation oncology operations and authorization leadership
Detect replanning and reopen only the affected administrative work
A new plan or course version triggers a source-by-source administrative comparison. The workflow identifies affected components, responses, schedules, and billing dependencies, then routes the case under current payer-specific change instructions instead of applying a universal reauthorization rule.
Agent actions
- Compare the authorized and current administrative versions
- Invalidate dependent readiness where a material field is unresolved
- Draft a source-linked amendment, notification, new-request, or no-change package for human review
Evidence produced
- Versioned replanning impact map
- Affected-owner and affected-record queue
- Human-approved payer change disposition
Human checkpoint: Clinical professionals control replanning and treatment; authorization leaders decide the payer interaction; coding and billing leaders decide downstream handling. Uncertainty remains on hold rather than being automatically waived.
Authorization and revenue-cycle leadership
Manage peer review, appeal, renewal, and course closeout
Denials, partial approvals, expiring scope, additional-information requests, and completed-course reconciliation stay attached to the same chronology. Each path has its own owner, deadline, source version, acknowledgement, and human decision.
Agent actions
- Coordinate qualified peer-review availability and acknowledgements
- Assemble the current chronology for human-approved reconsideration or appeal
- Reconcile final verified service records with authorization and billing handoffs
Evidence produced
- Peer-review and appeal timeline
- Renewal or expiration queue
- Final authorization-to-service reconciliation with open exceptions
Human checkpoint: Clinicians own professional discussion and clinical rationale; authorized appeal staff choose and submit the path; coders and billers control final claim treatment; legal or compliance personnel resolve disputed rights and liability.
Separate payer paths instead of one universal rule
Coverage, notice, authorization, and documentation requirements vary by program, plan, jurisdiction, service, and date. These paths show where teams must verify current authoritative instructions.
medicare
Original Medicare fee-for-service
Original Medicare coverage work starts with the current national and applicable local coverage documents, related billing articles, contractor jurisdiction, service, setting, and date. This page does not claim that every radiation oncology component requires prior authorization under one national program.
- Search the Medicare Coverage Database for current national and local documents and confirm the applicable contractor and effective version
- Keep coverage analysis, coding, authorization, claim submission, and payment status as separate decisions
- Use an Advance Beneficiary Notice of Noncoverage only when current Original Medicare rules and the specific facts support it; the ABN is not a universal payer notice
- Route uncertain coverage or potential patient-liability questions to qualified billing, compliance, and legal staff before communication
Human handoff: Authorized Medicare, coding, billing, and compliance personnel verify current sources and determine the applicable claim and notice path. A software flag never creates coverage, transfers liability, or substitutes for a properly executed notice.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicare advantage
Medicare Advantage plan and delegate
Medicare Advantage plans may use prior authorization subject to federal requirements and the plan's current coverage and utilization-management process. CMS course-of-treatment protections are important context, but they do not allow software to assume that an unreviewed replanning change, component, or date extension remains authorized.
- Verify the current plan product, delegate, portal or API, criteria source, service scope, and effective date
- Preserve the exact approved course duration and limitations stated by the plan while recognizing CMS continuity requirements
- When the course changes, compare the governing approval with current plan instructions and route uncertainty to the plan and qualified staff
- Do not transfer Original Medicare ABN logic, contractor articles, or notice forms into the Medicare Advantage path
Human handoff: Authorization leaders and qualified clinicians decide whether to seek clarification, submit a change, provide more information, request peer review, or appeal. The plan makes the coverage determination, and compliance staff interpret program obligations when the facts are disputed.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicaid
State Medicaid fee-for-service or managed care
Medicaid is administered through state programs and may involve fee-for-service agencies, managed care plans, delegates, state-specific forms, coverage criteria, authorization periods, appeal paths, and fair-hearing rights. A national template cannot safely replace the current state and product sources.
- Identify the state program, eligibility group, delivery system, managed care product, delegate, provider participation, and current instructions
- Verify whether each radiation treatment component, technique, fraction scope, or replanning change follows the same or a separate process
- Apply CMS interoperability requirements only to the impacted payer and provision in scope, with the applicable compliance date
- Route notice, appeal, fair-hearing, continuation, and patient-liability questions to staff qualified for that state and program
Human handoff: State Medicaid and managed care personnel remain the authoritative contacts for case-specific requirements. Provider authorization, clinical, compliance, and legal staff decide submissions and rights; the agent only preserves sources, versions, deadlines, and accountable next steps.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
commercial
Commercial, exchange, and employer-sponsored products
Commercial authorization requirements can vary by insurer, product, funding arrangement, employer plan, state, network, delegate, contract, service, and date. CMS-0057-F includes Qualified Health Plan issuers on the Federally Facilitated Exchanges in its defined impacted-payer scope; it does not cover every commercial product.
- Confirm the exact product, plan documents, network, delegate, treatment-course requirements, change instructions, and submission channel
- Keep benefit information, authorization, medical-necessity review, appeal rights, external review, patient estimate, and claim adjudication separate
- Verify which federal or state appeal and external-review rules apply instead of copying a deadline or right from another product
- Treat peer-to-peer scheduling and a clinician's clinical rationale as human-owned work even when administrative coordination is automated
Human handoff: Contracting, authorization, clinical, financial, compliance, and legal staff resolve product-specific requirements and rights. The insurer or its authorized reviewer decides coverage, and only approved staff communicate financial responsibility or pursue an appeal.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, American Society for Radiation Oncology
workers comp auto liability
Workers' compensation, auto, and liability coordination
A radiation treatment course may occasionally intersect with workers' compensation, no-fault, liability, or another responsible payer. Those cases require claim-specific, state-specific, contractual, and legal review; ordinary health-plan authorization logic cannot determine causation, responsibility, settlement, or payment order.
- Identify the potentially responsible program or insurer, accepted condition or disputed scope, adjuster or administrator channel, and current authorization rules
- When Medicare is also involved, preserve Medicare Secondary Payer and conditional-payment context without deciding legal responsibility
- Keep liability authorization, health-plan coverage, coordination of benefits, claim recovery, settlement, and patient communication as separate work
- Escalate disputed causation, responsibility, future medical, settlement, or recovery questions to qualified legal and compliance personnel
Human handoff: Workers' compensation, liability, coordination-of-benefits, revenue-cycle, compliance, and legal specialists determine the applicable path. The agent may organize evidence and deadlines but never makes a liability finding or represents that Medicare or another payer will pay.
Sources for this path: Centers for Medicare & Medicaid Services
Make version control and human authority part of the product
Radiation treatment-course authorization carries clinical, privacy, financial, and legal consequences. Governance therefore has to show what the agent read, which version governed, what changed, how confidence was calculated, who approved the next action, and which manual path remains available when a source or connection fails.
Requested, submitted, authorized, changed, and delivered stay separate
Each component and fraction basis has its own source-backed state. A status cannot flow forward merely because a neighboring field is approved, and a final service event cannot rewrite the frozen request or payer response that preceded it.
Every payer rule has a source, scope, owner, and review date
Requirements are versioned by program, product, jurisdiction, delegate, service, setting, and effective date. Stale, conflicting, unverified, or contract-only instructions generate a human task instead of an automated coverage conclusion.
Clinical and coding decisions are blocked from autonomous action
Agents may compare documented administrative facts and surface differences. They cannot choose treatment, technique, dose, fractions, plan quality, medical necessity, clinical rationale, codes, modifiers, units, or whether care should proceed.
Material change reopens dependent work
Buyer-defined dependency rules identify which authorization, schedule, financial, coding, and billing states may be stale after replanning or another course change. Only an authorized human disposition can restore the affected readiness state.
Minimum-necessary and role-based access are configured by purpose
The buyer defines which roles and agents may retrieve, display, submit, or retain each field and document. The workflow supports purpose-based disclosure and applicable HIPAA minimum-necessary controls while recognizing the rule's stated exceptions and the need for qualified privacy review.
Exceptions have owners, deadlines, and tested recovery paths
Low confidence, downtime, failed transmission, missing acknowledgement, duplicate identity, stale policy, ambiguous scope, and interface drift each create an explainable hold and manual recovery step. Silence and technical success never become payer approval.
- Human authority
- Radiation oncologists and other qualified professionals control clinical decisions; medical physicists, dosimetrists, and radiation therapists retain their professional and safety responsibilities; authorized coders control code selection; payer reviewers determine coverage; authorization staff control submissions; revenue-cycle and financial staff control claim and patient-financial actions; privacy, security, compliance, contracting, and legal leaders decide their respective high-risk questions.
- Audit trail
- Retain the source URI or document reference, retrieved timestamp, policy or form version, extracted field and passage, request version, response artifact, plan-version comparison, confidence factors, exception, human question, approval or override, channel acknowledgement, downstream acknowledgement, and final reconciliation. Records follow the buyer's retention, access, correction, and legal-hold rules and must support reconstruction without exposing credentials.
- Data boundary
- Operational deployments may process protected information only under approved access, security, privacy, contractual, and retention controls. Marketing analytics remain non-PHI and page-scoped: canonical route, page family, specialty slug, workflow slug, content cluster, CTA label, and CTA location only. Do not send patient, diagnosis, order, plan, fraction, payer-response, authorization, claim, appointment, document, portal, or credential values to GA4 or logs. Search Console review uses aggregate page and query clicks, impressions, CTR, and position without case data.
Connect the course ledger without replacing clinical systems
The operating model is a coordination layer around systems the buyer designates as authoritative. No universal or prebuilt integration, payer portal, API, clearinghouse, fax, oncology information system, treatment-planning system, or EHR access is claimed. Each touchpoint needs a validated data contract, permitted purpose, monitoring, reconciliation, downtime behavior, and manual fallback.
EHR and oncology information system
Information in scope
Read configured registration, coverage, order, consultation, course, note, schedule, and version metadata needed for the administrative workflow; write back only approved task, status, or document references under a validated interface contract.
Boundary
The clinical record remains authoritative. The agent cannot edit a treatment order, create a diagnosis, interpret a note, clear treatment, or silently overwrite a clinician's, therapist's, physicist's, dosimetrist's, or scheduler's work.
Treatment-planning and dosimetry systems
Information in scope
Receive only the approved plan-version events and administrative descriptors required to compare the version tied to the request with the version designated for the current course.
Boundary
The workflow does not calculate or evaluate dose, select technique, optimize a plan, control treatment equipment, perform quality assurance, or decide that a revised plan is clinically acceptable or authorization-equivalent.
Imaging, pathology, and document repositories
Information in scope
Retrieve permitted document identity, date, provenance, status, and relevant source passages when a current payer request calls for pathology, imaging, or other supporting evidence.
Boundary
The agent does not interpret images or pathology findings, diagnose disease, alter a report, or assume that a located document proves a payer criterion. Qualified professionals retain interpretation and disclosure authority.
Scheduling and treatment-delivery event feed
Information in scope
Use verified scheduled and completed administrative events to compare planned visits or fractions with the payer's stated date, count, unit, provider, facility, and component scope.
Boundary
The connection cannot prescribe timing, release a treatment session, attest delivery, change a fractionation plan, or decide whether a missed, interrupted, or added event is clinically appropriate.
Payer, delegate, clearinghouse, fax, and API channels
Information in scope
Prepare buyer-approved requests, attachments, status checks, acknowledgements, and responses through channels that have been contractually and technically validated for the exact payer product and transaction.
Boundary
Credentials remain isolated from content and marketing measurement. Unsupported portals stay manual; automated submission requires explicit authority; transmission success is not approval; and every returned response must be reconciled with its source artifact.
Coding, billing, and revenue-cycle platform
Information in scope
Provide the source-linked requested, authorized, changed, and final administrative component ledger plus unresolved discrepancies for qualified coding, billing, and revenue-integrity review.
Boundary
The agent does not assign final codes, create a claim, determine modifiers or units, post a charge, predict payment, write off a balance, or communicate patient responsibility without the buyer's authorized human process.
Put administrative capacity behind a formula your team can replace
Use a planning model based only on treatment-course authorization cases handled, administrative minutes saved per case, and the buyer's loaded labor rate. Replace every assumption with a measured local input from shadow mode. Do not add presumed denials avoided, revenue protected, treatments accelerated, fractions added, or clinical outcomes.
Monthly treatment-course authorization cases
180 cases
This is an illustrative planning input, not a QuickIntell customer volume or radiation oncology benchmark. The evaluating team should use its own count of in-scope authorization cases for the same period and pilot boundary.
Administrative time saved
14 minutes per case
This is an illustrative assumption, not a measured product result. Validate it by comparing the same defined retrieval, reconciliation, follow-up, and change tasks in shadow mode before and after the proposed workflow.
Loaded labor rate
42 dollars per hour
This is an illustrative employer-cost assumption. Finance should supply the appropriate blended loaded rate and decide whether any released time becomes usable capacity rather than treating the formula as cash savings.
Formula
180 treatment-course authorization cases × 14 administrative minutes saved per case × $42 loaded labor rate ÷ 60 minutes
Illustrative result
$1,764 of illustrative monthly administrative capacity
Illustrative planning model—not a customer result, guarantee, or quote.
Illustrative workflow examples
These examples explain process behavior. They are not customer stories, measured outcomes, clinical advice, or promises of coverage.
Illustrative example
A replan changes payer-facing scope after the course has started
A qualified clinical team creates a new plan version during an authorized course. The current payer response names a technique, component set, fraction scope, date span, provider, and facility, but the workflow cannot assume whether the new version is administratively equivalent or requires notification, amendment, or a new request.
- The Replanning Change-Impact Agent freezes the prior source lineage and detects the authenticated new version event
- It compares only the approved administrative descriptors and labels each as unchanged, changed, or unknown
- The Response and Course Ledger Agent marks affected readiness states for human review without erasing the prior approval
- Authorization staff verify current payer-product change instructions and ask the payer for clarification when required
- Qualified clinical and coding reviewers approve their respective statements before any supervised submission or downstream release
Illustrative outcome: The prior request, response, revised version, human decision, payer interaction, and downstream acknowledgements remain connected. The example does not promise that a change is accepted, that retrospective authorization is available, or that treatment or billing should proceed.
Illustrative example
A fraction or technique request receives a partial approval
A payer response approves only part of the submitted radiation treatment-course scope and provides a reason plus peer-review or appeal instructions. The result must be reconciled before a generic approved label reaches scheduling, coding, or patient-financial work.
- The Response and Course Ledger Agent attaches the governing response to the exact submitted packet and preserves the stated partial scope
- The Component, Code, and Fraction Scope Agent shows requested, submitted, and authorized fields side by side without recommending a clinical or coding change
- The Peer Review and Appeal Orchestration Agent records the applicable path, deadline, required role, clinician availability, and acknowledgement status
- The radiation oncologist supplies any clinical rationale and participates in professional review; authorized staff approve the administrative submission
- The final payer response is reconciled with the course ledger, schedule dependencies, and billing preparation by their human owners
Illustrative outcome: The team receives one traceable chronology and explicit next actions rather than an unexplained denial queue. No appeal-success rate, authorization outcome, treatment result, or payment result is inferred from this illustrative process.
Start with one course pattern and prove every handoff in shadow mode
Adoption should narrow risk before it expands automation. Choose one locally defined course pattern, a bounded payer and facility set, and a small group of accountable users. Validate the source and exception model without allowing autonomous clinical, submission, scheduling, coding, billing, appeal, liability, or patient-communication decisions.
Map the real course and decision rights
- Document the before-state from referral and consultation through simulation, planning, authorization, fractions, replanning, peer review, appeal, renewal, and final billing handoff
- Name authoritative systems, component definitions, version events, payer sources, human owners, deadlines, stop rules, and manual paths
- Select a bounded pilot course pattern, payer-product set, provider and facility context, and permitted actions
- Define non-PHI operational measures such as queue aging, duplicate touches, missing sources, routing accuracy, overrides, and reviewer time
Exit criteria: Clinical, authorization, coding, revenue-cycle, scheduling, privacy, security, compliance, integration, and legal owners agree on the pilot boundary, exclusions, source authority, human decision rights, acceptance measures, and manual fallback.
Validate data contracts and controls
- Test identity, coverage, request, response, document, component, fraction, date, schedule, and plan-version fields at source level
- Configure role access, disclosure rules, retention, credential isolation, audit fields, source freshness, low-confidence actions, and downtime behavior
- Verify each intended portal, API, clearinghouse, fax, and system touchpoint rather than assuming universal connectivity
- Build synthetic or approved de-identified scenarios for partial approvals, replanning changes, expiration, duplicate records, stale instructions, missing acknowledgements, and liability coordination
Exit criteria: Every in-scope input and output has a documented authority, access rule, update pattern, reconciliation method, error state, recovery owner, and tested manual route; unsupported connections and actions remain visibly out of scope.
Run shadow mode against qualified review
- Process representative cases without permitting agents to submit, schedule, clear treatment, select codes, bill, appeal, transfer liability, or contact a patient
- Compare agent findings with qualified reviewers and classify missed changes, false holds, false clears, wrong-source matches, routing errors, and stale-version errors
- Measure human review time, duplicate work, exception quality, alert burden, and adoption friction using the same defined task boundary
- Exercise downtime, rollback, audit reconstruction, policy updates, override review, and access revocation
Exit criteria: Governance owners accept the measured error profile, reviewer workload, source freshness, audit completeness, fallback test, training plan, and release limits. Unaccepted risk is repaired rather than waived for a launch date.
Release selectively and govern expansion
- Enable only approved administrative actions with visible sources, role-based queues, human approvals, and immediate manual fallback
- Monitor missed and false findings, response matching, unresolved replans, expiration alerts, duplicate outreach, overrides, channel failures, and downstream acknowledgement
- Review payer sources, course catalogs, code references, access permissions, interfaces, and exception ownership on named schedules
- Add another course pattern, payer product, facility, component, or automated action only after the same shadow validation and governance approval
Exit criteria: The live scope stays within approved quality, privacy, security, operational, and audit thresholds; staff can explain and reverse its actions; manual fallback works; and accountable owners approve any expansion.
Authoritative sources used for coverage context
Sources support the cited coverage and administrative context. Teams must confirm the current policy, contract, jurisdiction, and effective date for each real case.
New ASTRO survey finds that prior authorization delays lead to serious harm for people with cancer
American Society for Radiation Oncology · professional association · reviewed
Supports the stated 2024 survey context: respondents reported staff reallocation and hiring burden, and estimated that many initially denied requests were later approved on appeal. These physician-survey findings describe radiation oncology burden; they are not product results or a payer rule.
Medicare Coverage Database Search
Centers for Medicare & Medicaid Services · government · reviewed
Supports searching current national and local Medicare coverage documents, contractor jurisdiction, document status, effective dates, and related articles. It does not establish one universal radiation oncology authorization, code, or coverage rule.
Fee-for-Service Advance Beneficiary Notice of Noncoverage
Centers for Medicare & Medicaid Services · government · reviewed
Supports that the ABN is an Original Medicare fee-for-service notice used in certain situations when payment is expected to be denied and may transfer potential financial liability in certain instances. It is not a universal notice for every payer or denial.
2024 Medicare Advantage and Part D Final Rule (CMS-4201-F)
Centers for Medicare & Medicaid Services · government · reviewed
Supports Medicare Advantage utilization-management requirements concerning coverage criteria, prior authorization, transition continuity, and the duration of an approved medically reasonable and necessary course of treatment. Current plan, service, and change facts still require case-specific verification.
CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)
Centers for Medicare & Medicaid Services · government · reviewed
Supports the defined impacted-payer scope, phased compliance dates, prior-authorization process provisions, and API requirements. The commercial scope includes Qualified Health Plan issuers on the Federally Facilitated Exchanges, not every commercial health product.
Medicaid and CHIP State Profiles
Centers for Medicare & Medicaid Services · government · reviewed
Provides an official state-by-state starting point for Medicaid and CHIP program context. It supports routing to applicable state, delivery-system, managed care, and plan sources rather than applying one national radiation treatment authorization template.
Appealing Health Plan Decisions
Centers for Medicare & Medicaid Services · government · reviewed
Supports general internal-appeal and external-review context while expressly noting that application varies with plan status, product, state, and other facts. It does not allow one deadline or appeal path to be applied to every commercial course.
Medicare Secondary Payer
Centers for Medicare & Medicaid Services · government · reviewed
Supports coordination context when workers' compensation, no-fault, or liability insurance may pay before Medicare, including conditional-payment and recovery concepts. It does not determine a state claim's causation, authorization, settlement, legal liability, or final payment result.
Minimum Necessary Requirement
U.S. Department of Health and Human Services · government · reviewed
Supports purpose-based limits for many uses, disclosures, and requests for protected health information while identifying stated exceptions. Each organization must apply the rule to its role, facts, and legal obligations with qualified privacy review.
Radiation oncology workflow FAQs
Open a question to review the answer. The disclosure controls use native browser behavior and remain available by keyboard without page JavaScript.
Does radiation oncology prior authorization software replace our EHR, oncology information system, or treatment-planning system?
No. It coordinates administrative evidence and decisions around systems your organization designates as authoritative. Orders, treatment plans, dose information, professional documentation, schedules, delivery records, codes, and claims remain in governed systems. Each proposed connection requires field-level validation, access control, monitoring, reconciliation, downtime behavior, and a manual fallback.
Can an AI agent decide the radiation technique, dose, fraction count, or medical necessity?
No. Agents may compare explicit administrative descriptors, locate source passages, and show that two records differ. Radiation oncologists and other qualified professionals decide treatment; medical physicists, dosimetrists, and therapists retain their professional responsibilities; payer reviewers determine coverage; and qualified coders decide code treatment. Uncertainty goes to those people, not to an autonomous model.
How does the workflow manage several CPT or HCPCS references under one course?
It keeps each configured consultation, simulation, planning, dosimetry, image-guidance, delivery, and related component in requested, submitted, authorized, changed, scheduled, delivered, and billing-preparation states. Sources and effective dates stay visible. The ledger exposes mismatches, but qualified coding and revenue-integrity staff select and validate authoritative codes, units, modifiers, and claim treatment.
What happens when a qualified clinician orders replanning after authorization?
The workflow preserves the version tied to the request and response, detects the new authenticated version, compares payer-facing administrative attributes, and identifies dependent records that may be stale. Authorized staff then verify current payer instructions and choose a clarification, notification, amendment, new request, retrospective path, or documented no-change disposition. No one replan rule is assumed.
Does an approval automatically cover every fraction and every course change?
No. The ledger records only the components, technique language, dates, fractions, units, provider, facility, and conditions the governing response actually states. Medicare Advantage course-of-treatment protections matter, but plan-specific facts and current law still require review. An omitted or unclear field remains unknown; an earlier approval is not expanded by inference.
Can QuickIntell submit through every payer portal or radiation oncology delegate?
No universal portal, API, clearinghouse, fax, or payer coverage is claimed. Every payer product, delegate, transaction, endpoint, credential, attachment path, and response needs verified access and technical validation. Unsupported channels remain visible manual work. Humans approve submissions, and a successful transmission or portal banner is not treated as the payer's decision.
How are peer-to-peer discussions and appeals handled without automating clinical judgment?
The agents capture the governing reason and deadline, maintain the current evidence chronology, coordinate approved clinician availability, prepare an administrative packet, and track acknowledgement. A qualified clinician conducts professional review and authors clinical rationale. Authorized appeal staff select and submit the applicable path. The software neither impersonates a clinician nor predicts that a denial will be overturned.
How do Original Medicare, Medicare Advantage, Medicaid, and commercial payer rules stay separate?
Each course carries its program, plan product, state or contractor jurisdiction, delegate, provider, facility, source authority, effective dates, and human verifier. Original Medicare coverage documents and ABN rules do not automatically apply to Medicare Advantage. Medicaid remains state and delivery-system specific. CMS interoperability rules cover defined impacted payers and provisions, not every commercial product.
Can the software decide whether an ABN or another patient-liability notice is required?
No. The Original Medicare ABN is used in defined fee-for-service circumstances and is not a universal notice for Medicare Advantage, Medicaid, or commercial plans. The workflow can surface current approved guidance and missing facts, but qualified billing, financial, compliance, and legal staff decide notice use, timing, execution, estimates, and patient communication.
What if workers' compensation, auto, or liability coverage is involved?
The workflow opens a distinct coordination path and preserves the potentially responsible payer, accepted or disputed scope, authorization channel, and Medicare Secondary Payer context when applicable. It does not decide causation, responsibility, settlement, recovery, conditional payment, or legal rights. Specialized revenue-cycle, coordination, compliance, and legal personnel own those decisions.
How are payer policies and authorization instructions kept current?
Every rule needs an approved source, program and product scope, jurisdiction, service context, effective date, owner, and review date. Changed, stale, conflicting, unavailable, or contract-only instructions create a human-review state. The workflow never fills a missing requirement from model memory or silently transfers a policy from another payer, plan, facility, or course.
How are PHI, payer credentials, analytics, and search measurement separated?
Operational data and credentials stay inside approved security, privacy, contractual, role-access, and retention controls; credentials are never placed in content or analytics. GA4 receives only approved page and CTA context, never patient, treatment, payer-response, authorization, claim, schedule, document, or portal values. Search Console analysis remains aggregate and page-scoped across clicks, impressions, CTR, position, and query mix.
How should an organization measure economic value?
Measure a stable administrative task boundary in shadow mode, then use your own monthly treatment-course count, minutes saved per course, and loaded labor rate. The visible example is courses multiplied by minutes divided by sixty multiplied by the loaded rate. Do not add presumed denials avoided, clinical outcomes, throughput, revenue, or payment without separately governed evidence.
What does the zero-dollar implementation statement mean?
It means QuickIntell charges no implementation fee and no customization charges under the stated offer. It does not mean the software is free: software subscription and usage charges are separate. Buyers should also assess internal data preparation, connections, third-party channels, security and legal review, training, governance, staffing, and continuing operating costs.
Bring one difficult course change—not a polished demo case
Use a governed, non-PHI scenario to map the treatment-course components, payer path, evidence sources, fraction and validity scope, replanning trigger, peer-review or appeal handoff, clinical decision rights, and manual fallback. The review should end with a narrow pilot boundary, explicit exclusions, measurable acceptance criteria, required connections, and named human owners.