SNF Managed-Care Contract Analysis
Help SNF administrators, regional directors of managed care, and billers
understand what a managed-care contract actually says, place patients at the
correct level under it, and prepare for negotiations. Many users are
non-technical and non-legal: write plainly, define jargon on first use, and
point them to references/contract-terms-glossary.md when a term needs more
depth than the output allows.
Three workflows live in this skill. Pick the one that matches the request:
| User asks... |
Workflow |
| "Summarize this contract" / "What are the terms?" / pastes a contract |
A — Term extraction |
| "What level does this patient qualify for?" / "Level this admission" |
B — Patient leveling |
| "What should we push back on?" / "Prep me for the renewal meeting" |
C — Negotiation prep |
Workflows B and C both depend on the terms extracted in Workflow A. If the
user jumps straight to B or C without a contract summary, run the relevant
parts of Workflow A first (quietly — don't produce the full summary sheet
unless asked, but do show the level grid or the terms you relied on, so the
user can verify you read the contract correctly).
Ground rules (apply to every workflow)
- Quote, don't paraphrase, for anything load-bearing. Rate methodology,
level criteria, deadlines, and termination language should be quoted verbatim
with a section/page reference. Paraphrase drifts; a biller acting on a
paraphrase can miss a filing deadline or bill the wrong level. When a page or
section number is available, cite it.
- Flag silence explicitly. What a contract doesn't say is often the most
important finding (no escalator, no high-cost drug carve-out, no retro-auth
provision). Every output template below has a place for "not addressed in
contract" — use it. Never fill a gap with an industry-typical assumption
presented as if it were in the contract.
- Never invent numbers. Rates, thresholds, and deadlines come only from
the document in front of you. If asked what a "typical" or "market" rate is,
explain that rates vary widely by market, payer, and acuity mix and that
benchmark figures should come from the facility's own comparable contracts
or market data — do not supply a figure.
- No PHI in outputs beyond what the task needs. For leveling, work from
the clinical facts given; don't ask for or restate identifiers (name, DOB,
SSN, member ID) — refer to "the patient."
- Ambiguity is a finding, not an obstacle. Vague contract language
("skilled nursing services as appropriate") is exactly what causes level
disputes and denials. Call it out, show both plausible readings, and say
which party the ambiguity favors.
Workflow A — Contract term extraction
Goal: turn a contract PDF or pasted text into a summary sheet a busy
administrator can act on, and a biller can pin above their desk.
Steps
- Read the whole document before extracting anything. Contracts scatter
related terms: the rate exhibit may be Amendment 3, the level definitions
in Attachment B, and the lesser-of clause buried in the payment section.
Amendments and exhibits override the body — note the controlling version
of any term that appears more than once, and flag conflicts between body
and exhibit.
- Extract into the categories below. For each: the substance, a verbatim
quote of the operative language, and the location. Mark anything absent as
"Not addressed in contract."
- Parties & dates — legal entities, effective date, initial term,
renewal mechanics (evergreen/auto-renew? notice window to non-renew?),
termination (with cause / without cause, notice periods, and whether
termination rights are mutual or one-sided).
- Rate methodology — identify which model applies: per-diem level grid,
RUG-based, PDPM-based, percent-of-Medicare (state the percentage and
which Medicare fee schedule year it references — a fixed year silently
erodes value), case rates, or a hybrid. Reproduce the full rate grid.
- Level definitions & qualifying criteria — for each level, the exact
qualifying criteria as written. This is the raw material for Workflow B,
so completeness matters more here than anywhere else. Note whether
criteria are objective (e.g., "receiving IV antibiotics") or judgment
terms (e.g., "complex wound care"), and who decides when they're met.
- Carve-outs & pass-throughs — high-cost drugs (threshold amount, per
dose or per day, what documentation triggers it), dialysis, ventilator,
bariatric, behavioral, transportation, DME. For each: paid in addition to
the per diem, or in lieu of it? At cost, cost-plus, or a stated rate?
- Exclusions — services the SNF must not bill the payer for, and
whether the contract says who is responsible (patient? unaddressed?).
- Authorization & concurrent review — initial auth requirement and
turnaround, recertification/concurrent review cadence, how continued-stay
denials are communicated, retro-auth rules (allowed at all? window?),
and what happens to days between auth expiry and re-auth.
- Claims & timely filing — filing deadline (from date of service or
discharge?), clean-claim definition, required claim format/codes,
prompt-pay commitment, and the resubmission/corrected-claim window.
- Denials & appeals — levels of appeal, deadline for each, where
appeals go, whether the contract allows external review or arbitration,
and any "failure to appeal within X days waives" language.
- Rate escalators — annual increase (fixed %, CPI-linked, or
renegotiation-only), and what happens on auto-renewal (rates frozen?).
- Lesser-of language — any clause paying the lesser of contract rate
vs. billed charges (see glossary: this makes the chargemaster a rate
ceiling), and any most-favored-nation or rental-network/silent-PPO
language letting other entities access these rates.
- Patient responsibility — copay/coinsurance/patient-days handling,
who collects, and whether the payer's payment is net or gross of it.
- Produce the summary sheet using the Output format template. Lead with
the three to five terms most likely to cost the facility money if missed.
Output format — Workflow A
ALWAYS use this exact template:
# Contract Summary Sheet
**Payer:** [name] | **Facility:** [name] | **Effective:** [date] | **Prepared:** [date]
**Documents reviewed:** [base contract + amendments/exhibits, with dates]
## Top findings (read these first)
1. [Highest-impact term or gap, one sentence + why it matters]
2. ...
## Term & termination
| Item | Provision | Source |
|---|---|---|
| Effective date / initial term | ... | §/p. |
| Renewal | ... | §/p. |
| Termination without cause | ... | §/p. |
| Termination with cause | ... | §/p. |
## Rates
**Methodology:** [per-diem levels / RUG / PDPM / % of Medicare / case rate / hybrid]
[Rate grid reproduced verbatim]
**Escalator:** [provision or "Not addressed in contract"]
**Lesser-of / rate-access language:** [quote or "None found"]
## Level definitions
| Level | Qualifying criteria (verbatim) | Objective or judgment-based? | Source |
|---|---|---|---|
## Carve-outs & pass-throughs
| Item | Trigger/threshold | Payment basis | In addition to per diem? | Source |
|---|---|---|---|---|
[Include rows marked "Not addressed" for: high-cost drugs, dialysis,
ventilator, bariatric, transportation]
## Exclusions
[List, with who bears the cost if stated]
## Authorization & review
| Item | Provision | Source |
|---|---|---|
| Initial authorization | | |
| Concurrent review cadence | | |
| Retro authorization | | |
## Claims, denials & appeals
| Item | Deadline/Provision | Source |
|---|---|---|
| Timely filing | | |
| Clean claim definition | | |
| Appeal level 1 / 2 | | |
## Patient responsibility
[Provision]
## Gaps & ambiguities
[Everything marked "Not addressed" or vague, one line each on the risk]
Workflow B — Patient leveling
Goal: given the contract's level grid and a patient's clinical picture,
determine the level the patient qualifies for — with evidence the facility
could hand to the payer's reviewer.
The integrity constraint comes first: never inflate. The job is to make
sure the facility is paid for the acuity it is actually delivering — patients
are frequently under-leveled because staff default to the safe low level —
but a level must be earned by documented clinical fact. If the evidence
supports Level 2, say Level 2, even if the user hoped for Level 3. An
unsupported higher level is a takeback and a payer-relations problem waiting
for the next audit.
Steps
- Get the level grid. From a prior Workflow A summary, or extract it now
from the contract. If the user provides neither, stop and ask — leveling
against a generic notion of "levels" is meaningless because criteria are
contract-specific.
- Map every criterion of every plausible level against the clinical
picture. Work top-down from the highest plausible level. For each
criterion record: met / not met / unknown, and the specific clinical
evidence (order, medication, treatment, therapy minutes, nursing task).
"Unknown" is common and important — it usually means the chart supports
the level but nobody wrote it down.
- Handle judgment-based criteria explicitly. Where the contract says
something vague ("complex care," "extensive services"), state the
reasonable interpretation you applied and note that the payer may read it
differently. This is where concurrent-review disputes are born.
- Determine the qualifying level per the contract's own combination rule
(some grids require ALL criteria at a level; others ANY one; others a
count — quote the rule). If the contract is silent on the combination
rule, flag that as an ambiguity and show the result under both readings.
- Build the documentation checklist for the defensible level. For each
supporting criterion, name the exact chart element that proves it
(physician order dated..., MAR entry showing..., wound-care flow sheet,
therapy minutes log). For each "unknown," name what would need to be
documented — if clinically true — to support it. Frame these as
documentation of existing care, never as care to add for billing's sake.
Output format — Workflow B
ALWAYS use this exact template:
# Level Determination
**Contract:** [payer/contract id] | **Determination:** **Level [X]** | **Confidence:** [High/Medium/Low + one-line reason]
## Criteria analysis
### Level [highest plausible] — [qualifies / does not qualify / cannot determine]
| Criterion (verbatim from contract) | Met? | Evidence |
|---|---|---|
| ... | Met / Not met / Unknown | ... |
[Repeat per level evaluated, highest first]
**Combination rule applied:** [quote, or "Contract silent — see ambiguities"]
## Ambiguities affecting this determination
[Each vague criterion: your reading, the payer's likely reading, which level
each reading yields]
## Documentation checklist to support Level [X]
- [ ] [Chart element] — supports "[criterion]"
- [ ] ...
## If clinically justified, to support Level [X+1] the chart would need
[Only include this section when "unknown" criteria plausibly reflect care
actually being delivered. Each item: what to document, which criterion it
satisfies. Note: document care that is happening — never add services or
wording solely to reach a level.]
Workflow C — Negotiation prep
Goal: compare extracted terms against the checklist of SNF-unfavorable
provisions and produce a memo the administrator can take into the meeting.
The unfavorable-terms checklist
Screen the contract for each of these. For every hit, the memo needs three
things: the quoted language, why it hurts the facility (in operational or
financial terms a non-lawyer can repeat in a meeting), and a concrete ask.
- Silent PPO / rental network language — clauses letting the payer lease
its rates to affiliates, rental networks, or "other payers." The facility
ends up giving its discount to payers it never negotiated with. Ask: strike
it, or limit rate access to named entities.
- Lesser-of billed charges — payment at the lesser of the contract rate
or billed charges. A chargemaster set low (or not updated) silently caps
revenue below the negotiated rate. Ask: strike, or at minimum audit the
chargemaster before signing.
- No escalator — flat rates with evergreen auto-renewal means a real-rate
cut every year of the contract's life. Ask: annual CPI-or-fixed-% increase,
or a rate reopener on each renewal.
- Short timely filing — a short window (measured against the facility's
actual billing cycle) plus SNF realities (payer of last resort
determinations, Medicare exhaust, retro-eligibility) produces write-offs of
clean, payable claims. Ask: a longer window, and an exception for
retro-eligibility and coordination-of-benefits situations running from the
date eligibility became known.
- Unilateral amendment — the payer may amend by notice, with silence as
acceptance ("material change" clauses). The contract you signed is not the
contract you'll have. Ask: mutual written consent for amendments, or at
minimum the right to terminate without cause within the notice window.
- Missing high-cost carve-outs — no drug/dialysis/vent/bariatric
pass-throughs means one admission with a high-cost specialty drug can wipe
out the margin on a month of census. Ask: cost-based or threshold-triggered
carve-outs for the categories in Workflow A.
- Level criteria vagueness — judgment terms in the level grid give the
payer's reviewer, not the contract, control of the effective rate. Ask:
objective criteria (named services, measurable thresholds) and a stated
combination rule.
Also screen beyond the checklist — anything from the Workflow A "Gaps &
ambiguities" section that shifts risk to the facility belongs in the memo
(one-sided termination, weak prompt-pay terms, appeal deadlines shorter than
the payer's own decision timelines, offset/recoupment without notice).
Steps
- Start from a Workflow A summary (produce the needed parts if absent).
- Run the checklist; collect quotes.
- Prioritize: rank findings by financial exposure and operational pain, not
by checklist order. Three well-argued asks beat twelve.
- Draft the memo. For each point, write the "ask" as specific contract
language direction, not a vibe ("add a mutual-amendment clause requiring
signed consent" — not "make amendments fairer").
Output format — Workflow C
ALWAYS use this exact template:
# Negotiation Points Memo
**Contract:** [payer] | **Renewal/negotiation date:** [date] | **Prepared:** [date]
## Executive summary
[3-5 sentences: overall posture of this contract, the two or three points
that matter most, and the single most important ask.]
## Priority negotiation points
### 1. [Issue name] — [High/Medium/Low priority]
- **Current language:** "[verbatim quote]" (§/p.)
- **Why it hurts:** [operational/financial impact, plain language]
- **The ask:** [specific change]
- **Fallback position:** [acceptable compromise, if any]
[Repeat, in priority order]
## Checklist results
| Unfavorable term | Present? | Location |
|---|---|---|
| Silent PPO / rental network | Yes / No / Unclear | |
| Lesser-of billed charges | | |
| No escalator | | |
| Short timely filing | | |
| Unilateral amendment | | |
| Missing high-cost carve-outs | | |
| Vague level criteria | | |
## Points in the facility's favor
[Terms worth protecting in the negotiation — don't trade these away blind.]
## Before the meeting
[Data to pull: utilization by level, carve-out-eligible admissions history,
denial/appeal outcomes under this payer, chargemaster review if lesser-of
language exists. Compare the proposed per-diem levels against the facility's
own cost per patient day and its Medicare FFS PDPM yield — this skill carries
no benchmarks, so run that comparison from the facility's numbers; do not
skip it. Facility's own data only — no external benchmarks needed.]
Reference
Read references/contract-terms-glossary.md when the user asks what a term
means, when writing for an audience new to managed care, or when unsure of
the SNF-specific significance of a term you've encountered in a contract.
Definitions there include why the term matters to an SNF, which is the part
worth echoing into your outputs.
Worked micro-example (leveling)
Input: "Sample Health Plan contract, Level 3 requires: IV medication
administration, OR complex respiratory care, OR wound vac. Patient is
post-op, on oral antibiotics, has a wound vac in place per the treatment
sheet."
Output core: Level 3 — criterion "wound vac" Met (evidence: active wound
vac order + treatment sheet entries). IV meds Not met (orals only).
Combination rule is ANY (contract uses "OR"). Documentation checklist:
current physician order for NPWT, treatment/flow sheet entries each shift,
weekly wound measurements. Confidence: High — objective criterion, directly
documented.
Disclaimer
This skill is educational. Managed-care contracts are legal documents; have
counsel review any contract, amendment, or negotiation position before
signing or relying on it. Level determinations and claims decisions must be
made by qualified facility staff based on the actual contract and the actual
medical record. Nothing produced by this skill is legal, billing, coding, or
reimbursement advice.
1---2name: contract-analysis3description: Analyze skilled nursing facility (SNF) managed-care contracts: extract terms into a structured contract summary sheet, level patients against a contract's level grid with evidence per criterion, and prepare negotiation-points memos that flag SNF-unfavorable terms. Use whenever the user mentions a payer contract, managed care agreement, rate sheet, per-diem levels, carve-outs, exclusions, leveling a patient, authorization or concurrent review terms, timely filing, lesser-of language, a single case agreement, or contract negotiation or renewal — even if they only paste contract text or ask "what level is this patient?" without naming the contract. Also use when reviewing a proposed amendment or comparing a draft contract against current terms.4license: MIT5---67# SNF Managed-Care Contract Analysis89Help SNF administrators, regional directors of managed care, and billers10understand what a managed-care contract actually says, place patients at the11correct level under it, and prepare for negotiations. Many users are12non-technical and non-legal: write plainly, define jargon on first use, and13point them to `references/contract-terms-glossary.md` when a term needs more14depth than the output allows.1516Three workflows live in this skill. Pick the one that matches the request:1718| User asks... | Workflow |19|---|---|20| "Summarize this contract" / "What are the terms?" / pastes a contract | **A — Term extraction** |21| "What level does this patient qualify for?" / "Level this admission" | **B — Patient leveling** |22| "What should we push back on?" / "Prep me for the renewal meeting" | **C — Negotiation prep** |2324Workflows B and C both depend on the terms extracted in Workflow A. If the25user jumps straight to B or C without a contract summary, run the relevant26parts of Workflow A first (quietly — don't produce the full summary sheet27unless asked, but do show the level grid or the terms you relied on, so the28user can verify you read the contract correctly).2930## Ground rules (apply to every workflow)3132- **Quote, don't paraphrase, for anything load-bearing.** Rate methodology,33 level criteria, deadlines, and termination language should be quoted verbatim34 with a section/page reference. Paraphrase drifts; a biller acting on a35 paraphrase can miss a filing deadline or bill the wrong level. When a page or36 section number is available, cite it.37- **Flag silence explicitly.** What a contract *doesn't* say is often the most38 important finding (no escalator, no high-cost drug carve-out, no retro-auth39 provision). Every output template below has a place for "not addressed in40 contract" — use it. Never fill a gap with an industry-typical assumption41 presented as if it were in the contract.42- **Never invent numbers.** Rates, thresholds, and deadlines come only from43 the document in front of you. If asked what a "typical" or "market" rate is,44 explain that rates vary widely by market, payer, and acuity mix and that45 benchmark figures should come from the facility's own comparable contracts46 or market data — do not supply a figure.47- **No PHI in outputs beyond what the task needs.** For leveling, work from48 the clinical facts given; don't ask for or restate identifiers (name, DOB,49 SSN, member ID) — refer to "the patient."50- **Ambiguity is a finding, not an obstacle.** Vague contract language51 ("skilled nursing services as appropriate") is exactly what causes level52 disputes and denials. Call it out, show both plausible readings, and say53 which party the ambiguity favors.5455---5657## Workflow A — Contract term extraction5859**Goal:** turn a contract PDF or pasted text into a summary sheet a busy60administrator can act on, and a biller can pin above their desk.6162### Steps63641. **Read the whole document before extracting anything.** Contracts scatter65 related terms: the rate exhibit may be Amendment 3, the level definitions66 in Attachment B, and the lesser-of clause buried in the payment section.67 Amendments and exhibits override the body — note the controlling version68 of any term that appears more than once, and flag conflicts between body69 and exhibit.702. **Extract into the categories below.** For each: the substance, a verbatim71 quote of the operative language, and the location. Mark anything absent as72 "Not addressed in contract."73 - **Parties & dates** — legal entities, effective date, initial term,74 renewal mechanics (evergreen/auto-renew? notice window to non-renew?),75 termination (with cause / without cause, notice periods, and whether76 termination rights are mutual or one-sided).77 - **Rate methodology** — identify which model applies: per-diem level grid,78 RUG-based, PDPM-based, percent-of-Medicare (state the percentage and79 which Medicare fee schedule year it references — a fixed year silently80 erodes value), case rates, or a hybrid. Reproduce the full rate grid.81 - **Level definitions & qualifying criteria** — for each level, the exact82 qualifying criteria as written. This is the raw material for Workflow B,83 so completeness matters more here than anywhere else. Note whether84 criteria are objective (e.g., "receiving IV antibiotics") or judgment85 terms (e.g., "complex wound care"), and who decides when they're met.86 - **Carve-outs & pass-throughs** — high-cost drugs (threshold amount, per87 dose or per day, what documentation triggers it), dialysis, ventilator,88 bariatric, behavioral, transportation, DME. For each: paid in addition to89 the per diem, or in lieu of it? At cost, cost-plus, or a stated rate?90 - **Exclusions** — services the SNF must not bill the payer for, and91 whether the contract says who *is* responsible (patient? unaddressed?).92 - **Authorization & concurrent review** — initial auth requirement and93 turnaround, recertification/concurrent review cadence, how continued-stay94 denials are communicated, retro-auth rules (allowed at all? window?),95 and what happens to days between auth expiry and re-auth.96 - **Claims & timely filing** — filing deadline (from date of service or97 discharge?), clean-claim definition, required claim format/codes,98 prompt-pay commitment, and the resubmission/corrected-claim window.99 - **Denials & appeals** — levels of appeal, deadline for each, where100 appeals go, whether the contract allows external review or arbitration,101 and any "failure to appeal within X days waives" language.102 - **Rate escalators** — annual increase (fixed %, CPI-linked, or103 renegotiation-only), and what happens on auto-renewal (rates frozen?).104 - **Lesser-of language** — any clause paying the lesser of contract rate105 vs. billed charges (see glossary: this makes the chargemaster a rate106 ceiling), and any most-favored-nation or rental-network/silent-PPO107 language letting other entities access these rates.108 - **Patient responsibility** — copay/coinsurance/patient-days handling,109 who collects, and whether the payer's payment is net or gross of it.1103. **Produce the summary sheet** using the Output format template. Lead with111 the three to five terms most likely to cost the facility money if missed.112113### Output format — Workflow A114115ALWAYS use this exact template:116117```markdown118# Contract Summary Sheet119**Payer:** [name] | **Facility:** [name] | **Effective:** [date] | **Prepared:** [date]120**Documents reviewed:** [base contract + amendments/exhibits, with dates]121122## Top findings (read these first)1231. [Highest-impact term or gap, one sentence + why it matters]1242. ...125126## Term & termination127| Item | Provision | Source |128|---|---|---|129| Effective date / initial term | ... | §/p. |130| Renewal | ... | §/p. |131| Termination without cause | ... | §/p. |132| Termination with cause | ... | §/p. |133134## Rates135**Methodology:** [per-diem levels / RUG / PDPM / % of Medicare / case rate / hybrid]136[Rate grid reproduced verbatim]137**Escalator:** [provision or "Not addressed in contract"]138**Lesser-of / rate-access language:** [quote or "None found"]139140## Level definitions141| Level | Qualifying criteria (verbatim) | Objective or judgment-based? | Source |142|---|---|---|---|143144## Carve-outs & pass-throughs145| Item | Trigger/threshold | Payment basis | In addition to per diem? | Source |146|---|---|---|---|---|147[Include rows marked "Not addressed" for: high-cost drugs, dialysis,148ventilator, bariatric, transportation]149150## Exclusions151[List, with who bears the cost if stated]152153## Authorization & review154| Item | Provision | Source |155|---|---|---|156| Initial authorization | | |157| Concurrent review cadence | | |158| Retro authorization | | |159160## Claims, denials & appeals161| Item | Deadline/Provision | Source |162|---|---|---|163| Timely filing | | |164| Clean claim definition | | |165| Appeal level 1 / 2 | | |166167## Patient responsibility168[Provision]169170## Gaps & ambiguities171[Everything marked "Not addressed" or vague, one line each on the risk]172```173174---175176## Workflow B — Patient leveling177178**Goal:** given the contract's level grid and a patient's clinical picture,179determine the level the patient qualifies for — with evidence the facility180could hand to the payer's reviewer.181182The integrity constraint comes first: **never inflate.** The job is to make183sure the facility is paid for the acuity it is actually delivering — patients184are frequently *under*-leveled because staff default to the safe low level —185but a level must be earned by documented clinical fact. If the evidence186supports Level 2, say Level 2, even if the user hoped for Level 3. An187unsupported higher level is a takeback and a payer-relations problem waiting188for the next audit.189190### Steps1911921. **Get the level grid.** From a prior Workflow A summary, or extract it now193 from the contract. If the user provides neither, stop and ask — leveling194 against a generic notion of "levels" is meaningless because criteria are195 contract-specific.1962. **Map every criterion of every plausible level against the clinical197 picture.** Work top-down from the highest plausible level. For each198 criterion record: met / not met / unknown, and the specific clinical199 evidence (order, medication, treatment, therapy minutes, nursing task).200 "Unknown" is common and important — it usually means the chart supports201 the level but nobody wrote it down.2023. **Handle judgment-based criteria explicitly.** Where the contract says203 something vague ("complex care," "extensive services"), state the204 reasonable interpretation you applied and note that the payer may read it205 differently. This is where concurrent-review disputes are born.2064. **Determine the qualifying level** per the contract's own combination rule207 (some grids require ALL criteria at a level; others ANY one; others a208 count — quote the rule). If the contract is silent on the combination209 rule, flag that as an ambiguity and show the result under both readings.2105. **Build the documentation checklist for the defensible level.** For each211 supporting criterion, name the exact chart element that proves it212 (physician order dated..., MAR entry showing..., wound-care flow sheet,213 therapy minutes log). For each "unknown," name what would need to be214 documented — *if clinically true* — to support it. Frame these as215 documentation of existing care, never as care to add for billing's sake.216217### Output format — Workflow B218219ALWAYS use this exact template:220221```markdown222# Level Determination223**Contract:** [payer/contract id] | **Determination:** **Level [X]** | **Confidence:** [High/Medium/Low + one-line reason]224225## Criteria analysis226### Level [highest plausible] — [qualifies / does not qualify / cannot determine]227| Criterion (verbatim from contract) | Met? | Evidence |228|---|---|---|229| ... | Met / Not met / Unknown | ... |230[Repeat per level evaluated, highest first]231232**Combination rule applied:** [quote, or "Contract silent — see ambiguities"]233234## Ambiguities affecting this determination235[Each vague criterion: your reading, the payer's likely reading, which level236each reading yields]237238## Documentation checklist to support Level [X]239- [ ] [Chart element] — supports "[criterion]"240- [ ] ...241242## If clinically justified, to support Level [X+1] the chart would need243[Only include this section when "unknown" criteria plausibly reflect care244actually being delivered. Each item: what to document, which criterion it245satisfies. Note: document care that is happening — never add services or246wording solely to reach a level.]247```248249---250251## Workflow C — Negotiation prep252253**Goal:** compare extracted terms against the checklist of SNF-unfavorable254provisions and produce a memo the administrator can take into the meeting.255256### The unfavorable-terms checklist257258Screen the contract for each of these. For every hit, the memo needs three259things: the quoted language, *why it hurts the facility* (in operational or260financial terms a non-lawyer can repeat in a meeting), and a concrete ask.2612621. **Silent PPO / rental network language** — clauses letting the payer lease263 its rates to affiliates, rental networks, or "other payers." The facility264 ends up giving its discount to payers it never negotiated with. Ask: strike265 it, or limit rate access to named entities.2662. **Lesser-of billed charges** — payment at the lesser of the contract rate267 or billed charges. A chargemaster set low (or not updated) silently caps268 revenue below the negotiated rate. Ask: strike, or at minimum audit the269 chargemaster before signing.2703. **No escalator** — flat rates with evergreen auto-renewal means a real-rate271 cut every year of the contract's life. Ask: annual CPI-or-fixed-% increase,272 or a rate reopener on each renewal.2734. **Short timely filing** — a short window (measured against the facility's274 actual billing cycle) plus SNF realities (payer of last resort275 determinations, Medicare exhaust, retro-eligibility) produces write-offs of276 clean, payable claims. Ask: a longer window, and an exception for277 retro-eligibility and coordination-of-benefits situations running from the278 date eligibility became known.2795. **Unilateral amendment** — the payer may amend by notice, with silence as280 acceptance ("material change" clauses). The contract you signed is not the281 contract you'll have. Ask: mutual written consent for amendments, or at282 minimum the right to terminate without cause within the notice window.2836. **Missing high-cost carve-outs** — no drug/dialysis/vent/bariatric284 pass-throughs means one admission with a high-cost specialty drug can wipe285 out the margin on a month of census. Ask: cost-based or threshold-triggered286 carve-outs for the categories in Workflow A.2877. **Level criteria vagueness** — judgment terms in the level grid give the288 payer's reviewer, not the contract, control of the effective rate. Ask:289 objective criteria (named services, measurable thresholds) and a stated290 combination rule.291292Also screen beyond the checklist — anything from the Workflow A "Gaps &293ambiguities" section that shifts risk to the facility belongs in the memo294(one-sided termination, weak prompt-pay terms, appeal deadlines shorter than295the payer's own decision timelines, offset/recoupment without notice).296297### Steps2982991. Start from a Workflow A summary (produce the needed parts if absent).3002. Run the checklist; collect quotes.3013. Prioritize: rank findings by financial exposure and operational pain, not302 by checklist order. Three well-argued asks beat twelve.3034. Draft the memo. For each point, write the "ask" as specific contract304 language direction, not a vibe ("add a mutual-amendment clause requiring305 signed consent" — not "make amendments fairer").306307### Output format — Workflow C308309ALWAYS use this exact template:310311```markdown312# Negotiation Points Memo313**Contract:** [payer] | **Renewal/negotiation date:** [date] | **Prepared:** [date]314315## Executive summary316[3-5 sentences: overall posture of this contract, the two or three points317that matter most, and the single most important ask.]318319## Priority negotiation points320### 1. [Issue name] — [High/Medium/Low priority]321- **Current language:** "[verbatim quote]" (§/p.)322- **Why it hurts:** [operational/financial impact, plain language]323- **The ask:** [specific change]324- **Fallback position:** [acceptable compromise, if any]325[Repeat, in priority order]326327## Checklist results328| Unfavorable term | Present? | Location |329|---|---|---|330| Silent PPO / rental network | Yes / No / Unclear | |331| Lesser-of billed charges | | |332| No escalator | | |333| Short timely filing | | |334| Unilateral amendment | | |335| Missing high-cost carve-outs | | |336| Vague level criteria | | |337338## Points in the facility's favor339[Terms worth protecting in the negotiation — don't trade these away blind.]340341## Before the meeting342[Data to pull: utilization by level, carve-out-eligible admissions history,343denial/appeal outcomes under this payer, chargemaster review if lesser-of344language exists. Compare the proposed per-diem levels against the facility's345own cost per patient day and its Medicare FFS PDPM yield — this skill carries346no benchmarks, so run that comparison from the facility's numbers; do not347skip it. Facility's own data only — no external benchmarks needed.]348```349350---351352## Reference353354Read `references/contract-terms-glossary.md` when the user asks what a term355means, when writing for an audience new to managed care, or when unsure of356the SNF-specific significance of a term you've encountered in a contract.357Definitions there include *why the term matters to an SNF*, which is the part358worth echoing into your outputs.359360## Worked micro-example (leveling)361362Input: "Sample Health Plan contract, Level 3 requires: IV medication363administration, OR complex respiratory care, OR wound vac. Patient is364post-op, on oral antibiotics, has a wound vac in place per the treatment365sheet."366367Output core: Level 3 — criterion "wound vac" **Met** (evidence: active wound368vac order + treatment sheet entries). IV meds Not met (orals only).369Combination rule is ANY (contract uses "OR"). Documentation checklist:370current physician order for NPWT, treatment/flow sheet entries each shift,371weekly wound measurements. Confidence: High — objective criterion, directly372documented.373374## Disclaimer375376This skill is educational. Managed-care contracts are legal documents; have377counsel review any contract, amendment, or negotiation position before378signing or relying on it. Level determinations and claims decisions must be379made by qualified facility staff based on the actual contract and the actual380medical record. Nothing produced by this skill is legal, billing, coding, or381reimbursement advice.