PatientLT Core — Standalone

## The scenario You are a Junior Data Analyst on placement with the Data & Analytics team at a regional NHS Foundation Trust. The Associate Director of Information has asked you to produce a one-page Patient Snapshot for the upcoming Trust Board meeting — headline registration counts, age band distribution, GP practice coverage, data completeness flags, and the ten longest-registered patients still active. The Associate Director does not write SQL. She needs clean, labelled output she can paste straight into a briefing pack. Every column header must be report-ready; every row must be interpretable by a non-technical Board member. ## Dataset PatientLT is a synthetic NHS Trust dataset hosted on the CareerSwerve Azure SQL training database. For SQL Core you work exclusively with the `PatientLT.Patient` table — same discipline the course taught: master one table completely before joining. ## Deliverables Eight outputs (A–H), each demonstrating a specific SQL Core skill, submitted as a single annotated `.sql` file: **A.** Registrations by gender (NULL as explicit "Not recorded" category) · **B.** Registrations by year · **C.** Age band distribution with logical (not alphabetical) sort · **D.** Top 10 longest-registered active patients · **E.** GP practice patient distribution · **F.** New registrations in the most recent 12 months · **G.** Active vs historical UNION summary · **H.** Single-row data completeness audit. ## Acceptance criteria (summary) Queries run cleanly against PatientLT · result sets match specified columns and sort order · NULLs handled deliberately (CONCAT / ISNULL / IS NULL) · column aliases report-friendly · date filters use GETDATE/DATEADD/DATEDIFF (no hard-coded dates) · CASE-driven categorisation uses logical sort order · every query carries a 3-line purpose/author/date header comment. Defence is a 20-minute live walk-through with a CareerSwerve assessor. The full brief, ERD, and connection details appear inside the lesson once enrolled.