skills.rest
mark64oswald
mark64oswaldCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

healthsim-duckdb

Store and query HealthSim canonical entities in a DuckDB warehouse with SQL.

9|2|Updated Dec 9, 2025
Search Tags:#analytics#database#sql#persistence#duckdb#cohort#cross-product
One-click install
npx skills add https://github.com/mark64oswald/healthsim-workspace --skill healthsim-duckdb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: healthsim-duckdb
Source: https://github.com/mark64oswald/healthsim-workspace/tree/main/skills/common
Command: npx skills add https://github.com/mark64oswald/healthsim-workspace --skill healthsim-duckdb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DuckDB provides a centralized, persistent datastore for canonical HealthSim entities, enabling cross-product analytics without data duplication.

Core Features & Use Cases

  • Persist cohorts and query across PatientSim, MemberSim, TrialSim data with SQL
  • Cross-product data exploration with provenance and cohort linkage
  • Schema exploration, reference data access, and token-efficient cohort operations
  • Safe, read-only queries against canonical tables for analytics

Quick Start

Load a cohort into DuckDB and start cross-product analytics across all HealthSim entities in one workspace.

Frequently Asked Questions about healthsim-duckdb

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

FAQPage Schema
How do I run cross-product analytics across PatientSim, MemberSim, and TrialSim data?▼

You can run cross-product analytics by loading cohorts into a DuckDB warehouse that persists canonical HealthSim entities, enabling unified SQL exploration across patients, members, and trials with provenance linkage.

What is the best way to persist and query simulation cohorts for SQL exploration?▼

The best way to persist and query simulation cohorts is using a DuckDB-based warehouse that stores canonical HealthSim entities, enforcing a unified schema with provenance and cohort_id linkage for safe, read-only SQL access.

Can I use DuckDB to create cohorts and explore reference data across different HealthSim products?▼

Yes, DuckDB enables cohort creation and reference data access across all HealthSim products, applying a unified schema with cohort_id linkage to safely query patients, members, trials, and related entities.

Does the DuckDB analytics warehouse support read-only SQL queries against canonical tables?▼

Yes, the DuckDB analytics warehouse enforces safe, read-only SQL access against canonical tables, enabling scalable exploration of patients, members, trials, and related entities without data duplication.

Why do I need a unified schema for cross-product analytics in DuckDB?▼

A unified schema is needed for cross-product analytics in DuckDB to enforce cohort_id linkage and provenance across all HealthSim entities, preventing data duplication while enabling token-efficient cohort operations.

Related Skills

Explore More Data & Analytics Skills→
mark64oswaldmark64oswald
1

healthsim-networksim

Analyze real NPPES provider networks with DuckDB-backed analytics for synthetic healthcare cohorts.

Community
Advanced
matevipmatevip
839

sql_query

Generate and execute read-only SQL queries to extract insights from data sources.

Community
Advanced
mark64oswaldmark64oswald
1

healthsim-trialsim

Generate regulatory-grade synthetic clinical trial data across SDTM domains.

Community
Advanced
clawdataclawdata
24

duckdb

Query local DuckDB warehouses with SQL and ingest CSV, Parquet, and JSON files.

Official
Intermediate