agentleFS
AWSKnown publisherawslabs/hcls-agent-skills/skills/risk-stratification-indices/SKILL.md

risk-stratification-indices

Skill62 starsChanged 5 months agoMIT-0View on GitHub

Reasoning skill for clinical risk stratification index selection and interpretation. Use when the user asks about LACE scores, Charlson Comorbidity Index, Elixhauser Index, readmission risk scoring, comorbidity weighting, SDOH Z-codes, Area Deprivation Index, or population health stratification methods.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No PCP visit in 12 months (care disengagement)

    line 113
  2. Distinctive:

    When risk scores drive reimbursement or payment decisions (requires validated, audited implementation)

    line 126
  3. Distinctive:

    When stratification results will determine resource allocation across populations

    line 127
  4. Distinctive:

    When combining indices in novel ways not validated in literature

    line 128

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Risk Stratification Indices Reasoning

Overview

Guide selection and interpretation of clinical risk stratification indices (LACE, Charlson, Elixhauser) and SDOH factors (Z-codes, ADI) for population health management. Based on validated scoring systems from peer-reviewed literature.

Usage

  • Activate when selecting a risk stratification index for a specific use case (readmission, mortality, utilization)
  • Activate when interpreting LACE, Charlson, or Elixhauser scores
  • Activate when incorporating SDOH factors (Z-codes, ADI) into population health stratification

Core Concepts

Response Format

Apply scoring logic internally. Present the recommended index with justification, scoring interpretation, and risk tier. Do not narrate the full scoring calculation unless asked.

1. Choosing a Risk Stratification Method

What is the use case?
├── 30-day readmission prediction
│   └── Use LACE index (designed for readmission)
├── Long-term mortality risk adjustment
│   └── Use Charlson Comorbidity Index
├── Hospital resource utilization / cost prediction
│   └── Use Elixhauser Comorbidity Index
├── Medicare risk adjustment (payment)
│   └── Use CMS-HCC (Hierarchical Condition Categories)
└── Population health stratification
    └── Combine clinical risk (Charlson/Elixhauser) + SDOH factors

2. LACE Index (Readmission Risk)

ComponentScoringRange
L — Length of stay1d=1, 2d=2, 3d=3, 4–6d=4, 7–13d=5, ≥14d=70–7
A — Acuity of admissionEmergent=3, Urgent=2, Elective=00–3
C — Comorbidity (Charlson)0=0, 1=1, 2=2, 3=3, ≥4=50–5
E — ED visits (prior 6 months)0=0, 1=1, 2=2, 3=3, ≥4=40–4
TotalSum of L+A+C+E0–19

Risk tiers: Low (0–4), Moderate (5–9), High (10+)

3. Charlson Comorbidity Index

17 conditions with integer weights:

  • Weight 1: MI, CHF, PVD, CVD, dementia, COPD, connective tissue disease, peptic ulcer, mild liver disease, uncomplicated diabetes
  • Weight 2: complicated diabetes, hemiplegia, renal disease, non-metastatic cancer
  • Weight 3: moderate/severe liver disease
  • Weight 6: metastatic tumor, AIDS/HIV

Total score = sum of all applicable weights.

4. Elixhauser Comorbidity Index

AttributeCharlsonElixhauser
Conditions1731
WeightingFixed integerVaries by model (van Walraven common)
ScopeMortality predictionMortality + resource use
Mental healthLimited (dementia only)Depression, psychoses, substance use
Best forLong-term mortalityHospital utilization, readmission

5. SDOH Risk Factors

ICD-10 Z-Codes for SDOH

Key ranges: Z55 (education/literacy), Z56 (employment), Z57 (occupational exposure), Z59 (housing/economic — Z59.0 homelessness, Z59.41 food insecurity), Z60 (social environment), Z62 (upbringing/abuse), Z63 (family circumstances), Z65 (psychosocial/legal).

Area Deprivation Index (ADI)

ADI PercentileRisk LevelImplication
1–25Low deprivationStandard outreach sufficient
26–50ModerateEnhanced reminder systems
51–75HighCare coordination, transportation assistance
76–100Very highIntensive outreach, community health workers

Incorporating SDOH into Stratification

Weight members higher when:

  1. Any SDOH Z-code documented in claims
  2. High ADI score (≥51st percentile)
  3. Dual-eligible status (Medicare + Medicaid)
  4. Language barrier (non-English preferred)
  5. No PCP visit in 12 months (care disengagement)

Common Mistakes

  • Wrong: Using Charlson for readmission prediction → Right: Use LACE (purpose-built for 30-day readmission)
  • Wrong: Using Elixhauser for long-term mortality → Right: Use Charlson (validated for mortality prediction)
  • Wrong: Ignoring SDOH factors in population stratification → Right: Combine clinical index + SDOH for actionable tiers
  • Wrong: Applying same outreach to all risk tiers → Right: Tailor interventions by barrier type (transportation, literacy, engagement)
  • Wrong: Using ADI alone without clinical risk → Right: ADI indicates access barriers; combine with clinical severity for full picture
  • Wrong: Treating all Z-codes as equivalent risk signals → Right: Weight by relevance to the specific outcome (e.g., Z59.0 homelessness is higher barrier than Z56 employment)

When to Escalate

  • When risk scores drive reimbursement or payment decisions (requires validated, audited implementation)
  • When stratification results will determine resource allocation across populations
  • When combining indices in novel ways not validated in literature

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.