Append a dated, factual entry to an ongoing SNF/facility Admin Interaction Log in terse, cited, third-person prose that states facts without characterizing anyone's motive and without emotional language, so the log can later be attached to a complaint, appeal, or ombudsman filing. Creates the log file if one does not exist yet. Use when the user says "log an interaction", "add an entry to the admin log", "document this call with the facility", "note this for the log", or mentions a phone call / voicemail / visit / email exchange with facility staff that needs to be preserved for the case record.
Review and enrich elder-care audio transcripts from plan-of-care meetings, IDT calls, facility phone calls, voicemail, payer calls, JFS/ODM calls, or staff conversations. Supports local Whisper/Parakeet transcription outputs, speaker labeling/diarization reconciliation, timestamped statement attribution, casework evidence tagging, transcript-quality triage, and routing into admin logs, appeals, complaints, Medicaid disputes, legal-referral packets, and case-context ledgers.
Create or update a durable elder-care case context ledger for long-running Medicare, Medicaid, SNF, facility, payer, and regulatory matters. Use when the user says "case memory", "case context", "update the case file", "track deadlines", "remember this for the appeal", "build a case ledger", or needs canonical facts, contacts, deadlines, document inventory, evidence register, open questions, and decision log across multiple skills and large record productions.
Safely upgrade or migrate an existing elder-care case workspace created with an older plugin layout into the current privacy-first structure without losing source material. Use when the user says "upgrade my case project", "migrate old case folder", "move this case to the new layout", "prepare my existing case folder for this plugin", "don't lose existing findings", or needs a dry-run migration plan, checksums, backup manifest, case-context creation, and no-delete/no-overwrite transfer workflow before publishing or updating the plugin.
Draft a HIPAA records request, itemized billing request, or follow-up / second-request email to a Skilled Nursing Facility or its corporate entity. Style is direct, specific, and deadline-driven rather than hostile — it confirms the requester's legal authority, enumerates exactly what is requested, cites the HIPAA 30-day access right (45 CFR 164.524) and 42 CFR 483.21(c) where discharge planning is at issue, sets a firm response date, and names the regulatory escalation path without threatening litigation. The escalation agencies it names are Ohio's; users in other states must substitute their own state survey agency, insurance regulator, and attorney general before sending. Use when the user says "draft a records request", "follow up on the records request", "second-request email to [facility]", "send a HIPAA letter", needs to escalate unanswered records requests, or wants a narrow supplement based on snf-document-map / snf-review missing-document findings.
Assemble a ready-to-send intake packet for an elder-law attorney, a legal-plan referral (MetLife Legal Plan, LegalShield), or the Area Agency on Aging's legal-services line. Reuses `*_Timeline.md`, `*_HotItems.md`, and `*_Findings.md` from the `/snf-review` pipeline. Tone is cooperative and attorney-facing — the audience is on the user's side. Produces a markdown packet (optionally .docx) whose first page is always a case-in-a-page summary, because attorneys triage on page one. Use when the user says "/legal-referral-intake-packet", "draft MetLife legal plan intake", "elder-law attorney intake", "AAA legal services referral", "assemble legal referral packet", or otherwise signals that it's time to hand the case over (or up) to a lawyer.
Plan privacy-first local AI/model and deterministic-tool offload for expensive elder-care casework analysis. Use for local LLMs/VLMs such as Qwen, GLM, Gemma-class models, LM Studio/lms with OpenAI-compatible API or LM Studio API, Goose CLI, Ollama, llama.cpp, vLLM, local image analysis, OCR, ffmpeg media prep, Whisper, Parakeet, diarization, transcript enrichment, PDF/table extraction, and batch prompt planning. Defaults to plan-only until the user explicitly approves running jobs.
Draft a letter or email to a county Job and Family Services (JFS) caseworker or the Ohio Department of Medicaid, for the recurring patterns that show up when a facility has filed, misfiled, or withdrawn a Medicaid application. Supports six letter types — application-as-filed / withdrawal-documentation request, authorized-representative correction (replacing a facility-listed representative with the POA), backdating / retroactive-coverage request, pathway correction (LTC ↔ community), application-status inquiry, and copay / spend-down inquiry during pending adjudication. Cites OAC 5160:1-2-01 and ORC Chapter 1337 where applicable. Use when the user says "/medicaid-caseworker-correspondence", "draft JFS letter", "JFS withdrawal paperwork request", "Medicaid backdating request", "authorized-representative correction", "follow up with [county] JFS", or otherwise signals it's time to write to a JFS caseworker about a pending, withdrawn, or miscategorized Medicaid application.