medicaid-caseworker-correspondence

name

medicaid-caseworker-correspondence

description

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.

Medicaid Caseworker Correspondence

Draft a letter or email to the county JFS caseworker (or the Ohio Department of Medicaid where the county has kicked the matter upstairs) in the user's house voice. These letters move slowly by mail and faster by email; the standard output is a markdown email-ready letter, with an optional .docx twin for certified-mail backup.

The recurring reality: a facility's business office files Medicaid paperwork on the resident's behalf, sometimes misfiles it, sometimes withdraws it, sometimes lists the wrong authorized representative, sometimes picks the wrong pathway. The POA's correspondence is the corrective record.

Inputs to collect

1. Letter type — one of:

   • APP-FILED — Application-as-filed / withdrawal-documentation request
   • AR-CORRECT — Authorized-representative correction (replace facility-listed rep with POA)
   • BACKDATE — Backdating / retroactive-coverage request (withdrawals or misfilings against POA instruction)
   • PATHWAY — Pathway correction (LTC-to-community or community-to-LTC recharacterization)
   • STATUS — Application-status inquiry and written response request
   • COPAY — Copay / spend-down inquiry during pending adjudication

   If the user is unsure, briefly describe each type and what triggers it (one line each). Do not pick for the user. See references/letter_types.md for the full template-and-framing per type.

2. Case identifiers — county case number and state case number (if assigned). Caseworker name, email, direct phone if known. County of filing (the county JFS office is the primary venue; ODM handles appeals and certain escalations).

3. Facility identity — facility name, the business-office or admissions staff who originated the filing (by name if known), the corporate parent (where the corporate billing entity is different from the facility).

4. POA block — use the case profile's canonical POA / authorized-representative block when available; otherwise confirm the representative's role and resident identifiers. POA documentation is available on request; the boilerplate is "documentation of that authority is on file and available again on request."

5. Triggering event — 2–4 sentences on what happened that warrants the letter. Example: "facility's business office told me on 4/14 that they had 'withdrawn' the Medicaid application; I have received no paperwork documenting the withdrawal, the asserted reason, or who authorized it."

6. Findings directory (optional) — path to <prefix>_HotItems.md / <prefix>_Findings.md if the user wants to attach chart citations (most commonly the MEDICAID-tagged findings around signing dates vs. cognitive status). Fail gracefully if absent.

Preparation

1. Read references/letter_types.md in this skill's directory to load the per-type framing, required recitals, regulatory citations, and typical asks.
2. If a findings directory was supplied, read <findings-dir>/<prefix>_HotItems.md and <findings-dir>/<prefix>_Findings.md and identify MEDICAID-tagged findings and any LTC-DISPUTE findings relevant to pathway.
3. Re-read ${CLAUDE_PLUGIN_ROOT}/skills/snf-records-review/RUBRIC.md for tag semantics.

Letter structure (all types)

**To:** <caseworker name + email, or "Caseworker of Record"> — <County> County Job and Family Services
**Cc:** <supervisor if known>, <ODM contact if applicable>
**From:** {{POA_NAME}} ({{POA_ROLE}} for {{RESIDENT_NAME}}, DOB {{RESIDENT_DOB}})
**Date:** <full date>
**Subject:** <Letter Type>, Case <case number>, <Resident Name>

Dear <Caseworker Salutation>,

Body:

1. Opening recital — identify the resident and case number, identify the POA, identify the triggering event by date. One short paragraph.
2. POA authority — "In my capacity as the duly appointed {{POA_ROLE}} for {{RESIDENT_NAME}}, documentation of that authority is on file and available again on request." One sentence; do not re-argue authority.
3. What I am asking for — numbered list. Each item is a concrete, documentable deliverable: a copy of a filed form, a correction to the case record, a written response by a specific date. No "please help" asks.
4. Regulatory basis — short paragraph citing OAC 5160:1-2-01 for application processing obligations, and (where AR or POA issues exist) ORC Chapter 1337 for POA authority. Flag all Ohio-specific citations for user verification.
5. Why this matters — one paragraph framing the business consequence of non-response: the resident's coverage is at risk, the retroactive-coverage window is running, the spend-down is being calculated on assumptions that may be wrong, etc.
6. Deadline — firm business date for a written response. Bold it. Default: 10 business days out for routine status letters, 5 business days for a withdrawal-documentation request where the withdrawal is recent.
7. Close — confirmation-of-receipt request, correct routing for further correspondence, POA signature block with email and phone.

