For skilled nursing facility admissions, utilization-review, managed-care, MDS, therapy, nursing, revenue-cycle, billing, finance, compliance, privacy, and executive leaders who must accept appropriate referrals, preserve coverage evidence, and manage continued-stay work without letting administrative software make clinical, admission, discharge, or payer decisions.
Keep Every Skilled Nursing Admission and Continued-Stay Coverage Decision on Track
Turn hospital referrals, benefit checks, managed-care authorizations, skilled-need evidence, physician certifications, MDS work, authorized days, payer responses, notices, and transition tasks into one source-linked queue with a named human owner at every consequential decision.
Before this workflow, admissions staff often chase hospital records while utilization review works a payer portal, MDS and therapy teams reconcile a different census, and billing learns about a coverage change after the fact. After adoption, agents organize the same approved sources into one reviewable chronology, expose gaps and conflicts, and prepare bounded work for qualified people. The facility still decides whether it can safely admit and meet a resident's needs; clinicians still determine and document care; payers and programs still determine coverage; residents and representatives retain applicable notice and appeal rights.
The referral moves faster than the coverage record
A skilled nursing admission is a chain of distinct decisions, not one green checkmark. The hospital must send usable records; the facility must determine whether it can meet the person's needs; a qualified professional must address skilled-need and certification requirements; the payer or program must respond; and downstream teams must work from the same episode. When those states live in inboxes, portals, spreadsheets, and separate clinical systems, speed and certainty are easily confused.
The bed decision arrives before the hospital packet is coherent
Referral facesheets, inpatient-status references, discharge summaries, medication information, therapy evaluations, orders, operative notes, laboratory results, wound details, isolation information, and equipment needs can arrive in separate versions. A late correction may change the coverage question or the facility's operational review after staff have already started calling the payer.
Operational consequence
Admissions teams repeat outreach, clinical reviewers inspect stale material, transport planning begins against an unresolved destination, and a potentially viable referral can wait beside a referral that still lacks information required for a safe human decision.
Eligibility, authorization, and covered skilled care look like one status
An active member response does not establish a covered SNF stay. A prior-authorization number may apply to a different facility, level, date range, or service. Original Medicare eligibility conditions, Medicare Advantage plan processes, Medicaid nursing-facility pathways, commercial benefits, and liability coverage can require different sources and decisions.
Operational consequence
Staff may mistake a technical response for coverage, miss a plan-specific notification or concurrent-review step, or promise a financial result that no source supports. Later teams must rebuild what was known at admission and when it changed.
Skilled-need evidence, certification, MDS coding, and PDPM classification drift together
Hospital records and current SNF documentation can support different administrative purposes. Certification and recertification have defined Original Medicare content and timing; MDS items follow current RAI guidance; PDPM classifies covered Part A residents for payment; therapy and nursing documentation describe delivered care. None of those artifacts should silently substitute for another.
Operational consequence
A payment classification can be misread as a universal coverage determination, an assessment gap can remain hidden until billing, or clinicians can be asked to approve generated language that does not accurately reflect the record or their judgment.
The authorized-day ledger and the current stay tell different stories
Managed-care responses may state an approved date range, day count, level, condition, next-review date, or request for more information. Census, leave, hospital readmission, transfer, payer change, and discharge events may arrive later. Portal messages, calls, faxes, and letters can also conflict or supersede one another.
Operational consequence
A precise-looking balance can be wrong. Scheduling, finance, therapy coordination, notice preparation, and billing then act on different assumptions, while the actual next review or appeal handoff remains unowned.
Notices, transition planning, Medicaid conversion, and billing start too late
An end of covered services, a benefit exhaustion question, a noncovered service, a resident's decision to continue care, a Medicaid application, a managed-care adverse decision, and a discharge plan are different events. SNF ABN, NOMNC, DENC, plan notices, state Medicaid forms, and private-pay communications do not apply interchangeably.
Operational consequence
Residents or representatives may receive the wrong explanation, appeal work may lose time, financial counseling may begin without a verified liability path, and consolidated-billing or claim teams may learn about the coverage transition only after services are reconciled.
A named agent team with visible decision boundaries
Each agent handles a defined part of the admission and continued-stay coverage control workflow. Confidence signals and human escalation remain visible rather than being hidden behind an automation label.
Referral and Coverage Anchor Agent
Creates a source-linked administrative episode from the approved referral, identity, hospital, facility, payer, plan, benefit, and transfer references, then separates bed availability, clinical acceptance, network, authorization, and financial-clearance work instead of compressing them into one admission status.
Inputs
- Approved hospital referral, transfer, registration, and episode references
- Current payer, plan, member, benefit administrator, and effective-date response references
- Facility, unit, service level, network, contract, and bed-status references
- Existing notification, authorization, coordination-of-benefits, and liability-case references
Checks
- Matches the same person and episode across approved sources without relying on a name-only match
- Separates acute inpatient, observation, emergency, SNF, nursing-facility, custodial, and rehabilitation labels
- Flags payer, plan, product, network, facility, date, and benefit-owner conflicts
- Keeps the facility's clinical and operational acceptance decision outside coverage automation
Outputs
- A source-linked referral and coverage-anchor summary with unknowns left explicit
- Distinct human-owned tasks for record collection, clinical review, authorization, contracting, financial counseling, or coordination
- Confidence method
- Confidence depends on exact agreement among designated identity, episode, referring hospital, facility, payer, plan, product, level, event-time, and source-version fields. It falls when a record is incomplete, corrected, late, or could belong to a prior stay.
- Low-confidence action
- The agent leaves the episode unanchored, displays the conflicting references, and routes verification to admissions or patient-access staff. It does not merge episodes, select a payer path, reserve a bed, accept a resident, or represent that coverage exists.
- Human escalation
- Admissions, health-information-management, nursing, therapy, facility leadership, patient access, managed care, contracting, privacy, and compliance owners resolve episode, source, acceptance, payer, benefit, network, and transfer uncertainty before dependent automation proceeds.
Hospital Record Readiness Agent
Maps the facility's buyer-approved referral checklist to current hospital source documents, versions, signatures, service periods, and unresolved questions so qualified reviewers can see what is present without treating document presence as clinical sufficiency or admission approval.
Inputs
- Buyer-approved referral and service-line checklist with source and effective date
- Approved discharge summary, history, orders, medication, therapy, procedure, laboratory, wound, and infection-control references
- Hospital contact, document-request, acknowledgement, and correction history
- Facility capability, staffing, equipment, pharmacy, and vendor question templates approved for administrative routing
Checks
- Confirms document type, author, status, service period, signature, amendment, and source version
- Detects missing, duplicate, draft, contradictory, unreadable, or out-of-episode records
- Separates an administrative checklist match from a clinician's interpretation of risk, needs, and appropriateness
- Limits requests and displays to the buyer-approved minimum information for the stated purpose
Outputs
- A document-to-question readiness map with citations, versions, gaps, and accountable request owners
- A concise referral change summary for named clinical and operational reviewers
- Confidence method
- Confidence reflects document identity, authorship, approval state, recency, question match, legibility, and consistency across approved sources. It does not score clinical quality, facility capability, resident preference, or admission appropriateness.
- Low-confidence action
- The agent marks the question unresolved, requests the missing or corrected source through an approved channel, and stops the dependent administrative step. It never fills a gap with generated clinical facts or infers a safe transfer from neighboring fields.
- Human escalation
- Qualified nursing, medical, therapy, pharmacy, infection-prevention, wound, respiratory, social-work, admissions, and facility leaders decide whether the available information supports a safe and appropriate admission and what additional clinical information is required.
Skilled Need and Certification Evidence Agent
Organizes explicit source evidence for the selected coverage path and prepares certification or recertification prompts for authorized professionals, while keeping skilled-need judgment, medical necessity, care planning, signatures, and payer determinations with qualified humans.
Inputs
- Verified coverage path and current authoritative requirement source
- Approved hospital and SNF nursing, therapy, physician, and care-plan source references
- Current certification, recertification, order, and signature status references
- Prior released packet, payer question set, and response chronology
Checks
- Maps each requirement or payer question to an explicit source, a required professional judgment, or an unresolved gap
- Checks author, credential context, service period, signature status, amendment history, and source freshness
- Keeps Original Medicare certification timing and content within the cited federal scope
- Prevents MDS, PDPM, therapy minutes, diagnosis, or an agent confidence score from becoming an autonomous coverage conclusion
Outputs
- A requirement-to-source evidence map with missing judgments and signatures clearly identified
- A minimum-necessary draft review packet for named clinical, certification, and authorization reviewers
- Confidence method
- Confidence measures whether current approved sources explicitly answer administrative questions and whether the required human author or signer is identified. It never measures skilled need, medical necessity, care quality, or the likelihood of payer approval.
- Low-confidence action
- The agent leaves the clinical or certification question open, cites the missing or conflicting source, and routes it to the authorized professional. It does not draft unsupported rationale, backdate a statement, choose a diagnosis, or sign on anyone's behalf.
- Human escalation
- The responsible physician or other authorized professional, nursing and therapy leaders, MDS staff, utilization review, coding, compliance, and legal owners decide clinical meaning, certification content, signature authority, coverage interpretation, and corrective action.
MDS, PDPM, and Section GG Coordination Agent
Coordinates assessment dependencies, approved source citations, schedule states, and classification inputs under the current buyer-approved RAI and payment references, but does not perform an assessment, code by inference, optimize a payment group, or direct the resident's plan of care.
Inputs
- Current CMS RAI manual, item-set, PDPM, and buyer-approved operating references
- Approved MDS schedule, assessment reference date, completion, correction, and submission status references
- Nursing, therapy, Section GG, diagnosis, condition, service, and care-plan source references
- Payer path, Part A stay, interruption, transfer, discharge, and claim-period status references
Checks
- Verifies the cited manual or mapping version, effective date, assessment purpose, and payer scope
- Shows missing, conflicting, copied-forward, late, corrected, or unsigned source entries without choosing a code
- Separates MDS completion, Section GG evidence, PDPM classification, coverage, delivered care, and claim status
- Routes assessment, coding, clinical, and payment questions to the people authorized to resolve them
Outputs
- An assessment-dependency view with source citations, timing references, versions, and unresolved items
- A human-review brief for MDS, Section GG, PDPM, therapy, nursing, coding, and billing reconciliation
- Confidence method
- Confidence is based on source-version agreement, approved field provenance, timing consistency, completion state, and the absence of unresolved contradictions. A high score indicates administrative readiness only and is not a coverage or payment prediction.
- Low-confidence action
- The agent suppresses any classification or completeness claim, preserves competing values, and routes the issue to MDS, clinical, therapy, coding, or billing staff. It does not select a more favorable code, group, assessment date, or payer outcome.
- Human escalation
- Authorized assessment coordinators, nurses, therapists, physicians, coders, compliance staff, billing leaders, and payer specialists determine assessment responses, clinical support, correction, classification, claim use, and any required disclosure or submission.
Authorized-Day and Concurrent Review Agent
Maintains an inspectable ledger of the payer's stated authorization scope, internal preparation targets, review questions, service events, acknowledgements, and response versions without equating authorized days with delivered skilled care, claimability, payment, or a care decision.
Inputs
- Verified payer letter, portal, fax, phone, or approved API response references
- Current admission, census, leave, transfer, hospital-return, payer-change, and discharge event references
- Released review packet, acknowledgement, information-request, and response history
- Buyer-approved definitions for dates, days, levels, units, conditions, and internal preparation targets
Checks
- Separates request, release, transmission, acknowledgement, review, approval, partial approval, denial, and closure
- Keeps authorized, scheduled, delivered, documented, assessed, billed, adjudicated, and disputed states distinct
- Flags conflicts among start dates, through-dates, counts, levels, conditions, review dates, and response versions
- Shows every approved calculation and prevents ambiguous scope from producing a usable balance
Outputs
- A versioned authorized-scope and continued-review ledger with source references
- Human-owned exception tasks for missing information, peer review, adverse decisions, late responses, and downstream reconciliation
- Confidence method
- Confidence requires a readable substantive payer response matched to the correct episode, request version, facility, service level, and date meaning. A transmission receipt, portal upload, or phone attempt never carries approval confidence by itself.
- Low-confidence action
- The agent displays the competing source values, labels the authorization state unresolved, and blocks automatic ledger or downstream changes. It does not infer approval from silence, choose the most favorable scope, or direct continued care or discharge.
- Human escalation
- Managed-care, authorization, utilization-review, clinical, scheduling, MDS, billing, finance, contracting, payer, compliance, and legal owners resolve scope, deadlines, clinical discussions, adverse decisions, and appeals before consequential action.
Notice, Transition, and Appeal Agent
Separates coverage-ending, financial-liability, appeal, discharge, Medicaid-conversion, private-pay, consolidated-billing, and claim tasks, then presents the current source, trigger, form version, deadline, recipient, and human owner without choosing a notice or legal path autonomously.
Inputs
- Verified payer or program response, benefit, claim, and authorized-scope references
- Current resident or representative contact and communication-preference references from approved systems
- Buyer-approved SNF ABN, NOMNC, DENC, plan-notice, Medicaid, appeal, and financial-counseling sources
- Clinician-approved transition plan and current billing, vendor, therapy, pharmacy, and consolidated-billing status references
Checks
- Distinguishes Original Medicare, Medicare Advantage, Medicaid, commercial, private-pay, and liability notice paths
- Separates an SNF ABN financial-liability question from a NOMNC and any later DENC or plan denial notice
- Verifies source version, program, trigger, recipient, delivery method, accessibility need, deadline, and acknowledgement
- Keeps clinical discharge, resident rights, financial counseling, Medicaid eligibility, appeal, and claim decisions with qualified people
Outputs
- A source-linked notice and transition decision brief for named reviewers
- An accountable task register for delivery, acknowledgement, appeal, conversion, vendor reconciliation, billing, and closure
- Confidence method
- Confidence depends on an explicit program and trigger, a current approved form or instruction, matched episode and recipient references, and complete human decision ownership. Ambiguity about the reason services are ending or continuing makes confidence low.
- Low-confidence action
- The agent holds notice generation and financial-liability statements, shows the competing paths, and alerts notice, benefits, compliance, or legal staff. It does not select a form, calculate liability, waive rights, file an appeal, or change the care plan.
- Human escalation
- Qualified clinical, notice, social-work, resident-rights, managed-care, Medicaid, billing, finance, compliance, privacy, accessibility, appeal, and legal owners choose the correct path, approve communications, and preserve the resident's or representative's applicable choices and rights.
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.
Admissions and patient access
Anchor the referral, episode, and payer path
The workflow begins by matching approved referral, hospital, payer, plan, facility, service-level, and transfer references. It creates separate work for record readiness, clinical acceptance, network or contract review, authorization, financial counseling, and coordination of benefits so no one interprets an active queue item as an accepted or covered admission.
Agent actions
- Match designated referral, identity, episode, hospital, facility, payer, and plan sources
- Separate bed, clinical, coverage, network, contract, and transfer states
- Create source-specific exceptions for missing or conflicting anchors
Evidence produced
- Source-linked referral and coverage anchor
- Before-transfer exception list with named owners
- Chronology of what was known, by source and version
Human checkpoint: Admissions and patient-access staff confirm the administrative anchor. Qualified clinical and facility leaders independently decide capability and acceptance; payer and program sources determine coverage; no agent promises a bed, transfer, coverage, or payment.
Admissions and clinical intake
Build a reviewable hospital-record packet
The Hospital Record Readiness Agent maps each approved intake question to a current source or an explicit gap, then compares corrections and amendments. The output is a navigation aid for the facility's qualified review, not a clinical summary that substitutes for reading the underlying record.
Agent actions
- Cite current source sections for each buyer-approved referral question
- Detect drafts, duplicates, late corrections, missing signatures, and service-period conflicts
- Route minimum-necessary record requests through approved channels
Evidence produced
- Document-to-question readiness map
- Version and correction comparison
- Clinical and operational exception queue
Human checkpoint: Authorized nursing, medical, therapy, pharmacy, infection-prevention, social-work, and facility reviewers inspect the sources and decide whether needs can be met. Missing clinical evidence stays missing until an accountable source owner supplies it.
Utilization review and managed care
Confirm the administrative coverage prerequisites
The selected payer path determines which official, plan, state, contract, or liability sources apply. For Original Medicare, staff review current Part A eligibility conditions and certification requirements. Other paths use their own benefit, authorization, level-of-care, network, and notice rules rather than borrowing the Medicare checklist.
Agent actions
- Map each coverage question to its current source, scope, and effective date
- Prepare certification, authorization, or information-request prompts for authorized people
- Keep eligibility, skilled need, authorization, acceptance, and payment as separate states
Evidence produced
- Coverage-prerequisite evidence map
- Named certification, authorization, and source-gap tasks
- Human-approved admission coverage brief
Human checkpoint: Authorized professionals make certification and clinical judgments; facility staff make admission decisions; payer, plan, state, and program staff make coverage decisions. Compliance or legal owners resolve uncertain authority before release or representation.
MDS, nursing, therapy, and revenue cycle
Coordinate MDS, PDPM, Section GG, therapy, and current skilled evidence
After admission, agents maintain assessment and evidence dependencies under the current approved source versions. They show where delivered-care documentation, Section GG sources, MDS responses, certification status, PDPM inputs, and claim-period records agree or differ without asking software to code, optimize, or make a coverage judgment.
Agent actions
- Track assessment, evidence, signature, version, correction, and submission dependencies
- Compare approved source fields without inferring missing clinical or coding answers
- Route conflicts to the authorized MDS, clinical, therapy, coding, or billing owner
Evidence produced
- Assessment and skilled-evidence dependency view
- Source-version and timing exception record
- Human-reviewed classification and billing handoff
Human checkpoint: MDS coordinators, clinicians, therapists, coders, compliance staff, and billing leaders decide and attest to their respective work. A complete MDS or PDPM group does not independently establish continued coverage or payment.
Managed care and utilization review
Run continued review and reconcile payer responses
The agent team prepares a current source map for each payer question, keeps internal preparation targets distinct from payer deadlines, and records the released packet, destination, transmission, acknowledgement, substantive response, and ledger change as separate events.
Agent actions
- Prepare a minimum-necessary, source-linked review packet for named approval
- Preserve payer-stated dates, days, levels, conditions, reasons, and next steps
- Update the ledger only from a verified response or create a human-owned exception
Evidence produced
- Released packet version and approval record
- Transmission, acknowledgement, and response chronology
- Authorized-scope ledger with inspectable changes
Human checkpoint: Qualified clinicians approve clinical content and conduct any clinical discussion. Authorization staff approve destination and release. Payer staff determine coverage. Named operational, compliance, and legal owners decide peer, reconsideration, appeal, or contract action.
Cross-functional coverage council
Close the notice, transition, billing, and appeal loop
When covered services may end or the payer path changes, the workflow keeps notice, resident communication, clinical transition, Medicaid eligibility, private-pay, vendor, consolidated-billing, claim, and appeal work distinct. Each task closes only from its own acknowledgement and retains the source history needed for later review.
Agent actions
- Present the applicable notice and appeal candidates with source and trigger context
- Create separate transition, conversion, financial-counseling, billing, vendor, and claim tasks
- Reconcile final service, assessment, authorization, notice, and claim states without erasing disputes
Evidence produced
- Human-approved notice and communication record
- Coverage-transition and billing dependency register
- Final chronology with open appeal or retrospective-review ownership
Human checkpoint: Clinical teams own care and discharge decisions. Residents or representatives exercise applicable rights. Notice, Medicaid, managed-care, finance, billing, vendor, compliance, appeal, and legal staff approve their actions; the workflow cannot calculate final liability or waive review.
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: verify the Part A SNF path and notice branch
Medicare.gov describes limited Part A SNF coverage under stated conditions, including Part A status, available benefit-period days, a qualifying inpatient hospital stay subject to identified exceptions or waivers, timely SNF entry, daily skilled care, a Medicare-certified SNF, and a related condition. Current federal rules separately address certification and recertification. Those sources guide qualified review; they do not let software decide a real stay.
- Verify inpatient status and the qualifying-stay facts from authoritative sources; observation and emergency time are not silently counted, and any applicable waiver or successful status appeal needs its own source
- Confirm Part A entitlement, benefit-period context, timely entry, certified facility, related-condition context, and daily skilled-care decision without reducing them to one eligibility response
- Route certification and recertification content, timing, and signature authority under current 42 CFR 424.20 to authorized professionals
- Keep MDS completion and PDPM classification distinct from the case-specific coverage and skilled-need decision
- Use the current CMS notice source to distinguish an SNF ABN financial-liability path from NOMNC, any requested DENC, claim denial, and other communications
- Apply consolidated billing to the correct covered or noncovered stay and service context, including current exclusions, rather than to every vendor service by assumption
Human handoff: Qualified Medicare, clinical, certification, MDS, therapy, notice, resident-rights, coding, billing, compliance, and legal staff verify current authority and decide eligibility, skilled need, certification, notice, claim, appeal, and financial-liability actions.
Sources for this path: Medicare.gov, Electronic Code of Federal Regulations, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicare advantage
Medicare Advantage: preserve the plan decision and fast-track rights
A Medicare Advantage plan may have its own network, authorization, concurrent-review, cost-sharing, and organization-determination process, and Medicare.gov notes that a plan may waive the three-day inpatient minimum. Current CMS appeals guidance and notice instructions govern applicable organization-determination and fast-track paths; an Original Medicare checklist is not the plan's response.
- Verify the plan, product, delegated entity, network, facility, service level, channel, and effective date for the episode
- Capture the exact approved scope, conditions, reason, next-review requirement, and current standard or expedited route
- Separate authorization, concurrent-review response, NOMNC, DENC, integrated denial notice, claim, cost sharing, and payment states
- Treat any qualifying-stay waiver as plan- and episode-specific evidence, not a universal Medicare Advantage rule
- Apply CMS-0057-F only to its defined impacted payer, non-drug transaction, provision, exclusion, and compliance-date scope
- Do not claim that every plan supports a complete FHIR workflow, real-time response, portal integration, or automated appeal
Human handoff: Medicare Advantage, managed-care, clinical, notice, resident-rights, compliance, privacy, contracting, appeal, and legal specialists verify current plan and CMS instructions, interpret the organization determination, and approve every submission or notice.
Sources for this path: Medicare.gov, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicaid
Medicaid: resolve the state nursing-facility and conversion path
Medicaid.gov explains that nursing-facility services operate through Medicaid-certified facilities, state eligibility and level-of-care criteria, state plans, and—when applicable—managed-care or preadmission screening processes. A move from a short-term Medicare SNF path to Medicaid nursing-facility coverage is not an automatic conversion, and state requirements must be verified.
- Identify the state program, eligibility category, fee-for-service or managed-care path, plan contractor, facility certification, and effective date
- Confirm the current state level-of-care, application, asset or eligibility, authorization, patient-liability, and notice process through qualified sources
- Route any required Preadmission Screening and Resident Review question through the state's applicable process and authorized professionals
- Keep Medicare benefit status, Medicaid application status, Medicaid eligibility, nursing-facility coverage, private pay, and resident liability separate
- Do not import SNF ABN, NOMNC, DENC, Medicare certification timing, or a Medicare Advantage decision into the Medicaid path by assumption
- Preserve resident choice, transition goals, representative involvement, accessibility, and applicable state appeal rights in the human process
Human handoff: State Medicaid, eligibility, managed-care, nursing-facility, clinical, social-work, resident-rights, finance, compliance, and legal specialists confirm current requirements and make eligibility, level-of-care, notice, liability, transition, and appeal decisions.
Sources for this path: Medicaid.gov, Centers for Medicare & Medicaid Services, U.S. Department of Health and Human Services
commercial
Commercial and employer coverage: separate plan approval from payment
Commercial, self-funded employer, network, administrator, and contract terms vary. HealthCare.gov expressly states that preauthorization is not a promise that a plan will cover the cost. The workflow therefore preserves the exact benefit, authorization, contract, service, and claim sources without presenting one vendor rule as universal.
- Verify the responsible plan or administrator, product, funding arrangement, network, facility contract, service level, and channel
- Keep eligibility, benefit, notification, authorization, approved scope, single-case agreement, claim adjudication, resident responsibility, and payment separate
- Preserve the payer's cited criteria source and version without letting an agent apply clinical judgment or write unsupported rationale
- Confirm whether the plan uses calendar days, service days, levels, units, or another representation before building a ledger
- Route adverse determinations, peer options, external review, contract disputes, and liability communication to qualified owners
- Do not use a commercial authorization to decide clinical acceptance, continuation, transfer, or discharge
Human handoff: Managed-care, clinical, contracting, benefits, revenue-cycle, finance, notice, compliance, privacy, appeal, and legal specialists verify current plan and contract terms, interpret responses, and choose any peer, reconsideration, review, or billing action.
Sources for this path: HealthCare.gov, U.S. Department of Health and Human Services
workers comp auto liability
Workers' compensation, auto, and liability: confirm relevance first
A work-related injury, auto accident, no-fault claim, or liability case can introduce another payer, state process, legal representative, or Medicare Secondary Payer responsibility. The presence of an injury or attorney does not establish that this path applies, and it does not replace the facility's clinical, coverage, or resident-rights work.
- Confirm that a workers' compensation, no-fault, liability, or Medicare Secondary Payer path is actually relevant before collecting more information
- Separate compensability, causation, authorization, network direction, facility acceptance, claim payment, settlement, and Medicare recovery questions
- Use the applicable state, carrier, employer, legal, and CMS sources rather than importing a health-plan SNF authorization workflow
- Preserve conditional-payment and recovery questions for qualified Medicare Secondary Payer staff without predicting responsibility
- Limit disclosure to the approved purpose, role, recipient, channel, and minimum information under current privacy and legal review
- Do not let payment-order uncertainty direct clinical care, admission, continuation, transfer, or discharge
Human handoff: Workers' compensation, liability, managed-care, clinical, admissions, billing, privacy, compliance, legal, benefits-coordination, and Medicare Secondary Payer specialists determine responsibility, disclosure, authorization, payment, recovery, and appeal actions.
Sources for this path: Centers for Medicare & Medicaid Services, U.S. Department of Health and Human Services
Put human authority at every coverage boundary
SNF admission and continued-stay work combines time-sensitive referrals, vulnerable residents, clinical judgments, payer decisions, benefit transitions, notices, assessments, and financial consequences. Governance must therefore control source scope, clinical authority, episode matching, assessment semantics, authorized days, communications, integrations, and non-PHI measurement—not just who can open the software.
Admission and care-decision firewall
Agents cannot accept or reject a resident, determine facility capability, diagnose, prescribe, certify skilled need, choose a plan of care, continue or stop services, transfer, or discharge. Urgent clinical or safety issues bypass routine administrative queues and go directly to qualified teams.
Source, payer, program, and effective-date registry
Every official requirement, plan instruction, state source, contract rule, form, mapping, and internal standard carries its owner, payer or program, product, facility, service, jurisdiction, effective date, retrieval date, and version. Stale or conflicting authority creates an exception rather than a silent default.
Identity and episode integrity
Matching uses approved identifiers and episode context, not a name-only shortcut. Prior stays, hospital encounters, corrected referrals, payer changes, transfers, leaves, readmissions, and benefit transitions remain separate until authorized staff confirm the relationship.
Clinical, assessment, and payment separation
Clinical documentation, certification, MDS responses, Section GG evidence, PDPM classification, delivered therapy, coverage, coding, claim status, and payment stay distinct. Agents may cite and compare approved sources but cannot infer clinical facts or optimize a payment result.
Authorized-scope semantics
Payer-stated dates, day counts, levels, units, conditions, and review dates retain their original representation. Derived balances expose every input and rule. An ambiguity suppresses the balance, and no administrative value releases or blocks care.
Notice, rights, and communication control
Current program, trigger, form, version, deadline, recipient, accessibility, delivery, acknowledgement, and appeal context are presented to named reviewers. Agents cannot choose a notice, calculate liability, obtain a signature, waive rights, or file an appeal autonomously.
Minimum-necessary access and resilient integrations
Buyer-approved roles, purposes, fields, channels, retention, security, acknowledgement, correction, rollback, and downtime queues govern data movement. Portal credentials and secrets remain outside prompts and logs; uncertain disclosure or interface behavior creates a hold.
Non-PHI marketing and search measurement
GA4 may receive only approved route, page-family, specialty, workflow, content-cluster, engagement, and CTA context. Search Console review stays at aggregate page and non-sensitive query performance. Resident, clinical, payer, authorization, provider, facility, claim, notice, day, unit, portal, and free-text values stay out.
- Human authority
- Qualified clinicians and facility leaders retain clinical and admission authority. Authorized professionals own certification and assessment work. Payers, plans, and programs retain coverage decisions. Residents and representatives retain applicable rights. Named admissions, utilization-review, MDS, therapy, notice, Medicaid, privacy, compliance, coding, billing, finance, contracting, appeal, and legal owners approve their domains; an agent score or reminder cannot override them.
- Audit trail
- The audit record preserves source retrieval and effective dates, episode references, document versions, question-to-source citations, missing items, certification and assessment dependencies, human approvals, released packet versions, destination and channel, transmission and acknowledgement, payer response versions, ledger calculations, notices, delivery references, overrides, corrections, write-back acknowledgement, downtime actions, task ownership, timestamps, and final reconciliation.
- Data boundary
- Production use should apply the minimum approved data for the purpose, role-based access, encryption, environment separation, buyer-directed retention, vendor and subprocessor review, incident handling, and tested deletion or return. Do not place PHI, resident or representative values, clinical text, hospital or payer credentials, portal secrets, authorization numbers, claim values, notice details, or financial-liability data in marketing forms, analytics, Search Console exports, demos, evidence files, support logs, or unapproved prompts.
Connect the chronology, not just another inbox
This control tower is an orchestration layer, not a claimed EHR replacement or universal payer connection. Each proposed touchpoint starts with a field-level agreement: authoritative source, permission, purpose, freshness, acknowledgement, write-back, reconciliation, downtime, retention, vendor terms, and separate cost. Availability and behavior must be verified in the buyer's actual environment.
Referral intake, CRM, and secure document exchange
Information in scope
Approved referral identifiers, source facility, requested service, document references, contact history, correction history, task ownership, and receipt status can establish the intake chronology.
Boundary
An uploaded packet is not clinical acceptance, coverage, or proof that every page belongs to the episode. Duplicate, incomplete, late, and corrected records require reconciliation and a tested manual request path.
Hospital EHR, HIE, and discharge workflow
Information in scope
Approved inpatient-status, discharge, order, medication, therapy, procedure, laboratory, wound, infection-control, and transition source references can support qualified facility review.
Boundary
No connection, data right, real-time delivery, or completeness is assumed. Agents do not edit the hospital record, interpret clinical risk, decide transfer readiness, or treat observation and inpatient labels as interchangeable.
SNF EHR, census, MDS, and clinical documentation
Information in scope
Approved admission, census, leave, return, discharge, care-plan, nursing, therapy, MDS, Section GG, certification, signature, and source-version references can support evidence and dependency views.
Boundary
The workflow does not chart care, perform assessments, select MDS responses, classify PDPM by inference, sign certifications, change orders, or replace the official record. Write-backs are limited, approved, acknowledged, and reconciled.
Payer portals, fax, phone, clearinghouse, and approved APIs
Information in scope
Verified requirement sources, packet versions, release approvals, transmission evidence, acknowledgements, information requests, determinations, authorized scope, and review instructions can enter the payer chronology.
Boundary
No universal connectivity is claimed. Credentials, delegated access, terms of use, screen automation, API scope, response meaning, latency, downtime, clearinghouse behavior, and third-party charges need security, legal, payer, and vendor approval.
Therapy, pharmacy, laboratory, transport, and outside suppliers
Information in scope
Approved service-order, schedule, delivery, documentation, vendor, consolidated-billing, exception, and reconciliation references can help teams coordinate the covered or noncovered stay context.
Boundary
A scheduled or delivered service is not coverage or payment. Current consolidated-billing scope and exclusions require qualified review; the agent does not direct treatment, select a supplier, or adjudicate a vendor invoice.
Billing, claims, Medicaid eligibility, notice, and document archive
Information in scope
Approved claim-period, bill type, authorization, payer response, notice, delivery, application, eligibility, patient-liability, remittance, appeal, and document-version references can support closeout.
Boundary
The workflow does not determine final liability, eligibility, claimability, coding, payment, appeal merit, or legal sufficiency. Official notices and records remain in designated systems under approved retention and correction controls.
Estimate administrative capacity with a formula you can audit
Use a transparent cases × minutes saved × loaded labor rate model for referral assembly, source checking, review preparation, ledger reconciliation, and task routing only. This illustration uses 160 admission or continued-review cases per month, 24 administrative minutes saved per case, and a $40 hourly loaded labor rate. Replace every input with your own measured baseline and silent-run result; do not label the output as cash savings, revenue, denial reduction, coverage, payment, access, occupancy, or clinical improvement.
Admission or continued-review cases per month
160 cases
An explicitly illustrative volume for showing the formula. The buyer should count only the bounded referral and continued-review cases included in its own baseline and avoid combining unrelated work.
Administrative minutes saved per case
24 minutes
An explicitly illustrative time input for document navigation, requirement mapping, packet versioning, ledger reconciliation, and task routing. Required clinical, notice, coding, and payer review time remains in the process.
Loaded labor rate
40 dollars per hour
An explicitly illustrative wage-plus-burden planning rate. Finance should replace it with the approved loaded rate for the roles and administrative work included in the local measurement.
Formula
160 cases × 24 minutes saved per case ÷ 60 minutes per hour × $40 loaded labor rate = $2,560 illustrative monthly labor capacity.
Illustrative result
$2,560 of illustrative monthly labor capacity, before software subscription, usage, third-party data, interface, validation, source-maintenance, training, change-management, and internal governance costs.
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
The hospital-status references conflict before transfer
A referral packet contains one source describing an inpatient stay and a later source describing observation status. The Medicare coverage question and the facility's clinical review are both open. This example contains no real person, hospital, facility, date, payer, or record values.
- The Referral and Coverage Anchor Agent preserves both source versions and marks the qualifying-stay question unresolved.
- The Hospital Record Readiness Agent continues mapping clinical sources for qualified facility review without treating the coverage conflict as clinical rejection.
- Admissions staff request authoritative status clarification through the approved hospital channel and verify whether any documented waiver or appeal path is relevant.
- Qualified clinical leaders decide capability and acceptance separately; qualified Medicare staff decide how the verified status affects the coverage path.
Illustrative outcome: The illustrative result is a visible fork with accountable owners, not a guessed three-day calculation. Transfer, admission, coverage, and payment remain separate decisions, and no software output promises a covered Part A stay.
Illustrative example
A managed-care response contains two different authorization scopes
A payer response gives a day count that does not reconcile with its stated through-date, while the next concurrent review is approaching. A fax receipt confirms transmission of the last packet but does not establish how the payer resolved the conflict.
- The Authorized-Day and Concurrent Review Agent matches the response to the correct episode and released packet version, then preserves both scope fields.
- The ledger displays no remaining balance and keeps the internal preparation target distinct from the unresolved payer deadline.
- A managed-care specialist verifies the substantive response through the approved payer channel and records the human interpretation with source evidence.
- If services may end, notice staff use the current program and trigger to evaluate the applicable NOMNC, DENC, plan-notice, or other path rather than selecting a form from the authorization status alone.
Illustrative outcome: The illustrative result is a reviewable correction and notice-decision path. Clinical care does not change because of an arithmetic conflict, and downstream teams use the scope only after qualified verification.
Illustrative example
A Medicare coverage transition may also require Medicaid work
A resident may continue to need nursing-facility services after the current Medicare coverage path changes, and the business office is exploring a state Medicaid application. The clinical transition, Medicare notice, Medicaid eligibility, facility certification, private-pay, and claim questions are all distinct.
- The Notice, Transition, and Appeal Agent presents the current Medicare notice candidates and the separate state Medicaid workflow with their sources and unresolved triggers.
- Qualified notice staff decide whether an SNF ABN, NOMNC, requested DENC, plan notice, or another communication applies and approve delivery.
- Medicaid specialists verify the state program, facility certification, eligibility, level-of-care, application, managed-care, and resident-liability requirements.
- Clinical, social-work, resident-rights, finance, and billing teams keep the care plan, resident choices, coverage, claim, and payment states visible without treating an application as approval.
Illustrative outcome: The illustrative result is coordinated work without an automatic payer conversion or liability estimate. The resident or representative receives human-approved information and retains applicable decision and appeal rights.
Start with one referral lane and one payer path
Adopt a bounded workflow whose sources, roles, clocks, and failure modes are understood. Test with synthetic, non-identifying fixtures before any approved production use, then run silently beside the current process. A pilot is ready only when qualified users can explain every output, catch unsafe errors, override it, reconcile every write, and return to a tested manual queue.
Map the before-state and choose the first slice
- Choose one facility, referral source, service lane, payer or program, and admission or continued-review work type
- Document the current handoffs from referral through record collection, clinical review, coverage, certification, assessment, payer response, notice, billing, and appeal
- Name authoritative source owners, human decisions, approved channels, disclosure limits, downtime steps, and unresolved policy questions
- Baseline case volume, hands-on administrative time, queue age, repeated outreach, corrections, overrides, and explanation quality without moving PHI into marketing analytics
Exit criteria: Admissions, clinical, utilization-review, MDS, therapy, notice, billing, privacy, compliance, security, finance, contracting, legal, and resident-rights owners agree on scope, exclusions, baseline, manual fallback, and who can stop the pilot.
Configure sources, semantics, and decision rights
- Define episode matching, referral states, coverage paths, source hierarchy, skilled-evidence questions, certification prompts, assessment dependencies, and payer-response states
- Define date, day, level, unit, acknowledgement, supersession, notice-trigger, and transition semantics without inventing payer rules
- Configure minimum-necessary roles, fields, channels, retention, release approvals, accessibility handling, write-backs, reconciliation, correction, and rollback
- Document every proposed integration permission, vendor dependency, licensing term, response limitation, downtime queue, and separate cost
Exit criteria: Owners approve the source registry, clinical and admission firewall, data map, authorized-scope arithmetic, notice decision rights, security controls, test plan, and commercial assumptions. Unknown authority remains a hold.
Run synthetic tests and a silent comparison
- Exercise synthetic routine and exception fixtures for wrong episodes, observation conflicts, missing records, payer changes, late corrections, ambiguous scope, hospital returns, benefit transitions, and portal downtime
- Use approved minimum-necessary production references only after synthetic tests pass and buyer controls authorize the silent run
- Compare agent anchors, evidence maps, reminders, assessment dependencies, packet versions, response states, notice candidates, and downstream tasks with qualified staff
- Measure false matches, missed gaps, stale sources, misleading balances, unsafe suggestions, privacy exceptions, reconciliation failures, overrides, and explanation quality by risk
Exit criteria: The team accepts source fidelity, confidence thresholds, exception behavior, calculation accuracy, privacy and accessibility behavior, integration acknowledgement, manual fallback, and risk-based comparison results. Agents still do not release or write back autonomously.
Pilot with named approvals, then expand by change control
- Allow only named users to approve clinical-source use, certification prompts, packet content, disclosure, destination, release, response interpretation, ledger changes, notices, and appeal preparation
- Rehearse wrong-recipient, late-source, payer ambiguity, missing signature, portal outage, unsafe output, notice error, correction, rollback, and incident escalation
- Review adoption, explanation quality, exception burden, measured time, workload movement, subscription and usage charges, third-party costs, source maintenance, and unintended consequences
- Expand one facility, referral source, payer, program, service lane, notice type, response type, or integration at a time through documented approval
Exit criteria: Every risk owner signs the acceptance evidence for the released slice; users can explain and override outputs; clinical, facility, payer, resident, and legal authority remains intact; fallback is tested; total cost is understood; and humans approve 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.
Skilled nursing facility care
Medicare.gov · government · reviewed
Current official public description of limited Part A SNF coverage conditions, the qualifying inpatient hospital stay and identified waiver context, generally timely SNF entry, daily skilled care, certified-facility context, benefit-period days, and 2026 cost sharing. It does not determine a real stay.
42 CFR 424.20—Requirements for posthospital SNF care
Electronic Code of Federal Regulations · government · reviewed
Current eCFR text addressing Original Medicare posthospital SNF certification and recertification content, timing, and signature authority. It supports a human-reviewed certification workflow within its legal scope, not autonomous clinical or coverage decisions.
Beneficiary Notices Initiative
Centers for Medicare & Medicaid Services · government · reviewed
Current official CMS notice hub distinguishing the FFS SNF ABN financial-liability notice from FFS and MA NOMNC and DENC expedited-determination notices, along with stated provider types and purposes. Current forms and instructions still require case-specific human review.
Minimum Data Set (MDS) 3.0 Resident Assessment Instrument Manual
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS page for the current MDS 3.0 RAI Manual, item sets, change information, and Section GG guidance context. It supports version-controlled assessment coordination while leaving assessment responses and clinical interpretation to authorized professionals.
Patient Driven Payment Model
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS overview and resources for PDPM classification under the SNF prospective payment system for covered Part A stays. It supports keeping payment classification current and reviewable without presenting PDPM as a universal coverage decision.
SNF Consolidated Billing
Centers for Medicare & Medicaid Services · government · reviewed
Current official CMS overview of SNF consolidated-billing responsibility for covered Part A stays, the stated noncovered-stay therapy context, and limited excluded services. It supports service- and stay-specific reconciliation rather than a universal vendor-billing rule.
Medicare Managed Care Appeals & Grievances
Centers for Medicare & Medicaid Services · government · reviewed
Current CMS entry point for Medicare Advantage organization determinations, appeals, grievances, and updated 2026 Parts C and D guidance. It supports plan-specific response and appeal routing rather than treating an authorization status as the final answer.
CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS summary of defined impacted payers, non-drug prior-authorization operational provisions, denial-reason requirements, decision timeframes, and API compliance dates. It does not prove that a particular SNF transaction or integration is available.
Nursing Facilities
Medicaid.gov · government · reviewed
Official federal overview of Medicaid nursing-facility services, state certification and level-of-care context, state-plan variation, eligibility, Preadmission Screening and Resident Review context, and transitions from Medicare or private payment. State-specific verification remains necessary.
Medicare Secondary Payer
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS overview of situations in which another entity may pay before Medicare, including defined workers' compensation, no-fault, and liability contexts and conditional-payment concepts. It is not a case-specific coverage, settlement, recovery, or legal conclusion.
Minimum Necessary Requirement
U.S. Department of Health and Human Services · government · reviewed
Official HHS guidance on the HIPAA Privacy Rule minimum-necessary standard, organization-specific policies, routine and non-routine requests, and stated exceptions. It supports buyer-controlled purpose, role, and disclosure rules rather than a universal software limit.
Skilled nursing facilities workflow FAQs
Open a question to review the answer. The disclosure controls use native browser behavior and remain available by keyboard without page JavaScript.
What does skilled nursing facility utilization review mean here?
It means a governed administrative workflow for referral anchoring, hospital-record readiness, coverage-source mapping, certification prompts, MDS and PDPM dependencies, continued review, authorized-scope reconciliation, notices, payer transitions, billing handoffs, and audit history. It is not a utilization-review committee, payer, EHR, MDS assessor, clinical decision system, or guarantee of coverage or payment.
Does this replace our SNF EHR, referral platform, or billing system?
No replacement is assumed. The control tower can coordinate approved references and tasks around systems the buyer designates, then return limited status or audit information under validated field contracts. Every connector, permission, write-back, acknowledgement, reconciliation rule, downtime path, vendor dependency, and charge must be tested in the buyer's actual environment.
Can an AI agent decide whether a resident needs skilled care?
No. Agents can locate explicit source material, compare versions, and show which administrative question lacks an approved answer. They cannot diagnose, assess risk, determine skilled need or medical necessity, choose a level or plan of care, certify or recertify services, complete an assessment by inference, sign an attestation, conduct a clinical peer discussion, or replace qualified clinicians and payer reviewers.
Does the workflow automatically apply Medicare's three-day rule?
No. It presents current Medicare sources and the verified hospital-status chronology to qualified staff. Medicare.gov describes the qualifying inpatient hospital stay, explains that observation and emergency time do not count, and identifies waiver and appeal context. The workflow does not count uncertain time, assume a waiver, resolve a status appeal, or promise Part A coverage.
Does a completed MDS or PDPM group prove continued coverage?
No. MDS assessment work, Section GG source evidence, PDPM classification, clinical documentation, certification, coverage, coding, service delivery, claim adjudication, and payment are connected but distinct states. Authorized MDS, clinical, coding, billing, and payer professionals determine their own work from current sources; the agent only exposes dependencies and conflicts.
How does the authorized-day tracker avoid a false balance?
It preserves the payer's own start date, through-date, day count, service level, conditions, review date, and response version, then keeps authorized, scheduled, delivered, documented, assessed, billed, adjudicated, and disputed states separate. Any approved calculation shows its inputs. Conflicting or ambiguous scope produces no usable balance until qualified staff resolve it.
Is a fax receipt, portal upload, or API response treated as approval?
No. Drafted, approved for release, transmitted, acknowledged, under review, approved, partially approved, denied, and closed are separate states. A technical receipt proves only the event it records. The ledger changes from a verified substantive response matched to the correct episode and request version, with human review where required.
Are the SNF ABN, NOMNC, and DENC interchangeable notices?
No. CMS describes the SNF ABN as an Original Medicare fee-for-service financial-liability notice for its defined circumstances. CMS describes the NOMNC as an FFS and Medicare Advantage notice when covered services are ending, and the DENC as a detailed explanation given only after an expedited determination is requested. Qualified notice staff must verify the current program, trigger, form, instructions, and facts.
Can the workflow convert a Medicare stay to Medicaid automatically?
No. A Medicaid nursing-facility path depends on the state program, eligibility, facility certification, level-of-care process, managed-care arrangement, application, effective date, and other current requirements. The workflow can coordinate source-linked tasks, but state Medicaid specialists and authorized agencies make eligibility and coverage decisions, while residents or representatives retain applicable choices and rights.
Can one ruleset cover Original Medicare, Medicare Advantage, Medicaid, and commercial plans?
No. The shared chronology can coordinate the work, but benefit categories, qualifying conditions, authorization, network, level-of-care, certification, notice, review, appeal, claim, and payment rules vary by payer, plan, program, state, contract, setting, service, and effective date. Every branch records its selected source and accountable human owner.
How does consolidated billing fit the coverage workflow?
The workflow can make the verified covered or noncovered stay context, service date, supplier, order, and current CMS exclusion reference available for qualified reconciliation. It cannot decide that a service is bundled or separately payable, direct care, code a claim, adjudicate an invoice, or replace the SNF, supplier, billing, compliance, and Medicare contractor review.
How should a facility validate the agent team before adoption?
Start with synthetic fixtures, then run a bounded silent comparison under approved controls. Measure wrong-episode matches, missed document gaps, stale sources, deadline errors, misleading balances, unsafe clinical suggestions, notice-path errors, privacy exceptions, write-back failures, overrides, and explanation quality by risk. Require cross-functional sign-off, tested downtime, correction, and rollback before expansion.
What belongs in GA4 and Search Console measurement for this page?
Only approved non-PHI route, page-family, specialty, workflow, content-cluster, engagement, and CTA context belongs in GA4. Search Console evaluation uses aggregate page clicks, impressions, CTR, average position, and non-sensitive query themes. Resident, clinical, payer, provider, facility, authorization, claim, notice, day, unit, portal, credential, and free-text values stay out.
What does implementation cost, and is the software free?
No, the software is not free. $0 implementation fee. $0 customization charges. Those terms apply to the agreed implementation and customization scope. Software subscription and usage charges are separate and still apply. Third-party data, payer, clearinghouse, portal, interface, licensing, validation, migration, training, source maintenance, internal change-management, travel, and out-of-scope work may carry separate charges stated in the order form.
Bring one difficult SNF referral or continued-review lane
Choose one facility, referral source, payer path, and non-PHI process map. We will identify the current source chain, before-and-after handoffs, human decision rights, MDS and PDPM boundaries, authorized-scope semantics, notice branches, integration limits, validation measures, manual fallback, total-cost questions, and transparent cases × minutes × loaded-rate model. Do not submit resident, clinical, payer, provider, facility, authorization, claim, notice, day, unit, portal, credential, or free-text case values through the marketing form.