See how AdmitScore structures a referral packet review.
This public sample is synthetic and contains no PHI. It shows the type of payer, documentation, medication, operational fit, and verification prompts AdmitScore can surface for skilled nursing admissions teams.
Accept With Caution
Decision-support label for staff review, not an admission directive.
- Payer appears to require Medicare Advantage authorization verification.
- Therapy documentation may be incomplete for skilled-need support.
- Medication list includes a possible high-cost pharmacy review item.
- Wound care and isolation details should be confirmed before acceptance.
Every item is a prompt for verification.
The sample report is designed to show structure, not a clinical conclusion. Real workflows require secure intake, source-document review, and facility decision ownership.
- No PHI: the sample is synthetic and safe for public review.
- No guarantees: scores and margin context are planning aids only.
- Human decision: facility staff verify findings and make final decisions.
What a referral review can surface.
The live pilot scope determines which fields and review surfaces are enabled.
Payer and authorization
Plan type, network questions, authorized days, prior authorization needs, and continued-stay documentation prompts.
Documentation gaps
Missing therapy notes, skilled-need support, orders, history and physical details, or unclear hospital documentation.
Medication and care flags
Possible high-cost medications, wound care, isolation, therapy intensity, staffing, and service-line fit questions.
Administrator-only margin context
Planning context can be separated from clinical Referral Fit so financial pressure does not leak into clinical review.
The sample report shows the review structure, not a promise of admission outcome.
The public example is synthetic. It is meant to show how AdmitScore organizes a packet for staff verification before any real-packet pilot workflow is scoped.
Referral Fit
A financial-free surface for admissions and clinical review, focused on care, operational, payer, and documentation questions.
Margin Score
Administrator-only planning context that should be reviewed separately from clinical fit and never treated as reimbursement certainty.
Source-backed notes
Findings are useful only when staff can verify the source document or see that a source is missing.
Clarification requests
The best output often tells the team what to ask next rather than trying to force a yes-or-no answer.
Use the sample to decide whether a pilot is worth reviewing.
Public website forms should never receive PHI. Live-packet workflows require secure pilot setup.