ltc-ombudsman-referral-riverside-manor — PCC/MatrixCare/ALIS exploitation cluster
Riverside Manor ombudsman referral RM-OMB-2026-0312 on resident RES-88421 — break-glass PointClickCare access · cross-resident staff billing exports · MatrixCare progress_note revision hash drift · ALIS visitor check-in after hours. Fully synthetic.
what this proves
- all three LTC primary engines produce deterministic, fixture-locked output on the riverside manor synthetic packet.
- every output is generated 100% locally — facility audit exports never upload.
- pointclickcare break-glass and cross-resident staff pattern · matrixcare progress_note revision hash drift · alis visitor check-in after hours — smoke-honest counts from engine output.
primary engines locked to this fixture
build the case binder
runs all three primary engines on the synthetic evidence zip and opens a self-contained html binder. no upload.
runs all 8 primary engines locally on the synthetic evidence zip · opens a self-contained html binder · no upload
download the synthetic evidence
MIT-licensed, fully synthetic. includes pointclickcare audit ndjson · matrixcare chart export ndjson · alis activity log · ombudsman referral cover letter · chain of custody.
built deterministically from scripts/fixtures/build-ltc-ombudsman-referral-riverside-manor.mjs. seed: ltc-ombudsman-referral-riverside-manor:v1.
methodology
nursing home records audit starts with hashed exports and elder-abuse kit triage, then walks pointclickcare · matrixcare · alis parsers before counsel or ombudsman packet assembly. not clinical diagnosis. read the full nursing home records audit · LTC exploitation guide →