Back to Skills

dicom-series-preflight

Used for header-only preflight of one DICOM series folder before conversion or inference. Not for de-identification or clinical clearance.

2,759stars321forksUpdated 8/1/2026

Security Assessment

Safe(93/100)
Security Score93/100

About dicom-series-preflight

This NVIDIA MedTech skill performs a header-only preflight check on a single DICOM series folder before that data is converted or fed to inference. It solves an early quality-gate problem in medical-imaging pipelines: catching malformed inventories, unexpected orientation, or potential PHI flags at the metadata level before spending time on pixel decoding or a full conversion. It deliberately does not decode pixel data, de-identify, or make any clinical determination.

The skill runs an upstream Python entrypoint, scripts/preflight_series.py, over a DICOM directory and emits JSON containing an inventory, orientation axcodes, PHI flags, findings, and an overall preflight verdict of pass, warn, or fail. It can be paired with a verifier and run through documented make workflows to produce a trusted preflight pack, and ships with fixtures, an output schema validator, tests, and a benchmark report. Users are instructed to read the skill_manifest.yaml before changing arguments and to use the wrapper exactly as documented rather than reimplementing it. Its published benchmark reports a passing NVSkills-Eval verdict with a 100% security dimension.

It targets medical-imaging and MLOps engineers building DICOM ingestion or model-inference pipelines who need a fast, read-only sanity gate. Stated limitations are important to the intended use: it is header-only and cannot detect burnt-in PHI, its canonical-orientation gate assumes LPS-derived CT axcodes, compressed and multi-frame instances are warned rather than decoded, and it scans a single directory. The documentation is explicit that it is not for clinical deployment, regulatory de-identification, autonomous diagnosis, or production ingestion without a vetted converter.

FAQ

What does the preflight check produce?

A JSON report with an inventory, orientation axcodes, PHI flags, findings, and a preflight verdict of pass, warn, or fail.

Does it read or decode image pixels?

No. It is header-only and does not decode pixel data. As a result it cannot detect burnt-in PHI, and compressed or multi-frame instances are warned rather than decoded.

How do I run it?

Run the documented entrypoint, python scripts/preflight_series.py PATH_TO_DICOM_DIR, keeping outputs under a caller-provided run directory. It can also be driven through the provided make run-trusted and make run-workflow gates.

Is this suitable for clinical use or de-identification?

No. The documentation states it is not for de-identification, clinical clearance, autonomous diagnosis, or production ingestion without a vetted converter.

What are the prerequisites?

Python and the packages declared in skill_manifest.yaml under runtime side effects; commands are run from the repository root unless noted otherwise.

All Files

10 files
scripts/preflight_series.py12.6 KB
View
skill.oms.sig5.7 KB
View
fixtures/generate_fixtures.py2.0 KB
View
SKILL.md3.3 KB
View
BENCHMARK.md4.2 KB
View
skill_manifest.yaml3.5 KB
View
tests/test_preflight_series.py2.0 KB
View
evals/evals.json2.5 KB
View
skill-card.md3.7 KB
View
validators/output_schema.json1.5 KB
View

Install dicom-series-preflight

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