Skip to content
View in Notion

CPD Plans ​

Feature Overview ​

This spec covers the CPD Plan (annual plan lifecycle) and the CPD data model + Regulatory / Specialist HLSR framework — the core of the CPD capability, aligned with the "Plans" navigation item. The other CPD areas are now their own specs: CPD Home (dashboard), CPD Activities, CPD Report, CPD Resource Library, CPD Support, and CPD Automations.

Doctors must accumulate a required number of CPD hours/points per year across defined categories. PPP helps them track activities, manage their annual plan, generate completion certificates, and demonstrate compliance to their medical college.

PPP offers two tiers:

  • CPD Home — lighter plan, cheaper subscription (CPD tracking only)
  • PPP Full Platform — CPD + Surgical Logbook + Wellness + Timesheets + Appraisals

The CPD plan is a projection set at the start of year. Users compare actuals against the plan in their End-of-Year Reflection — the plan is not a target, the annual 50h is (5 May 2026).

Terminology (5 May 2026): "Surgical Logbook" is renamed Procedural Log Book in user-facing copy. Backend tables, services, and code paths retain the surgical* prefix until a coordinated rename ships.

Open Questions ​

All questions have been answered — see Closed Questions below.

Matt's 17 Apr 2026 Notion Brief — Requirements Update ​

Source: CPD Home Notion brief. Matt's brief is the heaviest screen-level commentary of the 18 feature briefs. Every bullet below is a regression-grade AC — the build must either address it or raise a question back on the Notion page.

Regulatory framing (re-asserted) ​

  • AU public doctors (as of 2023) must prove CPD annually through an AMC-accredited CPD Home. PPP is the CPD Home.
  • Pre-2023, public doctors were assumed to be meeting requirements because day-to-day public hospital activities exceed yearly targets — but those activities were never verifiable.
  • Dual outcome: audit-ready external-activity verification plus automation of workplace interactions as verified CPD.

Required changes against current moreton-vs-uat screens ​

CPD Home Dashboard:

  • Remove the Timesheet reminder from the CPD Home dashboard — it belongs on PPP Dashboard or Action Items (Q1).
  • Fix CPD Hours reminder accuracy — current text adds "undue pressure" and is not aligned with the Governing Document.
  • Set-Up Wizard must only appear for CPD-Home-only users — currently shown to full-platform users where it's irrelevant.
  • Revert dashboard to Moreton Blue level of fidelity (number accuracy, category detail). Refinements to spacing are OK; data loss is not.
  • Confirm colour semantics for verified vs unverified activities, including how that's represented in the wheel numbers.
  • Ensure wheel and tiles are clickable — each should filter Activities to the selected category.
  • Restore the activity log (did it move to Activities tab, or was it dropped?).

Make a Plan:

  • Confirm "suggested plan" can be adopted as the user's plan with a single click.
  • Long-term: PPP should recommend next-year CPD distribution based on the user's prior-year actuals + PGY + speciality.

