fatcousin
// investigation guide

nursing home records audit · LTC exploitation — methodology

this guide is for post-referral examiners — APS investigators, family fiduciaries, probate counsel, and ombudsmen reviewing skilled-nursing or assisted-living records alongside financial artifacts. it is not clinical diagnosis, not a capacity determination, and not a state survey citation template. resident PHI stays local-only in your browser — fatcousin does not upload exports. start with elder abuse financial exploitation kit on bank statements, caregiver device exports, and POA documents. PointClickCare and MatrixCare audit parsers are deferred to BUILD — use adjacent PMP and break-glass tools until those ship. for generic consumer scam intake without LTC context, see report this fraud.

resident privacy — HIPAA-local processing

  • confirm authorized need-to-know under APS, fiduciary, or facility policy before pulling exports
  • hash exports (sha-256) before sharing internally — run evidence-manifest-generator first
  • medication and diagnosis fields may appear in counts without displaying raw PHI in exported findings
  • no clinical diagnosis or capacity conclusions in tool copy — document what exports show
  • ombudsman and state survey contexts — this page documents export shapes, not what regulators should cite
  • loop designated counsel or APS — restorative or protective actions are outside this forensic path

the first 10 minutes

  1. confirm authorized scope — APS referral, fiduciary counsel, ombudsman, or facility compliance officer with need-to-know.
  2. freeze bank and joint-account statements for the disputed window before POA-holder deletes online access.
  3. export caregiver phone backup or device extract if exploitation may involve texts or payment apps.
  4. collect POA instrument pdf + any amendments — hash before sharing internally.
  5. pull PMP/MAR adjacency exports if medication noncompliance is part of the allegation — counts only in findings.
  6. run evidence-manifest-generator on every file before analysis.
  7. run elder-abuse-financial-exploitation-kit on bank + device + POA bundle locally.
  8. imminent harm or neglect in progress → local APS hotline or 911 — this page is not emergency services.

the path

preserve → financial exploitation kit → PMP/MAR adjacency (optional) → break-glass or breach kit (optional) → bundle for APS or counsel. merge exports in fatcousin-multi-tool-super-timeline-correlator when bank, device, and facility artifacts span the same referral window.

  1. 1. evidence manifest generator

    inventory bank csv, device exports, POA pdfs, and facility correspondence with sha-256 hashes before counsel or ombudsman review.why first: exploitation cases lose chain of custody when family members email screenshots. hash before you open statements.

  2. 2. elder abuse financial exploitation kit

    drop bank statements + caregiver device exports + power of attorney docs · exploitation pattern report · runs locally.why second: joint-account and POA misuse is the primary financial-abuse vector — start here until PointClickCare/MatrixCare parsers ship.

  3. 3. controlled substance pmp log forensic analyzer

    state PMP export adjacency when medication diversion or noncompliance is alleged — medication counts may appear without raw PHI in exports.why third: MAR/PMP rows anchor whether a caregiver had prescribing or pickup patterns outside the financial timeline.

  4. 4. hipaa break glass access log forensic analyzer

    break-glass and emergency-access rows when facility EHR access is in dispute — acute-care shaped, not LTC-native.why fourth: useful when you have a hospital break-glass export alongside LTC records — not a substitute for PointClickCare audit csv.

  5. 5. medical records breach investigation kit

    composite kit when unauthorized chart access or PHI disclosure is part of the same referral — distinct from exploitation-only path.why fifth: run when the allegation includes chart snooping or bulk export, not POA/bank misuse alone.

  6. 6. case report generator

    bundle hashed evidence + kit findings into a pdf timeline for APS, counsel, or ombudsman packet.why last: one readable package for investigators who were not in the original export pull.

common false leads

  • acute-care EHR audit (meditech expanse) — LTC PointClickCare/MatrixCare event shapes differ; do not treat as native facility audit.
  • healthcare-clinical vertical tools — skilled-nursing census/clinical modules are vendor-locked; kit-only path until BUILD ships.
  • this is the same as report this fraud — ic3/ftc prep when there is no POA, facility, or LTC records context.
  • nursing-home-records-audit-kit — not on disk; elder-abuse-financial-exploitation-kit is the SURFACE anchor until a dedicated kit ships.

what we can tell you, what we can't

we can tell you:

  • exploitation pattern counts across bank, device, and POA artifacts in the elder-abuse kit
  • PMP pickup/prescriber adjacency counts when state export is in scope
  • sha-256 evidence manifest for referral export packs
  • local pdf case report from hashed exports

we can't tell you:

  • whether a resident lacks capacity — counsel and clinicians decide
  • parse PointClickCare or MatrixCare audit csv natively — BUILD wave deferred
  • upload PHI to fatcousin servers — processing is browser-local only
  • substitute for ombudsman or CMS survey findings — document exports, not regulatory conclusions

deferred — BUILD wave

reference fixture ltc-ombudsman-referral-riverside-manor ships pointclickcare · matrixcare · alis parsers with goldens — run facility exports through those tools before the elder-abuse kit binder step.

handing it off

  • APS investigator: evidence manifest + case report pdf + elder-abuse kit finding csv exports.
  • probate / fiduciary counsel: POA instrument hash + bank timeline + kit entity csv.
  • long-term care ombudsman: export inventory only — no raw resident identifiers in shared email; use hashed manifest.

case type page → · elder care LTC vertical →

ready