domain-healthcare

Codify encounter-based grain, clinical code hierarchies, and NULL semantics for healthcare analytics.

475|25|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill domain-healthcare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-healthcare
Source: https://github.com/SignalPilot-Labs/SignalPilot/tree/main/benchmark/signalpilot-plugin/skills/domain-healthcare
Command: npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill domain-healthcare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Healthcare data science rules: encounter-based grain, clinical coding hierarchies, cost allocation, NULL semantics in clinical data.

Core Features & Use Cases

  • Establish consistent grain at the EVENT level (diagnosis/procedure) to preserve encounter-level detail.
  • Support hierarchical coding systems (ICD, CPT, HCPCS, SNOMED, LOINC, DRG, NUCC, NDC, RxNorm, NPI) with proper rollups.
  • Provide NULL semantics guidance and crosswalk-aware mappings for complete taxonomy coverage.
  • Use Case: build utilization reports that accurately reflect encounters with data, avoiding patient-level aggregation when not requested.

Quick Start

Set the data grain to the EVENT level (diagnosis/procedure) and validate patient-level aggregations only when explicitly required.

Frequently Asked Questions about domain-healthcare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does patient-level aggregation break my healthcare utilization reports?

Patient-level aggregation breaks healthcare utilization reports when the data grain is not set at the encounter or event level. Establishing consistent grain at the diagnosis and procedure level preserves encounter detail and prevents inaccurate rollups.

How do I map ICD and CPT clinical codes across different healthcare coding hierarchies?

Mapping clinical codes across healthcare coding hierarchies requires crosswalk-aware mappings to ensure complete taxonomy coverage. Proper rollups support hierarchical coding systems including ICD, CPT, SNOMED, LOINC, DRG, NDC, RxNorm, and NPI for accurate analytics.

What are NULL semantics in clinical data modeling and when do they matter?

NULL semantics in clinical data modeling define how missing clinical values are handled during cost allocation and hierarchical rollups. Applying safe NULL handling guidance and domain validation rules ensures missing data does not corrupt healthcare analytics.

What is the best way to allocate costs across healthcare encounters and procedures?

Allocating costs across healthcare encounters and procedures requires codifying encounter-based grain and applying crosswalk-aware mappings. Setting the data grain to the event level ensures cost allocation reflects accurate clinical hierarchies and taxonomy coverage.

Do I need domain knowledge validation rules to model healthcare data accurately?

Domain knowledge validation rules are required to model healthcare data accurately because they enforce grain integrity, safe NULL handling, and crosswalk-aware mappings. Clear documentation of these rules ensures reliable clinical coding hierarchies and cost allocation.