SQL Analyst Challenge Room
Eight real analyst scenarios across healthcare IT, QA, finance, and data migration. Each challenge gives you a schema, a situation, step-by-step guided hints, and a submit box. No multiple choice — just SQL thinking.
How It Works
Pick a Challenge
Read the situation brief. Every scenario is a real analyst problem — a missing charge, a HIPAA complaint, a data migration gap.
Study the Schema
Each challenge has a self-contained database schema. Understand the tables and relationships before writing SQL.
Use the Step Hints
Expand hints one step at a time — from "what to look for" to "which tables to join" to a partial query. Use only what you need.
Submit and Debrief
Submit what you found. Correct answers unlock the full solution with a practitioner debrief explaining the real-world lesson.
A physician signed a progress note two hours ago but no charge appeared in the charge review queue. Find the gap before the end of shift.
Three days after a data migration, patients appear twice in the system. Find the duplicates and identify which record to keep.
The CMO dashboard shows 2.1 days average LOS. The prior system showed 2.6 for the same population. The query runs — but the math is wrong.
A patient filed a HIPAA complaint. You have the Epic audit log. Find every access with no clinical treating relationship on the access date.
Claims denial rate spiked 12% last quarter. Nobody caught it until the CFO asked. Find the payer, service type, and denial code responsible.
The nightly ETL logged "Success" but the quality reports show yesterday's data. Find where records are being silently dropped between extract and load.
Epic's pre-computed READMISSION_FLG shows 4.2%. The quality director believes planned readmissions that CMS excludes are inflating the number. Prove or disprove it.
T-MSIS data shows members who received services but were not enrolled on the date of service. Find the members, the gaps, and the dollar exposure before the state audit.