agentleFS
AWSKnown publisherawslabs/hcls-agent-skills/skills/hedis-measure-specification/SKILL.md

hedis-measure-specification

Skill62 starsChanged 5 months agoMIT-0View on GitHub

Reasoning skill for HEDIS measure specification, enrollment logic, exclusion evaluation, NCQA audit requirements, and care gap prioritization. Use when the user asks about HEDIS measure definitions, denominator/numerator/exclusion logic, continuous enrollment rules, Star Rating impact, or care gap closure strategies.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    Every HEDIS measure follows:

    line 47
  2. Distinctive:

    Check the full measurement year for exclusion events

    line 103
  3. Distinctive:

    Document which optional exclusions are applied

    line 106
  4. Distinctive:

    Before submitting quality data affecting reimbursement or accreditation

    line 173

≈ “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

HEDIS Measure Specification Reasoning

Overview

Structured interpretation of HEDIS quality measures: denominator/numerator logic, continuous enrollment evaluation, exclusion application, NCQA audit readiness, and Star Rating-weighted care gap prioritization. Based on NCQA HEDIS Technical Specifications (MY 2024).

Usage

  • Activate when interpreting HEDIS measure denominator/numerator/exclusion logic
  • Activate when evaluating continuous enrollment rules or allowable gaps
  • Activate when prioritizing care gaps by Star Rating weight or SDOH barriers

Core Concepts

Response Format

Apply measure logic internally. Present the final specification, rate interpretation, or gap prioritization with justification. Do not narrate enrollment evaluation steps or exclusion logic walkthrough.

1. HEDIS Measure Structure

Every HEDIS measure follows:

Eligible Population (Denominator)
  → minus Exclusions
  → equals Eligible Denominator
  → Numerator (members who met the quality criteria)
  → Rate = Numerator / Eligible Denominator
ComponentDefinitionExample (CDC — Diabetes HbA1c)
DenominatorMembers eligible based on age, diagnosis, enrollmentAge 18–75, diabetes (E11.x), continuously enrolled
ExclusionsMembers removed due to clinical exceptionsHospice, ESRD, organ transplant
NumeratorMembers who met the quality criteriaHbA1c test performed during measurement year
RateNumerator ÷ (Denominator − Exclusions)Percentage with HbA1c testing

Five measure types: Process (service delivered), Outcome (clinical result), Structural (system capability), Patient experience (CAHPS), Utilization (resource consumption).

2. Continuous Enrollment Rules

RuleDefinition
Measurement yearJanuary 1 – December 31 of reporting year
Anchor dateDate member must be enrolled through (usually Dec 31)
Allowable gap≤45 days total gap permitted
Gap countingCalendar days without coverage; multiple gaps summed
Enrollment sourceMedical and/or pharmacy benefit, measure-dependent

Enrollment Evaluation Decision Tree

Is the member enrolled on the anchor date?
├── NO → Exclude from denominator
└── YES
    ├── Total gap days during measurement year?
    │   ├── ≤45 days → Continuously enrolled
    │   └── >45 days → Exclude from denominator
    └── Measure requires pharmacy benefit?
        ├── YES → Verify pharmacy enrollment separately
        └── NO → Medical enrollment sufficient

3. Exclusion Logic

CategoryApplies ToCondition
HospiceAll measuresHospice benefit or encounter
DeceasedAll measuresDeath during measurement year
ESRDDiabetes, kidneyN18.6, dialysis codes
Organ transplantDiabetes, kidneyZ94.x
PregnancyBP, diabetesO00-O9A
Frailty + advanced illnessAge 66+, multipleBOTH conditions required

Evaluation rules:

  1. Apply exclusions AFTER building the full denominator
  2. Check the full measurement year for exclusion events
  3. Frailty + advanced illness is compound — both must be present
  4. Hospice overrides all other logic
  5. Document which optional exclusions are applied

4. NCQA Audit Requirements

SourcePriorityUse For
Administrative claimsPrimaryDenominator, exclusions, process numerators
Electronic clinical data (ECDS)Primary (ECDS measures)Lab results, vitals
Supplemental dataSecondaryFills claims gaps (HIE lab results)
Medical record reviewTertiaryValidation, hybrid measures

Common Audit Findings

FindingSeverityRemediation
Supplemental data without source verificationHighImplement source validation
Enrollment gap calculation errorHighRevalidate against NCQA specs
Incorrect age calculationMediumUse age as of anchor date
Duplicate member countingHighDeduplicate on member ID
Stale value setsMediumUpdate code sets annually

5. Care Gap Prioritization

Prioritization Decision Tree

Is the measure triple-weighted for Star Ratings?
├── YES → High priority baseline
│   ├── Member high-risk (Charlson ≥3 or LACE ≥10)?
│   │   ├── YES → Critical priority — immediate outreach
│   │   └── NO → High priority — standard outreach
│   └── SDOH barriers (Z-codes, high ADI)?
│       ├── YES → Assign care coordinator
│       └── NO → Automated reminder sufficient
└── NO → Standard priority
    ├── >6 months remaining in measurement year?
    │   ├── YES → Schedule in next outreach batch
    │   └── NO → Escalate if feasible
    └── Process measure (screening/test)?
        ├── YES → High closure probability — include
        └── NO → Outcome measure — coordinate with PCP

Rate Interpretation

Rate RangeStar LevelAction
≥90th percentile5-starMaintain current programs
75th–89th4-starTargeted improvement
50th–74th3-starSystematic outreach needed
25th–49th2-starIntensive intervention, root cause analysis
<25th1-starUrgent remediation, leadership escalation

Common Mistakes

  • Wrong: Calculating age as of data extraction date → Right: Use measure-specific anchor date (typically Dec 31)
  • Wrong: Applying exclusions before building the full denominator → Right: Build complete eligible population first, then subtract
  • Wrong: Excluding members with ≤45-day enrollment gaps → Right: HEDIS permits ≤45-day allowable gap
  • Wrong: Mixing process and outcome sub-measures (e.g., HbA1c testing vs HbA1c <8%) → Right: Treat as separate rates
  • Wrong: Using prior-year value sets without updating → Right: Update ICD-10/CPT/HCPCS annually
  • Wrong: Counting members multiple times across enrollment segments → Right: Deduplicate on member ID
  • Wrong: Submitting supplemental data without source documentation → Right: Validate with date, value, provider before submission
  • Wrong: Treating all measures with equal priority → Right: Prioritize triple-weighted Star Rating measures (3× impact)

When to Escalate

  • Exclusion logic produces unexpected denominator drops (>10%)
  • Before submitting quality data affecting reimbursement or accreditation
  • Supplemental data sources change rates by >5 percentage points

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.