See payer risk and margin before the bed is held.
AdmitScore™ reviews referral packets so your team can decide on admissions with payer, authorization, documentation, and financial context already on the page. The Founding Facility Pilot is a structured 60-day evaluation with hands-on launch support.
Pilot pricing is scoped, not retail. Public forms remain PHI-free; secure data workflows are scoped separately under a signed BAA.
Built by people who have done admissions and operations.
Builds AdmitScore™ with healthcare operators in mind. Owns product, engineering, and pilot scoping for every founding facility.
Licensed Nursing Home Administrator with frontline operations and turnaround experience. Translates pilot findings into staff-friendly workflow.
Founding facilities work directly with Jack and Peter. No tiered support queue. Email and scheduled check-ins included throughout the pilot.
Scoped pricing, not a retail rate.
Founding Facility Pilot pricing is shaped by what the engagement actually involves, not a published price card. We share a quote after the screening call so the number reflects your real scope.
- Facility count: single facility or portfolio of locations.
- Monthly packet volume: estimated referrals reviewed during the pilot.
- Workflow complexity: payer mix, decision roles, integrations requested.
- Security scope: BAA, secure data exchange, and any custom contracting.
- Founding-partner status: discounted rates may apply for qualified pilot sites.
Range placeholder for VeriSight team to set: founding cohort typically $___-$___ per
facility per month. Edit in config/pilot-status.json via
publishedPriceRange.
Teams that need a more consistent referral review process.
Admissions leaders
Teams reviewing payer, documentation, service-line fit, and acceptance questions under time pressure.
Administrators and operators
Leaders who want visibility into why referrals are accepted, deferred, declined, or followed up.
Clinical and finance reviewers
Staff who need payer, medication, documentation, PDPM, and care-cost context before the decision.
A practical rollout, not a generic demo account.
Workflow review
Current intake process, decision roles, payer mix, packet volume, and follow-up patterns.
Configured review categories
Payer risk, authorization readiness, documentation gaps, medication flags, facility fit, and financial context.
Hands-on launch support
Training, usage review, support during early adoption, and refinement based on staff feedback.
Outcome tracking
Accepted, deferred, declined, and follow-up outcomes tracked by payer, source, risk type, and facility.
Security planning
Public forms stay PHI-free. Any live-data workflow requires appropriate contracting and secure workflow review.
End-of-pilot readout
Summary of usage, workflow fit, recurring risk patterns, and recommended next steps.
What we ask from your team during the 60-day pilot.
Reviews AdmitScore™ output on real referrals and confirms or adjusts the workflow flags.
Watches admissions decision patterns, payer mix shifts, and staff feedback; signs off on pilot scope changes.
Verifies medication, documentation, and PDPM context on flagged packets before acceptance.
Joins the kickoff call and the mid-pilot review with VeriSight Analytics™.
Commitment is structured to fit normal workflow. Pilots end with a written readout and no obligation to continue.
Defined scope keeps the pilot useful.
Pick pilot users
Admissions, administrator, clinical, finance, and implementation contacts are defined before launch.
Set packet volume
We agree on approximate monthly packet volume and the types of referrals the team wants to evaluate.
Review outcomes
We look at decision consistency, missing documentation patterns, payer issues, and staff feedback.
Clear limits make the evaluation more credible.
AdmitScore supports review. Facility staff remain responsible for final admission decisions.
Revenue and margin outputs are planning estimates, not reimbursement guarantees.
AI-extracted payer, authorization, and clinical information should be verified before action.
Do not submit patient records or confidential clinical information through public contact forms.
After you click “Request a Pilot.”
Timeline assumes a standard pilot scope. Multi-facility or custom security workflows extend kickoff by a few weeks.
Questions buyers ask before requesting a pilot.
Do we need a signed BAA before the pilot starts?
Yes for any live patient data workflow. The screening call covers the BAA template and contracted secure data exchange before AdmitScore™ reviews real referral packets. Public website forms remain PHI-free at all times.
How long is the pilot, and what's the time commitment?
The Founding Facility Pilot is 60 days from kickoff. Roles and weekly time are listed in the “Time commitment” section above. Pilots end with a written readout and no obligation to continue.
What integration is required to start?
None at minimum. AdmitScore can review uploaded PDF packets, email-forwarded referrals, or manual entry. Optional EHR or referral management integrations are discussed during scoping; the pilot can run before or instead of integration.
How does pilot pricing work?
Pilot pricing is scoped, not retail. The variables are listed in the “Pricing structure” section above. Founding-cohort discounts may apply. We share a quote after the screening call so it reflects your actual scope.
What does VeriSight Analytics™ do during the pilot?
Hands-on launch support, weekly check-ins, and direct founder access for the duration. Mid-pilot review at day 30. End-of-pilot readout with recurring risk patterns and recommended next steps.
What if AdmitScore doesn't fit our workflow?
The pilot is designed to surface that. If AdmitScore is not the right tool, the end-of-pilot readout says so and the engagement ends cleanly. No automatic conversion to a paid contract.
Request a Founding Facility Pilot.
Tell us your facility count, referral volume, biggest admissions challenge, and what you want to evaluate.
Request a Pilot