- North Star set: you named what the ontology is for, picked an archetype, and chose the questions that matter — before touching the schema
- Connected: ontology repo (live, git-backed) + warehouse (read-only) + your documents
- Validated: the model diffed against your actual schema, fixed via PR
- Terminology live: CCSR / HCC / chronic groupers joining in-sandbox, zero warehouse writes
- Governed answers: prevalence, PMPM, readmissions, utilization, RAF — SQL shown, decisions recorded
- Compliant by default: minimum-necessary, <11 suppression, sensitive-diagnosis gating
- Self-maintaining: not-yet-governed questions answered on the frontier and proposed back as PRs — discovery paid once, then reused
- Yours: definitions adapted in your repo, pinned with golden-query tests
Where to go from here
- Operate it: the Ontology Operations workshop covers the production loop — git workflows, access control, accuracy testing, scaling across teams.
- Understand the build: Build Your Ontology, End to End teaches the from-scratch method the starter packages up.
- Roll it out: point your analysts and business users at Self-Service Analytics — the ontology you just stood up is what makes their answers trustworthy.
- Licensing: before production, review
LICENSING.md(CPT/SNOMED/LOINC structural modeling; VSAC via your UMLS key).