cohort-compare

par nvidia

Analyser une cohorte de patients à partir de points de terminaison FHIR pour identifier les lacunes de soins et les tendances. Utiliser lorsqu’on demande de comparer des patients, de trouver des lacunes de qualité ou d’analyser une population.

npx skills add https://github.com/nvidia/dgx-spark-playbooks --skill cohort-compare

Analyze a patient cohort: $ARGUMENTS

Use your fhir-basics skill to query FHIR endpoints. Use your clinical-knowledge skill to identify care gaps and apply correct thresholds. Use your analysis-methods skill to write correct Python analysis code.

Execution Rules

  • Do NOT explore the workspace or list files. Begin the analysis immediately.
  • Write ONE Python script that does everything: FHIR queries, analysis, chart, and summary.
  • Write the script correctly the first time. Do NOT write a draft and then edit it.
  • Run it with python (NOT python3).
  • All HTTP calls must use subprocess.run(["curl", "-sf", "--max-time", "30", url], capture_output=True, text=True) -- the requests library does NOT work through the sandbox proxy. See the fhir-basics skill for the fhir_get helper pattern.
  • Save the script to /tmp/<name>.py, run it once, interpret the output.

Steps

  1. Identify the cohort -- Query GET /Condition?code={snomed_code}&_count=200 and follow pagination links to get all matching Condition resources. Extract unique patient IDs from entry[].resource.subject.reference. Report the cohort size.

  2. Pull clinical data in BATCHED queries (do NOT loop per-patient):

    • Lab values: Use get_latest_labs_batch(loinc_code, patient_ids) to fetch ALL observations for the LOINC code in one call and filter client-side. This queries GET /Observation?code={loinc_code}&_count=500&_sort=-date without a patient filter, then builds a dict keyed by patient ID. Handle both valueQuantity (numeric) and valueString (text) formats. For blood pressure, query the BP panel code 85354-9 in batch and parse components.
    • Medications: Use get_all_medications_batch(patient_ids) to fetch GET /MedicationRequest?status=active&_count=500 in one call, then filter to cohort patients client-side.
    • NEVER write a for pid in patient_ids: loop that makes FHIR HTTP calls inside the loop. The sandbox proxy adds 1-3s latency per call. With 24 patients x 4 LOINC codes = 96 calls = 5+ minutes. Batching brings this to 4-6 total calls = 30 seconds.
  3. Build a pandas DataFrame with one row per patient:

    • patient_id (string)
    • {lab_name} (float or None)
    • lab_date (string)
    • on_target_med (boolean -- True if the patient is on the specified medication class)
    • medications (comma-separated string of all active med names)
    • med_count (int)
  4. Data quality check:

    • Report how many patients have the lab recorded vs. missing
    • If > 30% missing, flag as a data quality issue but continue analysis
    • If < 5 patients have data, warn that the sample is too small for meaningful statistics
  5. Identify care gap patients: Apply the threshold and medication check:

    • Gap = lab value exceeds threshold AND patient is NOT on the specified medication class
    • Report: total with condition, total with lab data, total above threshold, total in care gap
    • Compute gap rate as percentage of patients with lab data (not total cohort)
  6. Generate visualization:

    • Histogram of the lab value distribution with threshold line
    • Use NVIDIA dark theme: plt.style.use('dark_background'), primary color #76B900, background #1a1a1a
    • Annotate with sample size (N = ...) and gap count
    • Save as PNG with dpi=150
  7. Write a plain-English summary including:

    • Cohort size and data completeness
    • Distribution statistics (mean, median, range)
    • Gap patient count and percentage with absolute numbers
    • Comparison to relevant CMS quality measure if applicable
    • Any notable patterns (e.g., "All gap patients had no medications recorded at all")
  8. Disclaimer: "This analysis is for research and operational purposes. Clinical decisions should be made by qualified clinicians."

Example: Diabetes Gap Analysis (CMS122)

