i4h-catheter-navigation

Orients users on the i4h catheter navigation workflow modes and routes to per-stage skills.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill i4h-catheter-navigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i4h-catheter-navigation
Source: https://github.com/NVIDIA/skills/tree/main/skills/i4h-catheter-navigation
Command: npx skills add https://github.com/NVIDIA/skills --skill i4h-catheter-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers approaching the Isaac for Healthcare endovascular catheter navigation workflow often do not know which pipeline stages exist, how fluorosim DRR rendering, XPBD catheter physics, and the vasculature digital twin fit together, or which stage-specific skill to invoke first. This Skill provides that orientation and routing without executing any pipeline stage itself.

Core Features & Use Cases

  • Workflow Orientation: Explains the catheter navigation architecture, including the fluorosim rendering stack, vasculature digital twin, and the ./i4h mode registry in metadata.json.
  • Mode Discovery: Lists supported modes (preprocess_ct, segment_vessels, render_drr, interactive_viewport) by running ./i4h modes catheter_navigation, with a documented fallback table when setup is incomplete.
  • Skill Routing: Directs users to the correct stage skill (setup, digital-twin, render-drr, viewport, smoke, e2e) based on their goal.
  • Use Case: A researcher with a contrast CT scan asks how to reach an interactive simulated fluoroscopy demo; the Skill explains the setup, digital-twin, and viewport sequence and names the exact skills to run next.

Quick Start

Ask your agent to explain what the i4h catheter navigation workflow includes, which modes it supports, and which skill to use next for your goal.

Frequently Asked Questions about i4h-catheter-navigation

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

FAQPage Schema
What is the i4h catheter navigation workflow and where do I start?

It is an Isaac for Healthcare workflow combining fluorosim DRR rendering, XPBD catheter physics, and a vasculature digital twin. Start by listing supported modes with ./i4h modes catheter_navigation, then run the setup skill before any hands-on stage.

How do I go from a patient CT scan to an interactive catheter simulation?

Run the setup skill first, then the digital-twin skill to preprocess the CT and segment vessels into a cache, and finally the viewport skill to launch the interactive fluoroscopy simulation. The viewport requires a GPU and display.

Which mode should I use for a quick render check without patient data?

Use render_drr in synthetic mode, which renders a single DRR frame from a synthetic phantom without any CT cache. Route this through the i4h-catheter-navigation-render-drr skill rather than the overview skill.

Does the catheter navigation workflow require a GPU?

GPU modes such as render_drr and interactive_viewport require an NVIDIA GPU with CUDA 12.8 or newer and a Vulkan-capable driver. CPU smoke tests in the workflow's tests directory run without a GPU.

Why does ./i4h modes catheter_navigation fail with mode not found?

This usually means the command was not run from the repository root or setup is incomplete. Change to the i4h-workflows root and retry, or consult the documented fallback table of supported modes.

Does this overview skill run the catheter simulation itself?

No. It is routing-only: it explains the architecture, lists modes, and points to stage skills such as setup, digital-twin, render-drr, and viewport. Each stage has its own dedicated skill that performs the actual work.