Skip to content

Super Admin Console ​

Feature Overview ​

The PPP Super Admin console is a PPP-staff-only surface that lets the platform's super admins tune system-wide behaviour — reminder cadence, AHPRA breach handling, feature flags, and audit timelines — without a redeploy. It is not a hospital-admin surface; hospital admins are scoped to their own organisation and use the Hospital Admin & Governance views.

The console exists because several pieces of regulated behaviour need to be tunable by the AMC-CPD-Home operator (PPP staff) but must not be tunable by clinicians or hospital admins:

  • CPD reminder cadence, copy, and thresholds (the canonical clinical-reminder copy must match the Governing Document; PPP staff own that)
  • AHPRA breach-list initiation (#5604) — PPP super admin sends the notification on behalf of the AMC CPD Home
  • CPD plan unlock requests (#4927) — admin holds the unlock key
  • Future: speciality high-level-requirement edits (Q5, cpd.md) when AMC publishes changes

Open Questions ​

#QuestionSource
Q2Confirm token allow-list per reminder type (Matt) — what placeholders does each template support?Awaiting Matt
Closed Questions ​
Resolved questions (kept for traceability)
#QuestionResolution
Q5Support view (#7912): read-only only, or is a controlled "act as user" mode ever permitted?Read-only only (Rob, 2026-06-02). Act-as / impersonation is out of scope; if ever needed it is a separate Phase 2 follow-up, not part of #7912.
Q6Support view (#7912): which fields are masked (wellness, payments, medical registration, raw evidence)?No masking — full parity with the user's own view, including wellness/clinical data (Rob, CTO decision, 2026-06-02). The view shows exactly what the user sees. Matt to confirm the GDPR/privacy basis for super-admin wellness visibility; consent/notification (Q4) and audit-log retention (Q7) remain open.
Q9Support view (#7912): beyond super_admin, is there a separate support role with narrower scope?No — super_admin only (Rob, 2026-06-02). No separate narrower support role for now; revisit if a non-super-admin support function is ever needed.
Q4Support view (#8168): does the doctor consent to or get notified when support staff open their profile?Resolved 2026-06 (Matt) — Option 2: Log + notify. No per-access consent gate; PPP staff may open any account at their discretion (we protect doctors by never exposing their data to Enterprise admins, not by gating PPP). Every access writes an immutable audit row AND sends the doctor a passive in-app notification ("A PPP team member viewed your account for support purposes"). Matt: "Ok lets go with 2." RESOLVED-IN-CODE code:api/backend-ppp/src/services/admin-and-org/superAdminService/supportView.ts (#9701).
Q7Support view (#8168): how long are support-access audit logs retained, and who can read them?Resolved 2026-06 (Matt) — retained indefinitely; PPP admin only can read. Retention is indefinite (no TTL/purge) — Matt: "we keep these indefinitely — the idea of our product is to create a life long cv." Only PPP super_admin accounts can read the audit log (auditTrail.search is adminProcedure-gated); Enterprise/Hospital admins never see individual-doctor data. Exact doctor-facing notification wording to be reconciled against the lawyers' privacy-policy output before it is treated as final copy (not a code gate). RESOLVED-IN-CODE code:api/backend-ppp/src/routers/procedures/admin-and-org/auditTrail/index.ts (#9701).
Q8Support view (#8168): is access scoped (only users who raised a support request) or any user?Resolved 2026-06 (Matt) — any user, at PPP discretion. Access is not scoped to users who raised a support request; a PPP super-admin may open any doctor's profile at discretion, with the audit trail (Q4) as the accountability mechanism for any future investigation. Matt: "PPP can access accounts at discretion. obviously we have the above referenced audit log (q4) if any investigation needed." (#8168)
Q1Should we surface the full Application Insights telemetry inline, or just a 5-row summary per reminder?Resolved 2026-06-03 — RESOLVED-IN-CODE — bounded 'Last 5 runs' summary per reminder (executedAt + sent/skipped/errors); App Insights query stubbed pending wiring. code:api/backend-ppp/src/services/superAdminService/cpdReminderSettings.ts getLastRuns.
Q3Should enabled=false also pause Pulumi-defined Container Apps Job, or just no-op the handler?Resolved 2026-06-03 — RESOLVED-IN-CODE — no-op the handler; the Container Apps Job always fires on cron and the runner logs+exits 0 when disabled. code:api/backend-ppp/scripts/run-cpd-reminders.ts.
Access Control ​
  • Role: super_admin (distinct from hospital_admin and hospital_super_admin)
  • Route: /super-admin/*
  • Auth gate: protectedProcedure + an explicit requireSuperAdmin middleware on every super-admin tRPC procedure (server-side, never trust the client)
  • Audit log: every mutation writes a row with userId, action, targetTable, before, after, timestamp
Console sections ​

CPD Reminder Settings ​

Detail of the underlying engine: cpd.md § CPD Reminders & Notifications and cpd.md § Production wiring — Azure Container Apps Jobs.

A table-style editor for the 6 CPD reminder types backed by the cpd_reminder_settings DB table (grew from 4 to 6 in #11052, which added cpd_at_risk_quarterly and cpd_deadline_reminder):

FieldEditable?Validation
Reminder typeNoRead-only label
EnabledYesBoolean toggle. When off the next scheduled run exits without sending
Message templateYesMarkdown; lints against an allow-list
Deficit thresholdYes (deficit only)0 < x ≤ 1; default 0.10 (10%)
Cooldown (days)Yes (deficit only)1–30; default 7
Deadline monthYes (deadline only)1–12; default 12 (December) (#11771)
Deadline dayYes (deadline only)1–31; default 31 (#11771)
Lead monthsYes (deadline only)Comma-separated positive integers, e.g. "3,2,1"; default "3,2,1" (#11771)
Last editedNoAuto-stamped from updated_at + updated_by_user_id

Behaviour:

  • Saving validates the template against the allow-list of tokens for that reminder type (cpd_deficit_prompt exposes ; others have their own set)
  • Save writes one audit-log row per change
  • A "Send test to me" button on each row triggers the corresponding handler with the current user as the recipient and the in-memory edited values (does NOT save) — lets the super admin preview copy before committing
  • Read-only "Last 5 runs" panel per reminder shows recent execution timestamps + count of notifications sent (sourced from Application Insights via a backend-cached query)

CPD Plan Unlock Queue ​

Existing implementation: cpd.md § CPD Plans — lifecycle (#4927).

Lists pending plan unlock requests with: user, year, requested-at, current status, requester note. Action: Approve (status locked → draft, audit row written) or Reject with reason.

AHPRA Breach List (#5604) ​

Existing spec: cpd.md § APHRA Escalation.

End-of-year list of users below 50h with notification status. Mutations record notifiedAt, notifiedBy, hoursAtNotification. Triggers an in-app notification to the user and writes an audit row.

PPP Passport Reviews (#5985, #12893) ​

Existing spec: ppp-passport.md.

/admin/passport-reviews (Super Admin only) is the staff step 2 of each Passport two-step flow. It lists pending submissions from every domain (registration, degree, indemnity, right to work) with a Domain column and a "View document" button; an immunisation-evidence section (Verify per vaccination); and the Passport documents awaiting verification for the recruiter share page ("Mark verified"). Approve / Needs more info / Reject records the reviewer, notes and timestamp.

AMC Yearly Review (Q5) ​

Resolves Q5 in cpd.md. Runbook: /runbooks/amc-yearly-review.

Annual reminder for the Super Admin to manually review the AMC CPD Home framework page for changes (HLSR specialty list, category minima, governance updates) and raise PRs against PPP's seed data when the AMC framework moves.

  • Trigger: amc-review, registered on the NAS in-process scheduler (ADR-0006; re-platformed from the Azure Container Apps Job super-admin-amc-review by #11838) on the same cron 0 22 1 2 * (Feb 1 22:00 UTC = Feb 2 09:00 AEDT) — fires after AMC's typical January publication cycle
  • Action on fire: writes one row to super_admin_todos (or equivalent) with type amc-yearly-review, year, AMC page URL, and last-reviewed-at; surfaces in the Super Admin console as a banner until completed
  • Super Admin completes the todo by either:
    • Clicking "Mark reviewed — no change" (audit row + last_reviewed_at stamp)
    • Or raising a code PR updating the relevant files (per the runbook), then closing the todo with a link to the merged PR
  • Why no scraping: AMC has no public API; HTML scraping breaks silently and creates a hidden compliance liability. Manual review with versioned code edits keeps the audit trail clean
  • Acceptance criteria:
  • ✅ amc-review has a registered scheduled caller (NAS in-process scheduler) and fires on schedule
  • ✅ super_admin_todos table (or extension to cpd_reminder_settings) carries the todo
  • ✅ Super Admin console shows an open AMC review banner when one exists
  • ✅ "Mark reviewed" writes an audit row with the current user, timestamp, and AMC page URL hash captured at review time

HLSR Requirements list management (#8729) ​

Built (#8729 PR): Super Admin owns the per-specialty HLSR (High-Level Specialist Requirement) list. ANZASM/college HLSR requirements are updated annually, so the SA needs to edit the list and confirm it is current for each CPD year.

A Super-Admin console page at /admin/cpd-hlsr-requirements to manage the specialty → HLSR requirements mapping:

  • View all specialties and their HLSR requirements (active + inactive), filtered by a specialty selector.
  • Add / edit / remove individual requirements per specialty. Remove is a soft delete (the row stays so historical completions still resolve).
  • Each requirement records description, frequency (yearly / every N years), minimum duration (hours), and evidence type (case form / activity / other).
  • Multi-year handling — Option A (confirmed by Matt on #8729): a multi-year ("every N years") requirement computes its next-due date from when it was last completed. In intermediate years it renders "Not yet due — next due 20XX" and does not count as a compliance gap. The display / export shows last-completed date + next-due date so a report communicates both current compliance and the next-due date.
  • Yearly confirmation prompt: at the start of each CPD year a banner asks the SA to confirm the list is up to date for [year]; until confirmed the banner shows on the HLSR admin screen. The SA marks it confirmed for the current CPD year (idempotent upsert keyed on year).
  • Deferred to follow-up (#8775): the push/email notification form of the yearly prompt (the in-app banner is built), and the "existing CPD plans flag a review prompt" when the list changes.
  • Canonical seed (#8736): the table is seeded at first deploy (migration 0166) with the canonical ANZASM / college requirements for the 10 specialist types — the 9 non-surgical specialties (Anaesthesia, Emergency Medicine, General Practice, Intensive Care Medicine, Obstetrics & Gynaecology, Pain Medicine, Psychiatry, Radiology, Sport & Exercise Medicine) each with their own requirement rows, plus the ANZASM surgical-case-form requirement seeded against every RACS surgical specialty (excl. Oral & Maxillofacial). Multi-year cadences (GP CPR every 3 years, ICU airway every 3 years, O&G BLS every 2 years, Radiology anaphylaxis every 3 years, Sport & Exercise both every 3 years) are seeded as every_n_years with their interval. The SA can then add/edit/remove rows. Source: the Specialist High-Level Requirements tab on professionalperformanceportfolio.com/cpd-activities (extracted 2026-06-17), reconciled against the in-repo NON_SURGICAL_HLSR constant and the RACS_SURGICAL_NAMES group.

Specialty Procedure Classification Review (#10339) ​

New Super Admin console surface. Replaces the current ad-hoc GitHub-issue sign-off (#6684–#6705) for principal-procedure / curriculum classification with an in-app review + sign-off screen — the same move HLSR Requirements (#8729) made for the specialty requirements list. Boundary: this screen is read + review/sign-off over the classification produced by the #6684–#6705 engineering work; it does not edit the HLSR requirements list (#8729) or critical-conditions requirements (SpecialitySettings), which stay where they are.

Route: /admin/specialty-classification-review (sibling of /admin/cpd-hlsr-requirements), super_admin-gated.

Per specialty (specialty selector, same pattern as HLSR Requirements), the screen surfaces three read views drawn from the seed data already in api/backend-ppp/scripts/seed-data/specialty-procedures/:

  1. Curriculum index procedures (from curriculum-structures/{slug}.curriculum.json): index procedure name, indicative case number, PBA sign-off level, phase grouping, and the certification note — plus the source citation (college curriculum title + URL + extraction reference) so Matt can see provenance without opening the raw file.
  2. Procedure classification (from {slug}-db-ready.json): each procedure's mapping — principalProcedure (which index-procedure group it rolls up to), broadArea, specificArea, treatmentAcuity, and SNOMED match status/confidence — so Matt can eyeball whether the re-key landed procedures under the right index-procedure and area.
  3. Critical conditions (from the curriculum criticalConditions block): condition list + certification requirement, presented read-only for review (editing lives in SpecialitySettings — this is the sign-off view, not the editor).

Principal-procedure + PBA/WBA framework roll-up (#10339 extension, per #6684/#6697/#6698/#6699/#6701/#6703): on every one of the per-specialty sign-off issues Matt asked, verbatim, for "the Principal procedures for this speciality", "how many level 4 PBAs are required for sign off per principal procedure", and "the Critical conditions that require WBA (eg CEX/CBD) level 4 for sign off". The screen surfaces that framework as a read-only roll-up derived from the same seed data (no new data capture):

  • A Principal procedures summary: the distinct principalProcedure values in {slug}-db-ready.json, each with the count of procedures mapped to it, the curriculum indicative case number, and the PBA sign-off level required per principal procedure (joined by name to the curriculum phase2IndexProcedurePbaCompetencies). Where the curriculum file records no per-procedure PBA level (true for 9 of the 10 specialties today — only General Surgery carries phase2IndexProcedurePbaCompetencies), the level shows "Not in curriculum" rather than a fabricated number, and the generic PBA certification note (indexProcedureCertification, e.g. "three or more PBAs to the level shown in appendix 4") is surfaced alongside.
  • The WBA completion requirement: the critical-conditions count plus the curriculum criticalConditionCertification prose verbatim (e.g. "CEX or CBD to level 4 in all the critical conditions … indicative number of 10 CBDs or CEXs"). The per-condition numeric completion targets and the trainee-facing progress tracking are out of scope here — that is logbook issue #9123 (a separate data model + trainee dashboard, gated on Matt-provided per-condition numbers). This screen is the Super-Admin review surface for the requirement as it already exists in the curriculum, not the trainee tracker.
  • cardiothoracic-congenital intentionally has no principal procedures / critical conditions (#6704 defers to parent #6705) — the roll-up correctly renders an empty summary for it rather than inventing entries.

Sign-off behaviour (replaces the GitHub ✅/✏️/🛑 pattern):

  • The Super Admin sets a review decision per specialty: approved, changes_requested (with a free-text note), or pending (default). A per-row flag affordance lets them mark an individual procedure/classification row as needing a change, captured in the same note.
  • Each decision writes an audit-log row (userId, action, targetTable, before, after, timestamp) — the same audit convention as every other SA mutation.
  • A specialty's review state (who signed off, when, decision, note) is persisted and shown as a status badge in the specialty selector, so the 10-specialty progress is visible at a glance — the in-app equivalent of walking the #6684–#6705 issue list.
  • changes_requested with its note is the durable record that used to be a GitHub comment; engineering picks it up from the screen, not from issue threads.

Sign-off cadence — per CPD year (Rob, 2026-07-10): sign-off is per-CPD-year, matching HLSR Requirements' yearly-confirmation pattern (#8729) for consistency (rather than one-time-until-curriculum-changes). A yearly banner asks the Super Admin to reconfirm the classification is still current for [year]; until confirmed the banner shows on this screen. A specialty's sign-off is scoped to a CPD year, and a new CPD year re-opens confirmation — curriculum republications between years are exactly what the re-confirmation catches.

Explicitly out of scope (carried from the issue): re-deriving/re-classifying the underlying curriculum data (that is the #6684–#6705 classification work itself), and any change to the HLSR Requirements screen (#8729) or SpecialitySettings.

Open Questions (for-discussion, pending Matt's spec review — the per-CPD-year cadence is a Rob decision on 2026-07-10, not yet Matt-confirmed): Matt to confirm the per-CPD-year sign-off cadence (vs one-time-until-curriculum-changes), and the sign-off granularity — per-specialty vs per-row. Until confirmed these stay open.

Level of Involvement reference (#10752) ​

Read-only Super Admin reference screen at /admin/level-of-involvement showing the logbook Level-of-Involvement lists (non-consultant confirmed #9187, consultant placeholder) side by side so Matt can read the full vernacular in-app and annotate it. Surfaces the hardcoded LoI constants only — no DB table, no editing. The consultant table carries an "awaiting confirmation" banner (labels pending Q-consultant-loi / #10076); the legacy dropped codes (TaT, PP) sit in a distinct legacy section. The governing AC lives in logbook.md (logbook.admin.level-of-involvement-reference) — every LoI concept is specified there; this is the console it is reached from. Route is AdminRoute-gated (no new server procedure — the data is client-side constants).

Support View into a user's profile (#7912) ​

Surfaced in Kristin's demo-walkthrough feedback (29 May 2026). Spec-first per Rob's deep-dive — build is a follow-up.

A permissioned, read-only view that lets PPP admin/support staff open a specific user's profile and account state to help that user (e.g. a doctor who has reported a problem). The goal is diagnostic visibility, not impersonation: support staff see what the user sees so they can advise, but do not act as the user.

Grounded behaviour (follows from the issue + existing audit patterns):

  • Role-gated to super_admin (and a future support role if Matt defines one) — never available to clinicians or hospital admins.
  • Read-only: the support view renders the user's profile/state but exposes no mutating actions on behalf of the user.
  • The target user is identifiable on screen — support staff always know whose account they are viewing (name + identifier), never an anonymous blob.
  • Every support access writes an audit-log row: who viewed, whose account, when, and what was viewed.
  • No silent act-as / impersonation — opening the view never logs the support user in as the target user.

Privacy policy — Matt-confirmed (#8168, June 2026):

The privacy posture is the "good bank" model: PPP staff can open a doctor's account to help, but every look is logged and the doctor is told it happened.

  • Consent/notify (Q4) — Option 2, log + notify. No per-access consent gate; a PPP super-admin may open any account at their discretion. Every access writes an immutable audit row and sends the doctor a passive in-app notification of type support_view_accessed: "A PPP team member viewed your account for support purposes." The notification is deliberately data-minimised (GDPR) — it names neither the staff member (senderId: null → generic "a PPP team member") nor the internal support reason (audit-trail-only), so it never leaks staff PII or investigation detail to the data subject.
  • Access scope (Q8) — any user, at discretion. Access is not scoped to doctors who raised a support request; the audit trail is the accountability mechanism.
  • Retention + reader scope (Q7) — indefinite; PPP admin only. Audit rows are retained indefinitely (no TTL/purge), consistent with PPP's "lifelong CV" principle. Only PPP super_admin accounts can read the audit log (auditTrail.search is adminProcedure-gated); Enterprise/Hospital admins never see individual-doctor data — "we protect the doctors."

Legal note (not a build gate): Matt confirmed the privacy policy itself is being drafted by lawyers. The exact doctor-facing notification wording should be reconciled against that output before it is treated as final copy, but it does not gate the shipped technical behaviour. Matt also asked to surface the "good bank" best-practice framing on the marketing website — tracked separately, out of scope for this spec.

Decided (see Closed Questions Q5, Q6, Q9): read-only only (no act-as), full parity with the user's own view including wellness/clinical data (no field masking), and super_admin-only scope. Consent/notify (Q4), retention + reader scope (Q7), and access scope (Q8) are now all confirmed by Matt (see Closed Questions) and shipped (#9701).

User Guide visibility (5 May) ​

The platform User Guide is not rendered under CPD Home. It lives outside the CPD Home surface and is filtered by the viewer's role so users only see the pages relevant to them.

  • Audience filter — exactly one of: cpd-home-only, full-platform, hospital-admin, super-admin.
  • Source of truth — page-level frontmatter on each User Guide article tags the audience(s) it applies to; the renderer hides articles the viewer is not in.
  • Authoring lives in the docs site; rendering is per-role.

Compliance Mailboxes (5 May) ​

Two dedicated mailboxes back the CPD Home Exemption + Appeal flows. Provisioned by ops; submissions land here and are also written to the user's audit trail.

HandleSource form (cpd-home.md)Owner
exemptions@professionalperformanceportfolio.com"Request an exemption"Kristen (CPD Home compliance ops)
appeals@professionalperformanceportfolio.com"Appeal program level"Kristen (CPD Home compliance ops)
  • Backend writes a copy of the form payload to compliance_form_submissions (or equivalent) so the audit trail does not depend on the mailbox.
  • Mailbox provisioning is an ops task, not a code AC; tracked in deployment notes.

Hospital Geo-Location Accuracy (#10201) ​

Hospital rows added or curated in the Hospitals settings section carry a latitude/longitude pair used by Smart GeoTag geofencing (see timesheets.md). UK NHS ODS registry rows do not supply coordinates and must be geocoded. AU rows are not reliably coordinate-supplied either — a live UAT audit found 553 active hospitals with NULL coordinates, 552 of them AU (only 1 UK), each a silent geofence dead zone — so backfilling coordinates covers any active hospital with NULL coordinates, AU included, not UK-only.†

Geocoding a hospital on add/curation must resolve to address/postcode-level precision, or be flagged low-confidence for review, rather than silently persisting a locality-centroid match that makes every geofence at that site undetectable.

  • super-admin.hospital-geo-location-accuracy — uses the free/open government hospital registries already integrated (NHS ODS, CQC, AIHW; G-NAF/healthdirect NHSD planned) geocoded via OpenStreetMap Nominatim, rather than a commercial geocoding API (e.g. Google Maps Geocoding/Places) — declined on cost grounds.†
  • The geocoding query is anchored on the hospital's postcode/address (when on file), not the hospital name alone — a bare name-only free-text query against the geocoding provider commonly resolves to the town/postcode-area centroid instead of the actual site.
  • A geocode produced without a postcode/address anchor (name-only) is treated as lower-confidence and reported for review rather than silently stored as if fully precise.
  • Existing geocoded hospitals can be swept: re-geocoding with the postcode-anchored query and comparing against the stored point surfaces any hospital whose position has drifted more than 500m from a fresh, address-anchored result. This is a report artifact for manual review, not an automatic overwrite — no correction is applied without a human looking at it.
  • Confidence/provenance as first-class, filterable DB columns (so a future Super Admin geo-review screen could query "show me all low-confidence hospitals") is deliberately out of scope here — there is no such screen yet (#10179 is open and unimplemented). Building filter-ready columns for a screen that does not exist would be speculative; this is a follow-up once #10179 lands.
  • A configurable geofence radius per hospital/facility type (large acute campuses under-covered by the fixed default radius) is also out of scope here — it depends on the architecture proposal in #10178, which is for-discussion and not yet a decided design. Note: the current fixed geofence radius is 100m, confirmed as a deliberate (not user-configurable) product decision on the Rob/Matt call of 2026-04-07 (see timesheets.md) — if a per-hospital override ever ships per #10178, it will need its own spec-modification pass against that stated AC, not just an additive change. (The two hot-fixed UAT rows in #10201 had their radius manually widened to 350m as a one-off operational mitigation, not a code change.)

Acceptance Criteria ​

Access control ​

  • ✅ super_admin role exists in the role enum and is seeded on a known PPP-staff account
  • ✅ All /super-admin/* routes return 403 for non-super_admin users
  • ✅ Every superAdmin.* tRPC procedure runs through requireSuperAdmin middleware (server-side, not just hidden in the UI)
  • ✅ Audit-log row written for every mutation (userId, action, before, after)

CPD Reminder Settings ​

  • ✅ Page lists exactly 6 rows (one per reminder type) seeded on first run (#5706, grew to 6 in #11052)
  • ✅ Toggling enabled to false causes the next scheduled Container Apps Job to exit without sending (#5706)
  • ✅ Editing message_template validates against the allow-list of tokens for that type (#5706)
  • ✅ Editing deficit_threshold outside (0, 1] returns a validation error (#5706)
  • ✅ Save triggers one audit-log row per changed field (#5706)
  • ✅ "Send test to me" delivers a single notification to the calling user using the in-memory (unsaved) values (#5706). Fixed 2026-10-05 (#11218 B3): it now passes forceDeliver, because every caller is an admin and the admin-recipient gate silently dropped the row while the UI toasted success; the toast now reports honestly when nothing was delivered.
  • ✅ "Last 5 runs" panel shows recent execution timestamps from job-run telemetry (#5706)
  • ✅ cpd_deadline_reminder row exposes deadlineMonth/deadlineDay/leadMonths editor fields, validated (month 1–12, day 1–31, lead months a comma-separated list of positive integers) and persisted via the existing updateSetting audit-logged mutation; the values are read by processCpdDeadlineReminders at job-run time (#11771 — the columns shipped in #11052 but were never admin-editable)

CPD Plan Unlock Queue ​

  • ✅ Approve flips plan status locked → draft
  • ✅ Reject closes the request and records the reason
  • ✅ Both actions write an audit-log row

AHPRA Breach List ​

User Guide visibility ​

  • ✅ User Guide article frontmatter tags the audience(s): cpd-home-only, full-platform, hospital-admin, super-admin
  • ✅ Renderer hides articles the viewer is not tagged for
  • ✅ User Guide is not rendered under CPD Home (route lives outside the CPD Home surface)
  • ✅ Super Admin sees every article regardless of audience filter

Provider Verification Log ​

Super Admins can view an audit trail of every CPD provider verification event — i.e. every time a provider successfully consumed an approval token and was promoted to the approved-authorizers list.

  • ✅ GET /superAdmin.providerVerifications.list returns verification rows joined with provider name, filterable by provider ID and date range, ordered newest-first, paginated
  • ✅ Each row exposes: providerId, providerName, providerEmail, activityId, verifierEmail, verifiedAt, ipAddress, sourceEmailMessageId
  • ✅ superadmin.cpd.ppp-verification-queue — Super Admin owns stage 2 of the two-stage CPD provider-approval flow (#8765): once a provider has replied to the verification email, the activity sits in status unverified (with PPP) and must be PPP-verified before it counts as verified hours. Two requireSuperAdmin tRPC procedures back this queue: superAdmin.providerVerifications.listUnverifiedActivities lists the CPD activities currently awaiting PPP verification (status unverified), and superAdmin.providerVerifications.verifyActivity (input { activityId }) verifies one (status unverified → verified) and writes an audit row. This sits alongside the stage-1 super-admin provider vetting queue (which approves the provider entity itself); the two stages are independent — provider vetting runs in parallel and does not re-send the provider email (which is now sent on submit, see cpd-activities.md § cpd.activity.status-model-unverified). † (#8765) ‡

Annual Member Audit (ATT43 5% sample) ​

Super Admins record the outcome of the ATT43 CPD Auditing Policy's 5% annual member audit — the four published compliance decisions Matt's July 2026 policy requires for every member the yearly sample selects (#11054).

  • 🟡 superadmin.cpd.annual-member-audit — a requireSuperAdmin-gated annualMemberAudit router lists selected members' audit rows (annualMemberAudit.list, filterable by audit year and outcome) and records one of the four published outcomes on a selected member (annualMemberAudit.recordOutcome, input { auditId, outcome, notes }), writing who decided it and when. Rows are created by the yearly runAnnualAuditSample job, not by this router — this is the review/decision surface, not the draw. Remaining: an admin console screen to actually work this queue (the backend transition is delivered; no UI yet). † ‡

Settings Dashboard (super-admin.settings-dashboard) ​

  • ✅ Super admin landing at /settings (no sub-path) sees a dashboard overview page — NOT the hospitals table (#6001)
  • ✅ Dashboard shows a stat card for each of the 7 settings sections (Hospitals, Specialties, Clinical Locations, Job Titles, Procedures, CPD Providers, Keywords); each card displays the count of active (non-archived) records (#6001)
  • ✅ Each stat card is a clickable link to the corresponding /settings/<slug> route (#6001)
  • ✅ Quick-action cards for CPD Reminder Settings (/admin/cpd-reminder-settings) and AHPRA Breach List (/admin/cpd-escalation-candidates) appear in a separate row and link to live screens; the admin-only sidebar lists every super-admin console screen (#6001, #11220)
  • ✅ Stats fetched via a single superAdmin.settingsSummary tRPC query (no N+1 waterfall); loading state shows skeleton cards (#6001)
  • ✅ Non-super-admin users reaching /settings are unaffected — existing section redirect applies (#6001)
  • ✅ super-admin.settings.mobile-keyboard — each settings-form input surfaces the correct mobile keyboard: Contact Support email uses type=email+inputMode=email, the CPD-integration AMC URL uses type=url+inputMode=url, the magic-link TTL fields use inputMode=numeric, and the hospital search field uses type=search+inputMode=search — email/url/search inputs also set autoCapitalize=none autoCorrect=off (#9329) † ‡
  • ✅ super-admin.settings.mobile-section-picker — on a mobile viewport (below the sm breakpoint) a deep-linked /settings/<slug> section page exposes an in-page section picker so a super admin can switch between settings sections (Hospitals, Specialties, …) without re-opening the nav drawer or going back to the dashboard. The picker is a select of every settings section (defaulting to the active one) plus a back affordance to the /settings overview; on sm+ it is hidden because the sidebar's expandable Settings entry already provides this (#9538) † ‡
  • ✅ super-admin.settings.mobile-create-hospital — on isMobileApp (the RN webview) the HospitalToolbar primary actions (Add Hospital, Search Registry, Import AU/UK, and the Super-Admin Refresh/Curate buttons) are all display:none; a dedicated mobile-only full-width Add Hospital affordance (44px touch target, inverse of the desktop buttons) is rendered so a super-admin can still create a hospital from a phone (#9537) † ‡
  • ✅ super-admin.settings-dashboard.wellness-scoring-weights — a "Wellness Scoring Weights" Quick Action card on the Settings Dashboard links to /admin/wellness-scoring-settings, where a super admin reviews and edits the 17-component wellness readiness score weight profile without a redeploy (#11770). See wellness.scoring.weights-admin-override in wellness.md for the full AC — weights validated as a whole set, stored in a wellness_scoring_weights_override table, cached and audit-logged. † ‡

Compliance Mailboxes ​

  • ✅ "Request an exemption" form on CPD Home submits to exemptions@professionalperformanceportfolio.com (#5687)
  • ✅ "Appeal program level" form on CPD Home submits to appeals@professionalperformanceportfolio.com (#5687)
  • ✅ Each submission also persisted to compliance_form_submissions with userId, form-type, payload JSON, submittedAt — independent of mailbox delivery (#5687)
  • ✅ super-admin.compliance-decision-queue — a super admin reaches /admin/cpd-compliance-decision-queue (sidebar: "Compliance Decisions") to list pending exemption/variation/appeal submissions and record a decision (approve/decline, or uphold/dismiss for appeals) with a required rationale, optional expiry date and reference. #11878 wired up ppp.complianceForms.list/.decide (requireSuperAdmin-gated) but built no UI to reach them; this is that entry point. (#11881) † ‡

Hospital Geo-Location Accuracy ​

  • ✅ super-admin.hospital-geo-location-accuracy — geocoding a UK (NHS ODS) hospital anchors the query on the hospital's postcode/address when on file, not the hospital name alone (#10201) †
  • ✅ A geocode with no postcode/address anchor (name-only) is flagged as low-confidence in the backfill script's summary output rather than being silently stored as if fully precise (#10201) †
  • ✅ A sweep of hospitals that already have coordinates re-geocodes each against its postcode/address and reports (never auto-overwrites) any stored point that disagrees with the fresh re-geocode by more than 500m (#10201) †
  • ✅ super-admin.hospital-geo-location-accuracy.full-dataset-sweep — a super admin can trigger a full-dataset geo-verification sweep of every active hospital (backfilling NULL coordinates, AU included — not UK-only) from the Hospital Geo Health screen: the cross-validated consensus batch runner (#10268) is invocable via a super-admin-gated tRPC procedure that returns immediately with a pollable run id and reports a live burndown, rather than sitting dead with no caller (#10174) †
  • ✅ Confidence/provenance DB columns and a Super Admin geo-review screen — shipped (#10265 columns, #10269 review-queue screen); supersedes the earlier #10179 deferral
  • ⏳ Per-hospital/facility-type configurable geofence radius — deferred, blocked on #10178 (for-discussion, undecided); would require its own spec-modification pass against timesheets.md's existing fixed-100m AC if it ever ships

Support View into a user's profile ​

Built (#7912 PR): read-only superAdmin.supportView router + read-only frontend page at /super-admin/support-view/:userId. Read-only / full-parity / super-admin-only are decided (Closed Questions Q5, Q6, Q9). Privacy policy — consent-notification (Q4), audit retention + reader scope (Q7), and access scope (Q8) — confirmed by Matt (Option 2, log + notify) and shipped in #9701; all now Closed Questions.

  • ✅ Support view is reachable only by super_admin; all other roles get 403 †
  • ✅ Support view is read-only; it exposes no actions that mutate the target user's data †
  • ✅ Support view shows full parity with the user's own view, including wellness and clinical data †
  • ✅ The viewed user is always identifiable on screen (name and identifier) †
  • ✅ Every support access writes an audit row: viewer, target user, timestamp, and optional reason †
  • ✅ Opening the view never logs the support user in as the target (no silent act-as) †
  • ✅ Server-side gate enforces the role; UI hiding alone is insufficient †

Matt-confirmed June 2026 (Option 2 — log + notify). Built and shipped in #9701 on top of the #7912 read-only view. Consent (Q4), retention + reader scope (Q7), and access scope (Q8) are Closed Questions.

  • ✅ super-admin.support-view.notify-on-access — opening a support view sends the target doctor a passive in-app notification of type support_view_accessed ("A PPP team member viewed your account for support purposes"), in addition to the audit row (Option 2 — log + notify) (#8168) †
  • ✅ super-admin.support-view.notify-unsuppressible — the access-transparency notification cannot be silently muted by the doctor's own per-category notification preferences: createNotification is called with a forceDeliver: true option that bypasses isNotificationTypeDisabledForUser for this call only (opt-in per call site, not a global behavior change to other notification types). Stays in-app-only — no email channel was added; this does not reverse Matt's Option-2 decision, only guarantees the in-app notification it already specifies is actually delivered (#11056 AC3) †
  • ✅ super-admin.support-view.notify-data-minimised — the doctor-facing notification is data-minimised: it names neither the staff member (senderId: null, generic "a PPP team member") nor the internal support reason (audit-trail-only), so it never leaks staff PII or investigation detail to the data subject (#8168) †
  • ✅ super-admin.support-view.no-consent-gate — access is not gated behind per-access doctor consent, and is not scoped to doctors who raised a support request; a PPP super-admin may open any account at discretion, with the audit trail as the accountability mechanism (Q4/Q8) (#8168)
  • ✅ super-admin.support-view.audit-reader-scope — the support-access audit log is readable only by PPP super_admin accounts (auditTrail.search is super-admin-gated); Enterprise/Hospital admins are FORBIDDEN from querying individual-doctor audit data (Q7/Q8) (#8168) †
  • ✅ super-admin.support-view.retention-indefinite — support-access audit rows are retained indefinitely: no TTL, purge job, or scheduled deletion is applied to the audit_trail support-view rows, consistent with the "lifelong CV" retention principle (Q7) (#8168)

HLSR Requirements list management (#8729) ​

  • ✅ Super Admin can view all specialties and their HLSR requirements in the admin panel †
  • ✅ Super Admin can add, edit, and remove requirements per specialty †
  • ✅ Each requirement records description, frequency, minimum duration, and evidence type †
  • ✅ Multi-year requirements use Option A: in intermediate years they show "Not yet due — next due 20XX" and do not count as a gap; the display/export carries last-completed + next-due dates †
  • ✅ A yearly in-app banner asks the Super Admin to confirm the list is up to date for the current CPD year †
  • ✅ Super Admin can mark the list as confirmed for the current CPD year †
  • ✅ All HLSR list-management procedures are super-admin-gated server-side †
  • ✅ Yearly confirmation prompt is also delivered as a push/in-app notification to every active Super Admin at the start of a CPD year; suppressed once the year is confirmed (#8775) †
  • ✅ An existing CPD plan flags a review prompt when an HLSR requirement for the plan owner's specialty changes after the plan was last built (#8775) †
  • ✅ The HLSR requirements table is seeded at first deploy with the canonical requirements for the 10 specialist types — 9 non-surgical specialties each with their own rows, plus the ANZASM surgical-case-form requirement against every RACS surgical specialty (excl. Oral & Maxillofacial); multi-year cadences seeded as every_n_years with their interval (#8736) †
  • ✅ Source URL and extraction date recorded in the seed migration comments for traceability (#8736) †

Specialty Procedure Classification Review (#10339) ​

  • super-admin.specialty-classification-review.access — the screen and all its tRPC procedures are requireSuperAdmin-gated server-side; non-super-admin users get 403 (#10339)
  • super-admin.specialty-classification-review.view-curriculum — for a selected specialty the screen shows the curriculum index procedures (name, indicative case number, PBA sign-off level, phase grouping, certification note) with the source citation, read from curriculum-structures/{slug}.curriculum.json (#10339)
  • super-admin.specialty-classification-review.view-classification — for a selected specialty the screen shows each procedure's classification (principalProcedure, broadArea, specificArea, treatmentAcuity, SNOMED match status/confidence) read from {slug}-db-ready.json (#10339)
  • super-admin.specialty-classification-review.critical-conditions — for a selected specialty the screen shows the critical-conditions list + certification requirement read-only (editing stays in SpecialitySettings) (#10339)
  • super-admin.specialty-classification-review.signoff — a super admin can set a per-specialty review decision (approved / changes_requested + note / pending) and flag individual rows; each decision writes an audit-log row and persists the reviewer, timestamp, decision, and note (#10339)
  • super-admin.specialty-classification-review.progress — each specialty's current review state is shown as a status badge in the specialty selector so 10-specialty sign-off progress is visible at a glance; the badge renders for every reviewed specialty in the selector, not only the one currently loaded (listReviewStates returns a slug per row and the selector keys badges by slug) (#10339, #10359)
  • super-admin.specialty-classification-review.boundary — the screen does not edit HLSR requirements (#8729) or critical-conditions requirements (SpecialitySettings); it is read + sign-off over the #6684–#6705 classification only (#10339)
  • super-admin.specialty-classification-review.yearly-confirmation — a yearly in-app banner asks the Super Admin to reconfirm the specialty classification is still current for the current CPD year; the SA can mark it confirmed (idempotent upsert keyed on year), mirroring HLSR Requirements' yearly-confirmation banner (#10339)
  • super-admin.specialty-classification-review.principal-procedures — for a selected specialty the screen shows a Principal procedures roll-up: the distinct principalProcedure values from {slug}-db-ready.json with the count of procedures mapped to each, the curriculum indicative case number, and the PBA sign-off level required per principal procedure (from phase2IndexProcedurePbaCompetencies); where the curriculum records no per-procedure PBA level it shows "Not in curriculum" rather than a fabricated number, alongside the generic indexProcedureCertification note (#10339, per #6684/#6697/#6698/#6699/#6701/#6703)
  • super-admin.specialty-classification-review.wba-requirement — for a selected specialty the screen shows the critical-conditions-as-WBAs completion requirement: the critical-conditions count plus the curriculum criticalConditionCertification prose (CEX/CBD to level 4 across all critical conditions + indicative count) verbatim; the per-condition numeric targets + trainee-facing progress tracking stay out of scope here (logbook #9123) (#10339, per #6684/#6697/#6698/#6699/#6701/#6703)
Status ​
Sub-featureStatusNotes
super_admin role + middleware⏳ SpecifiedNew role enum value + tRPC middleware
Settings Dashboard✅ Specified#6001 — stats overview + click-throughs; super admin lands here instead of bare hospitals table
CPD Reminder Settings UI⏳ SpecifiedDepends on cpd_reminder_settings DB table (cpd.md)
CPD Reminder Settings backend⏳ SpecifiedtRPC procedures + audit log
Container Apps Jobs (4 schedules)⏳ SpecifiedPulumi resources + scripts/run-cpd-reminders.ts runner; reads settings from DB at run time
CPD Plan Unlock Queue✅ Built#4927
AHPRA Breach List✅ Specified#5604
User Guide audience gating⏳ Specified5 May — frontmatter-driven role filter; lives outside CPD Home
Exemptions / Appeals mailbox routing⏳ Specified5 May — exemptions@ + appeals@ handles; payload also written to compliance_form_submissions
Provider Verification Log✅ Built#5779 — superAdmin.providerVerifications.list tRPC query; audit of every approval-token consumption
Support View into a user's profile✅ Built#7912 — read-only superAdmin.supportView router (search + getUserProfile) + read-only page /super-admin/support-view/:userId; audit-logged; super_admin-gated. Read-only/full-parity/super_admin-only decided (Q5/Q6/Q9). #8168 privacy policy — Option 2 (log + notify), indefinite retention, PPP-admin-only reader scope, any-user access — Matt-confirmed + shipped (#9701); Q4/Q7/Q8 now closed
Hospital Geo-Location Accuracy✅ Built#10201 — postcode/address-anchored geocoding + name-only/drift flagging in scripts/geocodeHospitals.ts; confidence/provenance columns + per-hospital radius override deferred, blocked on #10179/#10178 respectively
Specialty Procedure Classification Review⏳ Specified#10339 — /admin/specialty-classification-review; per-specialty read views (curriculum index procedures, procedure→principalProcedure/area classification, critical conditions) + per-CPD-year sign-off (approved/changes_requested/pending) replacing the #6684–#6705 GitHub-comment pattern; yearly SA reconfirmation banner mirroring HLSR (#8729). Ring-fences HLSR Requirements + SpecialitySettings
HLSR Requirements list management✅ Built#8729 — superAdmin.cpdHlsrRequirements router (list/create/update/remove + yearly getConfirmation/confirm) + page /admin/cpd-hlsr-requirements; Option-A multi-year due-date model; yearly SA confirmation banner. #8775 — yearly confirm delivered as a notification (notifyConfirmationDue) + existing-plan review-flag (cpdHlsrAttestation.getPlanReviewPrompt)
Wellness Scoring Weights admin UI✅ Built#11770 — Quick Action card + /admin/wellness-scoring-settings; full AC in wellness.md (wellness.scoring.weights-admin-override)
Compliance Decision Queue UI✅ Built#11881 — /admin/cpd-compliance-decision-queue; lists pending exemption/variation/appeal submissions against ppp.complianceForms.list and records a decision via .decide, both wired up procedure-only by #11878 (#11048 AC2)

Open issues on label:feature:super-admin — issue data unavailable at build time.Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Change Log ​
DateChangePR/IssueReason
2026-10-05The PPP Passport staff review queue at /admin/passport-reviews now spans every Passport domain (with a document viewer and an immunisation / Passport-document section), and the indemnity, indemnity-expired and training expiry notifications deep-link to /ppp-passport. See the ppp-passport spec change-log entry for the full set.#12893, #12896, #11212Task 13 audit defects D2, D5 and D9 (5 Oct 2026); covered by @issue-12893 in ppp-passport.feature.
2026-10-04Settings dashboard CPD quick actions now link to the real screens (/admin/cpd-reminder-settings, /admin/cpd-escalation-candidates). The admin-only sidebar now lists every super-admin console screen, and CPD Reminder Settings and AHPRA Notification Settings gain nav entries.#0, #11220Task 18 video checklist (T18-02, T18-03, T18-35, T18-36, T18-37). The quick actions pointed at /super-admin/* paths with no route, and an admin-only super admin could reach only 6 console screens from the sidebar.
2026-08-29Added super-admin.compliance-decision-queue AC — a super admin decision queue UI at /admin/cpd-compliance-decision-queue (sidebar "Compliance Decisions") listing pending exemption/variation/appeal submissions and recording decisions against ppp.complianceForms.list/.decide. Status table row added.#11969, #11881, #11048#11878 wired up the list/decide procedures (super-admin, procedure-only) but built no UI to reach them — #11048's AC2 ('a super-admin decision queue reads and updates them') was only half-satisfied without a reachable surface.
2026-08-28Add a requireSuperAdmin annualMemberAudit router (list + recordOutcome) for the ATT43 5% annual audit's four published outcomes.#11877, #11054The yearly audit sample now persists a row per selected member per audit year; Super Admin needs a decision surface to record the compliance outcome the CPD Auditing Policy requires (Compliant / Compliant with Minor Issues / Not Compliant – Rectifiable / Not Compliant – Non-Rectifiable).
2026-08-27AMC Yearly Review trigger AC updated from "Container Apps Job exists and fires on schedule" to a NAS in-process scheduler registration — the job body, cron cadence, and idempotency are unchanged.#11845, #11838Backend hosting moved off Azure to a self-hosted NAS (ADR-0006); the AMC review job's stated AC baked in the specific mechanism ("Container Apps Job"), so the re-platform required a spec edit rather than only a code change.
2026-08-24Added a "Wellness Scoring Weights" Quick Action card to the Super Admin Settings Dashboard, linking to the new /admin/wellness-scoring-settings page (#11770).#11781, #11770Makes the new wellness scoring weights admin page (built for #11770) discoverable from the Super Admin console landing page, matching the existing Quick Actions pattern for CPD Reminder Settings / AHPRA Breach List.
2026-08-24CPD Reminder Settings admin page now exposes deadlineMonth/deadlineDay/leadMonths for the cpd_deadline_reminder row — these columns shipped in #11052 (deadline-offset reminders) but were never admin-editable. Spec table updated from 4 to 6 reminder types (cpd_at_risk_quarterly and cpd_deadline_reminder had never been added to the table).#11780, #11771#11220 admin console audit (E1, #11766) flagged CPD Actions backend as substantially built but frontend wiring unconfirmed; this closes the one genuine gap found — reminder timing configurability per the CPD Home Document schedule. The AHPRA notify action (the epic's other AC) was found to already be fully built end-to-end and intentionally dormant per Matt's 6 May 2026 manual-fallback decision (cpd.md § APHRA Escalation) — no engineering work needed there.
2026-07-21Specialties settings grid now exposes a discoverable "Edit conditions & requirements" pencil row action that opens the existing speciality editor directly in edit mode (skipping the read-only view step), and the Critical Conditions column is visible from the md breakpoint (was lg) — so a Super Admin can add/edit a specialty''s critical conditions & HLSR in one click. Reuses the existing CreateViewUpdateSpeciality editor + speciality.update mutation via a minimal isEditMode wired to the useModalStates edit state; add/view callers keep their contract.#10812, #10778Matt (WhatsApp, 19 Jul 2026) couldn''t find where to edit critical conditions at Settings -&gt; Specialties: the editor existed but was buried behind an eye/view-only row action (eye -&gt; View -&gt; Edit) and the Critical Conditions column was hidden on a normal laptop, so every specialty read "No critical conditions" with no obvious way in. Discoverability fix only (clearer row action + column visibility) — a brand-new inline editor vs a dedicated per-specialty page remains Matt''s UX call per #10778.
2026-07-11Specialty Classification Review selector now badges every reviewed specialty, not only the currently-loaded one. listReviewStates returns a slug per row; the frontend keys badges by slug (decisionBySlug) instead of specialityId.#10377, #10359#10359 — the selector only knew the specialityId of the specialty getSpecialty had loaded, so every other option''s badge blanked despite listReviewStates already returning all 10 decisions. Cosmetic-only, fixed on the same branch before merge.
2026-07-10Closed the support-view privacy Open Questions (Q4 consent/notify, Q7 retention + reader scope, Q8 access scope) with Matt's confirmed answers — Option 2 (log + notify), indefinite audit retention, PPP-admin-only reader scope, any-user access at discretion. Moved Q4/Q7/Q8 from Open to Closed Questions, rewrote the Support View privacy narrative ("good bank" model), and added 5 privacy-policy ACs (notify-on-access, notify-data-minimised, no-consent-gate, audit-reader-scope, retention-indefinite) with corrected src: citations to the real admin-and-org/ paths.#10366, #8168The support-view privacy build (audit + passive notification, indefinite retention, super-admin-only reader gating) shipped in #9701, but the spec still carried Q4/Q7/Q8 as "Awaiting Matt" with no governing ACs — shipped behaviour with no spec. This reconciles the spec to Matt's confirmed decisions and the merged code, closing the drift.
2026-07-10Specialty Procedure Classification Review — read-only Principal-procedure + PBA/WBA framework roll-up: distinct principalProcedure list per specialty with mapped-procedure count, curriculum indicative number, and per-PP PBA sign-off level (from phase2IndexProcedurePbaCompetencies), plus the indexProcedureCertification / criticalConditionCertification prose and critical-conditions-as-WBAs count. Two new ACs (.principal-procedures, .wba-requirement). Derived from existing seed data — no new capture.#10364, #10339, #6684, #6697, #6698, #6699, #6701, #6703, #9123On every #6684–#6705 per-specialty sign-off issue Matt asked, verbatim, for the specialty's principal procedures, how many level-4 PBAs are required per principal procedure, and the critical conditions requiring WBA (CEX/CBD) level 4 for sign off — a framework to check + mark complete. This surfaces that on the review screen instead of separate GitHub comments. Read-only; per-condition numeric targets + trainee-facing tracking stay in logbook #9123. 9/10 specialties lack per-procedure PBA levels in the curriculum JSON — shown as 'Not in curriculum', never fabricated.
2026-07-10Corrected the stale "AIHW (AU) rows supply coordinates directly and are out of scope here" clause in the Hospital Geo-Location Accuracy section — a live UAT audit found 553 active hospitals with NULL coordinates (552 AU, 1 UK), so coordinate backfill covers any active hospital with NULL coordinates, AU included, not UK-only. Added an AC recording that a super admin can trigger a full-dataset geo-verification sweep (the #10268 consensus batch runner) from the Hospital Geo Health screen via a super-admin-gated tRPC procedure returning a pollable run id, with a server-side one-sweep-at-a-time guard. Flipped the confidence/provenance-columns + geo-review-screen AC from deferred (⏳, blocked on #10179) to shipped (✅, #10265 columns + #10269 review-queue screen).#10329, #10174The batch runner (#10268/PR #10321) shipped but had zero callers, so the existing 553 coordless hospitals were never swept — only future self-adds ran. The spec still asserted AU rows were coordinate-supplied and out of scope, which the UAT data reverses (552/553 are AU). Wiring one invocation surface makes the already-tested consensus engine runnable against the real backlog without reimplementing geocoding/cross-validation. Source: issue #10174 (UAT audit) + governance-trace verdict MATCHES_EXISTING_MODIFIED.
2026-07-10Added Specialty Procedure Classification Review section — Super Admin console screen (/admin/specialty-classification-review) surfacing per-specialty curriculum index procedures, procedure→principalProcedure/area classification, and critical conditions (all read-only) with per-CPD-year sign-off (approved/changes_requested/pending) + yearly reconfirmation banner. Replaces the ad-hoc #6684–#6705 GitHub-comment sign-off. 8 ACs added; Status table extended.#10339Rob (2026-07-09 Dev Session) — once the specialty-classification PRs land, Matt manages the remaining logbook specialty issues in the admin console; that surface for principal-procedure/curriculum classification did not exist yet. Governance-trace verdict NEEDS_NEW_SPEC (new section in super-admin.md, no capability-model change). Sign-off cadence set to per-CPD-year to match HLSR Requirements (#8729).
2026-07-08Added the "Hospital Geo-Location Accuracy" spec section (new — was previously ungoverned, per governance-trace NEEDS_NEW_SPEC). Hospital geocoding on add/curation is now anchored on postcode/address (not the hospital name alone); name-only geocodes and >500m drift on a re-geocode of existing coordinates are flagged for review in scripts/geocodeHospitals.ts's report output rather than silently stored/overwritten. Confidence/provenance DB columns and a per-hospital radius override are explicitly deferred, blocked on #10179 and #10178 respectively.#10201Two self-added UK hospitals (Basingstoke & North Hampshire, Royal Hampshire County) were geocoded 1.5-3.4km from the real site — a name-only Nominatim query resolved to the town/postcode-area centroid instead of the address. At a 200m geofence radius, an error of kilometres makes Smart GeoTag detection silently impossible for every doctor at that hospital.
2026-06-27Hospital settings now exposes a mobile-only Add Hospital affordance on isMobileApp. The desktop HospitalToolbar actions remain display:none in the RN webview, but a dedicated full-width Add Hospital button (44px touch target, data-testid hospital-mobile-add-button, inverse of the desktop buttons) restores the create path. Added AC super-admin.settings.mobile-create-hospital.#9611, #9537Child of the #9320 mobile sweep (Wave 2). Every HospitalToolbar primary action is hidden on isMobileApp and the native shell offers no replacement, so a super-admin could not create a hospital on a phone. Additive mobile-only button — desktop behaviour is unchanged.
2026-06-27Added super-admin.settings.mobile-section-picker AC + @smoke scenario: on a phone (below the sm breakpoint) a deep-linked /settings/<slug> now renders an in-page SettingsSectionPicker — a select of every settings section (defaulting to the active one) plus a back affordance to the /settings overview — so a super admin can switch sections without re-opening the nav drawer or returning to the dashboard. Hidden on sm+ where the sidebar's expandable Settings entry already provides this.#9538, #9320Child of the #9320 mobile sweep. On mobile the sidebar collapses into a drawer, so a deep-linked settings section stranded the user with no in-page way to switch sections short of going back to the dashboard.
2026-06-25Settings-form inputs now surface the correct mobile keyboard — Contact Support email (type=email + inputMode=email), CPD-integration AMC URL (type=url + inputMode=url), magic-link TTL fields (inputMode=numeric), and the hospital search field (type=search + inputMode=search); email/url/search inputs also set autoCapitalize=none autoCorrect=off. Added AC super-admin.settings.mobile-keyboard.#TBD, #9329Child of the #9320 mobile sweep. These settings forms triggered the wrong mobile keyboard (plain text) for email/url/numeric/search fields. Surgical prop additions only — no layout or behaviour change.
2026-06-17HLSR Requirements list management — shipped the two pieces deferred from #8729. The yearly "confirm the HLSR list is up to date for [year]" prompt is now also delivered as a push/in-app notification to every active Super Admin (suppressed once the year is confirmed), and an existing CPD plan now flags a review prompt when an HLSR requirement for the plan owner's specialty changes after the plan was last built. Flipped the two deferred acceptance criteria to built.#8810, #8775Completes the original #8729 acceptance criteria — the in-app banner and new-plan authority shipped in #8774; #8775 adds the notification channel and the existing-plan review-flag.
2026-06-17Added the HLSR Requirements list-management console: Super Admin can view/add/edit/remove per-specialty HLSR requirements (description, frequency, minimum duration, evidence type), with Option-A multi-year due-dates and a yearly SA confirmation banner#8774, #8729ANZASM/college HLSR requirements change annually; the Super Admin must own and confirm the list, and multi-year requirements must show 'Not yet due — next due 20XX' with last-completed + next-due dates rather than counting as a yearly gap (Option A confirmed by Matt on #8729)
2026-06-17Added the stage-2 PPP-verification queue: superAdmin.providerVerifications.listUnverifiedActivities lists CPD activities awaiting PPP verification and superAdmin.providerVerifications.verifyActivity verifies one (unverified → verified) (AC superadmin.cpd.ppp-verification-queue).#8768, #8765Operational provider-approval flow Matt greenlit 2026-06-16 (split from on-hold #7915). After a provider replies, the activity sits as 'unverified' (with PPP); a PPP super-admin must verify it before it counts as verified hours. Runs in parallel with the stage-1 provider-vetting queue.
2026-06-17Seeded the SA-managed HLSR requirements table at first deploy (migration 0166) with the canonical ANZASM/college requirements for the 10 specialist types: the 9 non-surgical specialties (Anaesthesia, Emergency Medicine, General Practice, Intensive Care Medicine, Obstetrics & Gynaecology, Pain Medicine, Psychiatry, Radiology, Sport & Exercise Medicine) each with their own rows, plus the ANZASM surgical-case-form requirement against every RACS surgical specialty (excl. Oral & Maxillofacial). Multi-year cadences seeded as every_n_years with their interval.#8736The HLSR list-management console (#8729/#8774) shipped an empty table; the canonical requirements must be present at first deploy so doctors see their specialty's HLSR without the SA hand-entering 16 rows. Seeded as data so the SA can still edit it (per #8727). Source: the Specialist High-Level Requirements tab on professionalperformanceportfolio.com/cpd-activities (extracted 2026-06-17), reconciled against the in-repo NON_SURGICAL_HLSR constant and RACS_SURGICAL_NAMES group.
2026-06-03Resolve Q1/Q3 to Closed Questions (5-run reminder summary; no-op-when-disabled handler) — both code-confirmed.#8166SGD governance sweep — transcript-grounded audit found these questions already answered; reconciled the spec to shipped reality and moved them out of Open Questions.
2026-06-02Support View into a user''s profile built (Option B): read-only, super-admin-gated, audit-logged superAdmin.supportView router (searchUsers + getUserProfile aggregating profile/cpd/wellness/passport/account by targetUserId) + read-only page at /super-admin/support-view/:userId with a "Viewing <name> — read-only support view" banner and wellness panel. Every access writes one audit_trail row (viewer, target, timestamp, optional reason). New audit action support_view_opened + entity support_view (varchar columns, no migration). Support View ACs/Status flipped to Built.#8033, #7912Surfaced in Kristin's demo-walkthrough feedback (29 May); Rob chose read-only diagnostic visibility (not impersonation). Read-only/full-parity-incl-wellness/super_admin-only decided in Closed Questions Q5/Q6/Q9; consent-notification (Q4), audit retention (Q7) and target scope (Q8) remain open for Matt, including the GDPR/privacy basis for super-admin wellness visibility.
2026-06-02Resolved support-view spec questions Q5/Q6/Q9 (read-only, full parity incl. wellness, super_admin-only) and firmed the acceptance criteria; Q4/Q7/Q8 (consent, retention, target scope) remain open for Matt.#8030, #7912Spec-design session with Rob (CTO decisions) on the #7912 support view surfaced from Kristin's 29 May demo feedback.
2026-06-01Add Support View capability — permissioned, read-only, audited view into a specific user's profile for admin/support staff (spec-first; build is a follow-up).#7978, #7912Surfaced in Kristin's demo-walkthrough feedback (29 May 2026) — support staff need to see a doctor's account state to help them. Spec-first per Rob's deep-dive; privacy/access-policy decisions left as Open Questions Q4–Q9 for Matt.
2026-05-19Add Super Admin Settings Dashboard — stat cards + quick-action links at bare /settings.#6293, #6001Super admins had no orientation page at /settings; they were immediately redirected to the hospitals table with no at-a-glance overview of platform health.
2026-05-06Added superAdmin.cpdReminderTrigger.trigger tRPC mutation that invokes any of the 4 CPD reminder jobs synchronously via the API, enabling real BDD step definitions for the reminder-job scheduler contract.#5814, #5761, #5698BDD scenarios for the CPD reminder Container Apps Jobs (#5698) had no-op step definitions tagged @wip. The trigger endpoint gives step defs an observable API surface to invoke and assert on without shelling out to the Azure Job runner.
2026-05-06Provider Verification Log: superAdmin.providerVerifications.list tRPC query; audit of every CPD approval-token consumption event#5779Super Admin surface for #5779 provider-verification audit trail; added to spec to prevent spec-drift
2026-05-05AMC Yearly Review: 5th Container Apps Job + super_admin_todos table + console banner/modal#5674Q5 resolution — manual annual AMC framework review with audit trail
2026-05-05Added User Guide visibility section (audience-gated rendering — cpd-home-only / full-platform / hospital-admin / super-admin; lives outside CPD Home) and Compliance Mailboxes section (exemptions@ + appeals@ handles; payloads also written to compliance_form_submissions for audit-trail independence). Status table extended.5 May call decisions — Matt scoped User Guide to be filtered by role (not visible under CPD Home), and Kristen onboarding as ops needs dedicated mailboxes for the new Exemption + Appeal forms.
2026-05-05Spec created. Captures the Super Admin console scope, starting with CPD Reminder Settings as the first concrete feature; lifts existing Plan Unlock + AHPRA Breach List from cpd.md as cross-referencesthis PRQ4 resolution required a place for the per-reminder enable/cadence/copy editor; the Super Admin role surface didn't exist as its own feature spec, so we add it now.

Internal documentation — org members only