Provide the packet through approved intake
Keep your current referral source and EHR. The secure pilot intake is scoped during kickoff before any live-data workflow begins.
AdmitScore™
Source-linked SNF referral review before you hold the bed.
AdmitScore™ turns each packet into a structured review of payer and Medicare Advantage authorization questions, documentation gaps, high-cost medications, facility fit, and role-appropriate financial context. Packet-derived findings link back to their source; modeled signals show their inputs. Staff verify every output and make the final decision.
- Packet-derived flags include a source quote and packet page
- Referral Fit for staff; Financial Fit and Margin for administrators
- Approved pilot intake without replacing your current systems
Fits beside your existing EHR, CRM, and referral portals. Pilot review does not require EHR integration.
Definition
What is an Admit Score?
An Admit Score is AdmitScore™'s structured read of a skilled nursing referral packet. It surfaces payer and Medicare Advantage authorization risk, documentation gaps, high-cost medications, and PDPM and margin context so your admissions team can review them before holding the bed. Staff verify every finding and make the final accept, defer, or decline decision.
Fits your current workflow
Keep your systems of record. Add a structured review before the decision.
AdmitScore is not an EHR, CRM, referral queue, bed board, or payer-approval tool. During a pilot, it sits beside those systems and returns a source-linked browser review for staff verification.
Review the evidence, not a black box
AdmitScore organizes payer, documentation, medication, facility-fit, and financial questions. Packet-derived findings link to a source quote and packet page; modeled signals show the inputs staff should verify.
Verify, follow up, and record the decision
Staff confirm the evidence, ask for missing information, and record the final accept, defer, or decline decision in the existing workflow.
One review, role-appropriate context
The same packet, framed for the person making the call.
Admissions and intake
Start with payer and authorization questions, missing documentation, follow-up items, and source links before the bed is held.
Clinical and DON review
Review care needs, medications, behavioral signals, and facility-capability flags without administrator-only financial context.
Administrator and regional operations
Optionally review Financial Fit, margin assumptions, denial-risk planning context, and recorded decision patterns.
What AdmitScore reviews
The admissions questions that matter before saying yes.
Payer and authorization risk
Helps identify payer signals, authorization readiness, and verification steps.
Documentation gaps
Surfaces missing or weak documentation that may affect acceptance, authorization, or handoff, including MDS Section GG signals that staff should verify.
Medication and care-cost flags
Highlights high-cost medication and service needs for facility review.
Scores by role
Referral Fit (financial-free, 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.
Follow-up questions
Creates targeted questions for the hospital, payer, pharmacy, or internal reviewers.
Facility analytics
Tracks decisions and outcomes by payer, referral source, risk type, and facility.
Human-review guardrails
AdmitScore supports review; the facility remains in control.
Final decisions stay with staff
AdmitScore does not replace clinical, operational, payer, or legal judgment.
Verification is required
AI-extracted payer, authorization, and clinical information should be checked against source documents.
No reimbursement guarantees
Revenue, margin, and cost estimates are planning aids and not guarantees.
No public PHI intake
Public forms and public examples should not contain patient records or identifying details.
Evaluate AdmitScore in a Founding Facility Pilot.
Scope pilot pricing by facility count, packet volume, and implementation support needs.
Request Pilot PricingNo PHI on public forms · Staff verify every output and make the final call · BAA in place before any pilot uses real data.