Activities:

  • Performance Review activity colour-coded (not grey — currently drift, should match other categories' colours).
  • Confirm unverified state styling — yellow pill or equivalent.
  • Remove redundant "notification" header when bell already shows a notification badge.

Add a CPD Activity:

  • Confirm "Create a CPD plan" button copy — should likely read "View your CPD Plan" and open the plan to pick a planned activity. Evaluate click cost.
  • Activities already present in the user's plan should float to top of dropdown.
  • Master-list activities must be clickable within the popup.
  • Auto-select category for activities that fit two categories (resolved 5 May): when the user picks an activity, PPP auto-selects the category. If the activity maps to a single category, that category is used. If it maps to multiple categories, the one with the fewest hours logged this year wins (deficit-driven, encourages a balanced plan). If two candidates are tied on hours, take the first in the activity's category list. The user can still change the auto-pick.
  • User must be able to change the category the system auto-picked.

Report:

  • Combined compliance metric for Measuring Outcomes + Review of Performance.
  • Confirm CPD Plan creation is evidenced on the report.
  • Program-Level Requirements — minimum 1 activity per category — should be listed (hours can still be shown).
  • Specialist high-level requirements per speciality must appear for consultant users (see existing Specialist High-Level Requirements section in this spec for the canonical list).

Automations ​

  • Rob task (@Rob tagged in brief): compile the spreadsheet mapping PPP platform interactions → CPD scoring. Requires Matt review.
  • Yearly check: PPP admin reminder to review speciality high-level requirements and update seed data; automate where possible.

Governing document ​

  • Latest submission: PPP_CPD_Home_Information_and_Policies_Updated_Nov_2025_v_4_(Kaneki_Edits_21.01.2026).docx (attached to Notion page). Any reminder copy, compliance metric, or category definition must match this document.
  • AMC has granted provisional approval; requests from AMC attached on Notion as they arrive.
CPD Reminders & Notifications ​

PPP automates four types of CPD reminder. All are clinical reminder types — they are suppressed for admin accounts and never shown to hospital/practice admins.

Tone policy (Governing Document): Reminder copy must be encouraging, not punitive. Doctors have demanding clinical workloads; reminders must acknowledge this and support behaviour change, not add administrative pressure.

1. CPD Plan Reminder (cpd_plan_reminder) ​

Fires once per year on 5 January for any user who has not yet created a CPD plan for the new year. This is the annual "you haven't started yet" nudge.

  • Triggered by: signup skip (cpdPlanSkippedAt set) → checkAndCreateCpdPlanNotificationsBatch called by admin on/after 5 Jan
  • Idempotency: unique DB constraint uq_notifications_cpd_plan_user_year (one per user per year)
  • Clears: automatically when the user creates their plan (cpdPlanReminderAt cleared)
  • Copy: "You haven't created your [year] CPD plan yet"
  • Code: api/backend-ppp/src/services/cpdPlanService/notification/index.ts

2. CPD Plan Submission Prompt (cpd_plan_submission_prompt) ​

Weekly escalating reminders for users whose plan is still in draft or not yet created. Tier is determined by month:

Month windowTierTone
Januarygentle"Create your CPD plan to stay on track"
February – Septembermoderate"You haven't created your plan yet" / "Plan is still in draft"
October – Decemberurgent"Please create/submit urgently to avoid non-compliance"
  • Triggered by: external scheduler (Azure Functions / EventBridge) calling processCpdPlanSubmissionReminders weekly
  • Idempotency: weekly key cpd_plan_submission:{userId}:{year}:W{isoWeek} — one per user per ISO week
  • Skips: users with submitted, approved, or locked plans
  • Code: api/backend-ppp/src/services/cpdPlanService/notification/submissionReminder.ts

3. CPD Deficit Prompt (cpd_deficit_prompt) ​

Fires when a user is behind their pro-rated target — i.e. they should have logged more hours by this point in the year than they actually have.

  • Formula: expected = annualTarget × (daysElapsed ÷ 365); fires when (expected − logged) > 10% of annualTarget
  • Cooldown: 7 days between notifications per user (prevents spam)
  • Triggered by: external scheduler calling processCpdDeficitNotifications daily/weekly
  • Idempotency: daily key cpd_deficit:{userId}:{year}:{dateStr} + 7-day cooldown window
  • Copy: "You're X points behind your CPD target — log an activity now"
  • Code: api/backend-ppp/src/services/scheduledNotificationService/processCpdDeficitNotifications.ts

4. CPD Milestone Achieved (cpd_milestone_achieved) ​

Positive reinforcement notification when a user crosses 25%, 50%, 75%, or 100% of their annual CPD target.

  • Fires once per milestone per plan year — never repeats for the same milestone
  • Idempotency: key cpd_milestone:{userId}:{planYear}:{pct}pct
  • Copy: "You've reached X% of your CPD target — Y/Z hours logged"
  • Triggered by: external scheduler calling processCpdMilestoneNotifications daily
  • Exposed via admin procedure: ppp.processCpdMilestoneNotifications
  • Code: api/backend-ppp/src/services/scheduledNotificationService/processCpdMilestoneNotifications.ts

Production wiring — NAS in-process scheduler ​

Superseded 2026-08-27 (#11819/#11836). The 4 CPD reminder jobs originally ran on Azure Container Apps Jobs, in the same Container Apps environment as the API container app. That mechanism went dormant when the Container Apps Environment was scaled to minReplicas=0 on 2026-08-09 as part of the NAS migration (ADR-0006) — the jobs simply stopped executing, silently, for 16+ days before #11819 caught it. Production scheduling for these 4 jobs now runs on the NAS's in-process node-cron scheduler, registered in api/backend-ppp/entrypoints/api-container.ts via the shared registerScheduledJob helper (api/backend-ppp/src/utils/scheduledJobRegistry.ts, #11835). Cron cadences are unchanged from the Azure Jobs; cadence source of truth also moved, from api/infra-azure/src/index.ts's cpdReminderJobSpecs to api/backend-ppp/src/services/notifications/scheduledNotificationService/cpdReminderSchedules.ts.

Job (cron const)Cron (UTC)Local time (AEDT)Calls
CPD_PLAN_REMINDER_TICK0 23 5 1 *Jan 6, 10:00checkAndCreateCpdPlanNotificationsBatch (annual)
CPD_SUBMISSION_PROMPT_TICK0 22 * * 0Mon 09:00processCpdPlanSubmissionReminders (weekly)
CPD_DEFICIT_TICK0 22 * * *Daily 09:00processCpdDeficitNotifications (daily)
CPD_MILESTONE_TICK0 22 * * *Daily 09:00processCpdMilestoneNotifications (daily)
CPD_AT_RISK_QUARTERLY_TICK0 22 1 1,4,7,10 *Quarterly, 09:00processCpdAtRiskNotifications (#11052)
CPD_DEADLINE_REMINDER_TICK0 22 * * *Daily 09:00processCpdDeadlineReminders (#11052)

The super-admin-amc-review job (annual, Feb 1) is tracked separately — see super-admin.md § AMC Yearly Review. It re-platformed onto the same NAS in-process scheduler in #11838, on the unchanged cron 0 22 1 2 *:

Job (cron const, api-container.ts)Cron (UTC)Local time (AEDT)Calls
amc-review0 22 1 2 *Feb 2, 09:00Creates a Super Admin todo to review the AMC CPD framework page (annual).

Why the NAS in-process scheduler now, having previously rejected node-cron for Azure:

The original rejection of node-cron ("would fan out across HPA replicas without a leader-election layer") was scoped to the Azure Container Apps deployment model, which auto-scaled the API container app across multiple HPA replicas — an in-process cron in that world means N replicas all firing the same tick, double- (or N-times-) sending every notification with no coordination. That premise does not hold on the NAS: ADR-0006's NAS deployment is a single Docker container with no horizontal auto-scaling, so there is exactly one process that could ever run the tick — the leader-election problem the original rejection was guarding against does not exist in this deployment shape. The reminder jobs' own scheduledKey idempotency (per-user/per-cycle, inside each processor) is unaffected by which mechanism calls it, and is what already protects against a double-send from any other cause (e.g. an overlapping retry).

  • Same process, image, and Managed Identity/secrets as the API — no separate deployment artifact (an even tighter version of the old Azure Jobs' "same image" argument, since there is no second container/job resource at all)
  • Failures land in the same log stream as the API (this repo's Log Analytics-equivalent for the NAS)
  • cpd_reminder_settings.enabled/threshold/template gate is read fresh on every tick (no per-invocation-only assumption), matching how it worked when a fresh CLI process re-read the row each Azure Job run
  • Azure Container Apps Jobs are dormant, not actively rejected as a mechanism in the abstract — see ADR-0006 for the full migration rationale (funding, not architecture, drove leaving Azure)

Super Admin reminder settings ​

The 6 jobs are scheduled by the NAS in-process scheduler (see above) but their enabled flag, message templates, and tunable thresholds live in a cpd_reminder_settings DB table that a Super Admin can edit from the Super Admin console. When a job's tick fires, it reads the current row for its reminder type and either skips (if disabled) or uses the live template/threshold for message copy.

Schema sketch (cpd_reminder_settings):

ColumnTypeNotes
idserial PK
reminder_typetextOne of cpd_plan_reminder, cpd_plan_submission_prompt, cpd_deficit_prompt, cpd_milestone_achieved (unique)
enabledbooleanMaster switch. If false, job exits without sending
message_templatetextMustache-style template (, , )
deficit_thresholdnumeric(deficit only) percentage of annual target before firing — default 0.10
cooldown_daysint(deficit only) min days between deficit notifications per user — default 7
updated_attimestamptzAuto-updated trigger
updated_by_user_idintFK → users.id; the Super Admin who last edited

The Super Admin UI is specified in super-admin.md § CPD Reminder Settings.

Regulatory Framework — Specialist High-Level Requirements ​

Source: RACS CPD Guide 2025

⚠️ Scope note (29 Apr): PPP is an AMC CPD Home, not a RACS-affiliated product. RACS-proprietary terminology (e.g. "CAPE") and RACS-specific targets (e.g. 65h consultant tier, RACS 10/40/15 split) must not appear in product surfaces or user-facing copy until a formal RACS agreement is in place. See cpd-home.md § Framework reference for the scope correction. The RACS CPD Guide is referenced here for HLSR technical data only (ANZASM membership list, surgical specialty groupings) — not as the governing compliance framework.

The RACS CPD Program defines three requirement tiers relevant to ANZASM eligibility: Category Requirements, Specialist High-Level Requirements (HLSR), and Cultural Safety / Ethics activities. For PPP's current AMC scope, only the HLSR (ANZASM participation) is implemented. Category and cultural safety requirements follow AMC rules, not RACS.

ANZASM — Surgical Specialties ​

From 2024, the Medical Board of Australia (MBA) mandates that all specialist surgeons (including all fields of specialty practice) must participate in the Australian and New Zealand Audit of Surgical Mortality (ANZASM) by completing all surgical case forms sent to the surgeon by ANZASM.

This applies to all RACS surgical specialties except Oral and Maxillofacial Surgery (which falls under a dental college).

RACS surgical group — PPP speciality mapping (Matt 27 Apr) ​

SpecialityIn ANZASM group?
Orthopaedic Surgery✅ Yes
General Surgery✅ Yes
Vascular Surgery✅ Yes
Cardiothoracic Surgery✅ Yes
Plastic and Reconstructive Surgery✅ Yes
Paediatric Surgery✅ Yes
Otolaryngology (ENT)✅ Yes
Urology✅ Yes
Neurosurgery✅ Yes
Ophthalmology✅ Yes
Obstetrics and Gynaecology❌ No — has its own HLSR list (AHPRA 2026)
Oral and Maxillofacial Surgery❌ No — explicit "excl. maxfac" exclusion (RACS CPD Guide 2025)

Implementation — codebase (29 Apr, #5600) ​

  • Specialty mapping constant — RACS_SURGICAL_NAMES (Set<string>) at api/backend-ppp/src/services/settingsServices/speciality.ts:99–113. Seeded into speciality.requirements JSONB via DB migration 0054. To be moved to packages-shared/ppp/src/constants.

  • ANZASM CPD activity types in instances/ppp/src/constants/cpd-activities.ts:237–264. These carry Kristin's published wording. #11105 briefly genericised them to Surgical mortality audit … under the 29 April RACS/CAPE ruling; Matt narrowed that ruling on the 2026-07-29 Dev Session call (#11025) to what PPP calls its own products and features (CAPE being the term he flagged), so college references in CPD activity titles are correct and the published spelling is restored across the in-app constant, the marketing copy, lookups.json and migration 0226. The speciality.requirements HLSR text names ANZASM too, and consistently so — no follow-up genericisation is needed.

    Activity typeCPD categoryHours/activity
    ANZASM surgical case formMeasuring Outcomes1
    ANZASM first line assessmentPerformance (Others)1
    ANZASM second line assessmentPerformance (Others)1
  • Tick logic — resolved (Matt, 29 Apr, GH #5600):

    • Surgeon must complete all ANZASM cases assigned to them (not ≥1)
    • Evidence is a yearly self-attestation upload (log / screenshot / CSV) of assigned + completed cases
    • Submission window: November only, rolling year — Jan→Nov evidence in year N requires Nov→Nov evidence in year N+1
    • Zero cases assigned ⇒ automatic ✅ (no upload required)
    • Future state: direct ANZASM API integration when available
    • DB shape: per-year anzasm_attestations row keyed (userId, year) capturing the uploaded evidence + admin-verified status
    • Tick is read-only on the dashboard (Evidence Integrity Rule); flips to ✅ when the year's attestation row exists and is admin-verified, OR when the surgeon's profile flag anzasmZeroAssigned[year] === true
  • CPDSpecialistAreas module (instances/ppp/src/modules/CPDSpecialistAreas/) — read-only reference table showing all HLSR requirements per specialty. Informational only; separate from the CPD Home tick.

Complete Specialist High-Level Requirements Map ​

SpecialtyHigh-Level Requirements
RACS Surgical Specialties (Cardiothoracic, General, Neurosurgery, Orthopaedic, Paediatric, Plastic, Urology, Vascular, ENT, Academic, Congenital Cardiothoracic)Participate in ANZASM by completing all surgical case forms sent to the surgeon by ANZASM
Maxillofacial Surgery(none — not a RACS specialty)
Anaesthetic SpecialistEmergency Response Activity; Clinical Audit or Structured Patient Survey or Multi-Source Feedback or Peer Review
Emergency Medicine SpecialistCore Airway Procedural Skill; Core Breathing Procedural Skill; Core Circulation Procedural Skill; one activity per year to reflect on and develop leadership skills contributing to workplace improvement, system-wide improvement and/or effective interdisciplinary teamwork (#11057)
General Practice SpecialistShow Completion of CPR course within last three years
Intensive Care SpecialistComplete an airway management of critically ill patients activity once every 3 years (min 3 hours, in-person practical workshop with CICO algorithms and simulation)
Obstetrics and Gynaecology SpecialistComplete an in-person Basic Life Support (BLS) program every two years
Pain SpecialistEmergency Response Activity; Clinical Audit or Structured Patient Survey or Multi-Source Feedback or Peer Review
Psychiatry SpecialistFormal Peer Review (10 Hours)
Radiology SpecialistShow Completion of Anaphylaxis Training as part of Basic or Advanced Life Support Training once every three years
Sport and Exercise Medicine SpecialistShow completion of WADA/Sport Integrity Australia anti-doping education every three years; Show Completion of one approved emergency care course within the last three years

Acceptance Criteria ​

CPD Dashboard ​

Moved (27 May). The CPD dashboard/home screen is owned by cpd-home.md § Core — dashboard compliance detail per the 23 Apr scope split ("CPD Home is the dashboard/home screen only … the CPD data model lives in cpd.md"). The category-colour mapping and combined Performance-Review tile ACs were migrated there; hours, layout/hierarchy and quick-add are already specified there. The small CPD progress widget on the PPP main dashboard (tap-to-open, refresh-on-mutation) is owned by dashboard.md. This section is a pointer so the same dashboard behaviour is not specified — and allowed to drift — in two places.

Annual target (Q6) ​

Anchors Matt's 29 Apr decision so future drift is caught by tests, not in production.

  • ✅ Annual CPD target is 50h universal for all userType values (consultant, non-consultant, registrar, etc.) — TOTAL_REQUIRED_HOURS = 50 in api/backend-ppp/src/services/dashboardService/cpd/index.ts
  • ✅ cpd.target.universal-50h — getCPDData returns the same breakdown[].requiredHours totals for any userType (regression test fixture covers consultant + non-consultant + registrar all returning 50h)
  • ✅ cpd.target.no-usertype-branch — there is no code path that reads userType to choose a CPD target value; an ESLint or static-analysis test asserts the absence of userType === adjacent to the target constant
  • ✅ cpd.target.no-racs-65h — repo-wide grep test fails the build if 65 appears as a CPD target value, or if CAPE / RACS-specific appears in any product surface or user-facing string (already covered by feedback_no_racs_cape_language policy; codify as a CI lint)
  • ✅ cpd.target.future-amc-extension — any future per-userType target arrives via the cpd_reminder_settings (or a sibling cpd_target_settings) Super-Admin-editable DB row, not via a code constant or a deploy. Documented migration path: add cpdTargetSettings table → expose via Super Admin console → constant becomes a fallback default
  • ✅ cpd.wheel.outer-ring-binds-50h — the dual-ring wheel's outer-ring boundary equals the universal 50h target on every userType (already implements this; codified as a Storybook/Playwright snapshot test gated to all 4 personas)

CPD Plans — lifecycle ​

  • ✅ Plan creation with annual target, categories, class breakdown
  • ✅ Status progression: draft → submitted → locked
  • ✅ Locked plans are read-only for the year
  • ✅ updateCpdPlan / deleteCpdPlan return FORBIDDEN on locked plans
  • ✅ lockCpdPlan is idempotent
  • ✅ Submit persists form state before locking
  • ✅ "Request change" writes cpd_plan_change_request audit-log row
  • ✅ cpd.lock.change-request-notifies-admin — change request fans out an in-app notification to every super admin
  • ✅ cpd.lock.admin-can-unlock-from-dashboard — super admin sees pending unlock requests in their dashboard and clicking Unlock reverts plan status locked → draft
  • ✅ cpd.lock.user-edits-and-resubmits — once unlocked, the user can edit the plan (mutation procedures no longer FORBIDDEN) and submit again
  • ✅ cpd.lock.auto-relock-on-resubmit — resubmitting an unlocked plan calls lockCpdPlan, returning status draft → locked and closing the change-request loop
  • ✅ cpd.plan.locked-after-entry — once a user has entered and submitted their CPD plan, the plan data is locked (read-only); users are not expected to return and modify it — it serves primarily as a compliance record. PPP Super Admin can unlock a locked plan on request (e.g. doctor changed specialty mid-year) via the change-request workflow. †
  • ⚠️ lockCpdPlan does not validate min-hours server-side
  • ✅ getCpdPlanForUserId rejects non-admin access to other users' plans
  • ✅ targetPoints preserves fractional hours
  • ⚠️ Bottom Submit in CPDActivityForm calls Save, not Lock — misleading

CPD Plans — status + UI ​

  • ✅ cpd.plan.typography-hierarchy — the CPD Plans page (/cpd-plans) renders a clear page → section → field typography hierarchy: the page title (<name>'s CPD Plan) at the h4 page-heading variant, all section headers (the category selectors, the High Level Specialist Requirements block, and "Program Level Requirements") sharing the subtitle1 variant stepped down from the title, and field/checkbox labels at body size. Sizes come from the shared TYPOGRAPHY_SCALE theme variants — no ad-hoc px. Previously every element rendered at a flat 16px (the title was the same size as a checkbox label), reading as out of proportion against other pages. † ‡ (#9146)
  • ✅ Awaiting Submission badge opens the plan
  • ✅ A plan counts as established (the "has a CPD plan" signal every surface shares, cpdPlanService/hasEstablishedPlan.ts) once it is no longer a draft. A plan saved as a draft is reported separately by hasDraftPlan so the CPD Home plan tile can read "Draft saved — awaiting submission" instead of "Not started"; a draft never counts as established. See cpd-home.md (#12603).
  • ✅ ?newPlan=1 on the CPD Plans page opens the plan editor, and only the plan editor — it is the target of the onboarding "Create your first CPD plan" step. The former ?add=1 deep link also opened the End-of-Year Reflection dialog (whose open-state uses the add param on this page), so it is no longer read for the editor. (#12549)
  • ✅ PDF certificate generated on completion; backend aggregation
  • ✅ cpd.certificate.issuance-requires-compliance — the CPD Statement of Completion is issued only when the member actually meets their CPD requirements, or holds an approved exemption/variation. The gate is the computed compliance predicate — PPP-verified hours met AND plan locked AND End-of-Year Reflection recorded — reusing the same rule the dashboard compliance tile derives from (deriveComplianceState, #5954). The member-ticked confirmEoy checkbox remains the statement of intent to close out the year but is NOT sufficient on its own. Hours are counted PPP-verified only, consistent with cpd.certificate.verified-only (#8770) — the dashboard tile's unverified-inclusive figure must not be used here, or the gate would admit a member the certificate face then renders as short of target. A refusal names the shortfall and the verified hours actually recorded, and points the member at requesting an exemption or variation. Both issuance paths are gated: the plan-completion trigger and the PDF-generation aggregation, which is separately reachable. The approved-exemption branch is not yet operable — compliance_form_submissions records an exemption request with no decision, approver, or year column and is never read anywhere in the product, so no approved-exemption state exists to consult; that dependency is stated rather than assumed. † ‡ (#11035)
    • ✅ AC4 resolved (#11264) — confirmed by Rob (2026-08-27): this artefact IS the policy's "CPD Statement of Completion". Terminology reconciled across the certificate title (certificateGenerationTrigger.ts, CpdCertificateDialog.tsx, CpdCertificatePreview.tsx, generateCertificatePdf.ts) and this spec so the policy and the product use one term. †
    • ⏳ Open (AC5) — audit how many already-issued certificates went to non-compliant members. Report the number; do not revoke without a decision.
  • ✅ 7-day dashboard nudge when plan not started; onboarding must not force immediate plan entry — users can defer and return later †
  • ✅ Notification icon on CPD Home menu when plan is due
  • ✅ Suggested plan wording does not use "fixed" — the UI copy must not state "fixed 15 hours" as values are adjustable †
  • ✅ cpd.plan.suggested-plan.atomic-replace — adopting a suggested plan auto-populates and replaces the draft plan atomically; no manual re-entry required; never merged per-row † (5 May)
  • ✅ cpd.plan.suggested-plan.single-per-user — only one suggested plan is shown per user per year; suggestions are pre-configured by profession/specialty so the user can review and modify before adopting † (5 May)
  • ✅ cpd.plan.suggested-plan.header-copy — the Suggested CPD Plan dialog renders the prompt "…here are AI-suggested activities for your CPD plan. Click Use this plan to add them all — you can edit or remove any activity on the plan before saving." above the list. Supersedes (Rob, 27 May) the earlier "Select desired suggestions…" copy — there is no per-activity selection (see cpd.plan.suggested-plan.adopt-all). † (27 May)
  • ✅ cpd.plan.suggested-plan.adopt-all — "Use this plan" adopts all suggested activities; there is no per-activity selection in the dialog (the cards are read-only/informational). The user edits or removes activities on the pre-filled plan before saving. The dialog lays the suggestions out as a responsive 2-column grid so it fits without scrolling. At sign-up the action merges into the doctor's manual picks rather than replacing them (#12766). † (27 May)
  • ✅ cpd.plan.suggested-plan.shows-underlying-activity — each suggestion card shows the master activity it logs as ("Logs as: …") when that differs from the friendly card title, so the plan's activity name is no surprise after "Use this plan". † (27 May)
  • ✅ cpd.plan.suggested-plan.role-correct-copy — the Suggested CPD Plan dialog's role-labelled copy only asserts the user's grade ("Based on your role as a Consultant / Non-Consultant") when the role is known, resolving it case-insensitively. When the role is missing or unresolved (e.g. the not-logged-in onboarding flow, ?from=onboarding, where user is undefined) the dialog drops the role label and shows neutral copy instead — a non-consultant is never shown "Consultant" describing their own role. The query still falls back to the non-consultant suggestion template when the role is unknown. † ‡ (#8938)
  • ✅ cpd.plan.suggested-plan.populates-every-category — "Use this plan" pre-fills every suggested category, including Measuring Outcomes, Review of Performance and Education — no suggested category is left blank. Both flows resolve identically: the no-plan path pre-fills the form and the plan-exists path adopts atomically, and both derive their activities from the same mapSuggestionsToFormValues mapper, which resolves each suggestion by id (falling back to name) and unions the target category group into selectedCategories so an activity whose master record lives only under another category (e.g. an "outcomes" suggestion whose activity is a DB member of "Review of Performance" only) still counts toward its intended category. † ‡ (27 May)
  • ✅ cpd.plan.suggested-plan.meets-category-minimums — the suggested-plan templates allocate hours that satisfy every AHPRA category minimum, so an adopted suggested plan can validate as complete with no "hours remaining" deficit. In particular Measuring Outcomes (MO) + Reviewing Performance (RP) combined ≥ 25h (the insert-schema.ts superRefine computes required = 25 - (MO + RP)), Education ≥ 12.5h, and the grand total ≥ 50h (the AHPRA minimum — the invariant is a floor, not an exact 50). The previous consultant and non-consultant templates allocated MO=10 + RP=10 = 20h (a built-in 5h MO+RP shortfall) while over-parking 30h in Education; autopopulate maps each suggestion to exactly one category group, so the Education surplus could never spill into MO/RP. Rebalanced to MO=13 + RP=12 = 25h (combined ✓). Each targetPoints value is now the genuine CPD-hour contribution of completing that activity, not a number fudged to force an exact 50h total (#9140) — an hours-unit activity counts 1:1 (e.g. "15 hours of supervised surgery" = 15 CPD hours). #9140 briefly un-capped supervision to 25h, which pushed the consultant template to a 60h overshoot (Education=35h). #9190 recalibrates the consultant template back to the 50h floor by suggesting fewer supervision hours — 15h, still an honest 1:1 figure, NOT a re-introduction of the old "claim 25 / count 15" fudge. The consultant template now lands at Supervision 15 (Education) + Clinical Audit 13 (MO) + Feedback 12 (RP) + Meetings 10 (Education) = MO=13, RP=12 (combined 25h ✓), Education=25h (15 + 10, ≥12.5 ✓), grand total 50h (the AHPRA floor). The Suggested-CPD-Plan card surfaces targetPoints as the CPD-hour chip so the number shown == the number "Use this plan" applies. The consultant MO suggestion is now a genuine Measuring-Outcomes activity (#9190). The earlier MO-categorised suggestion ("Assess Workplace-Based Assessments" → master activity "Peer review of cases / charts with feedback") was clinically a Reviewing-Performance activity tagged outcomes only to fill the MO minimum. Per the AMC CPD framework — Measuring Outcomes = clinical audit / review of patient-outcome data / M&M review — and this spec's HLSR map (which names "Clinical Audit … or Peer Review" as the canonical MO option), the consultant MO suggestion is now "Clinical Audit of Your Outcomes" → master activity "Clinical Unit Audit", a pure clinical-audit record that is a member of Measuring Outcomes only (measuring='x', all other categories blank in the master list) and is already seeded into cpd_activities_list. It is named in non-RACS terms, so it carries no MALT licensing dependency (#1740). The 13h MO allocation is unchanged from #8934 (an engineering default for the per-bucket split), now backed by a real audit activity rather than a mis-tagged peer-review one. † † † ‡ (#8934, #9140, #9190)
  • ✅ cpd.plan.suggested-plan.hidden-when-plan-exists — Suggested-plan entry-point is suppressed when the current-year plan already exists; the "suggested plan" button disappears if a user already has a plan †; mirror in cpd-home.md (5 May)
  • ✅ cpd.plan.suggested-plan.canonical-plr-labels — the plan-suggestions welcome banner lists the four Program-Level Requirements in canonical wording, resolved from the shared PLR_CANONICAL_NAMES so it matches the CPD Home ticks; governed by cpd-home.md (cpd.home.plr.canonical-label-consistency). † ‡ (#7647)
  • ✅ cpd.activity.plr-claim-field-label — the per-activity PLR claims checkbox on the CPD Activity Form (instances/ppp/src/forms/ManualCPDForm/**, jointly governed with cpd-activities.md cpd.activity.plr-claim-field-label) reads "Does this activity address any Program-Level Requirements?", without an "(optional)" suffix — the field itself stays optional at the per-activity level, but annual PLR coverage is now a required compliance condition (cpd.home.compliance.plr-required-for-verdict in cpd-home.md), so "(optional)" no longer read correctly. This AC records the ownership overlap between cpd.md and cpd-activities.md's code-paths for ManualCPDForm/**; the detailed rationale and code citation live on the cpd-activities.md AC of the same id. (2026-08-23) (#11046) †
  • ✅ cpd.activity.points-server-side-bounds — the points field on a CPD user activity is server-side bounded to 0 <= points <= 1000 on every write path in api/backend-ppp/src/routers/procedures/cpd/cpdUserActivities/** (jointly governed with cpd-activities.md cpd.activity.points-server-side-bounds, which is the detailed AC and code citation — this entry records the cpd.md/cpd-activities.md code-paths overlap for that router). (2026-09-21) (#12361)
  • ✅ cpd.plan.suggested-plan.save-surfaces-all-attestations — On the first Save of an adopted suggested plan, all missing required attestations are surfaced together in one pass — both the program-level acknowledgement checkboxes AND the End-of-Year-Reflection (confirmEoy) checkbox — with a single scroll-to-first-error (walking the visual FIELD_ORDER) and a single warning toast. The user reaches a saveable state in one correction cycle; no second/third Save is needed to reveal the next required item. CPDActivityForm.handleSubmit computes the external program-class check and the zod resolver in the same pass (no early return short-circuiting before the resolver runs) and merges the manual cpdClassIds error into the resolver's error map, so both error sets render at once. The program-class check matches cpd_classes rows to REQUIRED_PROGRAM_CLASSES by name via matchesRequiredProgramClass, which tolerates the pre-#12150 seeded PLR wording alongside the corrected canonical names — the matching cpd_classes DB rename was deferred (#12181), so without this tolerance two of the four PLRs could never be satisfied on this path regardless of what the user ticked (#12209). #12222 shipped the deferred rename as migration 0246_cpd_classes_plr_wording_correction (data-only, guarded, with a first-apply-only validator); the tolerance itself is retained for the deploy window before a given environment has applied it — prod is a manual workflow_dispatch — and its removal is tracked by #12236. † † ‡ (#9159, #12209)
  • ✅ cpd.plan.suggest.brand-colour — the "Suggest a Plan" button uses the PPP brand primary fill (theme palette tokens, no inline hex), matching the other primary CTAs — not the off-brand secondary cyan it previously used † (27 May)
  • ✅ cpd.plan.suggest.semantic-button — the "Suggest a Plan" control is a real semantic MUI <Button> (renders a <button>) reachable by getByRole('button', { name: /Suggest a Plan/i }) and operable by keyboard; it carries no aria-label override, so the visible label is its accessible name † ‡ (#7773)
  • 🅼 cpd.plan.personalised-recommendation.deferred — personalised AI/rules-based CPD plan recommendation engine is deferred; current implementation offers templated suggestions only. (closed — future exploration)
  • ✅ cpd.plan.view-button-removed — the read-only CPD Plans screen no longer renders a "View your CPD Plan" button. It duplicated the Edit button (both toggled setReadOnly) and revealed nothing new — the plan summary is already fully visible in read-only mode. Editing is reached via Edit only. † (27 May)
  • ✅ cpd.plan.reset.current-year-only — a Reset button is shown when a plan exists for the current year and is not yet submitted/locked; it is never shown for past years or submitted plans † (27 May)
  • ✅ cpd.plan.reset.confirm-before-delete — clicking Reset opens a confirmation dialog ("This permanently deletes the plan and cannot be undone") with Cancel / Reset Plan actions; no deletion occurs without explicit confirmation † (27 May)
  • ✅ cpd.plan.reset.deletes-and-restores-suggest — confirming Reset calls cpdPlan.resetCpdPlan (deletes the plan via deleteCpdPlan); the page returns to the no-plan state so the "Suggest a Plan" entry-point reappears and the user can start again † (27 May)
  • ✅ cpd.plan.reset.blocked-when-locked — resetCpdPlan enforces caller ownership and reuses assertPlanIsMutable, so a locked/submitted plan cannot be reset (returns FORBIDDEN); locked plans must use the change-request workflow instead † (27 May)
  • ✅ cpd.plan.save.returns-to-dashboard — saving an edited CPD plan that succeeds returns the user to the CPD feature home (/cpd-dashboard), mirroring the create flow (MakeCpdPlan already navigates there on success). The edit form previously only flipped to read-only and left the user parked on the plan page. † ‡ (#8936)
  • ✅ cpd.plan.guidance.single-master-list-button — the read-only CPD Plans header renders a single "Activities Master List" button, not the previous two ("Activity Master List" + "Specialist Areas"). Both old buttons opened the same GuidanceModal, differing only by which tab was preselected; the modal already exposes both as in-dialog tabs ("CPD Activities List" / "Specialist High-Level Requirements"), so the second button was a redundant entry point. The merged button opens the modal on the activities tab and the user switches to Specialist via the existing tab — no data or behaviour change, pure entry-point consolidation. This also trims one button from the header's mobile button stack. The CPD Activities page (/cpd-activities) header opens this same modal via its own "Activities Master List" button (#12743, see cpd.activity.master-list-from-activities-tab in cpd-activities.md). † ‡ (#8937)
  • ✅ cpd.plan.header.actions-packed-on-mobile — the read-only CPD Plans header packs its action buttons into a 2-column grid on mobile (xs) instead of a column of full-width buttons, so the header no longer dominates the viewport when 5–6 actions are present; sm+ keeps the inline wrapped row. † ‡ (#8937)
  • ✅ Activity-selection search with clear + empty state
  • ✅ Cancel button resets edits and calls parent onCancel; wire on CPDPlans
  • ✅ Plan section labels use "hours of Y required"
  • ✅ CPD Activities pagination counter accurate
  • ✅ Category-required validation suppressed while field disabled

End-of-Year Reflection ​

  • ✅ Availability window Nov 15 – Dec 31 enforced server-side
  • ✅ cpd.plan.eoy-button.hidden-until-available — on the CPD Plans page the EOY Reflection button is not rendered until the reflection window is open, unless a reflection already exists to view. It no longer shows a disabled "(available from Nov 15)" button the rest of the year, which only wasted toolbar space. Mirrors cpd-home. † (27 May)
  • ✅ cpd.plan.eoy-section.hidden-when-empty — on the CPD Plans page the "CPD End of Year Reflections" section (header + table) is not rendered while the user has no reflection rows. Reflections can only be filed inside the Nov/Dec window, so for most of the year the section was a header plus an empty box consuming vertical space (especially on mobile). The section appears as soon as there is at least one reflection to show; hiding is reversible (restore the <EmptyRows/> empty-state branch). † ‡ (#8939)
  • ✅ cpd.plan.reflection.december-for-hlsr — for a doctor whose specialty carries HLSR requirements, the Annual Reflection window opens 1 December (Dec 1 – Dec 31 of the plan year) instead of 15 November, so the reflection aligns with the HLSR verification window (cpd.home.hlsr.december-window, opens December #8728/#8730) — the reflection prompt must not let an HLSR user "complete" their year while their HLSR verification is still outstanding. Non-HLSR doctors are unchanged, keeping the Nov 15 – Dec 31 window. The selector isWithinReflectionWindow(hasHlsrRequirements, planYear, currentDate) routes HLSR users to isWithinHlsrReflectionWindow (Dec 1 start) and everyone else to isWithinEoyReflectionWindow (Nov 15 start); past plan years stay always-available and future plan years stay locked for both. The client EOY-button gate and the server createCpdEndOfYearReflection enforcement both read this shared selector so they cannot drift (#5005 invariant). HLSR users see a December-dated out-of-window message rather than the Nov 15 copy. † (#8735) (#8715) ‡
  • ✅ DEV_BYPASS_EOY_DATE gated on import.meta.env.DEV, stripped in prod
  • ⚠️ Plan lock does not block updates to linked EOY reflection
  • ⚠️ EOY JSONB accepts any key/value — no structural validation
  • ✅ DEV_BYPASS_EOY_DATE security scenario + step defs (the flag is gated on import.meta.env.DEV and tree-shaken from prod) ‡
  • ✅ The EOY Reflection modal keys its existing-reflection lookup and default "CPD Year" off the plan year it was opened from, not today's real-world year — opening the dialog from a past, locked plan no longer pre-fills (or risks persisting, on Add) the current year's reflection instead of that plan's own. (#12658; code:instances/ppp/src/modules/cpd/plans/components/EOYReflectionButton.tsx)
  • ✅ The EOY Reflection button's label/visibility ("View EOY Reflection" vs "EOY Reflection") is derived from the same plan-year-scoped reflection lookup the click handler uses, not the account-wide user.hasCpdAnnualReflection flag — a doctor with a reflection for one year no longer sees "View" on every other year while the click itself (correctly, since #12658) routes to Add. (#12665; code:instances/ppp/src/modules/cpd/plans/components/EOYReflectionButton.tsx)

CPD Activities ​

Moved (27 May) to its own spec/page: cpd-activities.md. The cpd.activity.* / cpd.activities.* / cpd.categories.* acceptance criteria — including multi-user supervisory credit and the activities-list default filter — now live there. (23 Aug update) cpd.activity.plr-claim-field-label (the per-activity PLR checkbox's "(optional)" wording removal, #11046) also lives there, alongside cpd.home.compliance.plr-required-for-verdict in cpd-home.md — PLR coverage is now a required condition of the annual compliance verdict, not advisory.

  • Meeting-credited activities show the meeting title in the Activities table name column (description fallback) — see cpd.activity.meeting-credit-shows-title in cpd-activities.md (#12462).

CPD Providers ​

  • ✅ New provider requests de-duped by email — match is case-insensitive and whitespace-trimmed; a request whose email matches an existing provider resolves to that provider with no duplicate row
  • ✅ Genuinely-new providers enter pendingApproval before verification email; new provider email must be vetted by PPP super admin before the verification email is deployed †
    • ✅ cpd.provider-vetting.pending-status — new (non-deduped) provider created with status pendingApproval; verification email is not sent at this point
    • ✅ cpd.provider-vetting.dedup-bypass — if submitted provider email matches an existing provider, skip vetting and proceed with the existing verification email flow
    • ✅ cpd.provider-vetting.superadmin-queue — Super Admin sees a pending-provider queue (extend the merge-providers screen #4823 or standalone); each entry shows provider name, email, submitting user, and submitted date
    • ✅ cpd.provider-vetting.approve — Super Admin approves a pending provider → status set to approved, verification email sent to provider
    • ✅ cpd.provider-vetting.reject — Super Admin rejects a pending provider with a reason → status set to rejected, submitting user notified in-app with the rejection reason
    • ✅ cpd.provider-vetting.audit-log — every approve / reject decision writes an immutable audit-log row (admin user, action, reason, timestamp)
  • ✅ cpd.admin.merge-duplicate-providers — super admin has dedicated screens for merging duplicate CPD providers; the merge UI is separate from the provider-vetting queue. Required for launch; NOT required for the 28 May 2026 demo. †
  • ✅ Audit log entry for every approve / reject / merge — each writes an audit_trail row capturing actor, action, provider id(s) and timestamp; the merge entry records both source and target provider ids
  • ✅ CPD approval email shows recipient name + allocated hours
  • ✅ cpd.provider-approval.token-consumption-audit-and-notify — every approval-token consumption writes a cpd_approve_token_consumed audit row (with IP + user-agent) and sends a confirmation email to the doctor with a "this wasn't me" support link. Default token TTL is 14 days (token-helper.ts; corrected 5 Oct 2026 — earlier text said 7 days, the BDD scenarios in cpd-provider-approval.feature pin the current value).
  • ✅ cpd.provider-approval.approver-identity — the approver's typed full name (remembered per provider email) is required on the provider approval page, and the token-consumption / decline audit rows record the approving person as an external actor (name, email, IP, browser, time). See cpd-activities.md. † (#12530)
  • ✅ cpd.provider-approval.master-list-link-semantics — "Open Activity Master List" rendered as MUI Link (component="button"), keyboard-focusable with visible focus ring, announced as a button by screen readers
  • ✅ cpd.provider-approval.evidence-proxy-route — emailed evidence links go through /cpd-evidence/:activityId/:token; the backend re-verifies the HMAC token, audit-logs the download, and returns a fresh 5-minute SAS. ‡
  • ✅ cpd.provider-approval.evidence-sas-ttl — superseded by evidence-proxy-route above: instead of a 24h SAS, the proxy issues a fresh 5-minute SAS per authenticated download (shorter exposure window). ‡
  • ✅ cpd.provider.verification.audit-log — on successful approval-token consumption, an immutable cpd_provider_verifications row is written capturing { providerId, activityId, verifierEmail, verifiedAt, ipAddress }; supports audit queries by provider / date range from Super Admin
  • ✅ cpd.provider.verification.audit-superadmin-view — Super Admin can list and filter provider verification events via trpc.ppp.superAdmin.providerVerifications.list (filterable by providerId, fromDate, toDate; paginated, newest-first)
  • ✅ cpd.provider.approved-list.add-on-verify — on successful token consumption, cpd_activity_providers.is_approved is set to true in the same DB transaction that writes the audit row; idempotent (no-op if already true)
  • ✅ cpd.provider.approved-list.reuse-on-submit — the CPD activity form exposes an "approved authorizers" dropdown (trpc.ppp.cpdUserActivities.getApprovedAuthorizers) populated with providers already verified for the current user; selecting one skips re-verification
  • ✅ cpd.provider-approval.token-issuance-audit — when a verification email is sent to a provider, an immutable audit row is written capturing { activityId, providerId, issuedAt, issuedByUserId, tokenHash }. Complements cpd_approve_token_consumed which covers consumption; together they form a complete token lifecycle audit trail.
  • ✅ cpd.unverified-hours.certificate-verified-only — the formal CPD certificate counts PPP-verified hours only; provider-replied (unverified) hours are excluded until a PPP super-admin completes stage-2 verification. The certificate is regulatory evidence, so only hours that have cleared PPP verification belong on it. ‡ † (#8770)
  • ✅ cpd.unverified-hours.progress-surfaces-include — the in-app progress surfaces — the to-do / checklist CPD gap and the roadmap milestone cadence — credit verified + provider-replied (unverified) hours. Once the provider has replied, the hours/assessments count toward the doctor's personal progress immediately even though PPP stage-2 verification is still pending. This deliberately diverges from the formal certificate (verified-only above). pending hours are never credited on any surface. ‡ † (#8770)
  • ✅ cpd.provider.evidence.authenticated-only — evidence-file URLs must never be publicly guessable blob URLs; all evidence and review links require authentication; unauthenticated access is blocked †. All evidence downloads must go through an authenticated backend route (/cpd-evidence/:activityId/:token) that validates session or HMAC token before streaming the file. Unauthenticated access returns 401. Implemented in #5772 — HMAC token validated, 5-min SAS TTL, download audit-logged. (Security — 6 May 2026) (closed — already done)
  • ✅ cpd.provider.notification-email.branding — the provider notification email (api/backend-ppp/src/utils/email/templates/cpd-approval.ts) needs significant improvement to explain who PPP is and what the provider's purpose is †; includes: (a) a plain-language explanation of PPP and its AMC CPD Home accreditation in the email body intro; (b) the purpose of the provider verification role and why they are being contacted; (c) a footer with the PPP logo and a text-only "Verify our accreditation" link to the AMC website. The PPP provider accreditation badge slot (EMAIL_ASSETS.amcBadge) is implemented and gated behind EMAIL_AMC_BADGE_ENABLED env var — it gracefully degrades to the text link until the badge PNG is supplied. AMC confirmed (18 May 2026) they do not issue badges; PPP will create its own provider accreditation badge — design tracked in #6167, engineering wiring in #6281. (6 May 2026) (closed —)
  • ✅ cpd.provider.notification-email.amc-link — provider notification email footer contains a branded footer with branding and a live hyperlink to verify the company's AMC accreditation; links to PPP's listing on the AMC accredited CPD Homes page (https://www.amc.org.au/accredited-organisations/cpd-homes/#:~:text=Professional%20Performance%20Portfolio) †. URL stored as amc_cpd_home_url in system_settings (Super Admin-editable, no-deploy updates). AMC URL confirmed in #6000 (18 May 2026). (6 May 2026)
  • ✅ cpd.provider.link-lifecycle.superadmin-view — Super Admin has a view (within the provider-vetting queue or a dedicated tab) showing per-provider: links sent count, links consumed count, links expired count, last-sent timestamp, ability to trigger re-send; users self-serve link regeneration via an expiry prompt rather than requiring super admin follow-up †. Backend aggregation + re-send mutation (api/backend-ppp/src/services/providerLinkLifecycleService/index.ts) and the Super Admin table (instances/ppp/src/modules/Admin/CpdProviderLinkLifecycle/index.tsx) delivered in #5978/#6145; #6375 wired the view into the provider-vetting queue (PendingProviders → "Link lifecycle" action, with a back-link the other way) so it lives within the vetting workflow as specified. (6 May 2026) (closed ——)
  • ✅ cpd.provider.logo.asset-management — the cpd_activity_providers table has no logo field (net-new). Add logo_file_key varchar(512) column; Super Admin provider create/edit form includes a blob upload; file key stored (not a URL); logo URL resolved at read time via fetchFileUrl; external URLs rejected at Zod validation layer. Requires DB migration + validate.sql. (6 May 2026)
  • ✅ cpd.provider.light-email-same-security — all email contacts, including "light" email variants sent to providers, must carry the same security controls and time-expiring links as standard verification emails; no email variant bypasses the authentication or expiry requirements †. Verified by code audit (2026-05-20): every provider-bound email path routes through generateApprovalToken (HMAC-SHA256, 14-day TTL via CPD_APPROVAL_TOKEN_TTL_DAYS, single-use enforced by approval_token_consumed_at). Audited paths: (1) initial submission email — cpdUserActivities/index.ts sendProviderApprovalEmail, (2) super-admin bulk re-send — cpdProviderVettingService/index.ts, (3) per-provider lifecycle reminder — providerLinkLifecycleService/index.ts, (4) doctor-triggered regenerate-expired — cpdUserActivities/regenerateCpdApprovalEmail.ts → resendCpdProviderApprovalEmail. No "light" provider email bypasses HMAC verification or TTL. Confirmation emails sent to the doctor (recordTokenConsumption.ts) carry no token because they contain no actionable verification link. (6 May 2026)

Specialist High-Level Requirements ​

  • ✅ Supervised training hours requirement confirmed at 15 hours — the full 15h allocation must be reflected in the HLSR requirement data, not a reduced figure †
  • ✅ RACS surgical specialties show ANZASM requirement
  • ✅ HLR selector hidden for non-specialists
  • ✅ Non-surgical specialties show their own requirements
  • ✅ cpd.plan.hlsr.generic-heading-speciality-subtext — on the CPD Plans page (/cpd-plans) the specialist block is headed with the canonical generic heading "High Level Specialist Requirements" (the CPD_PLAN_HLSR_HEADING constant) and the doctor's speciality (e.g. "Orthopaedic Surgery") is shown as subtext beneath, rather than baking the speciality into the heading ("Orthopaedic Surgery Requirements"). The block also renders as a tile within the CPD activity category grid rather than a full-width strip below it. Non-surgical specialities that carry an explicit requirements.label still render their items correctly; the subtext is the bare speciality name in all cases. This is the plans-page presentation only — CPD Home's HLSR block (resolveHlsrHeading) is unchanged. Supersedes (Matt, Dev Session 2026-06-23) the earlier Q8 resolution that derived the tile label from speciality.requirements.label else "<specialty> Requirements" for this block. † ‡ (#9145)
  • ✅ Requirements stored in speciality.requirements JSONB
  • ✅ Specialty hierarchy drives auto-distribution
  • ✅ BDD step defs for @requires-backend specialist scenarios
  • ✅ Deleted unused useIsSpecialist hook in favour of requirements-driven gating

CPD Report ​

Moved (27 May) to its own spec/page: cpd-report.md. The cpd.report.* / cpd.pdf.* / cpd.export.* acceptance criteria now live there.

CPD Reminders & Notifications ​

  • ✅ cpd_plan_reminder fires on 5 January for users without a plan — once per year, idempotent
  • ✅ cpd_plan_submission_prompt escalates weekly (gentle → moderate → urgent) based on month, skips submitted/locked plans
  • ✅ cpd_deficit_prompt fires when logged hours fall >10% behind pro-rated target, 7-day cooldown between notifications
  • ✅ cpd_milestone_achieved fires once per milestone (25/50/75/100%) per plan year — positive reinforcement
  • ✅ All four types are suppressed for admin accounts (CLINICAL_REMINDER_TYPES filter)
  • ✅ Reminder copy does not add undue pressure — matches tone policy in Governing Document
  • ✅ Azure Container Apps Jobs wired to call submission, deficit, and milestone batch functions on schedule in production (Q4)
  • ✅ Notification icon on CPD Home menu when plan is due for submission

APHRA Escalation (end-of-year, Super Admin) ​

PPP is the AMC-accredited CPD Home and is therefore responsible for notifying APHRA when a doctor fails to meet the annual 50h requirement. Confirmed by Matt (~22 Apr 2026): notifications are human-initiated by PPP Super Admins, not automated.

🅼 Manual fallback (deferred 6 May 2026). Reporting and CPD engagement take priority over APHRA alerting (Matt's call). APHRA escalation only fires once a year, end of cycle, and at current volume a Super Admin can hand-draft a one-off email to performanceframework@ahpra.gov.au if/when the situation arises. Templated infrastructure already shipped (DB table cpd_aphra_settings + tRPC ppp.superAdmin.cpdAphraSettings.{get,update} — see) and remains dormant. Reactivate when volume justifies it; legal sign-off (closed #5710) must be reopened before any production use.

  • ✅ Super Admin breach-list screen: all active users with logged hours < 50h as of 1 December, with deficit, plan status, last activity date, notification status
  • ✅ "Send APHRA notification" action per row + bulk — records notifiedAt, notifiedBy, hoursAtNotification
  • ✅ In-app notification to user when notified
  • ✅ cpd_aphra_notifications DB table (or equivalent record)
  • ✅ APHRA submission copy templates stored in DB (cpd_aphra_settings, draft only, dormant)
  • 🅼 Legal sign-off on production use of those templates — deferred (closed 6 May); manual hand-drafted email is the fallback until volume justifies reactivation
  • ⏳ APHRA API integration — out of scope until AMC provides an API
  • ✅ cpd.aphra.pre-notification-doctor-contact — before PPP sends a breach notification to the regulatory body, the Super Admin workflow enforces a mandatory pre-notification contact step: (1) an in-app notification + PPP-branded email is sent to the doctor using the PPP email template; (2) the email informs the doctor of: their personal obligations to the regulatory body (AHPRA for AU; alternate configured body for UK), the CPD provider's obligation to notify the regulatory body of non-compliance, and the 14-day window to rectify their CPD position; (3) the email includes a standard login link to the PPP app (not a magic link — doctor logs in normally to correct their CPD record); (4) the regulatory body is jurisdiction-aware — derived from the user's country profile field (AU = AHPRA, UK = configurable alternate body); (5) the contact attempt is logged with timestamp and actor; (6) Super Admin cannot proceed to the regulatory notification step until the 14-day window has elapsed — the workflow enforces this gate. Matt to confirm email body wording and jurisdiction mapping before finalising template. (22 Apr 2026)
  • ✅ cpd.aphra.policy-doc-copy — the breach-list screen displays a jurisdiction-aware link to the applicable CPD non-compliance policy document: AU = Medical Board of Australia CPD Registration Standard (https://www.medicalboard.gov.au/Professional-Performance-Framework/CPD.aspx); UK = configurable alternate body URL stored in Super Admin system settings. The AU URL is hardcoded (it is a stable government page); the UK URL is stored as a new regulatoryBodyPolicyUrl column in system_settings (requires DB migration). The link is displayed as a contextual info banner on the breach-list screen so admins can review their obligations before sending. (22 Apr 2026)
  • ✅ cpd.aphra.notification-template — the cpd_aphra_settings table (packages-shared/ppp/src/schema-groups/cpdAphraSettings.ts) currently uses a simple isDraft boolean (default true) with no approval audit trail. This AC adds: (1) a legalApprovalStatus pgEnum (pending | approved | rejected) column; (2) legalApprovedByUserId and legalApprovedAt columns tracking who gave legal sign-off; (3) a mattApprovedAt / mattApprovedByUserId column for Matt's sign-off; (4) the AHPRA notification workflow is gated — both legal approval AND Matt sign-off must be recorded before isDraft can be cleared to false; (5) Super Admin settings screen surfaces the current approval status and allows the appropriate user to record approvals. Requires DB migration + validate.sql. (22 Apr 2026)
  • ✅ platform.email-links.time-expiring — all magic-link tokens sent via email must be time-limited and single-use; users are informed of the validity period and can regenerate expired links †. Implemented: every emailed magic link carries a finite TTL — CPD provider verification 14 days (CPD_APPROVAL_TOKEN_TTL_DAYS, default 14, #5778), timesheet batch 14 days, 360 review 30 days, admin break-glass reset + signup welcome 24h (magicLinkTtl.ts central policy: env > DB system_settings > 24h default, #5972). Single-use is enforced: HMAC token verification rejects expired/tampered tokens; the CPD provider verification flow atomically stamps approval_token_consumed_at with an isNull guard so a replayed link returns the idempotent "Already Approved" page rather than re-processing; better-auth deletes the reset/signup verification value on successful POST. The CPD provider verification email and the timesheet batch approval email both state the link is single-use and the explicit validity window, and tell the recipient an expired link can be regenerated (timesheet self-serve from the link-expired page; CPD via Super Admin re-send, #6145, plus per-provider link-lifecycle counts #5978).the residual gap: the timesheet approval email now states its 14-day validity period and regeneration path explicitly (previously generic "will expire for security reasons" copy). (6 May 2026)

CPD Records Retention Lifecycle ​

  • ⏳ cpd.retention.archive-dispose — the published "Management, Access and Privacy of Practitioners' CPD Records Policy July 2026" §5/§8 commits to: CPD records archived after 1 year, disposed of after 3 years, a 90-day advance notice before each, a post-disposal notice, and a user-facing "retain for longer" option. This AC covers the archive/dispose job only (#11727, story child of #11037): a daily scheduled job (api/backend-ppp/src/services/cpd/retentionService/archiveDisposeJob.ts, registered via registerMaintenanceJob in entrypoints/api-container.ts) sets archivedAt on cpd_user_activities/cpd_end_of_year rows past the configurable archive cutoff (instance_config.cpd_archive_after_years, default 1) and hard-deletes rows past the purge cutoff (cpd_purge_after_years, default 3). AC4 — what "disposal" actually guarantees: an ordinary Postgres DELETE, so the row is immediately unreachable via every application/API path, but this is NOT deterministic disk-level erasure — the underlying storage is reclaimed only by a later VACUUM (opportunistic, not guaranteed — see the same caveat already documented for the audit-trail retention job, #10924), and pre-existing database backups/WAL archives retain the row until they age out on the backup-retention schedule, independent of this job. AC5 — explicitly not built by this slice: no 90-day advance notice, no post-disposal notice (both #11728), no user-facing retain-longer control (#11729) — until those ship, an archived/disposed user receives no notice of either event. (29 Aug 2026) †

General ​

  • ✅ No circular dependency crash on CPD Plans page (on-hold)
  • ✅ CPD-only accounts do not see Timesheet banner
  • ✅ CPD Home and full PPP Platform visually differentiated
  • ✅ CPD plan list clickable during sign-up
  • ✅ Extract shared <SearchableList> from CPD activity selector
Status ​
Sub-featureStatusNotes
CPD Dashboard chart accuracy⚠️ Driftopen; Matt call pending for Moreton parity
CPD widget stale after mutation✅ Fixed
CPD Plans CRUD + locking✅ Builtshipped
getCpdPlanForUserId IDOR✅ Fixed
lockCpdPlan min-hours validation⚠️ Bugopen
Certificate generation🔄 In progressclosed (frontend); open (backend)
Dashboard 7-day nudge✅ Built
CPD plan reminder (Jan 5 annual)✅ Builtcpd_plan_reminder — fires once/year
CPD plan submission prompt (weekly)✅ Built3-tier escalation; needs scheduler wiring (Q4)
CPD deficit prompt (pro-rated)✅ Built7-day cooldown; needs scheduler wiring (Q4)
CPD milestone notifications (25/50/75/100%)✅ BuiltOnce per milestone per year; needs scheduler wiring (Q4)
Production scheduler for reminders✅ BuiltAzure Container Apps Jobs wired —
EOY reflection window server enforcement✅ Built
EOY reflection + lock interaction⚠️ Bugopen
CPD Activities description length guard✅ Fixed
ApproveCPD success on invalid token⚠️ Bugopen
ApproveCPD fractional hours✅ Fixed
CPD Report CSV export✅ Built
CPD Report date filter timezone-safe✅ Fixed
Em-dash for null Category/Provider✅ Fixed
Pagination counter✅ Fixed
Category-required validation while disabled✅ Fixed
CPD-only accounts Timesheet banner✅ Fixed
Verification 3-colour palette⏳ Specified
Provider super-admin vetting✅ Built#4841 — cpdProviderVettingService
OCR hospital matching✅ Built
Specialist HLR surgical✅ Built
Specialist HLR visibility✅ Built
Specialist HLR hierarchy auto-distribution✅ Built#4845 — seeded via drizzle 0040/0054/0115
AMC/points per-regulatory-body config⏳ On-hold
CPD Home / Full PPP Platform differentiated✅ Built
CPD target universal 50h — test gates✅ Built
CPD Activities year-filter + URL sync✅ Built
HLSR mapping integrity regression✅ Built(BDD @wip pending step defs)
Activity MIME allow-list✅ Built
CPD Report column widths + provider list✅ Fixed
CPD Report combined MO+RP metric⏳ Specified#5697
CPD Report PDF export⏳ Specified#5696
PDF brand contract⏳ Specified#5708
Matt UX review — CPD Home Dashboard✅ Built8 questions resolved — see Closed Questions
APHRA escalation — Super Admin breach list✅ BuiltProd use gated on legal sign-off (deferred)

Open issues on label:feature:cpd — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Closed Questions (9) — click to expand
#QuestionResolution
Q1Timesheet reminder — relocate to PPP Dashboard or to Action Items?Action Item — never on CPD Home. Resolved by Matt on the Notion CPD Home page.
Q2Category-colour standard — canonical palette (verified vs unverified vs rejected)?Resolved: Category colour stays constant per category. Verification is signalled separately — verified = lighter pastel arc on wheel + status chip; submitted = dashed saturated arc + status chip; rejected = distinct hue + rejection icon. Category colour never recolours by status.
Q3"Create a CPD plan" button target — re-copy as "View CPD Plan" or alternate flow?Resolved (Matt, Notion CPD Home page): (1) Re-label button to "View your CPD Plan". (2) Reduce click cost by floating activities already in the user's plan to the top of the activity-picker dropdown — the button becomes a fallback rather than the primary path.
Q4Production scheduler wiring for the 4 CPD reminder batch functions.Resolved (engineering): Use Azure Container Apps Jobs (not GitHub Actions, not Function App) — same Container Apps environment as the API, reuses the existing image with a different entry point, inherits Managed Identity / Key Vault / VNet, scales to zero. 4 jobs: cpd-plan-reminder (0 23 5 1 *), cpd-submission-prompt (0 22 * * 0), cpd-deficit (0 22 * * *), cpd-milestone (0 22 * * *). Each job reads its enabled-flag, message copy, and threshold from a DB-backed cpd_reminder_settings table that a new Super Admin console edits (so cadence and copy can be tuned without redeploys). Implementation tracked separately.
Q5Yearly check on AMC website for spec-req changes — manual or semi-automated?Resolved (engineering): Manual yearly review by Super Admin, scheduled via the same Container Apps Jobs pattern. 5th job super-admin-amc-review runs annually on Feb 1 (after AMC's typical Jan publication cycle) and creates a Super Admin todo with link to the AMC page + runbook. Edits to seed data (specialty.requirements, category minima, HLSR map) go through code review (PR), not the console — keeps regulated content versioned. No AMC scraping. See super-admin.md § AMC Yearly Review and runbook at /runbooks/amc-yearly-review.
Q6Annual target by user type — 50h universal or surgeon variant?Resolved (Matt, 29 Apr): 50h universal for all user types. No userType variant. The RACS 65h consultant target (10/40/15 split) was rejected — PPP is an AMC CPD Home, not RACS-affiliated; RACS-proprietary targets must not appear in product until a formal RACS agreement is in place. Held at 50h until AMC publishes type-specific guidance (next AMC review fires via Q5 job). Display rule already shipped: cpd-home.md line 85 + dual-ring wheel binds outer ring to 50h.
Q7HLSR tick threshold — ≥1 form sufficient or all assigned forms?Resolved (Matt, 29 Apr — GH #5600 comment): All assigned forms must be complete — Option B. Compliance: surgeon completes every ANZASM case form sent to them. Implementation: surgeon submits annual evidence (log / screenshot / CSV) showing assigned cases + completion status. Submission window opens November only each year. Rolling-year basis — if a surgeon submits Jan→Nov evidence, the next cycle is Nov→Nov. Zero cases assigned = automatic ✅. Manual upload creates admin burden initially; future API integration with ANZASM (linking surgeon's ANZASM account) is the eventual target. Implementation tracked separately.
Q9"View your CPD Plan" button on the CPD Plans page duplicated the Edit button (same handleSetReadOnly toggle, identical editable form) — remove or repurpose?Resolved (Rob, session 2026-05-27): Removed the button — Edit covers it and the plan summary is already shown in read-only mode. See AC cpd.plan.view-button-removed.
Q8Procedural Log Book widget — what content surfaces for non-surgeon physicians?Resolved (engineering, 5 May): No separate widget. The "Procedural Log Book" widget IS the existing Specialist High-Level Requirements (HLSR) display — surgeons' ANZASM tile is just one specialty's flavour of HLSR. For non-surgeons, the same widget renders their specialty's HLSR rules per the existing map in cpd.md § Regulatory Framework (Anaesthetics → Emergency Response + Audit/Survey/MSF/Peer Review; ED → Core ABC procedural skills; GP → CPR course; Intensive Care → Airway management; O&G → BLS; Pain → Emergency Response + Audit; Psychiatry → Formal Peer Review 10h; Radiology → Anaphylaxis training; Sport & Exercise → WADA + emergency care). Tile label changes per specialty (read from speciality.requirements.label if present, else specialty name + "Requirements"). Specialties without an HLSR row → widget hidden. Reuses existing HLSR data infrastructure — no new model. Implementation tracked separately. Update (#9145, Matt 2026-06-23): on the CPD Plans page the block is now headed with the generic "High Level Specialist Requirements" label and the speciality is shown as subtext — see AC cpd.plan.hlsr.generic-heading-speciality-subtext. The per-specialty label resolution above still governs the CPD Home HLSR block (resolveHlsrHeading).
Change Log ​
DateChangePR/IssueReason
2026-10-05The CPD plan builder's High Level Specialist Requirements box lists the Super-Admin-managed HLSR requirements for the doctor's specialty (cpdPlanHlsr.getForCurrentUser, the same source as CPD Home), falling back to the legacy per-speciality text when none are configured.#11192Task 8 audit of 5 Oct 2026 (D-04): the box rendered empty for a consultant whose requirements live in cpd_hlsr_requirements, although CPD Home showed them.
2026-10-05The CPD Statement of Completion gate now also requires at least one verified Program-Level Requirement (shortfall plr_not_met), matching the dashboard verdict, and reads approved unexpired exemptions or variations from the decided compliance form rows instead of a hard-coded false. Provider approval token TTL text corrected to the built default of 14 days.#11192, #12955Task 8 reachability check of 5 Oct 2026 (items 5, 6, 8): a doctor with no verified PLR could be issued a certificate while the dashboard showed not compliant, and the exemption branch was inoperable.
2026-10-04Added hasDraftPlan beside hasEstablishedPlan in the CPD plan service, so a plan saved as a draft (Awaiting Submission) can be reported without counting as established. The "has a CPD plan" definition used by every surface is unchanged.#12603The CPD Home plan tile read "Not started" while a draft existed. Only the tile copy changes (see cpd-home.md); the established-plan rule from #7346/#7486 is kept so the tile, onboarding checklist and CPD Plans tab still agree on what counts as a plan.
2026-10-03Noted on AC cpd.plan.guidance.single-master-list-button that the CPD Activities page header now opens the same GuidanceModal via its own "Activities Master List" button (AC cpd.activity.master-list-from-activities-tab in cpd-activities.md). No change to the CPD Plans button.#12743Matt (Dev Session 2026-07-29): the master list "also needs to be added to the activities tab at the top" — dropped when #11039 closed.
2026-10-02EOY Reflection button label/visibility ("View EOY Reflection" vs "EOY Reflection") is now derived from the same plan-year-scoped reflection lookup the click handler uses, not the account-wide user.hasCpdAnnualReflection flag — a doctor with a reflection for one year no longer sees "View" when looking at a different year whose click would actually route to Add.#12665Follow-up from the Async Task 8 audit (#11192 / PR #12662's review, filed as #12665 item 3). Pre-existing mismatch, but #12658 made the year-scoped click-routing the norm, so it became reachable far more often. No AC text changes to the underlying #12658 year-scoping rule — this corrects the button's label/visibility to match the routing it already had.
2026-10-01EOY Reflection modal now keys its existing-reflection lookup and "CPD Year" default off the plan year it was opened from (EOYReflectionButton''s planYear prop), not today''s real-world year — previously a past, locked plan''s reflection pre-filled (and, on Add, could persist) the current year instead. Also records the modules/cpd/plans/** + ManualCPDForm/** joint-ownership overlap with cpd-activities.md''s #12659 entry (legacy classId UI removal) — the detailed AC/rationale for #12659 lives there.#12658, #12659Found during the Async Task 8 CPD Home Lifecycle audit (#11192), filed as its own bug per that issue thread's recommendation. Root cause: EOYReflectionButton.tsx looked up by currentDate.getFullYear() instead of its own planYear prop, and plans/index.tsx rendered the Add dialog with no initialData, so EOYReflectionForm fell back to new Date().getFullYear(). No AC text changes — this is a correctness fix, not a behaviour change.
2026-09-28The CPD provider-verification follow-up (cpd_provider_unverified_followup, § CPD Reminders & Notifications) is now bounded per activity — one notice once the 14-day verification window lapses, one final reminder at 28 days, then nothing — and each message names the CPD activity and the provider. Previously it repeated every day indefinitely and named neither.#12566, #12546, #5778Bug #12546 from the 28 Sep walkthrough. Open Question (engineering-led, Matt to ratify): the 14-day + 28-day two-stage cadence is not stated anywhere in this spec or in cpd-provider-recognition.md; it was chosen to match the token TTL (CPD_APPROVAL_TOKEN_TTL_DAYS, #5778) and the Governing Document's 'encouraging, not punitive' tone rule (§ Tone policy). If Matt wants a different bound or cadence, it is a constant change in processCpdProviderVerificationReminders.ts, not a redesign. Implementation detail is recorded in the notifications spec's Change Log (that spec's code-paths: own the scheduler).
2026-09-27Extracted reflection free text out of the shared JSONB blobs into dedicated nullable reflection_narrative text columns on activities and cpd_end_of_year (migration 0252 + .validate.sql). Every write path that sets the JSONB now dual-writes the narrative keys into the new column — activity learning / situation / summaryOfCase / feedback / comments, and the EOY reflection answers q1…q12_describe + signature (_quality stays in JSONB). The JSONB sub-keys are unchanged, so no read path, export or UI behaviour changes.#12403, #12364Step 1 of the #12364 reflection/PDP encryption-at-rest chain — Rob chose extraction to scalar columns (matching the urn / gender / dob_patient / timesheets.comments precedents, reusing pii-crypto.ts) over a new JSON-sub-key encryption primitive. The columns hold plaintext until #12404 encrypts them; existing rows stay NULL until the #12405 backfill; the export sweep + regression BDD is #12406.
2026-09-21Conformed the 13 activity names scripts/seedCpdActivities.ts still seeded off the published "CPD Activities by Category and Hours July 2026" table — the gap #11082's conformance guard left open, because that guard covered lookups.json and the in-app/marketing constants but not this separate seed source. CPD_ACTIVITIES_SEED_LIST (extracted from the script into src/utils/seed/cpdActivitiesSeedList.ts) now carries the published spelling for all 13, including the three college-named rows #11025 settled (Examiner, Attendance, Specialty group meetings). Migration 0251 renames/merges the existing UAT rows onto the published spelling, following 0226's remap-before-delete pattern for every FK and soft reference. cpdActivitiesSeedList.published-conformance.test.ts pins the seed list to the published table on the normalised key, closing the gap for future drift.#12374, #11089CD runs seedReferenceData.ts (which calls seedCpdActivities.ts) against UAT on every deploy, so these 13 off-list activities kept being offered to doctors and awarded hours against, contradicting cpd.activity.master-list-is-the-published-table and cpd.home.activity-master-list-matches-published. A rename in the seed script alone, without a companion migration, would have inserted the new spelling alongside the old row rather than fixing it — the trap #11089 called out. Live UAT row counts referencing each of the 13 could not be independently confirmed before this migration was written, so it treats every one of the 13 as a merge (not an assumed-clean rename) defensively; static analysis of lookups.json (which already carries the correct spelling for all 13) confirms this is in fact the real-world case for every pair, not just a conservative posture.
2026-09-21The points field on a CPD user activity is now server-side bounded (0 &lt;= points &lt;= 1000) on every write path in cpdUserActivities/** — new AC cpd.activity.points-server-side-bounds (jointly governed with cpd-activities.md, which carries the detailed AC).#12361Cross-reference entry for the cpd.md/cpd-activities.md code-paths overlap on api/backend-ppp/src/routers/procedures/cpd/cpdUserActivities/** — see the cpd-activities.md changelog fragment of the same date for the full reasoning.
2026-09-15Shipped the deferred cpd_classes canonical PLR rename as migration 0246_cpd_classes_plr_wording_correction — 'Cultural Safety' → 'Culturally Safe Practice' and 'Ethical Practice' → 'Ethics' — data-only, guarded with WHERE NOT EXISTS, paired with a first-apply-only validator asserting no row still carries the pre-#12150 wording.#12222, #12150, #12181, #12209#12150/PR #12181 corrected PLR_CANONICAL_NAMES to AMC's published wording but deferred the matching DB-data rename, so every environment's seeded cpd_classes rows still carried the old spelling. CPDActivityForm's findMissingProgramClasses() matches those rows against REQUIRED_PROGRAM_CLASSES by exact string, so two of the four program-level requirements were reported permanently missing regardless of what the user ticked on the ref-invoked submit path used by signup (#12209). No acceptance criterion changed — the AC text is updated only to record that the rename has shipped. The #12209 alias tolerance is deliberately retained until 0246 has applied to prod (manual workflow_dispatch) as well as UAT; its removal is tracked by #12236.
2026-09-13Program-level-requirement matching in the CPD plan form (cpdActivityForm.utils.ts) now tolerates the pre-#12150 seeded cpd_classes wording alongside the corrected canonical names, so the ref-invoked submit path (signup) no longer permanently reports "Culturally Safe Practice"/"Ethics" as missing.#12209, #12150, #12181, #12222#12150/PR #12181 corrected PLR_CANONICAL_NAMES to AMC's published wording but deliberately deferred the matching cpd_classes DB rename, leaving every environment's seeded rows on the old wording. Surfaced via #12209's nightly full-suite failure: exact-string matching against the un-migrated DB rows made two of the four PLR requirements unsatisfiable regardless of what the user ticked. No acceptance criterion changed — this restores the already-documented behaviour (cpd.plan.suggested-plan.save-surfaces-all-attestations) rather than altering it. #12222 tracks shipping the deferred DB rename and removing this alias.
2026-08-29The CPD certificate artefact is renamed "CPD Statement of Completion" everywhere it is user-facing or persisted — the DB title on issuance (certificateGenerationTrigger.ts), the dialog title (CpdCertificateDialog.tsx), the on-screen preview headline (CpdCertificatePreview.tsx), the downloadable PDF headline (generateCertificatePdf.ts), and the eligibility-refusal message (certificateEligibilityRule.ts). Previously the same artefact carried three different names across those surfaces ("CPD Completion Certificate" in the dialog/DB title/refusal text, "Certificate of Completion" on the PDF/preview headline), none matching the policy's exact term.#12033, #11264, #11035AC4 of #11035 asked whether this artefact IS the policy's "CPD Statement of Completion" — confirmed yes by Rob on #11264 (2026-08-27): "Same artefact, different name." Rob's decision directed reconciling terminology across the spec, the certificate title, and the policy reference so the policy and the product use one term, and marked the terminology fix itself fleet-dispatchable (no further product decision needed). Already-issued certificates keep their historical title as issued; retitling past records is a separate question from #11035's still-open AC5 (audit of already-issued certificates) and is not addressed here.
2026-08-29Added the CPD records archive-at-1yr + dispose-at-3yr scheduled job (archiveDisposeJob.ts, registered via registerMaintenanceJob in entrypoints/api-container.ts, daily 0 4 * * *), fulfilling #11037 AC1. Documented AC4's precise "secure disposal" guarantee (application-unreachable DELETE, not deterministic disk-level erasure) and flagged AC5's out-of-scope commitments (90-day/post-disposal notice #11728, retain-longer control #11729).#11727, #11037#11037's policy-conformance audit found the entire CPD records retention lifecycle unimplemented — no archival, no disposal, no notice. This is the archive/dispose story child; the enabler (#11726) added the schema + service shell this builds on.
2026-08-27Added amc-review (annual, 0 22 1 2 *) to the Production-wiring section as re-platformed onto the NAS in-process scheduler — same job, same cron, only the mechanism changed.#11845, #11838Backend hosting moved off Azure to a self-hosted NAS (ADR-0006); #11844 rewrote this section for the 4 CPD reminder jobs but explicitly left amc-review out of scope pending its own migration — this closes that gap now that #11838 has re-platformed it too.
2026-08-27Production wiring for the 6 CPD reminder jobs moved from Azure Container Apps Jobs to the NAS in-process node-cron scheduler.#11844, #11836, #11819The Azure Container Apps Environment was scaled to minReplicas=0 on 2026-08-09 as part of the ADR-0006 NAS migration, silently stopping all 4 CPD reminder Jobs (plus the #11052 at-risk/deadline pair) for 16+ days before #11819 caught it. The original node-cron rejection ("fans out across HPA replicas without leader election") does not apply to the NAS's single-container, no-HPA deployment model.
2026-07-31CPD Activity form exposes a data-testid="cpd-activity-form" anchor; four E2E step selectors re-anchored on it.#11296, #11288The selectors anchored on form input..., but the CPD Plans page renders no &lt;form&gt; — CPDActivityForm returns a &lt;Grid&gt; and submission is button-wired — so they matched zero elements. No acceptance criterion changes; this is test fidelity only.
2026-07-31CPD Completion Certificate issuance is gated on the computed compliance predicate (PPP-verified hours met AND plan locked AND End-of-Year Reflection recorded), reusing the deriveComplianceState rule (#5954). The confirmEoy checkbox remains the member's statement of intent but is no longer sufficient on its own. Both entry points are gated — certificateGenerationTrigger (new skipped_not_eligible result carrying the refusal reason and machine-readable shortfalls) and aggregateCertificateData, which is separately reachable from PDF generation. targetHours was previously display-only and never asserted; it is now enforced. A refusal names the shortfall and the verified hours actually recorded rather than failing silently.#11257, #11035Issuance was gated on the member-ticked confirmEoy checkbox and nothing else, so a practitioner with zero verified hours and no exemption could self-issue a PPP-branded certificate whose PDF read "Total 0 hrs / Target 50 hrs minimum". That contradicts the published "Granting Exemptions or Variations to CPD Requirements Policy July 2026" ("will not be awarded a CPD Statement of Completion"), and PPP is an AMC-accredited CPD Home, so the certificate is the artefact a doctor presents as evidence of meeting their obligations. Hours are counted PPP-verified-only to stay consistent with cpd.certificate.verified-only (#8770) — borrowing the dashboard tile's unverified-inclusive figure would admit a member the certificate face then renders as short of target. The approved-exemption branch of the policy is represented in the rule but is always false today and stated as such: compliance_form_submissions records a request with no decision, approver, or year column and is never read anywhere in the repo, so no approved-exemption state exists to consult. Whether this artefact IS the "Statement of Completion" (AC4) and the audit of already-issued certificates (AC5) remain open on the issue.
2026-07-31An activity name in a suggested CPD plan that does not resolve against cpd_activities_list is now logged as a warning naming the unresolved activities and the CPD hours they carry, instead of resolving to a silent null. Regression tests pin the consultant template's full 50-hour total against the divergent casing the CD seeder actually stores, and assert both that the warning fires with the lost hours and that it stays quiet when everything resolves.#11253, #11133#11082 fixed the case-sensitive lookup itself, but left the second half of the defect in place: a null cpdActivityId is ALSO the legitimate "not seeded yet" signal, so an unresolved activity was indistinguishable from a template that legitimately has no such activity. That is what hid the original 15-hour loss — a practitioner's compliance target was under-populated and neither they nor an admin got any signal. The existing integration test could not have caught it either: it seeds its fixtures from SUGGESTED_CPD_PLAN_TEMPLATES itself, so the DB spelling and the template spelling are identical by construction and a casing divergence is unrepresentable. The new tests seed the spellings seedCpdActivities.ts really writes, so the 50-hour total is asserted against the drift that actually occurs. The warning is observability only — it does not throw, because a partially-resolvable template is still more useful at signup than a hard failure, and the frontend already falls back to a name-based lookup when the id is null.
2026-07-29The ANZASM CPD activity types keep Kristin's published names, and the rename migration is renumbered 0222 → 0226 because uat had meanwhile taken 0222 through 0225. The migration now renames for case and punctuation fidelity only — nine rows, no college reference renamed away — and its first-apply validator stops asserting that "anzasm surgical case form", "malt with peer review" and the rest are stale names. Separately, resolveSuggestionsWithIds now resolves a suggested plan's activities on the same normalised key the rest of the CPD naming stack uses instead of an exact string match.#11082, #11025, #11040, #11057Matt's 2026-07-29 ruling on #11025 confined the RACS/CAPE ban to PPP's own product and feature naming, so the genericisation is reversed. Leaving the validator's normalised list untouched would have inverted it: it would have asserted Kristin's own strings were pre-conformance names and raised on a correctly-conformed database, failing the deploy precisely when the migration had worked. The suggestion-resolver fix is a live defect found in review — CD seeds "Supervision of Surgical Trainees" and "Surgical meetings including M&amp;M, multidisciplinary etc" while the plan templates spell both differently, so the exact match resolved those rows to null and the frontend had no id to pre-fill from; that is 15 of the consultant template's 50 points and 15 of the non-consultant's. The null was silent because it is also the legitimate "not seeded yet" signal.
2026-07-27Conformed the CPD activity master list and the Specialist High-Level Requirements table to the published July-2026 documents. Surgical Meetings including M&amp;M, Multidisciplinary etc — the only row published in all four category columns — now maps to Measuring Outcomes too, so it can be claimed toward that category's hard 5-hour minimum, and the duplicate Review of Performance mapping rows are gone. The off-list 102nd row Multi-Source Feedback is remapped onto the published Multisource feedback using a structured framework and removed; nine activity names are restored to the published strings. On the Specialist table the Emergency Medicine leadership row is back under Performance Review (of self) with both hours cells blank as published, Pain Medicine Specialist is renamed Pain Specialist, the seven stripped frequency qualifiers are restored, and the collapsed hours column is split back into the published Per Hour of Activity / Per Activity pair (removing a phantom seventh header column). Both HLSR fallback constants now list all four Emergency Medicine requirements, matching migration 0166. Migration 0222 is data-only and remaps all six referrers of cpd_activities_list.id before deleting anything, so no logged CPD is orphaned.#11082, #11040, #11057Six divergences between the published tables and the constants the product renders and awards from had reached UAT because nothing compared them. The Measuring Outcomes omission was the live harm — a practitioner attending routine surgical M&M could not count it toward a minimum the published table says they can. New conformance guards (cpd-activities.published-conformance.test.ts, specialist-areas/published-conformance.test.ts) pin all three copies of the activity table and both copies of the specialist table to a transcription that is itself anchored to the /information rendering, so neither side can drift silently again.
2026-07-17Populated the Super Admin CPD Activity Types screen (/admin/cpd-activity-types, #5988) from the CPD activity master list. Migration 0211 backfills one cpd_activity_type_settings row per cpd_activities_list activity (idempotent, data-only, first-apply validator per #10172), so the screen lists the full 61-activity master set instead of an empty state. The superAdmin.cpdActivityTypeSettings.list procedure now joins the master list to surface read-only points, point system (per activity / per hour), and max/year alongside the editable category/college/active fields, and rows whose master-list activity has no category are flagged "Needs category". The #5988 category/college edit path is unchanged.#10756, #10751The screen shipped with no data because nothing ever populated cpd_activity_type_settings, so Matt could not use it to classify activities. Backfilling it and surfacing the master-list points context lets him self-serve the ~5 unmapped supervision/teaching category assignments (notably "Supervision of Surgical Trainees") that unblock #9200, rather than answering in a GitHub comment.
2026-06-24Recalibrated the consultant Suggest-a-Plan template from a 60h overshoot back to the AHPRA 50h floor by suggesting 15h of supervision (honest 1:1, not the old claim-25/count-15 fudge), AND replaced the mis-tagged Measuring-Outcomes filler ("Assess WBAs" → "Peer review of cases / charts with feedback", clinically a Reviewing-Performance activity) with a genuine MO clinical-audit activity ("Clinical Unit Audit") — Supervision 15 + Clinical Audit 13 + Feedback 12 + Meetings 10 = 50h (MO 13, RP 12 combined 25h, Education 25h). Updated cpd.plan.suggested-plan.meets-category-minimums.#9233, #9190Demo rehearsal (2026-06-24): the consultant suggested plan overshot the 50h minimum at 60h (35h parked in Education) and had no genuine Measuring-Outcomes activity. Resolved from documented AMC CPD standards (Measuring Outcomes = clinical audit / outcome-data review / M&M; the spec HLSR map names Clinical Audit as the canonical MO option) — no clinical escalation needed; Clinical Unit Audit is a pure-MO master record named in non-RACS terms (no MALT licensing dependency, #1740).
2026-06-24Added AC cpd.plan.suggested-plan.save-surfaces-all-attestations — on the first Save of an adopted suggested plan, all missing required attestations (program-level acknowledgements AND the End-of-Year reflection) surface together in one pass with a single scroll-to-first-error and one warning, rather than sequentially across multiple Save attempts.#9224, #9159cpd-plans flow test (sprint 2026-06-23) found the first Save errored only on the program-level checkboxes and a second Save then errored on the EOY reflection — required items revealed one at a time (3 clicks). handleSubmit now runs the program-class check and the zod resolver in the same pass.
2026-06-23Gave the CPD Plans page (/cpd-plans) a coherent typography hierarchy. The page title (&lt;name&gt;'s CPD Plan) now renders at the h4 page-heading variant, all section headers (category selectors, the High Level Specialist Requirements block, and "Program Level Requirements") share the subtitle1 variant stepped down from it, and field/checkbox labels stay at body size — all from the shared TYPOGRAPHY_SCALE theme variants, no ad-hoc px. Governs cpd.plan.typography-hierarchy.#9165, #9146Every text element on the plan page rendered at a flat 16px — the title was the same size as a checkbox label, with no page → section → field step-down, reading as out of proportion against other pages. Matt (2026-06-23 catchup, ~00:32): "I think if it just gets streamlined in the same sort of font." Plus Rob/UAT: the CPD Plans page text looks out of proportion vs other pages.
2026-06-23On the CPD Plans page the specialist requirements block is now headed with the generic "High Level Specialist Requirements" label and the doctor's speciality (e.g. "Orthopaedic Surgery") is shown as subtext beneath, rather than baking the speciality into the heading ("Orthopaedic Surgery Requirements").#9156, #9145Matt feedback (2026-06-23 catchup, ~00:33-00:37) — the block read "Orthopaedic Surgery Requirements" via resolveHlsrLabel; he asked for the generic heading with the speciality as subtext, consistent with how the block reads elsewhere. CPD Home's HLSR block (resolveHlsrHeading) is unchanged — this is the plans-page presentation only. The heading wording follows the issue title (plural "Requirements", unhyphenated) rather than Matt's verbal singular.
2026-06-23CPD-plans sprint pass — design-system consolidation, accessibility, responsive, and the suggested-plan flow. (#9145) The CPD Plans specialist block is relabelled to the canonical generic "High-Level Specialist Requirements" with the speciality shown as subtext (was "&lt;speciality&gt; Requirements"), and now renders as a tile within the activity category grid instead of a full-width strip; the resolveHlsrLabel/parseSpecialityRequirements label derivation is retired for this block. (#9146) Plan-page typography hierarchy fixed and the bespoke title row replaced with the shared PageHeader primitive; category panels rewired to the WCAG-AA SEMANTIC_COLORS.cpdCategory palette (dark text on light fills); CPDActivityForm decomposed into presentational parts/ (CategoryActivityGrid, ProgramLevelRequirements, PlanReflectionToggle, PlanProgressFooter, PlanSaveActions). (#9140) Suggested-plan cards now show the CPD-hour value that "Use this plan" actually applies (targetPoints), and supervision counts 1:1 (25 logged hrs = 25 CPD hrs, was mis-capped at 15); the consultant template lands at 60h and the backend invariant relaxed from total == 50 to total &gt;= 50 (the AHPRA floor).#9155, #9140, #9145, #9146Matt feedback (Dev Session 2026-06-23) plus sprint flow testing. (#9145) Matt: the specialist block must read "High-Level Specialist Requirements" with the speciality as subtext, superseding the Q8 per-speciality label derivation. (#9146) Matt: "streamlined in the same sort of font" — the page title must read as a page heading distinct from field labels; raw saturated palette accents failed WCAG contrast as text/chips. (#9140) Sprint flow test: a card said "25 hours" but applied 15 — the number shown must equal the number applied, and the exact-50h template total was a fudge that forced supervision down to 15; the genuine per-activity CPD-hour value is the honest figure and the AHPRA requirement is a &gt;=50h minimum, not an exact 50.
2026-06-22Split provider-replied (unverified) CPD/WBA hours crediting across surfaces — the formal CPD certificate counts PPP-verified hours only, while the in-app to-do CPD gap and the roadmap milestone cadence now credit verified + provider-replied (unverified) hours. pending hours are never credited.#9131, #8770Matt's decision (2026-06-22, #8770) following the #8765 pending → unverified → verified status model. The certificate is regulatory evidence so only stage-2 PPP-verified hours belong on it; personal-progress surfaces should reflect provider-replied work immediately rather than stranding it until stage-2 verification (#8769) lands.
2026-06-22Completed the bdd-features: mapping to name all existing CPD fragment feature files (activities, reports, resource-library, support, provider-framework) and added a core CPD-plan @smoke scenario.#9068, #9055, #9056SGD C4/C6 alignment drift — the built CPD spec under-listed its existing Gherkin fragments, leaving the core CPD-plan flow without name-matched smoke coverage.
2026-06-20Consolidated CPD plan fixes — edit-save returns to the dashboard; Suggested-plan dialog shows role-correct (or neutral) copy; the End of Year Reflections section is hidden when empty; the suggested-plan templates are rebalanced so MO+RP combined reaches 25h and an adopted plan can validate complete.#8965, #8936, #8938, #8939, #8934The CPD plan edit form never auto-exited on save (#8936); the suggested-plan role label misfired in onboarding and could label a non-consultant "Consultant" (#8938); the EoY Reflections section was an empty header/box most of the year (#8939); and the consultant/non-consultant suggested-plan templates under-funded the 25h MO+RP combined requirement (10+10=20) while over-parking Education, so a suggested plan could never read complete (#8934). The #8939 hide-when-empty candidate and the #8934 exact hour split (MO=13/RP=12) are flagged for Matt's confirmation.
2026-06-17HLSR-specialty doctors now get their Annual Reflection window in December (Dec 1 – Dec 31) instead of mid-November; non-HLSR doctors keep the Nov 15 – Dec 31 window. A shared isWithinReflectionWindow selector routes by hasHlsrRequirements and is read by both the client EOY-button gate and the server createCpdEndOfYearReflection enforcement so they cannot drift.#8830, #8735Matt's 2026-06-17 Dev Session decision (#8715): the HLSR evidence flow opens in December to stop gaming — a doctor could otherwise complete HLSR activities early, get the tick, then accumulate new outstanding items before the CPD year closes. The reflection prompt must not let an HLSR user finish their year while HLSR verification is still outstanding, so the reflection window is aligned to the December HLSR verification window (#8728/#8730).
2026-06-17Super Admin can manage the per-specialty HLSR requirements list (add/edit/remove; each with description, frequency, minimum duration, evidence type), with Option-A multi-year handling and a yearly SA confirmation banner#8774, #8729ANZASM/college HLSR requirements are updated annually; the SA needs to own and confirm the list, and multi-year requirements (e.g. every 3 years) 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-17Unified two-stage provider-approval admin screen for Super Admins at /admin/pending-providers. Stage 1 is the existing CPD provider vetting queue (approve/reject before verification emails go out). Stage 2 is the new PPP-verification queue: it lists CPD activities the provider has replied to (status unverified — doctor, provider, hours, replied-at) and a Verify action moves each unverified → verified via superAdmin.providerVerifications.verifyActivity. The two previously-separate controls now live on one tabbed screen.#8769, #8765Deferred frontend half of #8765 (backend shipped in #8768). Without this UI there was no in-app way to move a provider-replied activity from unverified → verified, so those hours sat stuck in the unverified bucket.
2026-06-17CPD provider-approval flow: the provider verification email is now sent on submit (no longer gated by super-admin approval), and CPD activities follow a pending → unverified → verified status model. Pending and unverified both show as unverified hours on the widgets; only verified counts as verified.#8768, #8765Operational provider-approval flow Matt greenlit on 2026-06-16, split from on-hold #7915. The previous super-admin-gates-before-email behaviour delayed the provider request; doctors also could not tell when a provider had already replied (with PPP) versus still awaiting the provider.
2026-06-17Super Admin is now redirected away from /cpd-dashboard to the SA landing page on login and direct nav#8712SA accounts have no CPD record; showing them a 0-hrs CPD view was confusing and implied they should be logging CPD hours
2026-06-17Fixed unverified hours to show per-category breakdown, matching verified hours display#8669Unverified hours were showing as a single total with no category detail, inconsistent with verified hours breakdown
2026-06-02Spec status promoted from in-progress to built — core CPD (home, activities, plans, resource library, support) is shipped and demoable on UAT.Reflect delivered state for stakeholder review; reporting and automations remain tracked as their own in-progress sub-specs (cpd-report, cpd-automations), and two open product questions (#7915 verified-provider model, #7764 resource-library framing) remain but do not block the built state.
2026-05-28Filter bars now consume the shared PillDateRangeFilter; doughnut widgets share the THIN_DOUGHNUT_CONFIG from the canonical ThinDoughnutChart component.DRY refactor — eliminate duplicated chip-preset and chart-radius logic so a single source of truth governs the date-range pill and thin-doughnut look across the app.
2026-05-27Added AC cpd.plan.suggest.brand-colour — the "Suggest a Plan" button uses the PPP brand primary fill (theme tokens, no inline hex), matching the other primary CTAs, replacing the off-brand secondary cyan.#7772, #7762Surfaced during the investor demo (Rob — "is this button not our brand colour?"). Also tokenised remaining hardcoded button colours across the frontend per no-hardcoded-brand-values (#7525).
2026-05-27Removed false "AI-suggested" wording from the Suggest a Plan flow (tooltip + dialog copy); suggestions are rule/role-based templates, not AI.#7753, #7749The Suggest a Plan suggestions are rule/role-based templates, not AI-generated. The misleading wording was inaccurate and risked misleading the investor + legal audience.
2026-05-27Hide the EOY Reflection button on the CPD Plans page until the reflection window is open (unless a reflection already exists to view), instead of showing a disabled "(available from Nov 15)" button year-round.Rob — "don't show the EOY Reflection button until it can be used - it wastes UI space otherwise." Mirrors cpd-home.reflection.hidden-out-of-window. Also made all CPD Plans toolbar buttons size="small" and consistent (EOY Reflection was size="large", stretching Submit/Edit on its flex line).
2026-05-27Add a "Reset" button to the CPD Plans page (current-year, non-locked plans only) that deletes the plan after confirmation so the user can start again, restoring the "Suggest a Plan" entry-point.Once a plan existed the AI "Suggest a Plan" button was permanently hidden (cpd.plan.suggested-plan.hidden-when-plan-exists) with no user-facing way to delete and start over. Rob requested a "Reset" affordance scoped to the current year. New cpdPlan.resetCpdPlan procedure reuses deleteCpdPlan + assertPlanIsMutable (locked plans blocked).
2026-05-27Suggested CPD Plan dialog — "Use this plan" adopts all suggestions (remove the misleading per-activity tap-to-select that was ignored), update the prompt copy, and lay the cards out as a 2-column grid so the dialog fits without scrolling.Rob asked whether you pick-and-choose; the tap-to-select highlight had no effect (onAutopopulate always used all suggestions). Decision: keep adopt-all, remove the fake select, refresh the copy, and avoid scrolling. Supersedes the 5 May "select desired suggestions" header-copy.
2026-05-27Suggested CPD Plan cards show "Logs as: <activity>" when the friendly label differs from the master activity that's adopted.Rob asked why Measuring Outcomes "didn't populate" — it did, but the card label differed from the adopted activity name, which was confusing.
2026-05-27Remove the redundant "View your CPD Plan" button (duplicated Edit); migrate the CPD dashboard-screen ACs (category-colour mapping, combined Performance-Review tile) to cpd-home.md and replace cpd.md's CPD Dashboard section with a pointer.Rob — "View your CPD Plan seems to take you to the same screen as edit … Remove it." And the CPD dashboard ACs belonged in cpd-home.md per the 23 Apr scope split (CPD Home owns the dashboard screen; cpd.md owns the data model), not duplicated in cpd.md.
2026-05-26Traceability + test pass for provider request dedup-by-email and approve/reject/merge audit logging. The behaviour was already built (dedup #7462; approve/reject audit #4841; merge audit #4823/#7013); this tags the five covering BDD scenarios in cpd-super-admin.feature with @issue-7589 and adds a unit test asserting approveProvider writes a cpd_provider_approve audit row with actor + provider identity. No AC semantics changed.#7618, #7589#7589 was decomposed from #7314 without awareness that the dedup + audit work had already shipped under earlier issues; closing it required making its ACs explicitly traceable rather than re-implementing.
2026-05-26Verified and hardened non-surgical specialty HLSR requirements (speciality.requirements JSONB). Added @smoke/@regression BDD scenarios (#7590) for a non-surgical specialty consultant seeing its own requirements rather than the surgical ANZASM rule, and for a specialty with no configured requirements degrading gracefully (widget hidden, page still renders). Added unit coverage for the CPD Home resolver helpers resolveHlsrRequirementText / resolveHlsrHeading.#7611, #7590#7590 (decomposed from #7314) asks that non-surgical specialties surface their own CPD requirements from a speciality.requirements JSONB column. The column, view, Zod schema, shared parse helper and seed migration 0119 were delivered under #7464; this closes #7590 by proving the behaviour with executable scenarios + unit tests and covering the graceful-degradation acceptance criterion.
2026-05-26Spec-accuracy pass — flipped two stale Status-table rows from ⏳ Specified to ✅ Built after verifying the implementing code. Provider super-admin vetting (#4841) is built in cpdProviderVettingService; Specialist HLR hierarchy auto-distribution (#4845) is seeded via drizzle 0040/0054/0115. No AC semantics changed; the corresponding bullet ACs were already ✅.#7562, #7561Closed/shipped work was still showing ⏳ in the CPD Status table, so the spec misrepresented the build state. Same kind of accuracy pass as #7313 did for cpd-home.
2026-05-26Escaped a bare &lt; 50h token in the APHRA breach-list AC (wrapped in backticks) and removed stray trailing **** artifacts so the spec renders. No AC semantics changed.#7548The bare &lt; was parsed by VitePress (Vue compiler) as an unclosed HTML tag, failing the Build VitePress CI gate on every open PR. Companion changelog-fragment fixes apply the same escaping to auth, logbook, profile-doctor, and timesheets fragments.
2026-05-26Supervisory CPD credit point/hour rules (#7457): the derived supervisor-owned credit record from #7456 is now scored via computeSupervisoryCredit — operative-time-driven supervisory hours (default per-case contribution when absent), capped at the confirmed 15h supervised-training requirement, points at 1/hour — and tagged with an auto-generated provenance flag (attributes.derivedCredit = true). Spec AC at cpd.md:453 flipped ⏳→✅.#7517, #7457, #7314#7456 delivered the derived-credit record model (supervisor-owned activities row, derivedFromActivityId self-FK, participant_role = 'consultant') but deliberately deferred the supervisory point/hour calculation to #7457. This PR adds that scoring so the named supervisor automatically accrues supervisory-role CPD hours/points toward the 15h requirement without logging the activity manually, with the entry visibly distinguishable from manual activities. Per Transcript 2026-04-01 §18 — "consultant roles correctly trigger supervisory roles and subsequent CPD points".
2026-05-26Non-surgical specialties surface their own High-Level Specialist Requirements (HLSR) in the existing HLSR widget, read from the speciality.requirements JSONB column. Added shared parseSpecialityRequirements/resolveHlsrLabel helper normalising both the legacy string[] shape and the new non-surgical { label, items } object shape; seeded non-surgical HLSR objects via migration 0115 (idempotent, only where requirements were NULL) and the fresh-DB seed path; tile label now reads requirements.label when present else "{specialty} Requirements"; widget hidden when no HLSR row exists.#7479, #7464Resolved Q8 (cpd.md:638) — the Procedural Log Book widget IS the existing HLSR display; non-surgeons get their specialty's HLSR rules via the same data infrastructure, no new model. Flips cpd.md:499-500 to implemented.
2026-05-26Multi-clinician CPD credit for shared logbook cases — a surgical logbook case naming a distinct supervisor now generates an independent derived CPD credit record owned by that supervisor (consultant/supervising role), landing the credit in the supervisor's own compliance total. Flips the dual-credit AC to done.#7476, #7456, #7314Implements the dual-credit AC under "Multi-user CPD credit (collaborative cases)" (Transcript 2026-04-01 §CPDDoubleCredit). Previously only the case author accrued credit, under-crediting the supervisor and producing an incorrect CPD total. Introduces an additive activities.derived_from_activity_id self-FK + the multiClinicianCreditService sync (idempotent create/update/remove on logbook save) so both clinicians are credited per role. The derived-record model is the foundation the supervisory point/hour rules (#7457) extend.
2026-05-26De-dup new CPD provider requests by email (case-insensitive, whitespace-trimmed) in both the user activity-submission path and the admin create path; confirm approve/reject/merge each write an audit_trail row (actor, action, provider id(s), timestamp), with merge recording both source and target provider ids. Flip the "de-duped by email" and "audit log for approve/reject/merge" ACs to done.#7475, #7462, #7314Provider-management hardening from the #7314 CPD spec-audit (Category B) — duplicate provider rows polluted the vetting/merge queues, and every privileged provider decision must be auditable.
2026-05-26OCR sticker scanner consistently extracts the date-of-birth field — normalised to day-first DD/MM/YYYY, validated to reject implausible (future) and out-of-range dates, returned empty without regressing URN/gender when absent, and pre-populated into the logbook-case dobPatient form field. Flipped cpd.ocr.dob-extraction to built.#7473, #7459Transcript 2026-04-13 §OCR (~01:29:53) — Matt Randell identified a required enhancement for the OCR to consistently extract the date of birth. Hardened validation closes the implausible-date gap (a DOB can never be in the future).
2026-05-21Seed four AMC PLR categories (Cultural Safety, Addressing Health Inequities, Professionalism, Ethical Practice) as distinct cpd_categories rows (migration 0112); add per-PLR data-testid attributes to CPDHomeV2 ticks; mark AC cpd.categories.professionalism-ethical-split as implemented.#7156, #7010AMC compliance — every doctor must complete ≥1 CPD activity per PLR to be compliant; Professionalism and Ethical Practice must never appear combined (#6369).
2026-05-21Mark cpd.plan.locked-after-entry AC complete — plan is read-only after submission; admin unlock via change-request workflow. Add @regression BDD scenario @issue-7009.#7153, #7009Implementation was live since #4839/#4927 but the AC remained ⏳ without a directly-linked scenario. This PR closes the gap by cross-linking the existing locking enforcement (FORBIDDEN guard, change-request audit, admin unlock loop) to the AC and adding a composite regression scenario that traces the full read-only → request-change → admin-unlock → resubmit lifecycle.
2026-05-21Add @smoke BDD scenario for cpd.export.report-structure — verifies the three-part export structure (summary dashboard, activity log, evidence appendix) with no evidence hyperlinks.#7151, #7014Closes the BDD gap for the cpd.export.report-structure AC. The implementation (dashboard page #6689, evidence appendix #6691, hyperlink exclusion #6377) was verified as complete; the missing piece was a unified smoke scenario tracing all three structural requirements to a single executable test.
2026-05-21Mark cpd.activity.card-pastel-colours AC complete. Activity-card category chips use getDisplayCategoryPastelColor() (pastel token) not the saturated dot colour; verified in columnDefinition.tsx and CategoryColorIndicator. BDD regression scenario added tagged @issue-7012.#7150, #7012AC was already implemented via #6371 (getDisplayCategoryPastelColor wired to Chip backgroundColor) but remained ⏳ pending formal closure. #7012 adds the spec mark-up and a dedicated regression scenario so the trace is unambiguous.
2026-05-21Mark cpd.admin.merge-duplicate-providers as ✅ — dedicated merge screen at /admin/cpd-providers is separate from the vetting queue at /admin/pending-providers; BDD smoke scenarios added for #7013.#7149, #7013AC already implemented via #4823 (service + tRPC + frontend); this PR adds the BDD traceability and flips the spec status to done.
2026-05-20Super-admin provider vetting queue now shows ABN and org type as inline-editable fields per row; Approve action persists both fields when supplied. Collapsible "Assessment criteria" accordion with 6 informational non-blocking checkboxes added per AMC framework ATT43/ATT53. Backend listPendingProviders() and approveProvider() extended accordingly.#6741, #6688ATT43/ATT53 require reviewers to check ABN and organisation type before approving a new CPD provider. Fields were already on the schema (#6720) but not surfaced in the queue UI or persisted at approval time.
2026-05-20Verify light-email-same-security AC — all four provider-bound email paths (initial submission, super-admin bulk re-send, lifecycle reminder, regenerate-expired) use HMAC-SHA256 + 14-day TTL via generateApprovalToken. Flipped ⏳ → ✅.#6653, #6376Matt called out at Dev Session 2026-05-06 §LightEmailSecurity that "light" provider email variants must share the same security and time-expiring links as standard verification emails. Code audit confirms no variant bypasses HMAC or TTL.
2026-05-19a11y: added default aria-label="Loading" to MuiCircularProgress and MuiLinearProgress via the PPP MUI theme so every loading spinner satisfies WCAG 2.1 SC 1.1.1 (axe aria-progressbar-name). Per-usage aria-label props still override the default.#6588, #6523Axe scan against UAT (e2e/a11y/cpd-activities-accessibility.spec.ts, 2026-05-19) flagged a serious aria-progressbar-name violation on the CPD Activities page. Fixing the theme defaultProps covers all ~480 spinner usages across the app in one change.
2026-05-19Verified SGD AC cpd.provider.link-lifecycle.superadmin-view: the Super Admin per-provider link-lifecycle backend (sent/consumed/expired counts + last-sent timestamp + re-send mutation) and table were delivered by #5978/#6145. Closed the remaining discoverability gap by wiring the view into the provider-vetting queue (PendingProviders → 'Link lifecycle' action + a back-link the other way). Flipped AC to ✅ and added two @regression @issue-6375 BDD scenarios.#6575, #6375SPEC-DRIFT — #6375 is the SGD gap-analysis sibling of #5978/#6145; the feature itself already existed end-to-end. The spec requires the view 'within the provider-vetting queue or a dedicated tab' and it was an orphan route, so #6375 added cross-navigation only. No backend application code required.
2026-05-19Verified SGD AC platform.email-links.time-expiring: every emailed magic-link token is time-limited, single-use, states its validity period, and is regenerable. Flipped AC to ✅ and added a @regression @issue-6379 BDD scenario. Closed the residual gap by making the timesheet batch approval email state its explicit 14-day validity window and regeneration path (previously generic 'will expire for security reasons' copy).#6562, #6379Duplicate-scope verification — the magic-link expiry/single-use/regeneration policy was implemented across #5778 (CPD 14-day TTL), #5809 (timesheet 14-day + regenerate), #5972 (central magicLinkTtl policy: admin-reset/signup 24h, env &gt; DB &gt; default), #6145 (Super Admin re-send) and #5978 (per-provider link-lifecycle counts). Only the timesheet email copy did not state the validity period explicitly, which #6379 fixed; the BDD adapter (email-render.ts) was also realigned to mirror the backend cpd-approval/timesheet-approval expiry copy.
2026-05-19Fixed flaky keyboard-focus E2E check for the CPD Plans year selector (e2e/a11y/cpd-plans-accessibility.spec.ts). The prior assertion read document.activeElement synchronously after .focus(), racing with React commits and MUI Autocomplete's outer-wrapper → inner-input focus swap. Replaced with Playwright's auto-waiting expect(locator).toBeFocused(). Added @regression @issue-6536 BDD scenario.#6536Test reliability — the e2e keyboard-accessibility job was failing intermittently. The component itself (MUI Autocomplete) IS keyboard-focusable; only the test's focus-detection pattern was racy.
2026-05-19Verified SGD AC cpd.activity.provider-declined.notify-user: the submitting doctor receives an in-app notification (including the provider's reason) when a provider does not authorise their submitted CPD activity. Flipped AC to ✅ and added a @regression @issue-6373 BDD scenario.#6493, #6373Duplicate-scope verification — the decline-notification pipeline (declineByProvider → declineCpdUserActivity → recordCpdDeclineTokenConsumption → cpd_activity_provider_declined notification) was implemented end-to-end by #5952. No new application code required; #6373 is the SGD gap-analysis sibling of #5952.
2026-05-19Super Admin can filter the Provider Details list (/settings/provider-details) by status using radio-style checkboxes (Verified / Pending Verification). Default view shows all statuses; selecting one narrows to that status only; re-selecting clears back to all.#6492, #6372Implements gap issue #6372 — traceable to Dev Session 2026-05-06 §UnverifiedFilter (~00:09:42): 'a way for the super admin to filter the activities list by those that are not verified'.
2026-05-19Verified the CPD dashboard combines "Performance Review of Self" and "Performance Review of Others" into a single "Review of Performance" tile (via useCpdScoreBreakdown's aggregatedBreakdown) and that an Education tile is present alongside Measuring Outcomes and Review of Performance. Added a @regression BDD scenario locking the combined-tile behaviour.#6487, #6367Spec-drift gap: the behaviour was already correct in code but the AC was unverified and lacked regression coverage that would catch a future split of the Performance Review metric.
2026-05-19Closed the spec gap for cpd.report.pdf-export: marked the AC verified and added a @smoke @issue-6378 BDD scenario asserting both the CSV and PDF export buttons are visible on the CPD Activities Report. The PDF export itself (auto-sized columns, branded header, audit footer via @pdfme/generator) already shipped in #5696/#5708/#5865.#6484, #6378The PDF export button was implemented but the acceptance criterion was still marked unverified with no scenario tracing it to a GitHub issue.
2026-05-19Resolve 2 on-hold gap issues: (1) CPD plan lock confirmed — locked after entry, PPP Super Admin can unlock on request (e.g. specialty change mid-year); (2) duplicate provider merge confirmed required for launch but NOT required for the 28 May 2026 demo.#6480, #6368, #6374Matt confirmed answers on 2026-05-19 via GitHub comments on #6368 and #6374.
2026-05-13Provider decline flow: magic-link page Decline button + dialog (10–500 char mandatory reason), in-app bell notification to doctor (cpd_activity_provider_declined, no email), rejected banner on activity detail with Edit & resubmit action, SA Rejected filter chip, resubmit mutation (fresh approval token to same provider), full audit trail (cpd_decline_token_consumed, cpd_resubmit).#6182, #5952Doctors had no visibility when a provider declined their activity request. This closes the feedback loop so doctors can correct and resubmit.
2026-05-13Mandatory AHPRA pre-notification doctor contact step with 14-day rectification window before regulatory body escalation.#6164, #5960Regulatory compliance requirement — CPD providers must give doctors 14 days to rectify their CPD position before notifying AHPRA (or alternate UK body). The workflow gate is enforced server-side so Super Admins cannot skip the pre-notification step.
2026-05-13Add jurisdiction-aware AHPRA policy document info banner to the CPD Reminder Settings screen; AU uses hardcoded Medical Board of Australia URL, UK uses configurable system_settings.regulatory_body_policy_url column.#6157, #5964Super Admins need to review CPD non-compliance obligations before sending breach notifications. The jurisdiction-aware banner surfaces the correct regulatory body policy document per instance country code.
2026-05-13Provider link lifecycle view — re-send action and accurate last-sent timestamp (approval_email_sent_at column replaces updated_at proxy).#6145, #5978Deferred from #5978 / PR #6144. The updated_at proxy for last-sent drifted on unrelated row edits; the new column records the authoritative send time. Re-send button lets Super Admin trigger a fresh verification email for a specific activity without leaving the lifecycle view.
2026-05-13Super Admin CPD Activity Types settings screen at /admin/cpd-activity-types. Backed by new cpd_activity_type_settings table (migration 0076) and superAdmin.cpdActivityTypeSettings tRPC procedures (list/create/update, all requireSuperAdmin gated). Each row carries name, description, category (education/research/teaching/clinical/other), college mapping (amc/anzasm/racs/gmc/none), and an isActive flag. Deactivated types stay on historical user records but are excluded from the activity creation dropdown.#5988Matt asked for a dedicated Super-Admin screen to manage and classify the master list of CPD activity types — previously these were a hard-coded Postgres enum that required a deploy to change. New table lets Super Admin add/edit/classify types without redeploy.
2026-05-13CPDProgressWidget and CPDCategoryWheel now round displayed hours using Math.round (AMC formula) instead of toFixed(1).#5956AMC auto-scoring uses round(minutes ÷ 60); all hour displays must be consistent. e.g. 12.7h → 13h, 12.4h → 12h. Decimal accumulation is preserved in the DB.
2026-05-13Added two-party legal + Matt approval gate to AHPRA notification template; is_draft can only be cleared once both approvals are recorded. New DB columns, approval audit table, backend hard-gate service, and Super Admin UI.#0, #5967Regulatory risk management — notification template contains legal obligations and must not be used in production without formal legal sign-off and product-owner sign-off. Simple isDraft boolean provided no audit trail or workflow enforcement.
2026-05-13Add Super Admin /admin/cpd-provider-link-lifecycle view + trpc.ppp.superAdmin.providerLinkLifecycle.list procedure. Returns per-provider counts of CPD approval links sent / consumed / expired (sent > 14d, not consumed) plus last-sent timestamp, sourced from cpd_user_activities grouped by provider_id.#5978Closes the read-only half of cpd.provider.link-lifecycle.superadmin-view. Re-send action and sort/filter UX deferred to follow-ups so the baseline observability lands now.
2026-05-13Add form resource type to the CPD Resource Library and seed 10 PPP-authored clinical reflection forms under a dedicated "PPP Clinical Forms" section.#5990, #5846Surfaces the existing PPP-authored .docx forms (downloaded via the trpc.support.getFormDownloadUrl SAS endpoint, #5846) inside the Resource Library so doctors can discover and filter them alongside other CPD resources. Lands ahead of the full DB-backed migration (#5958); the seeded entries carry a formSlug metadata field so they can be migrated into the resource_library_items table when that lands.
2026-05-13Activities Report surfaces a combined Measuring Outcomes + Review of Performance compliance tile alongside the per-category breakdown (Matt 17 Apr Notion brief).#5697Matt's Notion brief called for a combined MO+RP metric so users see the AMC 25h combined cap at a glance. Underlying combined total already existed in the categorySummary util; this surfaces it on the report.
2026-05-06Drift re-baseline — reconcile spec ACs against built state#5834, #5343Spec was auto-flagged as partially drifted; ACs updated to reflect current implementation: ⏳→✅ for #5055 (widget cache invalidation), #5690 (50h universal target test gates), #5698 (Container Apps Jobs scheduler wired), #5699 (CPD Home visual differentiation), #5685 (MIME allow-list), #5695 (HLSR mapping integrity), #5746+#5760 (Activities year-filter + URL sync), #5684 (report column widths + provider list), #5105 (plan label wording), #5604 (APHRA breach-list screen). Status table updated to match. New rows added for #5697, #5696, #5708 (still open).
2026-05-06APHRA escalation work parked — manual hand-drafted email is the fallback; legal sign-off (#5710) closed. Templated infrastructure (#5707) shipped but dormant.#5710Matt's call (6 May 2026) — reporting and CPD engagement take priority over APHRA alerting, which only fires once a year at low volume. Super Admin can hand-draft an email to performanceframework@ahpra.gov.au if/when the situation arises. Reactivate the templated path when volume justifies it.
2026-05-06Default /cpd-activities list to current calendar year with a one-click All-years toggle and ?year= URL persistence.#5746, #3636, #5351Aligns the activities list with the AMC CPD calendar-year cycle (#3636) and matches the dashboard widget scoping introduced in #5351; deep-links and reloads now preserve the chosen filter.
2026-05-06Retired the legacy Reviewing Performance (Self) / (Others) bracketed split; canonicalised on a single Review of Performance category across constants, seed JSON, mocks, stories, services, and the database (drizzle 0060 merge migration). Added § Category Vernacular to make the canonical labels the spec's source of truth.#5748Bracketed labels were a historic artefact left in baseline data after an earlier UI iteration removed the split. Mismatch caused the activity selector to render only four categories. AMC framework defines one Review of Performance category, not two.
2026-05-05Wire 4 CPD reminder Container Apps Jobs in Pulumi (Q4) — plan-reminder, submission-prompt, deficit, milestone.#5739, #5698Closes cpd.md Q4 — the 4 scheduled reminder jobs are now provisioned in the UAT Pulumi stack, reusing the API image. Each job reads its cpd_reminder_settings row at run time so enabled/disabled and thresholds are operator-adjustable without a redeploy. BDD scenarios added for enabled/disabled toggle, threshold change, and idempotent re-runs.
2026-05-05AHPRA notification copy templates stored in cpd_aphra_settings DB table (Super Admin editable without redeploy); seeded with [DRAFT — pending solicitor review] copy; prod rollout gated on legal sign-off (#5710).#5707, #5710PPP is an AMC-accredited CPD Home and must notify AHPRA when a practitioner fails the annual 50h requirement. Copy must not be hard-coded; Super Admins need to adjust tone/wording without a code deploy.
2026-05-055 May call sweep — added Open Question Q8 (Procedural Log Book widget for non-surgeons); new ACs for suggested-plan atomic-replace + single-per-user + header copy + hide-when-plan-exists; activity-selector default = All Activities; upload MIME allow-list (images + PDFs); HLSR mapping integrity regression; Activities Report column-widths + provider-list regression + MO+RP combined compliance metric; locked framing that the plan is a year-start projection; surgical → procedural log book terminology note.Consolidate two weeks of catchup decisions (Notion brief + 22 Apr to 5 May calls) into the spec so future agents work from a single, current source. Companion sweep on cpd-home.md and super-admin.md.
2026-04-29Added APHRA Escalation AC section and Status row — Super Admin breach-list screen listing users below 50h by 1 Dec, Send APHRA notification action, cpd_aphra_notifications DB record.#5606, #5604Matt confirmed ~22 Apr 2026 that PPP Super Admins (not Executive Admins, not automated) are responsible for initiating APHRA notifications. Issue #5604 captures the full build spec.
2026-04-29Spec reorg — added RACS surgical group mapping, ANZASM implementation details, and Q5/Q6/Q7 (moved from cpd-home.md Q7/Q9/Q10) to Regulatory Framework section.#5606cpd.md owns compliance rules and business logic; these items were misplaced in the dashboard spec (cpd-home.md).
2026-04-29Align CPD category chip colours with marketing site — Option C approved palette + lighter variants.#4817In-app colours did not match the marketing site palette; users saw different colours pre- and post-signup. Option C (docs/site/design/cpd-palette-comparison.md) is the approved palette — all bg+text pairs verified WCAG 2.1 AA (≥ 4.5:1).
2026-04-13Transcript audit 2026-04-13 — §OCR classified R (requirement); 1 new AC added under OCR section; 1 @wip BDD scenario added.#~§OCR (~01:29:53) of the 2026-04-13 Dev Session transcript ("Dev environment strategy, timesheet governance, OCR, enterprise pricing") identified that the OCR sticker scanner must consistently extract the date-of-birth field from scanned documents, in addition to the hospital matching already implemented. All other paragraphs were classified C or CONFIRM (linked accounts merge, CPD wording, provider vetting, timesheet approver, external approver — all already captured in existing specs).
2026-04-01Transcript audit 2026-04-01 — §18 classified R (requirement); 2 new ACs added under new "Multi-user CPD credit (collaborative cases)" section; 2 @wip BDD scenarios added.#~§18 of the 2026-04-01 Dev Session transcript ("Testing readiness — infrastructure bugs, mobile menu, CPD logic") clarified that when a registrar logs a surgical case with a named consultant supervisor, both clinicians should independently receive CPD credit calculated per their respective roles (performing/assisting vs supervising). The consultant supervisory credit should be awarded automatically without requiring a separate activity log entry. This collaborative credit mechanism was not previously captured in the CPD spec.
2026-04-28Admin unlock loop for locked CPD plans: change request now fans out an in-app notification to every super admin; new admin-only unlockCpdPlan procedure reverts status locked → draft; user re-edits and resubmits → lockCpdPlan auto-relocks. New admin dashboard page lists pending unlock requests. cpd_plan_unlock added to audit-action enum (no DDL — varchar column).Matt's call (Option B): admin holds the unlock key — explicit audit trail trumps speed; users won't typically amend a submitted plan, so the rare unlock path stays gated behind super-admin review.
2026-04-21Added "Export CSV" button to the CPD Activities Report page. Exports the current filter-respected activity set with user-friendly column headers (CPD Activity, CPD Category, Hours, Date, CPD Provider, Status, Description) and formula-injection-safe escaping. PDF export is scoped as a follow-up.CPD Activities Report had no export controls despite every other tabular report (Logbook, WBA, Multi-Feature) offering them. Users could not download their CPD data for college submission or local record-keeping.
2026-04-21Security regression coverage added for updateCpdPlan locked-plan guard — integration test + @regression @requires-backend @issue-4990 BDD scenario verifying FORBIDDEN surface and DB snapshot unchangedFraser audit: updateCpdPlan guard (shipped in) had unit coverage only — a direct-API bypass attempt was not exercised against the live DB. Hardens zero-trust.
2026-04-21DEV_BYPASS_EOY_DATE localStorage bypass in isEOYReflectionAvailable is now gated on import.meta.env.DEV so it is tree-shaken out of production builds — previously any user could unlock the EOY Reflection window year-round by setting the localStorage keySecurity: dev-only escape hatch was shipping to production, bypassing the Nov 15 – Dec 31 availability window client-side. Blocks (server-side window enforcement).
Apr 2026CPDActivityForm Cancel button now wired — resets form to initialValues and calls a new optional onCancel prop so parents can close/dismiss the formCancel button rendered with no onClick handler — clicking it did nothing, leaving Submit/reload/navigate away as the only exits from an in-progress edit.
Apr 2026Submit (lock) on CPD Plan now saves the current form state before locking — prevents silent loss of unsaved edits when user presses Submit without first clicking SaveFraser repro: editing a plan field and pressing Submit without Save discarded the edits and locked the stale version. Lock semantics are now "save, then lock".
Apr 2026Activity selector in CPD sign-up: client-side text search with clear button + "no matches" empty stateMatt (03 Apr 2026): the scrollable checkbox list of activities has no filter, making it slow to find a specific activity when signing up.
Apr 2026Plan lifecycle: added submitted enum value (forward compat), tightened locked semantics — mutation procedures reject writes (FORBIDDEN), requestCpdPlanChange procedure writes cpd_plan_change_request audit entry, frontend "Locked for {year}" banner + request-change modalMatt (call 13 Apr 2026, ~00:30:13): users won't change plan post-submission, locking enforces the compliance contract.
Apr 2026CPD provider verification email gated behind PPP super admin vetting for genuinely-new providers#4841Matt (call 13 Apr 2026, ~00:56:36): without vetting, any user can trigger an unsolicited verification email to anyone — risk of impersonation and misuse.
Apr 2026Activity verification colour states defined (submitted / verified / rejected) with WCAG 2.1 AA contrastMatt (call 13 Apr 2026, ~00:57:50): existing dark "verified" colour was visually inconsistent; need at-a-glance differentiation that meets accessibility.
Apr 2026OCR-detected hospital from sticker scans must map to user's linked hospitals (auto-link or prompt)Matt (call 13 Apr 2026, ~01:29:53): OCR detected "Hampshire Hospital NHS FT" but the case wasn't connected to his linked hospitals.
Apr 2026Specialty-specific requirements hierarchy added (surgery excl. Maxillofacial, orthopaedic)#4845Auto-distribution is live but specialty-specific buckets weren't being seeded automatically.
Apr 2026Suggested-plan template wording must not say "fixed" — values are adjustable up to category maxMatt (call 13 Apr 2026, ~01:04:06): existing copy is misleading users about the editability of the suggested values.
Apr 2026Documented RACS CPD framework; populated ANZASM requirement for all surgical specialtiesRACS CPD Guide 2025 mandates ANZASM participation for all specialist surgeons (except Maxillofacial). Requirements data was missing from seed data and live database.
Mar 2026Dashboard nudge completed with localStoragePR, PR thisImplemented using cpdPlanSkippedAt + 7-day threshold; localStorage gives instant dismissal, DB persists cross-device; spec corrected from "30 days" to "7 days"
Jan 2026AMC points-based support identified as gapWalk-through notesMatt noted AMC colleges use points not hours
Jan 2026Notification icon for plan-due identifiedWalk-through notesMatt requested CPD Home menu indicator
Oct 2025Certificate generation addedFeature completion workflow
2026-04-22Drift re-baseline — ACs reconciled against 12 closed issues (21 Apr sweep) and 26 open issues; flipped ✅ for; added ACs for; removed duplicated OCR AC; deduplicated triplicate Change Log trailer; 8 product questions flagged for Matt (CPD Home 22 Apr call) — status remains partial-drift#5343, #5338/drift-fix cpd — audit: docs/features/.drift-audits/cpd.md
Sources & Recordings ​
SourceNotes
https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6EDescription pending SGD audit
https://docs.google.com/document/d/1YhgQSFL9iOlQLoTrQYSwxRNXH4Dg4wefkItcwljQZmoDescription pending SGD audit

Internal documentation — org members only