Quick answer
Use a fixed synthetic revenue-cycle packet to test whether a platform preserves evidence from assessment and prebill dependencies through claims, remittance and cash. Compare observed behavior with the supplied answer key, including business-claim counts, submitted versions and unresolved differences. The calculations here are completed paper exercises; they are not results from a live vendor, payer connection or Ease product.
Bring an answer key, not a feature checklist
This original synthetic packet lets a CFO, MDS lead and business-office manager evaluate the connection between clinical evidence and finance. All identifiers, decisions and amounts are invented. The arithmetic has a completed answer key below; no live product or payer was tested.
A general usability demo can measure navigation. This exercise asks whether the financial record remains true when a source changes, a response is missing and cash initially fails to match.
The CMS SNF Billing Reference identifies accepted-assessment alignment and monthly claim sequencing as real SNF dependencies. The CMS payment and remittance guidance distinguishes claim and provider-level financial events. The packet turns those boundaries into original software acceptance cases rather than providing real claim codes or coverage decisions.
Packet 1: Two accounts, three open questions
Use two fictional October accounts, A and B, at one provider. Assume qualified reviewers have independently established the coverage and clinical facts needed for the exercise.
| Account | Starting state | Open question |
|---|---|---|
| A | Draft claim A0: $6,500 | Accepted-assessment evidence is not linked |
| A | Same draft; prior-period claim P is separate historical context | Required preceding-period processing evidence is unresolved |
| B | Claim B0: $3,600 transmitted | No usable receipt/status evidence yet |
There are two accounts and three dependencies. Historical claim P is not included in the packet's October receivable or payment totals.
First supply the accepted assessment for A. Expected result: one dependency for A closes; the sequencing dependency remains. A single upload must not mark the whole account ready. Then supply the required prior-period processing evidence and complete the relevant release review. Claim A0 can proceed through the exercise's approved submission path.
Supply a matched response for B. An automated status job with 20 attempts but 18 usable matched responses should report 18 usable results and 2 exceptions, not 20 completed status tasks. Use one of those exceptions to test B's follow-up ownership before providing its response.
Packet 2: A correction must preserve what left the system
After A0 is transmitted and acknowledged, introduce reviewed source evidence changing the correct draft amount to $6,400. Create corrected version A1 and follow the applicable correction workflow. Label external responses in the demo as simulated unless they are verified live test responses.
The answer key now has:
- Two current business claims: A at $6,400 and B at $3,600; current total $10,000.
- Three transmitted versions: A0, $6,500; A1, $6,400; B0, $3,600.
- One correction movement: − $100 on A, with A0 retained exactly as transmitted.
The sum of every transmitted version is $16,500, but that is not the current receivable. A report using that total fails the fixture. The original assessment and correction evidence should remain tied to the versions that used them.
Have a facility backup take over. That person must locate the accepted assessment, resolved sequence condition, current claim version and actual response without a verbal explanation from the demonstrator. Record whether the task required the vendor's elevated access or can be performed by the intended staff role.
Packet 3: Reconcile adjudication before the bank
Provide this fictional remittance for the two current claims. Assume its claim-level reductions are supported contractual obligations of the provider; they are separate from the provider-level additions and deductions below. The exercise does not create resident balances.
| Item | Claim basis | Claim-level reduction | Payment |
|---|---|---|---|
| A1 | $6,400 | $400 | $6,000 |
| B0 | $3,600 | $600 | $3,000 |
| Claim total | $10,000 | $1,000 | $9,000 |
Add a $400 provider-level deduction and a $25 provider-level addition. Expected transfer is:
$9,000 − $400 + $25 = $8,625.
The initial bank evidence is $8,525. The correct output is $100 unexplained, with a reconciliation owner. Reducing A's payment by $100 to clear the warning fails the test. So does marking the bank match complete merely because a remittance was imported.
Next supply a separate $100 bank entry with evidence confirming that it belongs to the same payment reference. Combined receipt becomes $8,625 and the reference matches. Retain both bank entries and the earlier open difference. Reimport the remittance: no second financial posting should appear.
Record observable outcomes and blocking failures
Use one result per checkpoint: passed with retained evidence, passed with an identified manual control, failed, or not tested. Add observed output, staff role, elapsed effort and the artifact proving the result. Do not fill “observed” from this article's expected column.
| Checkpoint | Expected invariant | Blocking failure |
|---|---|---|
| Dependencies | 2 accounts; 3 initial questions; partial closure stays partial | One document falsely clears every hold |
| Claim history | 2 current claims; $10,000; 3 submitted versions | $16,500 reported as current value or A0 lost |
| Adjudication | $9,000 claim payments; $1,000 claim reductions | Provider item forced onto an arbitrary resident |
| Bank | $8,625 expected; $100 initial difference; then matching two receipts | Unexplained difference hidden |
| Repeated import | Same financial totals; attempt recorded | Duplicate posting |
| Takeover/export | Backup reproduces selected evidence and calculations | Only the presenter can explain the account |
A weighted average must not hide a duplicate payment or lost submitted claim. Repair and rerun the affected path before accepting that financial workflow. A manual control can be an explicit tradeoff if the facility can staff it and retain its evidence; record the recurring work rather than calling it automated.
Carry the packet into implementation
For a new facility or outsourced billing arrangement, assign who supplies evidence, releases claims, monitors responses and reconciles cash. The service's ability to operate a screen does not delegate every clinical, accounting or enrollment decision.
Retest the same packet with the configured facility roles and exports before relying on the first operating cycle. Keep licensing, enrollment and payer authorization prerequisites outside the software test's claim of success. A correct answer key and a reproducible test record establish what was evaluated; they do not establish live availability, coverage or payment performance.
Questions & answers
Does this article report a completed live product test?
No. It provides a synthetic packet and calculated answer key. A buyer must record actual observed outputs separately; a simulated payer response cannot prove a production connection.
Why count both claims and submitted versions?
A corrected claim can create another submitted version without creating another business claim. Counting every version as a new receivable inflates volume and can duplicate payment work.
Can a high total demo score compensate for a duplicated payment?
No. Treat duplicate financial effects, lost submitted history and hidden unexplained cash differences as blocking failures until corrected and retested.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.