Back to Skills

dicom-metadata-extract

Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use.

2,741stars319forksUpdated 7/31/2026

Security Assessment

Safe(93/100)
Security Score93/100

About dicom-metadata-extract

DICOM Metadata Extract is a small, self-contained NVIDIA MedTech skill that extracts selected metadata from a single DICOM medical-imaging file and flags the presence of standard-tag PHI (protected health information). It is deliberately narrow: it reads one file with pydicom and emits JSON to stdout containing fields like transfer syntax, modality, grouped study/series/image metadata, a phi_present flag, and the list of PHI tags found. It is explicitly not for anonymization, de-identification, or clinical use, and serves as the reference "smallest end-to-end" example skill for the Medical AI Skills layout.

The workflow is a documented wrapper: the agent reads skill_manifest.yaml before changing arguments, runs scripts/extract_metadata.py (either directly via Bash/Python or through a host `run_script` interface), keeps outputs under a caller-provided run directory, and can validate results against an output schema and an optional quality verifier for evidence review. It extracts only literal DICOM header values and does not infer modality, body part, diagnosis, or clinical meaning. Documented limitations are clear: it covers only a small PS3.15-inspired standard-tag subset, does not check private tags, does not detect burnt-in pixel PHI, has minimal multi-frame handling, and is not for clinical deployment, regulatory de-identification, autonomous diagnosis, or patient-facing use.

Target users are developers and engineers doing development-time review of DICOM files — inspecting header metadata and getting a coarse PHI-presence signal. It is research-and-development only, requires the pydicom dependency, and is designed to be run from the repository root.

FAQ

What does this skill extract?

It reads one DICOM file with pydicom and emits JSON including transfer_syntax, modality, grouped study/series/image metadata, a phi_present flag, and phi_tags_found (the standard PHI tags detected).

Can I use it to anonymize or de-identify DICOM files?

No. It only flags standard-tag PHI presence and is explicitly not for anonymization, regulatory de-identification, or clinical use.

What are its known limitations?

It covers only a small PS3.15-inspired standard-tag subset, does not check private tags, does not detect burnt-in pixel PHI, has minimal multi-frame handling, and is not for clinical deployment or diagnosis.

How is it run?

Run scripts/extract_metadata.py with a DICOM path (optionally --output result.json) from the repository root, or via a host run_script interface if available. It requires pydicom and the packages declared in skill_manifest.yaml.

Is it safe to use on real patient data?

It is intended for research and development only, at development time. It reads literal header values and does not transmit data externally, but it is not validated for clinical or patient-facing use.

All Files

12 files
evals/baseline.yaml2.2 KB
View
skill-card.md3.5 KB
View
AGENTS.md0.5 KB
View
scripts/extract_metadata.py5.3 KB
View
tests/test_basic.py2.5 KB
View
evals/evals.json1.8 KB
View
SKILL.md3.2 KB
View
BENCHMARK.md4.1 KB
View
skill_manifest.yaml4.9 KB
View
validators/output_schema.json2.3 KB
View
fixtures/generate_sample.py2.9 KB
View
skill.oms.sig6.1 KB
View

Install dicom-metadata-extract

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills