Individual skill
ehr-data-analysis
Electronic health record analysis — phenotyping, missingness, bias, and observational study design with EHR data.
skills/ehr-data-analysis/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 53
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- design Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,487 bytes
Read excerpt
## Overview
ehr-data-analysis covers secondary analysis of electronic health record data: defining computable
phenotypes, handling the systematic missingness and biases of clinical data, and designing
observational studies (cohort, case-control, target-trial emulation) that produce credible
evidence rather than artifacts of documentation practice.
EHR data was collected for billing and clinical care, not research. Every analysis must reckon
with that: who gets tested, who gets coded, and who shows up at all are all non-random.
## When to use
- Defining computable phenotypes from diagnoses, labs, medications, and notes.
- Assessing data quality: completeness, plausibility, temporal coverage.