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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
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.
Frequently asked questions
What does FactClaim represent?
Why separate specialty from provider?
What is a disease group used for?
More data warehouse examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.