.tql) in a git repo: TextQLLabs/ontology-starter-kits/tree/main/healthcare — your TextQL team grants access and sets up your own fork (your adaptations live in your fork; the template stays pristine).
What you’ll do
Set your North Star
Name what the ontology is for — Ana scans your data and drafts it; you confirm.
Tour the six layers
Entity spine, metrics, terminology, governance, decisions, validation.
Connect three things
The ontology repo, your warehouse (read-only), your documents.
Validate against your schema
Ana diffs the model vs. your tables and opens the fix as a PR.
Light up the terminology
ICD-10 groupers, HCC/RAF, chronic conditions — zero warehouse writes.
Ask governed questions
Prevalence, PMPM, readmissions, utilization, risk — with the SQL shown.
Govern & customize
PHI defaults, golden queries, and making the definitions yours.
What ships in the box — Free / public-domain code systems and groupers (ICD-10-CM/PCS, ICD-9 + GEMs, HCPCS, NDC, RxNorm, MS-DRG/APC, CCSR, CMS-HCC, CCW chronic) are in the repo — yours to keep and extend. Licensed systems (CPT, SNOMED, LOINC) are modeled structurally; certified VSAC value sets are fetched with your own UMLS key.
No customer data — ever — The starter is built entirely from public standards (CMS / AHRQ / US Census). Connecting it never uses your data to improve the template; it runs read-only, and your adaptations live in your own repo, never back in the template.
For facilitators — running this as a guided session
For facilitators — running this as a guided session
T-minus-1-day pre-flight: run the workshop’s key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. Pacing: when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. Group sessions: attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.
🤖 Prefer to have Ana run this workshop? Open a thread with your data connected and paste the prompt below — Ana walks you through it on your own data, one step at a time. You run each prompt; she coaches. (Air-gapped / VPC tenants where Ana can’t reach the web: download
ana-runner.md and paste its module list instead.)Run with Ana