Get hands-on with dim_payer — the payer catalog that anchors every RCM query. Practice basic single-table SELECT, GROUP BY with COUNT(*), and a two-level ORDER BY (descending on the metric, ascending on the dimension as a stable tiebreaker).
First week on the billing team — Linda asked me to learn our payer mix before the AR cleanup project. From dim_payer, give me a count of payers grouped by plan_type, sorted by count descending so the dominant plan_type leads. Tiebreaker: alphabetical on plan_type so the order is stable when two types tie. Two columns: plan_type and payer_count.
| Column | Type | Key |
|---|---|---|
| payer_id | INT | PK |
| payer_name | TEXT | |
| plan_type | TEXT | |
| expected_pct_of_billed | REAL | |
| is_in_network | INT |
Each hint you reveal reduces the XP you can earn. Try the query first.
Single-table aggregate. dim_payer is the only table you need; group by the plan_type column and count.
Group by the plan_type column and COUNT(*). Linda's onboarding sheet expects the count alias as payer_count.
You'll need a two-level sort to keep the order stable when plan_types tie — descending on the count, ascending on the plan_type as tiebreaker.