rwe-analyze
# RWE Cohort Analysis Skill
What this skill does
# RWE Cohort Analysis Skill This skill provides real-world evidence (RWE) analysis using PhenoML APIs. It enables biopharma analysts to define patient cohorts, generate population statistics, compare cohorts, and assess study feasibility. ## How It Works A single script (`fetch_cohort.py`) fetches patient data and generates IPS (International Patient Summary) natural language summaries. YOU (Claude) then interpret these summaries to provide whatever analysis the user needs. ## When to Use This Skill Use this skill when users need to: - Define and analyze a patient cohort from natural language criteria - Generate population-level statistics (demographics, conditions, medications) - Compare two patient cohorts (e.g., treatment vs control groups) - Assess feasibility of a clinical study against a patient population ## Prerequisites Before using this skill, ensure: 1. Python 3.10+ is installed 2. Required packages are available: `python-dotenv`, `phenoml` 3. PhenoML credentials are configured (PHENOML_USERNAME, PHENOML_PASSWORD) ## Workflow ### Step 0: Verify Environment Always start by checking the environment configuration: ```bash python skills/rwe-analyze/scripts/check_env.py --env-file .env ``` If credentials are missing, guide the user to set up their `.env` file with: - PHENOML_USERNAME - PHENOML_PASSWORD - PHENOML_BASE_URL (defaults to https://experiment.app.pheno.ml) ### Step 1: Fetch Patient Data Use the single fetch script for all use cases: **Single cohort:** ```bash python skills/rwe-analyze/scripts/fetch_cohort.py \ --cohort "<natural language criteria>" \ --env-file .env ``` **Two cohorts for comparison:** ```bash python skills/rwe-analyze/scripts/fetch_cohort.py \ --cohort "<first cohort>" \ --cohort-2 "<second cohort>" \ --env-file .env ``` ### Step 2: Analyze the IPS Summaries The script outputs IPS natural language summaries. YOU (Claude) then analyze them based on what the user asked for: **Population Analysis:** - Total patient count - Age distribution (mean, range, brackets) - Gender breakdown - Most common conditions with prevalence - Most common medications with prevalence **Cohort Comparison:** - Patient counts for each cohort - Demographics differences - Condition prevalence differences - Medication differences **Study Feasibility:** 1. Parse the user's study criteria (age, required conditions, exclusions, medications) 2. Check each patient's IPS against criteria 3. Generate feasibility report: - Total patients in cohort - Number and percentage eligible - Breakdown by criterion - Overall assessment (High ≥70%, Moderate 40-69%, Low <40%) ## Important Guidelines 1. **Always use --env-file**: Pass the `.env` file path explicitly. 2. **Natural language cohort descriptions**: The PhenoML API accepts natural language: - "patients with type 2 diabetes" - "females over 65 with hypertension" - "patients diagnosed with breast cancer in the last 2 years" 3. **IPS format**: The IPS summaries include sections for: - Patient demographics (name, DOB, age, gender) - Allergies and Intolerances - Medication List - Problem List (conditions) ## Example Interactions ### Example 1: Basic Cohort Analysis **User**: "I need to understand our diabetic patient population" **Response**: Run fetch_cohort.py with `--cohort "patients with diabetes"`, then analyze the IPS summaries to report demographics, common comorbidities, and medication patterns. ### Example 2: Comparing Treatment Groups **User**: "Compare patients on metformin versus those on insulin" **Response**: Run fetch_cohort.py with `--cohort "diabetic patients on metformin" --cohort-2 "diabetic patients on insulin"`, then compare the IPS summaries. ### Example 3: Study Feasibility **User**: "How many diabetics aged 40-70 without kidney problems would qualify for our trial?" **Response**: Run fetch_cohort.py with `--cohort "patients with diabetes"`, then evaluate each patient's IPS against the criteria (age 40-70, no kidney disease) and report eligibility. ## API Methods Used | Script | PhenoML APIs | |--------|--------------| | fetch_cohort.py | `tools.analyze_cohort()`, `fhir.search()`, `summary.create(mode="ips")` |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.