phenotype-lab-spec

Generate YAML-ready phenotype and lab-usage definitions from EHR data.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/tito-gh/healthcare --skill phenotype-lab-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phenotype-lab-spec
Source: https://github.com/tito-gh/healthcare/tree/main/.claude/skills/phenotype-lab-spec
Command: npx skills add https://github.com/tito-gh/healthcare --skill phenotype-lab-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables researchers and clinicians to translate complex phenotype and laboratory value criteria into machine-executable definitions, ensuring reproducibility and scalable validation across large EHR datasets.

Core Features & Use Cases

  • Computer-executable phenotype definitions: Create structured, reusable definitions for Population, Exposure, Outcome, and Covariates that can be run against EHR data.
  • Lab value mapping and time-series handling: Define lab variable mappings, normal ranges, and longitudinal processing to support robust analyses.
  • Validation planning and templates: Provide built-in validation templates (PPV targets, sensitivity targets) and evaluation plans to ensure clinical relevance.

Quick Start

Create a phenotype definition for an NDMM exposure to daratumumab using IMWG criteria, and generate an accompanying validation plan.

Frequently Asked Questions about phenotype-lab-spec

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

FAQPage Schema
How do I create computer-executable phenotype definitions from EHR data for clinical research?

To create computer-executable phenotype definitions from EHR data, you input structured parameters like PHENOTYPE_NAME, DRUG, INDICATION, and REFERENCE_DEFINITION to generate YAML-ready, machine-executable outputs covering population, exposure, outcome, and covariate phenotypes.

What is the best way to map lab values and handle time-series data when defining EHR phenotypes?

Mapping lab values and handling time-series data for EHR phenotypes requires defining lab variable mappings, normal ranges, and longitudinal processing specifications, which are structured to support robust clinical research analyses and reproducible execution.

How do I generate a validation plan for exposure phenotypes using IMWG criteria?

Generating a validation plan for exposure phenotypes using IMWG criteria involves applying built-in validation templates that specify PPV targets, sensitivity targets, and evaluation plans to ensure clinical relevance across large EHR datasets.

Do I need structured inputs to build covariate and outcome phenotypes from EHR data?

Yes, building covariate and outcome phenotypes from EHR data requires structured inputs such as PHENOTYPE_NAME, DRUG, and INDICATION to automate the creation of reproducible, machine-executable definitions and lab-usage specifications.

What format are the automated phenotype definitions output in for EHR data processing?

Automated phenotype definitions for EHR data processing are output in a YAML-ready format, enabling researchers to directly execute structured population, exposure, outcome, and covariate definitions against large datasets.

Can I use this approach to define phenotypes for both drug exposure and disease indications?

Yes, you can define phenotypes for both drug exposure and disease indications by providing structured inputs like DRUG and INDICATION, translating complex clinical criteria into machine-executable definitions with scalable validation planning.