Hedis Measure Specification logo

Hedis Measure Specification

Organization
awslabs
hedis-measure-specification

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.

Overview

Publisherawslabs
Repositoryhcls-agent-skills
Skill namehedis-measure-specification
Stars
71
Forks
14
Bundled files
Instructions only
LicenseMIT-0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by awslabs on GitHub. Read the source before you install it.

Installation

Install the Hedis Measure Specification AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/awslabs/hcls-agent-skills/tree/main/skills/hedis-measure-specification
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/awslabs/hcls-agent-skills.git /tmp/hcls-agent-skills
mkdir -p .claude/skills
cp -r /tmp/hcls-agent-skills/skills/hedis-measure-specification .claude/skills/hedis-measure-specification
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hedis Measure Specification in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hedis Measure Specification on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hedis Measure Specification is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Hedis Measure Specification AI skill do?

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.

Why use Hedis Measure Specification on TypingMind?

Because you install it once and use it with any model. Hedis Measure Specification is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hedis Measure Specification in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/awslabs/hcls-agent-skills/tree/main/skills/hedis-measure-specification. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Hedis Measure Specification?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hedis Measure Specification?

As many as you like. As long as a model supports skills, you can use Hedis Measure Specification with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hedis Measure Specification AI skill free?

Yes. It is published on GitHub by awslabs under the MIT-0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