Tone and style

• Direct, specific, and deadline-driven. State facts rather than conclusions, cite every factual sentence, enumerate the asks, and set a firm response date. No rhetoric and no adjectives of outrage — anger gives the reader a reason to discount the letter.
• Caseworkers are not the adversary; they are often the bottleneck. Write to someone who wants to do their job but has 400 other cases. Make it easy to say yes.
• Do not editorialize about the facility's conduct in the caseworker letter. That is the subject of a different letter (→ state-agency-complaint). Here, the caseworker needs documentation and a path forward.
• First-person throughout. "I am writing," "I understand," "I request."
• Enumerate. JFS staff triage letters by scanning the numbered asks. A 600-word paragraph of narrative gets skipped; a 200-word numbered list gets answered.

Citations to anchor on

• OAC 5160:1-2-01 — Ohio Administrative Code, Medicaid application processing. Application receipt, determination timelines, applicant rights, documentation of withdrawals.
• Three-month retroactive coverage window — Ohio Medicaid's retroactive-coverage provision. Reference by name; user: verify before submission — confirm current OAC section, timeframe, and any pathway-specific variation before relying on this in a letter.
• ORC Chapter 1337 — Uniform Power of Attorney Act. Cite where the facility has acted contrary to POA instruction, especially for AR-CORRECT and BACKDATE letters alleging that a withdrawal or filing was contrary to POA direction.

Every state-specific citation carries the [user: verify before submission] marker, same pattern as snf-appeal-supplement.

Execution

1. Create the output directory if it doesn't exist. Default: the user's workspace root or a medicaid-correspondence/ subdirectory.
2. Output filenames:
   • Markdown (email-ready) — Email_<County>JFS_<LetterType>_<YYYY-MM-DD>.md
   • Optional .docx (for certified mail) — same stem, .docx extension, via the docx skill.
3. Show the draft to the user for approval before finalizing. Highlight every [user: verify before submission] marker in a short post-draft checklist.
4. On approval, suggest an admin-interaction-log entry recording that the letter was drafted / sent, with the case number and deadline.
5. If case-context/ exists, suggest adding the letter to document_index.md, the response date to deadlines.md, and any case-status uncertainty to open_questions.md.
6. If the Gmail draft tool is available (gmail_create_draft), offer to create a draft; otherwise the markdown file is copy-paste-ready.

Guardrails

• No legal advice. The user can cite ORC 1337; the skill can explain the statute's existence; it should not assert how the statute applies to the case. Frame as "the following appears to be contrary to ORC 1337's POA provisions, and I ask that the case record be corrected accordingly."
• No medical advice. Do not characterize cognitive-status findings. Cite the finding; note the date proximity to the signature date; let the record speak.
• Preserve citations verbatim. Never paraphrase a chart quote when passing it from _HotItems.md into the letter.
• PHI handling. Case number, name, and DOB are appropriate for JFS correspondence. SSN only if the caseworker has asked for it in writing; do not include reflexively.
• Scope to the letter type. Do not mix letter types — six separate letters are better than one omnibus letter, because each gets tracked and answered separately. If the user describes two distinct issues, offer two letters.
• County vs. state. If the matter has been formally appealed to ODM or a state hearing is pending, the letter should still be addressed to the county caseworker with a cc to the ODM contact; do not bypass the county. If the user is not sure whether to cc ODM, ask.
• Deadline realism. 5 business days is aggressive; 10 is standard. Do not draft shorter than 5 without a specific reason (e.g., the retroactive-coverage window closes in fewer days).