DATA WAREHOUSE

Healthcare claims snowflake schema

This healthcare claims snowflake schema places billed and paid amounts in FactClaim. The claim references date, patient, provider and diagnosis dimensions. Provider details roll through specialty to department, while diagnosis codes roll through disease group. The normalized structures prevent the same specialty, department or disease group text from being repeated on every dimensional row. Analysts can aggregate claims by date, clinical department, specialty or disease group while retaining a clear relationship back to the individual claim. This is useful where reporting hierarchies are governed separately from transaction data. It can also make changes to clinical groupings visible and reusable across reports.

UPDATED 2026-09-24
TYPEErd
EXAMPLEHealthcare claims snowflake schema
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Claims analytics

Key decisions

  • Claim grain: Store one row per submitted claim.
  • Provider hierarchy: Separate specialty and department.
  • Diagnosis grouping: Keep diagnosis groups independent of codes.

When to reuse this

Use this for claims reporting that rolls providers and diagnoses into managed hierarchies.

FAQ

Frequently asked questions

What does FactClaim represent?01
It represents one claim and its billed and paid measures.
Why separate specialty from provider?02
A specialty can be shared by many providers and managed once.
What is a disease group used for?03
It groups individual diagnosis codes for higher-level analysis.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.