Condition: Type 2 Diabetes (SNOMED 44054006) Lab: HbA1c (LOINC 4548-4) Threshold: > 9.0% Gap medication: insulin or GLP-1 agonist Quality measure: CMS122v12 (poor glycemic control)

INSULIN_AND_GLP1 = ["insulin", "liraglutide", "semaglutide", "dulaglutide",
                     "exenatide", "tirzepatide", "victoza", "ozempic",
                     "trulicity", "byetta", "mounjaro", "rybelsus"]

def is_on_insulin_or_glp1(med_list):
    med_lower = [m.lower() for m in med_list]
    return any(drug in med_text for drug in INSULIN_AND_GLP1 for med_text in med_lower)

Example: Hypertension Gap Analysis (CMS165)

Condition: Essential Hypertension (SNOMED 38341003) Lab: Systolic BP (LOINC 8480-6) -- use component Observation pattern Threshold: >= 140 mmHg Gap medication: any antihypertensive Quality measure: CMS165v12 (controlling high blood pressure)

Note: Use get_latest_bp() from the analysis-methods skill to handle both BP panel (85354-9) and standalone systolic Observations.

ANTIHYPERTENSIVES = ["lisinopril", "enalapril", "ramipril", "benazepril",
    "losartan", "valsartan", "irbesartan", "olmesartan", "telmisartan",
    "amlodipine", "nifedipine", "diltiazem",
    "metoprolol", "atenolol", "carvedilol", "bisoprolol",
    "hydrochlorothiazide", "hctz", "chlorthalidone",
    "furosemide", "spironolactone"]

def is_on_antihypertensive(med_list):
    med_lower = [m.lower() for m in med_list]
    return any(drug in med_text for drug in ANTIHYPERTENSIVES for med_text in med_lower)

Plus de skills de nvidia

compileiq-debug
nvidia
Utilisez quand quelque chose ne va pas : Search() bloque, toutes les évaluations retournent INVALID_SCORE, les scores ne s'améliorent pas, chaque configuration retourne le même nombre, erreurs ptxas…
create-github-pr
nvidia
Créer des pull requests GitHub en utilisant l'interface en ligne de commande gh. Utiliser lorsque l'utilisateur souhaite créer une nouvelle PR, soumettre du code pour révision, ou ouvrir une pull request. Mots-clés de déclenchement -…
nemoclaw-maintainer-cross-issue-sweep
nvidia
Analyse les autres problèmes ouverts pour trouver ceux qu’une PR donnée pourrait également corriger ou casser accidentellement. Génère des opportunités de correctifs adjacents et des risques de contradiction avec fichier:ligne…
fhir-basics
nvidia
Apprend aux agents comment fonctionnent les API FHIR R4, quelles ressources sont disponibles, comment les interroger avec des paramètres de recherche, et comment analyser correctement tous les formats de réponse…
compileiq-validate-result
nvidia
Utiliser APRÈS qu'une recherche soit terminée et AVANT de réclamer un accélérateur ou d'expédier un ACF. Charge le CSV dump_results, extrait les K meilleurs candidats (mono-objectif)…
changelog-audit
nvidia
Auditer le CHANGELOG.md de Warp avant une publication : récupérer les entrées perdues, trier par impact utilisateur, affiner le langage des entrées, ajuster les retours à la ligne et (en mode branche de publication) mettre à jour la comparaison…
maintain-dynamic-plugins
nvidia
Maintenir les chargeurs de plugins dynamiques NeMo Relay, les manifestes, les SDK natifs Rust, le protocole worker gRPC, le SDK worker Python, la documentation, les tests et la couverture du workflow de publication
dgx-diagnose
nvidia
Diagnostiquer les problèmes courants du DGX Station GB300 — plantages CUDA, ciblage incorrect du GPU, bugs de conteneur vLLM/SGLang, problèmes d'état MIG, erreurs NVLink/Fabric Manager,…