AdmitScore™ — source-linked referral review
Know what to verify before you hold the bed.
A source-linked review of every referral packet — payer and authorization gaps, missing documentation, high-cost medications, facility fit, and margin — beside your current EHR and referral portals. Staff verify. Staff decide.
- Packet-derived flags include a source quote and packet page
- Payer, documentation, medication, and facility-fit questions in one review
- Referral Fit for staff; financial context only for administrators
Focused review layer beside your current systems — not an EHR, CRM, bed board, or payer-approval tool · Built with a licensed Nursing Home Administrator · BAA before any PHI
SNF admissions teams are making high-stakes calls from incomplete packets.
Referral review often happens quickly, across disconnected documents, payer rules, operational constraints, and uncertain financial assumptions.
Payer risk is easy to miss
Medicare Advantage authorization, network status, carve-outs, and approved days can change the real answer.
Documentation gaps slow follow-up
Missing therapy notes, orders, med lists, or skilled need support can create back-and-forth at the worst moment.
Financial fit is rarely visible up front
Teams need planning context for PDPM, payer assumptions, medications, and care requirements before saying yes.
Six operator questions organized before you say yes.
Six checks on every packet — payer, authorization, documentation, medications, role-based scores, and the follow-up questions to ask. Every packet-derived flag carries its source quote and packet page for staff to verify. For a deeper look, see how AdmitScore works as SNF admissions software and what a referral packet review covers.
Payer and MA signals
Identifies payer type, Medicare Advantage indicators, network status, and the verification questions to confirm with the plan.
Authorization readiness
Calls out missing details that prior auth or continued-stay review typically require, so staff can submit a complete packet the first time.
Documentation gaps
Surfaces missing therapy notes, skilled-need support, orders, and history-and-physical items that slow follow-up after acceptance. See the MDS Section GG admissions guide.
High-cost medications and care flags
Highlights medications, isolation, wound, therapy, and staffing items that can change the cost or feasibility of admitting.
Referral Fit, Financial Fit + Margin
Referral Fit (financial-free, visible to all roles) keeps the clinical conversation clinical. Financial Fit and Margin (admin-only) layer in PDPM and denial-risk for administrators. Estimates are planning aids, not guarantees of payer reimbursement.
Questions to verify before acceptance
Produces targeted follow-up questions for the hospital, payer, family, pharmacy, or internal clinical team.
From referral packet to review-ready admissions intelligence.
Provide the packet through your approved intake
Teams provide referral documents through the configured workflow — synthetic demo first, live data only after a signed BAA.
AdmitScore builds a structured review
The system extracts payer, clinical, documentation, medication, and financial signals for staff review.
Facility staff verify and decide
Admissions, clinical, and finance users verify source documents, ask follow-up questions, and record the final decision.
The review your team sees on every referral.
Every screenshot below is the real application rendering a synthetic sample packet — pilot conversations focus on workflow value without exposing patient information.
Questions to verify before acceptance
- Has prior authorization been approved for SNF level of care?
- Are therapy notes and skilled need documentation included?
- Are any medications carved out or unusually high cost?
- Does the facility have the staffing and service line fit?
Designed to help teams catch authorization-readiness issues earlier.
AdmitScore does not guarantee payer approval or reimbursement. It helps staff identify potential payer and documentation issues that should be verified before acceptance.
Plan and payer verification
Helps flag payer information that should be confirmed against the referral packet and payer portal. See the Medicare Advantage authorization readiness workflow.
Authorization readiness
Calls out missing details that may be needed for prior authorization or continued stay review.
Skilled need support
Highlights documentation that appears relevant to skilled level of care, for staff verification.
Planning context before acceptance, analytics after the decision.
PDPM and revenue context
Where documentation supports it, AdmitScore provides planning estimates for reimbursement context, including PDPM admissions signals. Estimates are not guarantees.
Cost-driver visibility
Medication, therapy, service, staffing, and supply considerations are surfaced for facility review.
Outcome tracking
Leaders can review accepted, deferred, and declined referrals by payer, source, risk signal, and downstream result.
Built inside a Wisconsin SNF family, piloted with hands-on founder support.
AdmitScore is shaped by the operating reality of skilled nursing admissions: incomplete packets, payer friction, staffing constraints, and the need for staff to verify every output. VeriSight works with each pilot facility to define packet volume, review expectations, risk categories, and outcome tracking.
Admissions leaders, administrators, DONs, finance leaders, and operators evaluating a structured referral review process for one or more facilities.
Healthcare workflows need verification, not black-box decisions.
VeriSight supports admissions review; it does not replace clinical, operational, payer, or legal judgment.
AI-extracted payer, authorization, and clinical information should be checked against the referral packet.
Revenue, margin, and cost outputs are planning estimates and do not guarantee reimbursement or admission outcomes.
Do not submit patient records, PHI, or confidential clinical information through the public website.
Evaluate AdmitScore for your facility.
Request a Founding Facility Pilot to review fit, packet volume, implementation scope, and pilot pricing.
No PHI on public forms · Staff verify every output and make the final call · BAA in place before any pilot uses real data.