nvidia/clinical-delegation
How to delegate clinical tasks to specialist agents. Always use sub-agent runtime with explicit agentId — never ACP. Never call FHIR via web_fetch.
npx skills add https://github.com/NVIDIA/dgx-spark-playbooks --skill clinical-delegation
When you delegate work to specialist agents, you must use the sub-agent runtime, not ACP.
Do not use web_fetch or any HTTP tool to call FHIR APIs from the coordinator. The coordinator does not have the correct FHIR base URL in context when it invents URLs. Specialist agents (patient-data, labs-vitals, medications, analyst) have the configured FHIR endpoint and write Python that runs on the server.
The only FHIR server in use is https://r4.smarthealthit.org. Never use placeholder domains like fhir.example.com.
Use sessions_spawn with:
patient-data, labs-vitals, medications, analyst, or molecularruntime: "acp". Omit runtime or use runtime: "subagent" so the request goes to the correct clinical agent.{ "agentId": "patient-data", "task": "Find the first patient and return demographics and active conditions.", "mode": "run" }
{ "agentId": "labs-vitals", "task": "Get latest HbA1c and eGFR for patient abc123", "mode": "run" }
{ "agentId": "analyst", "task": "Run care gap analysis for diabetic patients with A1c > 9%", "mode": "run" }
"runtime": "acp" without agentId — causes "ACP target agent is not configured"| agentId | Use for |
|----------------|---------|
| patient-data | Find patients, get demographics, list conditions |
| labs-vitals | Labs, vitals, BP, observations |
| medications | Active medications, drug classes |
| analyst | Python analysis, care gaps, charts |
| molecular | Drug molecular structure, OpenFold3 NIM 3D visualization |
Take nvidia/clinical-delegation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.