Skip to content
View in Notion

CPD Home ​

Feature Overview ​

Audit-ready, user-friendly landing for CPD tracking — either in isolation (CPD-only subscribers) or as a feature within the full PPP platform. Solves the AMC 2023 mandate requiring AU public doctors to prove CPD yearly, by verifying day-to-day public-hospital involvements (previously an "assumed compliance" model) and automating scoring.

Scope boundary clarified 23 Apr: CPD Home is the dashboard/home screen only. The automation rules that score workplace involvements as CPD live in cpd-automations.md (a separate feature). The CPD data model lives in cpd.md.

🚨 Scope correction 29 Apr: Engineering had silently introduced CAPE/PLR groups (Cultural Safety / Quality Improvement / Structured Peer Discussion), the RACS-specific 65-hour consultant target with 10/40/15 split, and cross-references to AHPRA framework details beyond the basic 50h target. Matt rejected all three. They are now removed from the V2 build. Wheel = simple total hours vs 50h annual target. "Other requirements" = Annual CPD Plan + Annual CPD Reflection ticks.

RACS/CAPE language is banned until a formal RACS agreement exists. "CAPE" appears to be RACS-proprietary terminology — using it without affiliation risks copyright/IP breach. PPP is an AMC CPD Home and complies with AMC directions only. RACS-specific rules, targets, and acronyms must not appear anywhere in PPP until a RACS deal is in place.

AMC provisional approval (5 May 2026): AMC has granted CPD Home approval and billing is unblocked. Compliance reviews from this point on run through the dedicated ops account (Kristen) — see super-admin.md § Compliance Mailboxes.

CPD Home is highest-priority feature for next development cycle. †

Source ​

Open Questions (Matt) ​

#QuestionProposed answer / statusRef
Q13For a doctor to be compliant for the year, do they need at least one Program-Level Requirement covered, or an activity in each of the four (Culturally Safe Practice, Addressing Health Inequities, Professionalism, Ethics)?Open. Your CPD Home Notion brief (Report → "Needs additions") says "Requirements of Program Level Requirements - ie minimum 1 activity of each"†. The published Assessment and Recognition policy (Appendix 1) says "at least one of the below", and Rob decided on that wording on 11 Aug (#11046). The app currently uses "at least one" (cpd.home.compliance.plr-required-for-verdict). Your 1 Sep AMC wording on #12150 ("Program level requirements set at least in the four areas of …") describes the programme, not what each doctor has to log.notion-cpd-home-brief, #11046, #12150
Closed Questions (10) — click to expand
#QuestionResolutionRef
Q1Wheel/tile clickability — confirm target screens and pinning behaviourResolved 29 Apr — click scrolls to filtered activity table (built)Matt
Q2Verified/unverified colour scheme — final decisionResolved 29 Apr — pastel inner arc (verified) + dashed saturated arc (submitted) on the wheel (built). List uses status chip, not colour variation.Matt
Q4Reminder cadence — exact timings per policy docResolved 29 Apr — AMC does not prescribe cadence. PPP product decision: pro-rata deficit (built) + fixed windows at 1 Oct / 1 Dec / 17 Dec. Message copy still needed from Matt.Eng
Q6Speciality → high-level-req mapping bug — #5404 Wave 2Resolved 28 Apr — Matt confirmed full mapping in #5404. Ready to implement.Eng
Q8RACS/CAPE language — AMC only, or other college requirements?Resolved 29 Apr — PPP is an AMC CPD Home only. CAPE appears to be RACS-proprietary terminology; using it without a formal RACS agreement risks copyright/IP breach. No RACS language anywhere in PPP until a deal is in place. Comply with AMC directions first and foremost.Matt
Q7Yearly AMC spec check — manual or semi-automated?Moved to cpd.md Q5 — operational/admin question, not a dashboard questionEng
Q9Annual target by user typeMoved to cpd.md Q6 — business rule, not a dashboard questionEng
Q10HLSR tick thresholdMoved to cpd.md Q7 — business logic, not a dashboard questionEng
Q11Procedural Log Book widget on PPP Dashboard — what content surfaces for non-surgeon physicians?Resolved 5 May (engineering): No separate widget. The "Procedural Log Book" widget IS the existing HLSR display, generalised across specialties — surgeons' ANZASM tile is just one specialty's flavour. For non-surgeons it renders their specialty's HLSR rules from the existing map in cpd.md § Regulatory Framework. Tile label is per-specialty. Reuses HLSR data — no new model. See cpd.md Q8 resolution.Eng
Q12Combined-hours tracking & AMC guideline cross-references — in scope?Out-of-scope rejection (29 Apr): Engineering had introduced combined-hours tracking and cross-references to AMC guideline details (e.g. 'Kate groups', 'racks rules') beyond the basic 50h target. Matt explicitly rejected these as not directions from the CPD Home. † Combined-hours tracking and AMC framework cross-references beyond the 50h target are OUT OF SCOPE. Do not re-introduce. Update 2026-05-26 (#7357): the Combined (MO + RP) 25h breakdown tile was a misinterpretation of this rejection — Matt re-confirmed Option A ("misinterpretation on what needed to be removed") and the tile is reinstated (AC cpd.home.combined-tile). Only the broader AMC guideline cross-references ('Kate groups', 'racks rules') remain out of scope.Eng
Matt's Requirements (from Notion + 23 Apr call) ​

Issue ​

As of 2023 AU public doctors must prove CPD yearly through an AMC-accredited CPD Home. Previously they were assumed compliant via day-to-day hospital involvements (MDTs, M&M, audits, teaching). No current way (pre-PPP) to verify these public involvements digitally — which has created a secondary market for paid conferences/courses.

Purpose ​

  • 100% audit-ready CPD Home via PPP verification process
  • Validate verified workplace interactions as official CPD (automation for platform users only)
  • Simple, frictionless — deload the clinician's administrative burden
  • Downloadable, portable, high-value

Function ​

  • Operates under AMC CPD Home compliance (may adjust once approval lands — AMC reciprocal API integration is out of scope for the Investor Demo (14 May 2026) and deferred until AMC approval lands)
  • CPD activity upload + verification process (manual, for CPD-only users)
  • CPD automation of PPP platform involvements / workplace activities (full platform only — lives in cpd-automations.md)
  • Dashboard tracking: overall hours, Program-Level Requirements (PLRs), High-Level Specialist requirements, CPD Plan, Yearly review †
  • Reminders — keep users on track if behind (per compliance policy doc)
  • CPD resources — links to free podcasts etc.
    • ⚠️ Podcast/online-resource completion verification parked — "can of worms" (Apple-account integration). Post-MVP.
  • Remedial assistance — positive prompts, example emails in policy doc
  • Escalation / APHRA notification — automated flag to Executive Admin first, then human intervention before notification. Post-MVP (only needs to function end-of-year) †
  • Exportable report + communication of verified activities with attached evidence
Framework reference ​

⚠️ Language note (29 Apr): PPP is an AMC CPD Home, not RACS-affiliated. Do not use RACS-proprietary acronyms (e.g. "CAPE") or RACS-specific rules in product surfaces or user-facing documentation until a formal agreement with RACS is in place. The current build targets AMC CPD Home compliance only.

Annual target rule and HLSR compliance logic live in cpd.md. This spec covers only the dashboard display. Quick reference:

  • Annual target: 50h, all user types (held at 50h until AMC confirms type-specific guidance — see cpd.md Q6)
  • HLSR specialty mapping + ANZASM activity types + tick logic → cpd.md § Regulatory Framework

High-Level Specialist Requirements (HLSR) — display only ​

Full HLSR logic, specialty mapping, and ANZASM implementation details are in cpd.md § Regulatory Framework. This section covers only what CPD Home renders.

The HLSR block is displayed only when user.userType === 'consultant' && user.isSurgeon && user.specialityId maps to the RACS surgical group (canonical mapping in cpd.md).

  • UI placeholder at CPDHomeV2/index.tsx:798 — "coming soon" text gated on consultant && isSurgeon
  • Full block (real tick, specialty check, zero-assigned state) implemented by #5600
  • ❌ cpd.home.hlsr.manual-attestation — REMOVED from UI in #8714 (Evidence Integrity Rule violation). The self-attestation button ("I have met my HLSR" / "Clear attestation") has been removed from HlsrBlock. The HLSR block is now informational only: shows requirement heading and description text. The backend ppp_cpd_hlsr_attestations table and cpdHlsrAttestation tRPC router are preserved; existing records are untouched. The full HLSR evidence model is pending design in for-discussion issue #8660. (#7579 original, removed #8714)
  • ✅ cpd.home.hlsr.pull-by-specialty — The SA-managed HLSR requirements for the doctor's selected specialty (the cpd_hlsr_requirements master list from #8729, seeded by #8736) are pulled into the doctor's CPD plan and surfaced in the HlsrBlock: the doctor-scoped cpdPlanHlsr.getForCurrentUser procedure resolves user.specialityId and returns the active requirements for that specialty, each rendered with its description + cadence (yearly / every N years) + minimum-duration line. When the specialty carries no active SA-managed requirements the block falls back to the legacy per-specialty text (speciality.requirements JSONB → static map, #5969); when neither exists the block is hidden, not rendered empty. Read/surface-only — no schema change; the master list and its seed are maintained separately (#8729/#8736). (#8728) † ‡
  • ✅ cpd.home.hlsr.december-window — The HLSR verification/attestation submission flow opens in December of the CPD year, analogous to the CPD Plan Review / EOY Reflection window (opens November). Before December the flow is locked: HlsrBlock surfaces an Opens December [year] pill (requirement text stays visible, read-only), and the backend cpdHlsrAttestation.setStatus (doctor self path) rejects an early self-attestation with a clear PRECONDITION_FAILED message via the shared isWithinHlsrVerificationWindow constant. From December onwards (and for past CPD years) the doctor may submit for Super Admin review; Super Admin verification (setForUser) is never blocked by the window. The dashboard HLSR tick stays grey until SA-verified (Evidence Integrity Rule, #8714). Logic-only — the window is date-derived, no migration. † (#8730) (#8715)
  • ✅ cpd.home.hlsr.simple-tick — The CPD Home hero panel shows a single binary HLSR tick — complete (green ✅) / not complete (outlined ⬜) — alongside the wheel sidebar, mirroring the PPP Dashboard CPD widget tick (dashboard.cpd-widget.hlsr-tick) so both surfaces present the doctor's HLSR completeness "in their entirety". There is deliberately no per-requirement breakdown at widget level — that detail stays in the HlsrBlock separator box below, unchanged. The tick is read-only (Evidence Integrity Rule, #8714): it flips to complete only when the persisted per-user/per-year attestation flag is set (cpdHlsrAttestation.getStatus, scoped to the selected year pill), never a fabricated default; it carries no onClick/onChange. Hidden when the user is not a consultant, has no specialty, or the specialty carries no HLSR obligation (hidden, not empty). The same shared HlsrTickRow component renders on both surfaces (single source of truth). † ‡ (#8732)
Dashboard — Fidelity & Gaps vs Moreton Blue (23 Apr) ​

Matt's synthesis from the call + Notion: "don't put back to MB screens but don't remove the features that are required."

  • Keep img-live-6 chrome (clean cards, typography, modern UAT look)
  • Keep img-mbb-2 info density (PLR checklist · Plan/Reflection tickboxes inside the wheel panel · Combined as hero · Activities table with Specialist High column)

Missing on current CPD Home dashboard: † †

  • ❌ Combined number is wrong †
  • ❌ Annual CPD Plan tile
  • ❌ Annual CPD Reflection tile
  • ❌ Program-Level Requirements block
  • ❌ High-Level Specialist Requirements block (consultant users only, driven by Profile → Speciality) †

Errors to fix on current UAT:

  • CPD Home button/nav incorrectly redirects to the 'My Profile' page instead of the dashboard. † CPD home nav item must include a dropdown menu with a CPD Dashboard option. †
  • Timesheet reminder toaster appears on CPD Home — remove (belongs on PPP Dashboard / bell-icon notifications only) †
  • CPD Hours reminder — numbers inaccurate, adds undue pressure; must match policy doc
  • Graphical representation of category tiles (particularly combined 'measuring outcomes and reviewing performance' section) not clearly representative of the 50 total points required. †
  • Setup wizard — only display if CPD-Home-only user, not for full-platform users †
  • Verified vs unverified colours + wheel representation — TBD
  • Add-activity button — consider moving to top
  • Wheel tile click → filtered activity list with selected category at top
Evidence Integrity Rule (23 Apr — critical) ​

Tick-boxes on CPD Home are READ-ONLY evidence indicators, not user-controlled toggles. A user must never be able to mark a compliance item "Complete" by clicking a checkbox. This is fundamental to the platform's audit-ready value proposition and non-negotiable.

ItemTick turns green when…
Annual CPD PlanUser authors a Plan document (self-owned artefact — no external verification needed for authorship)
Annual CPD ReflectionUser authors a Reflection document
Hour-category minima (MO/RP/EA)Sum of verified hours meets the minimum for the user's framework
HLSR (consultant surgeons only)No tick rendered — self-attestation UI removed (#8714, Evidence Integrity Rule). HLSR block is informational only pending full evidence model (#8660).

Clicking any tick-box opens the creation or activity-linking flow — it never toggles state client-side. The engine that flips the tick is the verification pipeline, not the user.

HLSR — self-attestation UI removed (#8714). The interim self-attestation button introduced in #7579/#7942 has been removed as an Evidence Integrity Rule violation. The HLSR block is now informational only. The backend ppp_cpd_hlsr_attestations table and tRPC router are preserved pending the full evidence model design (#8660). Until #8660 ships, the HLSR row in the tick-table above shows no tick at all — not a false green, not a false pending.

Prototype Decisions (23 Apr — locked by Matt) ​
#Decision
Q1Wheel/tile click → scrolls to CPD Activities table on the same page, applies category filter, pins clicked category at top. Matt's "auto set-up to activities with filter applied" — confirmed.
Q2Unverified rendered with dashed outline + lighter treatment on wheel AND list (same hue). Verified gets a ✓ tick badge
Q3Add-activity button at top of page, scroll-past (not sticky). If testing shows it gets in the way, revert to sticky
Q4MVP = Dashboard (hours + plan + reflection + PLRs + HLSR) + hours breakdown + full activity list below. Show both empty "day-one" + filled exemplar
Q5Annual CPD Plan / Reflection tile shows a tick-box / checkbox (binary done-not-done), not a progress bar. Label "Not started" until ticked (a plan saved as a draft reads "Draft saved — awaiting submission", still unticked — #12603)
Q6Orthopaedics → Surgery mapping bug filed as a separate Wave 2 issue (#5404), not blocking this prototype
Annual lifecycle coverage (Async Task 8, #11192) ​

Matt's Task 8 brief asks to "Show both types of users completing Yearly lifecycle of CPD home completing all requirements for that users ie entering appropriately CPD activities, PLR, HLSR (for consultant), end of year review (and if built Yearly Appraisal and PDP plan for following year). Show dashboard interactions and exportable report".† The brief adds no new behaviour. It is the yardstick for the 1-year walkthrough, and each clause maps to existing ACs (refreshed 2026-10-03):

Brief clauseWhere it is specifiedNotes
"both types of users"consultant vs non-consultant: cpd.home.layout.hlsr-heading-consultant, cpd.home.hlsr.simple-tick (consultant-only)Matt confirmed again on 14 Jul (~01:04:55) that HLSR belongs to consultants: "high level specialist requirements are related to consultants". CPD-only vs full-platform scope gating is under § Scope gating.
"entering appropriately CPD activities"cpd-activities.md (cpd.activity.master-list-is-the-published-table, cpd.activity.auto-select-category, cpd.activity.master-list-from-activities-tab ⚠️ #12743); auto-scored credit in cpd-automations.md (⚠️ #12725, #12742)
"PLR"cpd.home.plr.four-separate-ticks, cpd.home.plr.tick-from-claims, cpd.home.compliance.plr-required-for-verdictWhether compliance needs one PLR or each PLR is Q13 (open).
"HLSR (for consultant)"cpd.home.hlsr.pull-by-specialty, cpd.home.hlsr.december-window, cpd.home.hlsr.simple-tick; CPD Plans heading cpd.plan.hlsr.generic-heading-speciality-subtext (cpd.md)
"end of year review"cpd-home.reflection.* (Nov–Dec window, December for HLSR doctors), cpd.plan.reflection.december-for-hlsr (cpd.md)The EOY reflection now keys off the plan year it was opened from (#12658, Task 8 audit PR #12662).
"Yearly Appraisal and PDP plan for following year"cpd-home.annual-cpd-review-tile → appraisals-wba.md appraisals.yearly.annual-cpd-review-compliance-step, appraisals.yearly.review-rolls-into-appraisalBuilt. PR #12662 confirmed the "not built" note was stale.
"dashboard interactions"§ Dashboard layout & hierarchy, § Verification display, § CPD Activities panel; year pill cpd.home.hours.year-pill-filter
"exportable report"cpd-report.md cpd.export.report-structure, cpd.report.pdf-export, cpd.report.compliance-metric-mo-rp, cpd.certificate.verified-only

Acceptance Criteria ​

Core — dashboard compliance detail ​

  • ✅ CPD Home surfaces the dashboard onboarding checklist for CPD-only users (built: instances/ppp/src/modules/CPDHomeV2/index.tsx renders OnboardingChecklist). The Phase 2 Setup Wizard and the old Outstanding-Onboarding banner were removed in #8027 — onboarding lives solely in this checklist, whose steps reflect live completion and which auto-hides once complete. See onboarding.md. (#8027) Its close button is offered only once every step is complete, and a checklist dismissed early is shown again (#12551). While the current user is still loading, CPD Home holds the checklist's space only if the checklist was shown there on the previous visit, so it does not arrive late and push the page down (#12554).
  • ✅ Display current-year overall hours accurate to sum of verified CPD activities — built in CPDHomeV2
  • ✅ Display Annual CPD Plan tile (present / absent + quick-create) — built in CPDHomeV2. Implementation note: tile state must be driven by dashboardCpd.getCPDData → hasCpdPlan (an established, non-draft plan exists for the current year — ne(status, 'draft'), i.e. a bare draft row left over from an abandoned "Create plan" attempt does NOT count), NOT cpdPlanNudge.getStatus.shouldShow — the nudge returns false for any user who never clicked "skip" during onboarding, incorrectly showing the tile as green for users with no plan. This hasCpdPlan signal is the single canonical "has a CPD plan" answer shared by this tile, the onboarding checklist's createCpdPlan step and the CPD Plans tab, so all three surfaces always agree (#7346). The definition is now centralised in one shared backend helper — cpdPlanService.hasEstablishedPlan(userId, year, ctx) / establishedPlanCondition() — through which every reader (this tile, onboarding, the CPD Plans tab and the profile/to-do surfaces) routes, so the surfaces cannot silently diverge when new plan statuses become reachable (#7486). Draft state (#12603): a plan saved as a draft ("Awaiting Submission") is still not established — the tile stays unticked, with no "Submitted" state and no "View →" — but it no longer reads "Not started": it shows "Draft saved — awaiting submission" with a "Continue →" CTA, driven by a separate dashboardCpd.getCPDData → hasDraftCpdPlan signal (cpdPlanService.hasDraftPlan, only true while no established plan exists for the year). hasCpdPlan and every other reader are unchanged.
  • ✅ Display Annual CPD Reflection tile (present / absent + quick-create) — built in CPDHomeV2. The tile is hidden outside the Nov–Dec window unless a reflection has already been submitted (hide, not lock — see cpd-home.reflection.hidden-out-of-window); it is not rendered with a disabled/countdown state year-round. (#7743) †
  • ✅ cpd-home.annual-cpd-review-tile — CPD Home wheel sidebar renders an Annual CPD-plan review RequirementTile (appraisals-wba S2, #9093) that lets the doctor review last year's CPD plan and create a new one; completing it drives the appraisals-wba S1 state machine not_started → in_progress → completed and logs the annual-review step. The tile tracks the CPD Home year pill (selectedYear) and delegates read/start/complete to appraisalWorkflow.getAnnualCpdReview / startAnnualCpdReview / completeAnnualCpdReview. On completion the tile also rolls the completed review into the yearly appraisal + PDP via appraisalWorkflow.rollIntoAppraisal — the two records stay distinct ("two separate things, linked, not merged") and the success message reflects the roll-in ("…logged and rolled into your yearly appraisal."). The full AC lives in appraisals-wba.md § appraisals.yearly.annual-cpd-review-compliance-step and § appraisals.yearly.review-rolls-into-appraisal. † ‡ (#9093, #9094)
  • ⏳ Display Program-Level Requirements block with per-category progress vs minima — REMOVED 29 Apr (Matt rejected CAPE/PLR scope)
  • ✅ cpd.home.plr.four-separate-ticks — the CPD Home dashboard renders four separate, individually-labelled AMC Program-Level Requirement ticks: Culturally Safe Practice · Addressing Health Inequities · Professionalism · Ethics (wording corrected by #12150, 2026-09-01 — previously "Cultural Safety" / "Ethical Practice"). "Professionalism" and "Ethics" must never appear as a single combined tick. All four are read-only indicators per the Evidence Integrity Rule — driven by verified activity data, never user-toggled. Built in CPDHomeV2 (#7010) — each tick has its own data-testid (cpd-plr-cultural-safety · cpd-plr-addressing-health-inequities · cpd-plr-professionalism · cpd-plr-ethical-practice; the testIds are historical slugs and were not renamed by #12150); met is derived from verified activity counts, never a client toggle.† ‡
  • ✅ cpd.home.plr.shared-source — the four PLR definitions and the verified-match / provider-rejection (isPlrRejected) logic that drives the CPD Home dashboard ticks live in a single shared constant, consumed unchanged by the dashboard and by the CPD User Activities report Program Requirements chips so the two surfaces can never disagree on what counts toward a PLR. The dashboard tick behaviour is unchanged — the inline definitions were extracted, not modified (#7945). See cpd-report.md § cpd.report.program-requirements.real-counts. † ‡
  • ✅ cpd.home.plr.tick-from-claims — each CPD Home PLR tick is derived from the activity's plrClaims tags (the claim/tag model, gated by !isPlrRejected), not by matching the activity's category name to the PLR name. Category-name matching is retained as a fallback only until the data migration (#7646 PR2) removes the legacy PLR cpd_categories rows. Read-only per the Evidence Integrity Rule — never user-toggled. (#7646) † ‡
  • ✅ cpd.home.plr.canonical-label-consistency — the four canonical AMC PLR label strings (Culturally Safe Practice · Addressing Health Inequities · Professionalism · Ethics) are defined once in the shared package (@ppp-org/ppp/constants → PLR_CANONICAL_NAMES) and rendered identically on every displayed surface: CPD Home ticks, the CPD plan-suggestions banner, and the CPD Support guidance pages. No in-app surface uses paraphrased or older wording. The legacy PLR category/class row names stay as categoryNames aliases until #7646 PR2 renames the DB rows; the cpd_classes half of that rename shipped in #12222 as migration 0246_cpd_classes_plr_wording_correction, with the front-end aliases retained until it has applied to prod as well as UAT (#12236). (#7647) Wording corrected by #12150 (2026-09-01) — Matt quoted AMC's actual published language verbatim ("culturally safe practice, addressing health inequities, professionalism and ethics") and said "I think Kristin was correct here", reversing the earlier "Cultural Safety" / "Ethical Practice" wording this AC previously required (itself sourced from #7525/#6369). Capitalisation follows this tuple's existing convention, since no authoritative AMC document with proper-case wording exists in the repo or Drive — see the constant's own header comment for the full trace. † † ‡
    • ⚠️ EXCEPTION, still open — marketing /information policy pages, re-tracked by #12150. These pages remain verbatim transcriptions of Kristin's July-2026 source PDFs (Rob's #11024 "publish verbatim" decision is unchanged), and — as of #12150's own 2026-09-01 Google Drive check — those PDFs have not been updated with any wording, old or new. The PDFs' own text for the first PLR ("Culturally Safe Practice") already happens to match the corrected canonical wording, but the PDFs still disagree with each other and with the corrected constant on the fourth PLR (they use "Ethical Practice"/"Ethics" inconsistently across sections) — so this AC is not yet met on the marketing surface even though the in-app surfaces now are. Engineering did not reword these components: doing so would violate both the verbatim-transcription policy and verify-policy-fidelity.mjs, which checks components against the (still uncorrected) source PDFs, not against PLR_CANONICAL_NAMES. This resolves only when Kristin's PDFs are corrected to the same wording and the components are re-transcribed against them. See marketing.md § CPD information pages. † † ‡
  • ✅ Display High-Level Specialist Requirements block for registered specialists (hidden otherwise) driven by user.specialityId → HLSR group constant — built in CPDHomeV2. Q10 resolved → moved to cpd.md Q7 (all assigned ANZASM forms must be complete; zero-assigned = auto-pass). † †
  • ✅ cpd.home.combined-tile — The Hour-category breakdown renders a Combined (MO + RP) tile alongside MO, RP and EA, showing combined Measuring Outcomes + Review of Performance hours against the 25h hard AHPRA minimum (/ 25). Hours are derived client-side by summing the MO and RP breakdown rows (mirrors ensureCombinedBucket). Clicking the tile scrolls to the CPD Activities panel and applies a combined MO OR RP filter — narrowing the accordion to the Measuring Outcomes and Review of Performance sections (an OR-set; the Education and Other sections are hidden) and lighting the tile's active-state border like the other tiles. There is no single "Combined" CPD category, so the filter is resolved via a sentinel (COMBINED_FILTER_KEY) that unions the two real categories rather than matching one group key; clicking the active tile again clears the filter. Re-added in CPDHomeV2 (cpd-category-card-combined testid). Reinstated 2026-05-26 — wrongly removed on 29 Apr; Matt re-confirmed Option A on #7357 ("misinterpretation on what needed to be removed"). Made filterable 2026-05-27 (#7750) — the tile previously looked clickable but did nothing (confusing UX); it now applies the combined filter consistently with the other tiles. † †

Provider framework page — public AMC Criterion 2.2 disclosure ​

  • ✅ cpd-home.provider-framework.public-page — A public page at /cpd-provider-framework is accessible without authentication. It publishes the four assessment criteria (Educational Quality, Relevance, Appropriateness, AHPRA/AMC Alignment) verbatim from ATT52 2.2.2, the pre-approved provider categories, and the how-to-apply process (email, timeframes). Built in CPDProviderFramework. The full assessment-pathway and provider-recognition-application build (ATT43/ATT53, CPD Advisor role, fees, Committee oversight, AI-assisted decision support) lives in cpd-provider-recognition.md.
  • ✅ cpd-home.provider-framework.link-from-dashboard — The CPD Home dashboard header includes a "Provider criteria" link button navigating authenticated users to /cpd-provider-framework. Built in CPDHomeV2.

Annual Reflection — November-only input window ​

  • ✅ cpd-home.reflection.november-only — The Annual Reflection input form is open from November through December (a 2-month window), defined by REFLECTION_OPEN_MONTH / isReflectionOpen. † (#6360) (#7006) ‡
  • ✅ cpd-home.reflection.hidden-out-of-window — Outside the Nov–Dec window, and when no reflection has been submitted, the Annual CPD Reflection tile is not rendered at all — it does not occupy sidebar space with a locked/countdown state. The tile is wrapped in {(reflectionOpen || reflectionSubmitted) && …}. Supersedes the previous behaviour where the tile rendered a locked/disabled state with an "Opens in November" countdown year-round. † (#7522) ‡
  • ✅ cpd-home.reflection.visible-in-window — During the Nov–Dec window the Annual CPD Reflection tile renders with a Create action (or View when already submitted). † (#7522) ‡
  • ✅ cpd-home.reflection.submitted-always-shows — A submitted reflection keeps showing its submitted (✓ / View) tile state even outside the Nov–Dec window, because the wrap also tests reflectionSubmitted. † (#7522) ‡
  • ✅ cpd-home.reflection.december-for-hlsr — For a doctor whose specialty carries HLSR requirements, the Annual Reflection input window opens 1 December (Dec 1 – Dec 31 of the plan year) instead of 15 November, aligning the reflection with the December HLSR verification window (cpd.home.hlsr.december-window, #8728/#8730) so an HLSR doctor is not told they are "done" while their HLSR verification is still outstanding. Non-HLSR doctors are unchanged (Nov 15 – Dec 31, per cpd-home.reflection.november-only). The shared selector isWithinReflectionWindow(hasHlsrRequirements, planYear, currentDate) routes HLSR users to the December window and everyone else to the existing window; the same selector backs the CPD Plans EOY button (cpd.plan.reflection.december-for-hlsr) and the server createCpdEndOfYearReflection gate, so client and server cannot drift. Past plan years remain always-available and future plan years remain locked for both cohorts. Logic-only — the window is date-derived, no migration. † (#8735) (#8715) ‡
  • ✅ cpd-home.reflection.compliance-tracks-year-round — The reflection requirement remains tracked year-round by the compliance tile (CpdComplianceTile via deriveComplianceState({ hasReflection })), so hiding the tile out-of-window never hides the requirement. † (#7522) ‡

Compliance — escalation and platform role ​

  • ✅ cpd-home.compliance.escalation-human-gate — When non-compliance escalates toward AHPRA notification, the system must first raise an automated flag to the super admin for a personal human-level review before any official notification is sent to AHPRA. No automated AHPRA notification may fire without a super-admin review step. The end-to-end escalation framework is documented in the PPP CPD Home Information & Policies document (GDrive: https://drive.google.com/drive/u/1/folders/1_ciarfAfP3-ZXHk8xBoXTvvHorW-RlUO). Implemented via cpd_aphra_pre_notification table + assertPreNotificationWindowElapsed server-side gate + CpdAphraPreNotificationPanel SA UI (#7007). †
  • ✅ cpd-home.compliance.non-upload-is-non-compliance — On registration, PPP becomes the user's official CPD Home provider by default unless they explicitly inform us otherwise, and doctors have the full year to reach compliance. The default cadence is supportive prompts, not punitive flags: when a CPD-Home doctor has low involvement or has been away from the platform, the system sends friendly nudges (e.g. "haven't seen you in a while", "anything to upload to save leaving it all to the last minute?", "Can we help?"). Built in #7295: users.is_ppp_cpd_home boolean defaults to true on the registration path (migration 0116), so PPP is the CPD Home of record unless the doctor opts out; and processCpdHomeAwayNudges (daily 22:00 UTC scheduled sweep registered in api-container.ts with a boot-time armed check — built in #12759, previously admin-callable only so no doctor received it automatically — plus the cpd_home_away_nudge system-generated notification type) sends the supportive away/low-involvement reminder with a gentle cooldown, never marking the doctor non-compliant during the year. Eligibility requires an account older than the 60-day away threshold (DEFAULT_AWAY_THRESHOLD_DAYS, read from users_view.created_at): a doctor who has just registered has naturally logged nothing yet, and that is not the "extended time away" Matt's wording describes, so they are never nudged before their account is 60 days old (#12759 review, PR #12775). † (#6362) (#7295)
  • ✅ cpd-home.compliance.non-upload-as-assumed-non-compliance-escalation — Only after persistent non-engagement does escalation route toward AHPRA notification, where failure to upload is treated as assumed non-compliance because PPP is the CPD Home of record. This step is deliberately NOT automated off is_ppp_cpd_home — it routes through the human gate (see cpd-home.compliance.escalation-human-gate, implemented via cpd_aphra_pre_notification + super-admin review, #7007). Persistent non-engagement is the exact AMC-submission §3.2 criteria (confirmed by Matt 2026-06-03 on #7690, option 1): no established CPD plan more than 30 days after enrolment, OR nothing logged within 60 days of enrolment, OR under 25% complete (vs the 50h annual target) once it is on/after 1 August. Built in #7690: listEscalationCandidates (SA-only tRPC query) classifies doctors meeting any of those criteria — evaluated after the supportive nudge cadence (#7295) — and surfaces them on the /admin/cpd-escalation-candidates Super-Admin review surface with the supportive "requirement to comply to prevent AHPRA notification" framing (Matt-approved tone: doctors are busy and fatigued, lead with support not blame). Listing never fires anything — the SA reviews each candidate and only the existing CpdAphraPreNotificationPanel human gate (#7007, 14-day window) can send the pre-notification. When a human-gated pre-notification is sent, every active super admin receives an in-app cpd_aphra_escalation_admin_notice compliance notification (Matt: "our PPP admin user requires notification of human-gated escalations so we remain compliant"). † † (#6362) (#7295) (#7690)

Scope gating ​

  • ✅ Hide Timesheet reminder on CPD Home (move to PPP Dashboard / bell-icon notifications) — done in V2 †
  • ✅ Hide Setup wizard unless user is CPD-Home-only tier — done in V2 †
  • ✅ Show quick-add at top of the page — done in V2

Dashboard layout & hierarchy (5 May) ​

Locks the section order, heading levels, and clickability that Matt called out on the 5 May call. Future drift caught by Storybook/Playwright snapshot, not in production.

  • ✅ cpd.home.layout.50h-above-plr — "50 hours" total-hours header sits above the Program-Level Requirements section. (#5700)
  • ✅ cpd.home.layout.eoy-above-action — "CPD End of Year Reflection" heading sits above the "Complete end of year reflection plan" CTA. (#5700)
  • ✅ cpd.home.layout.plr-heading-larger — Program-Level Requirements is a section heading (h2/h3 — same level as the wheel section), not an inline label inside another card. (#5700)
  • ✅ cpd.home.layout.hlsr-heading-consultant — "High-Level Specialist Requirements" heading rendered as a top-level section for userType === 'consultant'; hidden otherwise. (#5700)
  • ✅ cpd.home.layout.wheel-centered-clickable — wheel widget is horizontally centred in its column and the entire surface (wheel + label) is keyboard-clickable to open the activity breakdown. (#5700)
  • ✅ cpd.home.layout.plr-beside-compliance — the Program-Level Requirements panel sits to the right of the Annual CPD compliance tile when there is room, and stacks below it on narrow viewports. † ‡ (#7779)
  • ✅ cpd.home.layout.hours-header-actions-wrap — the hours-update header row wraps its action(s) onto a new line on narrow viewports so the "Add activity" button is never clipped off the right edge on mobile. ‡
  • ✅ cpd.home.layout.not-customisable — the CPD dashboard is a fixed clinical layout (dual-ring wheel → hour-category breakdown → HLSR → activities accordion), NOT a reorderable widget grid, so the customise-dashboard edit mode (#8241/#8592) is intentionally NOT offered here: the category cards are filter pills bound to the activities accordion and the wheel is the clinical anchor, so reordering/hiding them would break the wheel→breakdown→drill workflow. Same fixed-design precedent as cpd.home.layout.wheel-centered-clickable and the wellness readiness cards.†‡ (#8592)
  • ✅ cpd.home.layout.greeting-first-name-only — the "Welcome Back, {name}" header greeting addresses the doctor by first name only, never first + last name, even when both are set on the profile. A self-facing greeting echoing the user's own surname back to them reads as hyper-personal. Mirrors the same rule already applied to the PPP Dashboard's rotating greeting (cpd-home.provider-framework.link-from-dashboard sibling surface, #7763/#8061). Derivation is the pure deriveUserFirstName helper (falls back to last name, then "User", if first name is absent) so the rule is directly unit-tested, not just asserted at the component. (#11984) † ‡

Suggested Plan visibility (5 May) ​

  • ✅ cpd.home.suggested-plan.hides-when-plan-exists — "Suggested Plan" CTA hidden when a current-year plan already exists (hasCpdPlan === true). The CTA lives in the CpdPlanNudgeBanner rendered on CPD Home; it returns null when the server-side cpdPlanNudge.getStatus reports shouldShow === false, and the nudge service short-circuits to shouldShow: false as soon as user.hasCpdPlan is true. Suggested-plan flow lives in cpd.md § CPD Plans. ‡ ‡

Verification display ​

  • ✅ Dual-ring wheel — outer ring = 50h annual target boundary (full circle track), inner ring = actual category hours. Outer ring fills faintly as total hours accumulate. Built 29 Apr. †

  • ✅ cpd.home.a11y.wcag-aa-contrast — every text/background pair on the CPD Home surface meets WCAG 2.1 AA (≥ 4.5:1) — including wheel labels, status chips, and the verified-vs-unverified treatment. Contrast audit added to the snapshot test gate (5 May).

  • ✅ Wheel tile / category click → scrolls to CPD Activities table, applies category filter, active card highlighted with primary border. Built 29 Apr.

  • ✅ cpd.wheel-verified-pastel — verified hours render as a lighter pastel arc on the inner ring; unverified/submitted render as a dashed saturated arc. Both share the same hue. CPD_WHEEL_PALETTE.<category>.verifiedPastel tokens added. Pastel split activates when status === 'verified' on activities; single-tone arc is the fallback. Built 29 Apr.

  • ✅ cpd.list-verified-single-colour — Category chip uses a single colour per category regardless of verification state (getCategoryChipColors in utils/misc-utils.ts:67 takes category only, no status). Verification signalled by separate status chip + icon. Issue closed as completed 28 Apr.

  • ✅ cpd.home.category-colours-single-source — All CPD category colours on the CPD Home surface (wheel, legend, category cards and the MO/RP/EA filter pills) derive from a single source of truth: SEMANTIC_COLORS.cpdCategory in themes/tokens.ts (documented at /brand/colour). CPD_WHEEL_PALETTE.<category>.primary/.fill derive from the tokens' dot/bg; the filter pills consume getCategoryChipColors. No CPD category hex is hardcoded on the surface, so the colours can never drift between the wheel, legend, grid chips and marketing. This fixed the Education (EA) filter pill rendering brand-blue instead of its green Education tone. Built 26 May (#7546). ‡

  • ✅ cpd.home.category-completion-state — Each Hour-category breakdown tile shows an unmistakable completion state once its accrued hours reach the tile's required minimum: a green completion tick plus the brand success colour (light-green tint background, success-green border and a fully-filled success-green progress bar). The completion flag is derived from the same hours >= softTarget threshold that fills the progress bar, so the tick can never disagree with the bar; a category still below its minimum shows neither tick nor success colour. Colours come from SEMANTIC_COLORS.status.completed (no hardcoded hex), reusing the same green tier as the verified/HLSR ticks. This is a per-category minimum-met indicator only — it does NOT imply overall CPD compliance (see cpd.home.compliance.wheel-full-does-not-imply-compliant). Surfaced in Kristin's demo-walkthrough feedback (29 May 2026). (#7910) † ‡

  • ✅ cpd.home.compliance.wheel-full-does-not-imply-compliant — reaching 50h on the wheel does NOT automatically set the user's compliance status to "compliant". Compliance requires: 50h logged AND CPD Plan submitted AND CPD Reflection submitted AND at least one Program-Level Requirement met (see cpd.home.compliance.plr-required-for-verdict). The wheel displays hour progress only; a separate "compliance status" indicator shows whether all four conditions are met. The status label must never say "compliant" when only hours are met. (22 Apr 2026) (#5954) † (#6363) ‡

  • ✅ cpd.home.compliance.plr-required-for-verdict — Program-Level Requirement (PLR) coverage is a required 4th condition of the annual CPD compliance verdict, not advisory: isCompliant is only true when hours + plan + reflection and at least one verified, unrejected PLR claim are all met. Before this AC, PLR coverage was excluded from deriveComplianceState entirely, so a user with hours + plan + reflection met but zero PLRs claimed was shown as compliant. "Met" mirrors the CpdWheelSection PLR ticks exactly — the same matchVerifiedPlrActivities matcher, so the compliance tile and the wheel's PLR ticks can never disagree. (2026-08-23) (#11046) † ‡

  • ✅ cpd.home.compliance.items-read-as-actions-when-unmet — Each row of the Annual CPD compliance card reads as an action to take while unmet ("Log 50 CPD hours", "Submit your CPD plan", "Submit your annual reflection") and only flips to a past-tense/ticked statement ("CPD Plan submitted", "Annual Reflection submitted") once the underlying record actually exists. An unmet criterion must never read as already completed — so the compliance card can never claim the plan/reflection is "submitted" while the action card beside it says "not started". The met/unmet flags are derived from the same deriveComplianceState source the action cards (RequirementTile hasPlan/reflectionSubmitted) read, so the two panels can never disagree on the same screen. (2026-06-24) (#9183) The reflection row carries no month suffix (#12834): the earlier "(Nov)" read as a November due date, but the reflection only opens in the Nov–Dec window and is due at the end of the CPD year. † ‡

  • ✅ cpd.home.compliance.follows-year-pill — the compliance sentence names the CPD year selected on the year pill ("Compliant for 2025" under the 2025 pill), never today's year, and the HLSR block's "Opens December" window is evaluated for that same selected year, so a past year does not show an "Opens December <this year>" pill. (#11192, Task 8 audit D-01/D-02, 2026-10-05)

  • ✅ cpd.home.activities-list.follows-year-pill — The CPD Activities list (the category accordion at the foot of CPD Home) is scoped to the selected CPD year, the same year pill that scopes the wheel and compliance tile (cpd.home.hours.year-pill-filter). Its per-category hour totals therefore match the wheel — a single category can never show two different figures (e.g. "6h" in the 2026 wheel vs "35h" all-time in the list). The list subtitle names the selected year explicitly ("&lt;year&gt; CPD activities and their verification status") so the scope is unambiguous. Activities with no date fall through to the selected year so a freshly-added activity stays visible. (2026-06-24) (#9184) † ‡

  • ✅ cpd.home.activity-master-list-matches-published — The CPD activity master list the product offers and awards hours from reproduces the published CPD Activities by Category and Hours (July 2026) table exactly: the same 101 activities, under the published spelling of each name, each mapped to exactly the category columns the published table marks it in, with its hours taken from whichever one of the two published hours columns carries a value. Three copies are held in step — the in-app constant, the public marketing copy and the backend seed the database is built from — because a divergence in any one of them changes what a doctor may claim. Two consequences are load-bearing rather than cosmetic: Surgical Meetings including M&M, Multidisciplinary etc is published in all four category columns, so it is claimable toward the Measuring Outcomes minimum (cpd.plan.category-minimums), and no activity is offered that the published table does not list, so hours can never be awarded for an off-list activity. Activity names are the strings that appear on an exported CPD record, so they must match the published list character-for-character for a regulator to reconcile an export against it. Conformance is enforced by a test, not by review: divergence in any copy fails the build. Since #11089, the UAT deploy seed scripts/seedCpdActivities.ts (via CPD_ACTIVITIES_SEED_LIST) is covered too — it previously seeded 13 off-list names outside this guard's reach. (#11040, #11057, #11089) † † † † ‡

  • ✅ cpd.home.unverified-chart — CPD Home displays an additional summary showing unverified/pending-verification hours as a distinct count separate from the verified arc. The unverified total appears as a numerical callout (e.g. "X hrs pending verification") so users understand how many hours still need provider sign-off to reach the verified target. (23 Apr 2026) (#5955)

  • ✅ cpd.home.unverified-per-category — Unverified/pending hours are surfaced as a per-category breakdown on the Hour-category cards — each category card with pending hours shows its own "X hrs pending verification" line — not as a single grouped total. The per-category pending figures are derived from the same current-year status === 'pending' activities the wheel headline uses (the Combined (MO + RP) card sums MO + RP pending, mirroring its hours derivation), so the sum of the per-card pending figures reconciles with the wheel's headline unverified total. Each pending figure is clamped to its category's total hours so a card never reports more pending than it has. (2026-06-17) (#8669) † ‡

  • ✅ cpd.home.verified-unverified-split — the CPD dashboard data (dashboardCpd.getCPDData) returns the counted hours split into two explicit fields, verifiedHours and unverifiedHours, that drive the verified arc and the pending-verification callout. Only activities with status verified contribute to verifiedHours; activities with status pending (with the provider) and the new unverified stage (provider replied, awaiting PPP — see cpd-activities.md § cpd.activity.status-model-unverified) both contribute to unverifiedHours. This makes the verified-vs-unverified treatment on the wheel (cpd.wheel-verified-pastel) and the pending callout (cpd.home.unverified-chart) accurate even after the provider has replied but PPP has not yet verified — a doctor's hours are not double-counted as verified until PPP signs off. † (#8765) ‡

  • ✅ cpd.home.hours-unit-clarity — Hours on the CPD Home dashboard are rendered with the unambiguous "hrs" unit, never a bare "h" suffix. A bare "h" (e.g. "0h") was misread as "Oh"/zero in Kristin's demo-walkthrough feedback. The wheel centre total, the wheel sub-label, the below-wheel callout, the per-arc hover tooltip, the activity-row hours, the accordion category chip and the per-section hour header all use the "hrs" unit. (#7909) † ‡

    • The same #7909 bare-unit regression survived in CpdComplianceTile's "Log 50 CPD hours" compliance row — it rendered a bare "30h" instead of "30 hrs so far". Fixed to use "hrs" consistently with the rest of the surface. (#12661; code:instances/ppp/src/modules/cpd/dashboard/CpdComplianceTile.tsx)
  • ✅ cpd.home.wheel.current-year-only — The CPD Home wheel reflects a single CPD year (annual 50h target), never cumulative hours across multiple years. The getCPDData query is scoped to a one-year date range (1 Jan → 31 Dec of the selected year), and the client-side verified/unverified hour memos are filtered to that same year, so a multi-year user's wheel total cannot exceed the annual target by summing prior years. The year defaulted to new Date().getFullYear() and was fixed; #8668 makes the year user-selectable via the year pill (see cpd.home.hours.year-pill-filter) while keeping the single-year scoping invariant intact. (#7511) † ‡

  • ✅ cpd.home.hours.year-pill-filter — The CPD hours (measuring-outcome) screen carries a standard year pill filter consistent with the pill styling used elsewhere. It defaults to the current CPD year and lets the doctor select a previous year (current year plus any earlier year they have activities in, newest first) so they can review or prove prior-year CPD for export. Changing the pill rescopes the getCPDData query date range and the verified/unverified hour memos to the selected year, so the wheel, compliance tile and category totals all recompute to the chosen year — including the plan/reflection compliance conditions (see cpd.home.compliance.conditions-follow-year-pill). Supersedes the always-current-year behaviour previously locked by cpd.home.wheel.current-year-only. (#8668) † ‡

  • ✅ cpd.home.compliance.conditions-follow-year-pill — When the doctor selects a previous year on the CPD hours year pill (cpd.home.hours.year-pill-filter), the hours/plan/reflection compliance conditions feeding deriveComplianceState recompute to the selected year, not just the hours: the plan condition (hasCpdPlan) is derived server-side for the selected year (getCPDData takes the year from the requested dateRange.endDate, falling back to the current year when no range is supplied) and the reflection condition (hasReflection) is scoped client-side to the reflection whose year matches the selected year. The Annual CPD Plan tile and Annual Reflection tile therefore also reflect the selected year. This closes a mismatch where the hours rescoped with the pill but the plan/reflection conditions still described the current calendar year. The PLR condition (cpd.home.compliance.plr-required-for-verdict) does NOT follow the year pill — matchVerifiedPlrActivities is computed over the full unfiltered activity list, mirroring the CpdWheelSection PLR ticks, which are likewise unfiltered by year; tracked as a known inconsistency, not addressed by this AC. (#8726) † ‡

  • ✅ cpd.home.wheel.excludes-combined-rollup — The wheel/score-card total hours exclude the synthetic Combined (MO + RP) rollup emitted by getCPDData. Because that bucket is itself MO + RP summed, including it in the total double-counts MO and RP (previously showed ~197h for a ~127h dataset). computeCpdScoreBreakdown filters the Combined bucket out of the total, the category aggregation and the donut segments. (#7511) † ‡

  • ✅ cpd.home.wheel.arc-tooltips — Each coloured category arc on the wheel exposes an accessible hover tooltip giving the category name plus hours and, when known, the verified/pending split (e.g. "Measuring Outcomes: 12h (8h verified, 4h pending)"). Rendered as a native SVG &lt;title&gt; element inside both the single-tone arc path and the verified-split arc group, with cursor: help. (#7514) † ‡

  • ✅ cpd.home.wheel.category-legend — A category colour legend (MO / RP / EA swatches + labels) is rendered with the wheel, restoring the doughnut legend from Matt's Moreton-vs-UAT design so users can map each arc colour to its CPD category. Swatch colours are driven by the same CATEGORY_CARDS palette the arcs use, so legend and arcs always match. (#7514) † ‡

CPD Activities panel — accordion by category (#7547 / Option C #7525) ​

  • ✅ cpd.home.activities.accordion-by-category — The CPD Activities panel on CPD Home renders the user's activities as an accordion grouped by CPD category — one collapsible section per real CPD category (Measuring Outcomes / Review of Performance / Education), replacing the previous fixed-height scrolling data grid. Each section header shows the category name, its total hours (sum of that category's activity points) and the activity count in the category's brand colour. The first non-empty section is expanded by default; the others start collapsed. The full sortable/filterable grid remains on the dedicated /cpd-activities page. † ‡
  • ✅ cpd.home.activities.no-plr-section — The accordion does not surface Program-Level Requirements (Cultural Safety / Professionalism / Addressing Health Inequities / Ethical Practice) as activity-category sections — Matt confirmed PLRs are not CPD categories. Any activity whose category is none of the three real CPD categories falls into a neutral "Other" group rather than an invented PLR section; the existing PLR ticks block elsewhere on CPD Home is unchanged. † ‡
  • ✅ cpd.home.activities.row-opens-activity — Each activity row inside an expanded accordion section shows the date, title/description, provider, hours and a verified/pending status badge, and is clickable (and keyboard-operable) to open the existing CPD activity view dialog. The verified/unverified and category filter pills narrow the accordion: a category pill expands/limits the panel to that section, the verification filter narrows the rows shown. † ‡

Reminders & escalation (scheduled — #6165) ​

Reminder scheduling logic, notification types, cadence, and deficit processor are specified in cpd.md § CPD Reminders & Notifications. APHRA breach list is in cpd.md § APHRA Escalation. This section covers only what the CPD Home dashboard surface displays.

Communication channel matrix (#6165) ​

All reminder types use in-app banner on CPD Home as the primary channel. Push notifications and email are noted as future scope and are not implemented in this iteration.

Reminder windowTriggerIn-app bannerPush notificationEmail
Plan reminder (January)User has no submitted CPD plan in January✅ PrimaryFuture scopeFuture scope
Pro-rata deficit (rolling)User is behind pro-rata hours at any time✅ PrimaryFuture scopeFuture scope
Fixed window — 1 OctDate-based: 1 October each year✅ PrimaryFuture scopeFuture scope
Fixed window — 1 DecDate-based: 1 December each year✅ PrimaryFuture scopeFuture scope
Fixed window — 17 DecDate-based: 17 December (final reminder)✅ PrimaryFuture scopeFuture scope

Approved copy (#6165) ​

Engineering-led draft copy approved 2026-05-13. Super Admin can edit live via super-admin.md § CPD Reminder Settings.

  • ✅ cpd.home.reminder-banner — When a reminder fires, it surfaces as a banner/notification on the CPD Home screen — positive tone, specific deficit + call-to-action. Engineering-led draft copy approved: (#6165)
    • Plan reminder (Jan): "Welcome to — set your CPD plan in a couple of minutes so we can track you toward your 50 hours. → Create plan"
    • Submission prompt — gentle (Jan): "You haven't started your plan yet. We'll keep this gentle for now. → Build my plan"
    • Submission prompt — moderate (Feb–Sep): "Your plan is still in draft. Locking it now means we can track progress automatically. → Submit plan"
    • Submission prompt — urgent (Oct–Dec): " ends in days and your plan isn't submitted. Submit now to stay compliant. → Submit plan"
    • Deficit prompt (rolling pro-rata): "You're hours behind your pro-rata target (%). Logging an activity takes a minute. → Log activity"
    • Fixed window — 1 Oct: "October is here — days remain in your CPD year. You have hours to log. → Log activity"
    • Fixed window — 1 Dec: "December has arrived — days until your CPD year closes. hours still to go. → Log activity"
    • Fixed window — 17 Dec (final): "Final reminder — your CPD year ends in days. hours remaining. Don't let it slip. → Log activity"
    • Milestone (25/50/75/100%): "You've reached % of your CPD target — / hours logged. Keep going."
    • Tone: acknowledges clinical workload, specific deficit/progress numbers, single primary CTA, no exclamation marks. All tokens drawn from the allow-list defined in super-admin.md § CPD Reminder Settings.
  • ✅ APHRA escalation is a Super Admin action implemented in cpd.md § APHRA Escalation. CPD Home itself has no work — when the Super Admin acts, the user receives the in-app notification through the existing notification pipeline; no dashboard widget required.

Resource Library & Compliance Forms (5 May) ​

The Resource Library, FAQ forum, Exemption form, and Appeal form sit on (or accessible from) the CPD Home surface. Engineering owns the link-test automation; ops owns the inbox routing.

  • ✅ cpd.home.resources.link-checker — every external resource link is health-checked weekly; broken links open a Super Admin todo (see super-admin.md). †
  • ✅ cpd.home.resources.faq-moderated — user-submitted FAQ entries land in a draft state and only render publicly after Super Admin approval. The approving surface is the moderation queue at /admin/faq-moderation, specified in cpd-support.md as cpd.support.faq-moderation-queue; without a reachable approving surface this AC's second half is unsatisfiable, which is how it stood until #11053. † ‡
  • ✅ cpd.home.resources.exemption-form-distinct — "Request an exemption" is rendered as its own form (not a dual-purpose form). Submissions route to exemptions@professionalperformanceportfolio.com via super-admin.md. †
  • ✅ cpd.home.resources.appeal-form-distinct — "Appeal program level" is rendered as its own form. Submissions route to appeals@professionalperformanceportfolio.com. †
  • ✅ cpd.home.user-guide-link — The User Guide is reachable from CPD Home as the "User Guide" item in the sidebar (every tier; useSidebarMenuClusters.tsx → /guide) and from the CPD Support pages; it is not a text link at the bottom of the page (the BDD scenario asserts the sidebar item). Re-point to a page-bottom link only if Matt asks. (#5832; corrected 5 Oct 2026, Task 8 reachability check)
  • ✅ cpd.home.user-guide.role-filtered — the user guide content at /guide is filtered by the user's role and subscription type. A CPD-only subscriber sees only the CPD-relevant guide sections; a full PPP subscriber sees all sections; hospital admin and super admin see their respective guide sections. Role detection uses the same profile-driven capability flags used elsewhere in the app. (23 Apr 2026) †
  • ✅ cpd.home.resources.instructional-videos-placeholder — Resource Library includes a placeholder section for instructional walkthrough videos (how to log an activity, how to submit a plan, etc.). Videos are not yet produced; the section is rendered with a "coming soon" state rather than hidden, so it sets user expectations and is easy to populate without a UI deploy. (23 Apr 2026) (#5961)
MVP Cut (23 Apr — Rob's action) ​

To hit 19 May demo, the following must be in MVP:

  • Dashboard fidelity (overall hours, Annual Plan, Annual Reflection, PLRs, High-Level Specialist)
  • Verified vs unverified display
  • Quick-add
  • Scope gating (no timesheet toaster, no setup wizard for full users)

Post-MVP (end-of-year functionality):

  • Reminder banners on CPD Home when deficit thresholds fire (logic in cpd.md) — channel confirmed: in-app banner; copy approved 2026-05-13 (#6165); UI implementation scheduled
  • Online-resource completion verification (parked)
  • PDF export/audit report (specified in cpd.md § CPD Report)
  • APHRA escalation (Super Admin screen in cpd.md #5604)
Status ​
Sub-featureStatusNotes
CPD wheel (50h total against annual target)✅ BuiltV2 #5588 — simple total ring per Matt 29 Apr
Per-category cards (MO / RP / Combined / EA)✅ BuiltV2 #5588 — MBB img-mbb-2 icon style (BarChart, School). Combined (MO + RP) 25h tile re-added #7357.
Annual CPD Plan tile✅ BuiltV2 #5588
Annual CPD Reflection tile (Nov-only enabled)✅ BuiltV2 #5588 — HIDDEN outside Nov–Dec window unless already submitted (#7522, Rob 2026-05-26); was previously a locked countdown tile. Compliance tile still tracks reflection year-round.
Quick-add bar at top of page✅ BuiltV2 #5588
Timesheet toaster suppression✅ BuiltV2 #5588
Setup wizard tier-gating✅ BuiltV2 #5588
Verified vs unverified display (wheel pastel split)✅ BuiltPastel inner arc (verified) + dashed outer arc (submitted). Fallback to single arc when no verified activities. #4958
Verification legend (✓ verified · ◌ unverified)✅ BuiltStatic key below the wheel — matches prototype design. Added 29 Apr round 2.
Category card click → filtered activity list✅ BuiltScroll + client-side filter + active card highlight. Q1 decision 23 Apr
Dual-ring wheel (target outer + hours inner)✅ Built29 Apr — outer ring = 50h target, inner ring = category arcs
HLSR block placeholder (consultant surgeons)✅ BuiltGated on userType=consultant AND isSurgeon. Full specialty mapping in #5600. Only non-integrated element on the page — intentionally deferred.
Local dev Docker services (Postgres + Redis)✅ Builtdocker-compose.dev.yml + scripts/local-services.sh. Eliminates Neon cold-start. Use bash scripts/local-services.sh up && migrate && seed then update Doppler dev DATABASE_URL + REDIS_URL.
Program Level Requirements block — 4 separate AMC ticks✅ BuiltV2 #7010 — four individually-labelled, individually-tickable AMC PLRs: Cultural Safety · Addressing Health Inequities · Professionalism · Ethical Practice (Professionalism and Ethical Practice are NOT combined). Read-only; driven by verified activity counts. AC cpd.home.plr.four-separate-ticks.
Annual Reflection November-only window✅ BuiltAC cpd-home.reflection.november-only. Tile HIDDEN outside Nov–Dec unless submitted (#7522); ACs cpd-home.reflection.hidden-out-of-window / .visible-in-window / .submitted-always-shows / .compliance-tracks-year-round.
AHPRA escalation human-gate✅ SpecifiedAC cpd-home.compliance.escalation-human-gate added. Super-admin review required before any automated AHPRA notification. Post-MVP.
Non-upload = non-compliance✅ BuiltCPD-Home-default flag (is_ppp_cpd_home, default true on registration) + supportive away/low-involvement nudge cadence built in #7295 (cpd-home.compliance.non-upload-is-non-compliance ✅). The AHPRA assumed-non-compliance escalation is now built behind the human gate (cpd-home.compliance.non-upload-as-assumed-non-compliance-escalation ✅, #7690): listEscalationCandidates classifies the AMC §3.2 persistent-non-engagement criteria (no plan >30d / nothing logged >60d / <25% by Aug, Matt-confirmed 2026-06-03), surfaces candidates with the supportive "requirement to comply to prevent AHPRA notification" framing, and notifies the PPP admin on each human-gated escalation.
RACS 65h consultant target with 10/40/15 split❌ RejectedMatt 29 Apr — never briefed; engineering pulled from RACS framework, removed
Combined (MO + RP) 25h tile✅ BuiltRe-added #7357 — wrongly removed 29 Apr; Matt re-confirmed Option A 2026-05-26 ("misinterpretation on what needed to be removed"). 4th breakdown card, derived MO+RP hours vs 25h hard AHPRA minimum. Now applies a combined MO OR RP filter on click (#7750).
High-Level Specialist Requirements block✅ BuiltHlsrBlock implemented in CPDHomeV2 (#5600). Specialty mapping from constants; tick driven by ANZASM activity log. Zero-assigned = auto-pass. Manual submission path; API integration deferred.
Speciality → high-level req mapping✅ ConfirmedMatt 28 Apr — full mapping table in issue
Reminder banners on CPD Home✅ ScheduledChannel confirmed: in-app banner (primary). Push/email future scope. Copy approved 2026-05-13 (#6165). UI implementation pending.
APHRA escalation⏳ Post-MVPSuper Admin screen in cpd.md #5604. Only dashboard surface: in-app notification to user after admin acts.
Exportable audit report⏳ Post-MVPSpecified in cpd.md § CPD Report. Not a cpd-home item.
CPD Activities accordion by category✅ Built#7547 — replaces fixed-height grid; one collapsible section per CPD category (MO / RP / EA) + neutral Other bucket; first non-empty section default-open; rows keyboard-operable, open view dialog. PLRs are not surfaced as accordion sections.
Online-resource completion verification❌ Parked"Can of worms"; revisit when AR glasses 😉

Open issues on label:feature:cpd-home (2)

#Title
#12847CPD Home compliance card: "Opens Nov" copy, reflection gating on compliance, and the stale PLR need a product decision (split from #12834)
#12855fix(bdd): CPD plan scenarios navigate to a stale "CPD Plans" sidebar label and never run (post-merge sentinel, PR #12848)

Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Change Log ​
DateChangePR/IssueReason
2026-10-05CPD Home follows the year pill end to end: the Annual CPD compliance sentence reads "Compliant for &lt;selected year&gt;" (it previously always named the current year) and the High-Level Specialist Requirements block evaluates its December window against the selected year, so a past year no longer shows an "Opens December &lt;this year&gt;" pill. The CPD plan page''s High Level Specialist Requirements box now lists the Super-Admin-managed requirements for the doctor''s specialty (the same rows CPD Home shows), falling back to the legacy per-speciality text only when none exist.#11192Task 8 audit of 5 Oct 2026 (D-01, D-02, D-04). Seed-only changes in the same lane: cpd_classes seed names now use the canonical PLR wording (Culturally Safe Practice / Ethics, #12150), and the cloud seed now includes CPD reminder settings, the activity-types master list, a provider magic link, a Stage 2 queue item, prior-year HLSR evidence and a trainee case awaiting sign-off so the recording steps can be shown.
2026-10-05The CPD Home Annual Reflection tile now follows the server window (year pill aware; 15 Nov, or 1 Dec for HLSR doctors; a past year is always open) instead of opening on 1 Nov for everyone. The User Guide entry point is the sidebar item, not a page-bottom link. Two stale @wip scenarios asserting a locked Opens in November tile were retired.#11192, #12956, #12957Task 8 reachability check of 5 Oct 2026 (items 1, 2, 28, D-16, D-18).
2026-10-04Super-admin PPP verification of a CPD activity tagged with a high-level requirement (verifyCpdUserActivityByPpp) now sets the doctor's per-year HLSR attestation (year = the activity date's year), so the CPD Home HLSR tick can turn green. The doctor still cannot set it themselves.#11192, #8715Matt (#8715, 17 Jun) said HLSR evidence goes "through our verification process like a regular CPD activity", but nothing ever called the attestation writer from the UI path, so the tick could never light. Assumption to confirm with Matt: any one verified HLSR-tagged activity completes the whole year''s tick (the tick is binary, "in their entirety"); no per-requirement tracking.
2026-10-04The CPD Home "Annual CPD Plan" tile no longer says "Not started" when the plan is saved as a draft: it reads "Draft saved — awaiting submission" with a "Continue →" CTA, from a new hasDraftCpdPlan signal. The tile still only ticks (Submitted / View →) for an established plan; hasCpdPlan is unchanged.#12603Found on UAT during the #10561 B2C walkthrough: a saved draft (Awaiting Submission) still read "Not started". Prototype decision Q5 ("Not started until ticked") is kept for the no-plan case; a draft is started but not submitted, so it gets its own unticked label.
2026-10-04The Annual CPD compliance card''s reflection row no longer carries a "(Nov)" suffix ("Submit your annual reflection" / "Annual Reflection submitted"), matching the labels this spec already lists for cpd.home.compliance.items-read-as-actions-when-unmet.#12834The suffix read as a November due date, but the reflection only opens in the Nov–Dec window and is due at the end of the CPD year. The requested "Opens Nov" wording, gating the reflection on compliance and the unidentified stale PLR are not in this spec and need Matt, so they are not changed here (split to a follow-up issue).
2026-10-03The CPD Home away nudge now requires an account older than the 60-day away threshold (DEFAULT_AWAY_THRESHOLD_DAYS, read from users_view.created_at). A doctor with no CPD activity no longer counts as "away" from the day they register.#12775, #12759Review of PR #12775: once the nudge ran daily, a doctor who registered that day (no activity yet, so lastActivityDate is null) would be nudged at the next 22:00 UTC run. Matt on #6362 (2026-05-19) describes the trigger as 'low involvements or extended time away', which a brand-new account cannot have.
2026-10-03The supportive CPD Home away/low-involvement nudge (processCpdHomeAwayNudges) now runs on a registered daily schedule (22:00 UTC, CPD_HOME_AWAY_NUDGE_TICK) via registerScheduledJob, with the boot-time armed self-check. Previously its only caller was an admin-only tRPC procedure, so no doctor received it automatically. Built in #12759.#12759Matt on #6362 (2026-05-19): friendly 'haven't seen you in a while' reminder for low involvement or extended time away. The spec AC was marked built (#7295) but the sweep had no scheduled caller — same shape as #11104.
2026-10-03Task 8 spec refresh. New § Annual lifecycle coverage maps each clause of Matt's #11192 brief to the existing ACs. The HLSR consultant-only scope now also cites Matt's 2026-07-14 confirmation. New Open Question Q13: does compliance need at least one PLR or an activity in each PLR? Matt's Notion brief and the published policy plus Rob's 2026-08-11 decision disagree. notion-last-synced set to 2026-10-03 (page last edited 2026-05-05; nothing new since the last sync). No AC changed.#11192, #11046, #12150Async Task spec refresh (#11192). The dated ledger turned up no Matt statement that changes a CPD Home AC since the 2026-10-01 Task 8 audit (PR #12662). WhatsApp has nothing on CPD Home behaviour. The 2026-08-30 and 2026-09-01 CPD-home-only screenshot remarks are about marketing screenshots, not the app. Spec-only, no BDD.
2026-10-01CpdComplianceTile''s compliance-row label ("Log 50 CPD hours") now reads "30 hrs so far" instead of a bare "30h" — the exact misread-as-"Oh" bug #7909 fixed elsewhere, which had survived in 3 spots written after #7909 closed.#12661Found live during the Async Task 8 CPD Home Lifecycle audit (#11192) — confirmed via DOM text before/after on /cpd-dashboard. No AC text changes; this restores the already-documented "hrs" unit convention (#7909) rather than altering it.
2026-09-15The cpd_classes half of the PLR canonical-wording rename shipped as migration 0246_cpd_classes_plr_wording_correction, so the seeded row names now match PLR_CANONICAL_NAMES exactly.#12222, #12150, #7647cpd.home.plr.canonical-label-consistency noted the legacy PLR class/category row names would stay as categoryNames aliases until the DB rows were renamed. 0246 renames the cpd_classes rows; the front-end categoryNames aliases are retained only until the migration has applied to prod as well as UAT (#12236). The marketing /information exception in the same AC is unaffected — it is blocked on Kristin's source PDFs, not on this rename.
2026-09-14The legacy categoryNames PLR aliases (cpd.home.plr.shared-source) and the plrClaims-tag matcher (activityClaimsPlr) now correctly tolerate the pre-#12150 seeded wording ("Cultural Safety" / "Ethical Practice") alongside the corrected canonical names ("Culturally Safe Practice" / "Ethics"), restoring the CPD Home tick, CpdWheelSection, and CPD User Activities report chips for activities/categories still carrying the old wording.#12225, #12224, #12209, #12150, #12181, #12222#12150 renamed PLR_CANONICAL_NAMES but the positional destructuring in program-level-requirements.ts made the categoryNames alias arrays self-referential, silently dropping the actual legacy row names they were meant to alias — found via code review of #12223 (filed as #12224) and confirmed live in #12219's CI. A related plrClaims-matching bug (activityClaimsPlr compared only against the new canonical name) was found and fixed in the same PR. No acceptance criterion changed — this restores the already-documented alias behaviour rather than altering it.
2026-08-29CPD Home's "Welcome Back, {name}" header greeting now addresses the doctor by first name only. Previously it rendered the full name (first + last) whenever both were set on the profile. Added the new cpd.home.layout.greeting-first-name-only AC and the pure deriveUserFirstName helper backing it.#11992, #11984Matt Randell's explicit instruction (2026-08-25 call): a self-facing greeting must never echo the user's surname back to them — it reads as hyper-personal. That instruction had previously only been implemented as a marketing-screenshot image edit (PR #11809/#11817), never actually fixed in the live app. Mirrors the rule already applied to the PPP Dashboard's rotating greeting (#7763/#8061).
2026-08-23Program-Level Requirement (PLR) coverage is now a required 4th condition of the annual CPD compliance verdict (deriveComplianceState.ts / CpdComplianceTile), alongside hours, plan, and reflection. Previously PLR coverage was excluded from the verdict entirely.#11744, #11046Appendix 1 of the Assessment and Recognition of CPD Activity Policy reads "Must meet the minimum CPD Requirement and at least one of the below" — a hard requirement, not advisory. Found by the policy-to-code conformance audit (#11022); scoped and decided mandatory by Rob on #11046 (2026-08-11), matching the pattern set on #11041/#11044.
2026-07-27Adds cpd.home.activity-master-list-matches-published: the CPD activity master list the product offers and awards hours from reproduces the published "CPD Activities by Category and Hours (July 2026)" table exactly — the same 101 activities under the published spelling of each name, each mapped to exactly the category columns the published table marks it in. Two consequences are load-bearing rather than cosmetic: "Surgical Meetings including M&M, Multidisciplinary etc" is published in all four category columns and is now claimable toward the Measuring Outcomes minimum, and no activity is offered that the published table does not list (the off-list 102nd row "Multi-Source Feedback" is gone). The in-app constant, the marketing copy and the backend seed are held in step by test.#11082, #11040, #11057A policy-to-code conformance audit (#11022) found the product had drifted from the published table in six places, none visible because nothing compared them. The live harm was #11040: Measuring Outcomes carries a hard 5-hour minimum enforced at plan lock, and the mark had been dropped from the one row the published table marks in all four categories — so a practitioner attending routine surgical M&amp;M could not claim it toward a minimum the published table says they can. Activity names are the strings that appear on an exported CPD record, so a regulator reconciling an export against the published list got no exact match on nine of them. The spec records what the product promises, so it has to move with the correction rather than describe the pre-audit behaviour.
2026-07-27cpd.home.resources.faq-moderated now names its approving surface — the Super Admin moderation queue at /admin/faq-moderation, specified in cpd-support.md as cpd.support.faq-moderation-queue — and carries a code citation for it.#11079, #11053The AC read ✅ while only its first half was true. Entries did land in a draft ('pending') state, but ModeratorInterface — the screen that approves them — was imported by nothing: no route, no nav entry, a repo-wide grep returned only its own definition. Approval was unreachable, so the queue could never be drained and the member-facing "it will appear here once approved" copy was a promise the product could not keep. An AC asserting "after Super Admin approval" with no cited path to the approving screen is unfalsifiable; the code citation is the evidence the original entry lacked.
2026-07-26Recorded a tracked EXCEPTION under cpd.home.plr.canonical-label-consistency — the marketing /information policy pages no longer satisfy it, because #11028 publishes Kristin's finalised July 2026 policy PDFs verbatim and those PDFs use the paraphrased PLR wording the AC forbids ("Culturally Safe Practice", "Maintaining Professionalism", "Addressing Health inequities", "Health Inequities", "Ethics"). No code and no in-app surface changed; PLR_CANONICAL_NAMES and every consumer of it are untouched.#11028, #11022, #11024The AC asserted that NO surface uses the older wording, and named those exact strings. That became false the moment the policies were published, so leaving it unqualified would have left the governing spec contradicting the live site. Engineering deliberately did not reword a controlled regulatory document AMC is about to read — #11024 is the open decision for Matt (correct the source PDFs and re-transcribe, or carve a verbatim-transcription exception into this AC).
2026-06-24Added AC cpd.home.activities-list.follows-year-pill — the CPD Activities category accordion is scoped to the selected CPD year (the same year pill as the wheel + compliance tile), so a category never shows two different figures; the list subtitle names the selected year explicitly.#9219, #9184Demo rehearsal (2026-06-24) showed the wheel scoped to 2026 (Measuring Outcomes 6h) while the activities list showed all-time totals (Measuring Outcomes 35h), inviting "is it 6 or 35?". The list totals must follow the same year scope as the wheel.
2026-06-24Added AC cpd.home.compliance.items-read-as-actions-when-unmet — the Annual CPD compliance card renders each row as an action to take ("Submit your CPD plan") while unmet and only flips to past-tense/ticked ("CPD Plan submitted") once the record exists, derived from the same deriveComplianceState source the action cards read.#9216, #9183Demo rehearsal (2026-06-24) surfaced the compliance card reading "CPD Plan submitted" (past tense) while the action card beside it read "Not started" at 0 of 3 complete — a contradiction. Unmet criteria must read as actions, not completed statements.
2026-06-23The CPD Home Annual CPD-plan review tile now rolls the completed review into the yearly appraisal + PDP. On completion handleComplete chains start → complete → rollIntoAppraisal (appraisalWorkflow.rollIntoAppraisal), creating the yearly appraisal and linking it without merging ("two separate things, linked"); the success snackbar reflects the roll-in. AC cpd-home.annual-cpd-review-tile extended with the roll-in delegation and cross-references appraisals-wba § review-rolls-into-appraisal.#9164, #9094appraisals-wba S3 (#9094, #8178) wires AnnualCpdReviewTile.tsx (owned by cpd-home) to the appraisal roll-in. The component change is behavioural (extra mutation + new success message), so cpd-home.md must record it for the spec-drift gate. The full crossover AC lives in appraisals-wba.md (Matt 2026-06-03).
2026-06-23CPD Home wheel sidebar now renders an Annual CPD-plan review RequirementTile (appraisals-wba S2) — doctor reviews last year's CPD plan and creates a new one; completing it drives the appraisals-wba S1 state machine not_started → in_progress → completed and logs the annual-review step. AC cpd-home.annual-cpd-review-tile added as a cross-reference to appraisals-wba.md.#9151, #9093AnnualCpdReviewTile.tsx lives in CPDHomeV2/components/ and CpdWheelSection.tsx wires it into the CPD Home wheel sidebar — cpd-home.md must record the surface-level AC so the spec-drift check passes. The full feature AC lives in appraisals-wba.md (Matt 2026-06-03, #8178).
2026-06-19AC cpd-home.compliance.non-upload-as-assumed-non-compliance-escalation flipped ⏳ → ✅. Added listEscalationCandidates (SA-only) classifying the AMC §3.2 persistent-non-engagement criteria (no plan &gt;30d / nothing logged &gt;60d / &lt;25% by Aug), a /admin/cpd-escalation-candidates review surface with the supportive "requirement to comply to prevent AHPRA notification" framing, and a cpd_aphra_escalation_admin_notice to all super admins on each human-gated escalation. Reuses the #7007 human gate and #7295 nudge cadence; no migration.#8911, #7690Matt confirmed the AMC-submission criteria (option 1), the supportive AHPRA-notification wording, and the admin-notify requirement on 2026-06-03 (#7690). Resolves the for-discussion threshold/tone that previously held this AC at ⏳.
2026-06-18The CPD Home hero panel now shows a single binary HLSR tick (complete / not complete), mirroring the PPP Dashboard CPD widget tick so both surfaces present the doctor's HLSR completeness "in their entirety". The per-requirement breakdown stays in the HlsrBlock separator box below, unchanged. The shared HlsrTickRow component (extracted from CPDProgressWidget) now renders on both surfaces — single source of truth. The tick is read-only and driven by the persisted per-user/per-year attestation flag (cpdHlsrAttestation.getStatus, scoped to the selected year pill); it is hidden for non-consultants, users with no specialty, or specialties with no HLSR obligation. New AC cpd.home.hlsr.simple-tick.#8842, #8732Matt described the widget UX explicitly in the 2026-06-17 Dev Session (~00:22:09-00:22:47): on both the PPP dashboard and the CPD home dashboard the widget should show just a tick box for whether the doctor is complete with their HLSR in their entirety, rather than the breakdown — the big box below keeps the breakdown. The PPP Dashboard tick already existed (#5969); this closes the gap by surfacing the same shared tick on the CPD Home widget.
2026-06-17HLSR verification/attestation window now opens in December of the CPD year. Before December the doctor self-submission flow is locked — the HLSR block surfaces an "Opens December [year]" pill (requirement text stays visible) and the backend cpdHlsrAttestation.setStatus procedure rejects an early self-attestation with a clear PRECONDITION_FAILED message. Super Admin verification (setForUser) is never blocked by the window. The dashboard HLSR tick remains grey until SA-verified (unchanged, Evidence Integrity Rule #8714). New AC cpd.home.hlsr.december-window.#8824, #8730, #8715Matt's decision in #8715 (2026-06-17 Dev Session, ~00:23:21): the HLSR evidence window must open in December — a doctor could otherwise complete HLSR activities in February, get the tick, then accumulate new outstanding items before the CPD year closes in December, gaming the requirement. Analogous to the CPD Plan Review / EOY Reflection window (opens November). Self-attest was already removed in #8714/#8743; this adds the time-gate to the preserved attestation API plus a lock/unlock UI on the HLSR block.
2026-06-17getCPDData now returns an explicit verified/unverified hours split (verifiedHours / unverifiedHours); both pending and the new unverified status count as unverified hours, only verified counts as verified (AC cpd.home.verified-unverified-split).#8768, #8765Operational provider-approval flow Matt greenlit 2026-06-16 (split from on-hold #7915). Keeps the wheel's verified arc and the pending-verification callout accurate after a provider has replied but before PPP has verified — hours are not counted as verified until PPP signs off.
2026-06-17Year pill now rescopes the plan and reflection compliance conditions, not just the hours.#8764, #8726Follow-up to #8668 found during /sgd:pr-review of #8722 — selecting a previous year rescoped the hours totals but the plan/reflection compliance conditions still reflected the current calendar year. getCPDData now derives the plan year from the requested dateRange and the reflection lookup is scoped to the selected year client-side.
2026-06-17Removed the self-attestation button from the HlsrBlock component. The HLSR block is now informational only — shows requirement heading and description text, no attestation UI (no button, no tick, no status label). Updated cpd.home.hlsr.manual-attestation AC to reflect removed-from-UI status. Updated the Evidence Integrity Rule HLSR row and exception note to record that self-attestation UI was removed pending the full evidence model design (#8660).#8743, #8714Self-attestation violates the Evidence Integrity Rule: ticks must be read-only indicators driven by verified data, not user toggles. The button was an interim measure from #7942. Removing the UI is the immediate fix; the proper HLSR evidence model is tracked in for-discussion issue #8660. Backend table and tRPC router are preserved; existing attestation records are untouched.
2026-06-17Unverified hours now break down per category on the Hour-category cards (cpd.home.unverified-per-category), not a single grouped total#8669Dev Session 2026-06-16: pending hours were all grouped into one figure rather than shown per category; per-card pending figures reconcile with the wheel's headline unverified total
2026-06-17Added a standard year pill filter to the CPD hours (measuring-outcome) dashboard, defaulting to the current year with prior years selectable so the wheel, compliance and category totals recompute to the chosen year.#8668The CPD hours screen showed only the current CPD year with no way to scope to a previous year, so doctors could not review or prove prior-year CPD for export. Dev Session 2026-06-16 (lines 402-431) — Rob+Matt agreed to "put the standard pill filter so it's consistent across screens … default to the current year, but have the option to select previous years and different periods." This makes the year user-selectable, superseding the always-current-year wheel scope (#7511).
2026-06-10Record the deliberate decision NOT to offer the customise-dashboard edit mode (#8241/#8592) on the CPD dashboard. Adds cpd.home.layout.not-customisable.#8619, #8592Cascade of #8241 asked for the customise edit mode on every page with a widget grid. The CPD dashboard (CPDHomeV2) is a fixed clinical layout — dual-ring wheel → hour-category breakdown → HLSR → activities accordion — whose category cards are filter pills bound to the activities accordion and whose wheel is the clinical anchor; reordering/hiding them would break the wheel→breakdown→drill workflow. Same fixed-design precedent as cpd.home.layout.wheel-centered-clickable and the wellness readiness cards, so the framework is intentionally not adopted here (judged per the issue's widget-vs-fixed-chrome guidance).
2026-06-10Split 2047-line CPDHomeV2/index.tsx into single-responsibility section + component files (sections/, components/, cpdHomeConstants.ts) — behaviour-locked refactor, zero functional change.#8584, #8222index.tsx was a 2047-line monolith tripping the max-lines / max-lines-per-function lint warnings; decomposing it makes each section independently navigable and reviewable and mirrors the just-merged PPP-dashboard split (PR #8516, #8221). The guided-tour anchor, every data-ac/data-tour/data-testid/section-id/aria attribute, the localStorage key shapes and the exact render + hook call order are preserved.
2026-06-10Narrowed code-paths: packages-shared/ppp/src/constants/** → cpd-*.ts + hlsr.ts + program-level-requirements.ts#8483, #8481The whole shared-constants dir (wellness, timesheets, pricing, EPA…) false-tripped the drift gate against cpd-home on every non-CPD constant edit (e.g. #8449)
2026-06-03Align the four AMC Program-Level Requirement labels to one shared canonical source across CPD Home, the plan-suggestions banner, CPD Support guidance and the marketing site.#8296, #7647The labels had drifted ("Health Inequities" / "Culturally Safe Practice" / "Maintaining Professionalism") because the backend plan-suggestions service kept its own hardcoded copy; hoisting them into PLR_CANONICAL_NAMES (@ppp-org/ppp/constants) makes recurrence impossible. Legacy DB category/class names deferred to #7646 PR2 (tracked in #8290).
2026-06-02CPD Home PLR ticks now derive from the activity's plrClaims tags (claim/tag model, gated by !isPlrRejected), not category-name matching; category-name retained as a fallback until the #7646 PR2 data migration.#8091, #7646Matt (#7525) — "PLRs are a claim/tag on an activity within MO/RP/EA and NOT A CATEGORY OF THEIR OWN." PR1 switches the tick derivation; the spec-drift gate correctly flagged the CPDHomeV2/index.tsx behaviour change against cpd-home.md.
2026-06-02CPD Home now surfaces the dashboard onboarding checklist (OnboardingChecklist) for CPD-only users instead of the removed Outstanding-Onboarding banner.#8049, #8027Part of #8027 (remove Phase 2 Setup Wizard). The OnboardingOutstandingBanner was deleted and onboarding consolidated into the dashboard checklist, which is now mounted on CPD Home (CPDHomeV2).
2026-06-01CPD Home category breakdown tiles now show a clear completion state once a category's accrued hours reach its required minimum — a green completion tick, a light-green tint background, a success-green border and a fully-filled success-green progress bar, plus a data-complete attribute. A category still below its minimum shows neither tick nor success colour.#8001, #7910Surfaced in Kristin's demo-walkthrough feedback (29 May 2026, sent to Matt + Rob) — when a user reaches a category's required minimum it was not obvious the requirement was met. The completion flag reuses the existing hours-vs-softTarget threshold that fills the progress bar (no duplicated logic) and the brand SEMANTIC_COLORS.status.completed green tier (no hardcoded hex). It is a per-category minimum-met indicator only and does not imply overall CPD compliance.
2026-06-01The four AMC Program-Level Requirement (PLR) definitions and the verified-match / provider-rejection (isPlrRejected) logic behind the CPD Home dashboard PLR ticks were extracted into a single shared constant, constants/program-level-requirements.ts, now consumed unchanged by both the dashboard and the CPD User Activities report Program Requirements chips. The dashboard tick behaviour is unchanged — this is a pure extraction so the two surfaces cannot drift on what counts toward a PLR.#7992, #7945A screen-by-screen review (#7945) found the report Program Requirements chips reading "0 hrs (0)" while the CPD Home dashboard correctly ticked the same PLRs 1/1 for the same user, because the report grouped by the legacy cpd_classes dimension and the dashboard keyed off cpdCategory.name. Sharing one PLR definition removes the divergence at its root. The dashboard side is a mechanical refactor only (new AC cpd.home.plr.shared-source documents the shared source); the behavioural fix lives in cpd-report.md (cpd.report.program-requirements.real-counts).
2026-06-01HLSR manual attestation — the doctor self-attests "I have met my HLSR" per CPD year via a control in the CPD Home HlsrBlock; the attestation is persisted per user/per CPD year (DB-backed) and the completion tick turns green only once attested, staying honestly pending otherwise. Provider may optionally confirm or clear it. Recorded the HLSR exception to the Evidence Integrity Rule.#7942, #7579, #7577Surfaced by #7577 — the HLSR tick had no backing data source (speciality.requirements is free-text only, no attestation flag / completion date / ANZASM log / activity→requirement link). Locked decision (Rob, 2026-06-01 SGD grooming) chose Option (a) manual attestation over derived completion (Option b, deferred). The self-attestation is an explicit audited affirmation, not a silent client toggle, so the Evidence Integrity Rule gets a documented HLSR exception rather than a silent divergence.
2026-06-01The CPD Home hours-update header row now wraps its action(s) onto a new line on narrow viewports (flexWrap + rowGap + minWidth:0/maxWidth:100%), so the "Add activity" button is never clipped off the right edge on mobile.#7925Incidental mobile-responsiveness fix carried in the onboarding tidy-up PR — on narrow screens the header action button could be clipped off-screen. Documented here so the CPD Home spec stays in sync with the layout change.
2026-06-01Hours on the CPD Home dashboard now render with the unambiguous "hrs" unit (wheel centre total + sub-label, below-wheel callout, per-arc hover tooltip, activity-row hours, accordion category chip, per-section hour header) instead of a bare "h" suffix.#7920, #7909A bare "h" hours suffix (e.g. "0h") was misread as "Oh"/zero in Kristin's demo-walkthrough feedback; "hrs" removes the ambiguity.
2026-05-27On CPD Home, the Annual CPD compliance tile and Program Level Requirements panel now sit side by side as equal-width columns on wide viewports and stack on narrow ones, with the Annual CPD Plan and Reflection tiles below them.#7797, #7779Requested by Rob for the investor/legal demo so the dashboard uses the available horizontal space rather than leaving the compliance and PLR panels stacked in a single narrow column. Pure layout change preserving the compact CPDHomeV2 aesthetic and the existing #5700 layout invariants.
2026-05-27PLR panel sits to the right of the Annual CPD compliance tile when there is room (responsive lg row), stacking on narrow viewports.#7779Rob — make the Program Level Requirements panel and Annual CPD compliance dynamic so the former sits to the right of the latter when space allows, preserving the compact CPD Home aesthetic.
2026-05-27Combined (MO + RP) hour-category tile now filters the CPD Activities panel — clicking it narrows the accordion to the Measuring Outcomes and Review of Performance sections (an OR-set) and lights its active-state border like the other tiles, instead of looking clickable but doing nothing.#7754, #7750The Combined tile is a synthetic MO + RP bucket with no single CPD category, so it was previously non-filtering — clicking it had no effect, which read as broken UX during investor-demo prep. A sentinel filter resolves the tile into the two real categories so it behaves consistently with MO/RP/EA.
2026-05-27Reword the Annual CPD Reflection Core-AC from "November-only enabled state" to the shipped hide-not-lock behaviour (tile hidden outside Nov–Dec unless submitted), and refresh nine stale ‡/code: code citations to the current index.tsx symbol locations after #7557/#7558 reshuffled the file and extracted deriveComplianceState.#7752, #7743Post-merge residue from #7560 — four of the five flagged items reconciled themselves as the six CPD PRs landed; the remaining two (stale Reflection wording + drifted citations) are docs-only. The AC-index validator only checks src: citations, so the drifted ‡ lines were not auto-caught.
2026-05-26Centralise the canonical "has a CPD plan" signal behind one shared backend helper (hasEstablishedPlan / establishedPlanCondition) routed through by the Annual CPD Plan tile, onboarding, CPD Plans tab and profile/to-do surfaces.#7622, #7486, #7346Four readers each defined "has a plan" inline and were behaviour-equivalent only by accident of reachable statuses; consolidating prevents silent divergence (the #7346 bug class) once new statuses become reachable (#4839).
2026-05-26Single-sourced the CPD category colours on the CPD Home surface. CPD_WHEEL_PALETTE now derives its per-category primary/fill tones from SEMANTIC_COLORS.cpdCategory (themes/tokens.ts, /brand/colour) instead of re-declaring the same hex, and the MO/RP/EA category filter pills are driven by getCategoryChipColors. Added AC cpd.home.category-colours-single-source. Also moved the "{year} · target {n}h annual" subtitle onto the same row as the "Overall Yearly CPD Requirements" heading to save vertical space.#7557, #7546Brand colours already live in SEMANTIC_COLORS.cpdCategory; the wheel held a second hardcoded copy, and the CPD Home filter pills had their own hardcoded hex which left the Education (EA) pill rendering brand-blue instead of its green Education tone. Deriving from one source removes the drift and fixes the EA pill colour. Resolved hex values are unchanged, so the wheel/legend/cards are visually identical.
2026-05-26Replaced the scroll-bar CPD Activities grid on CPD Home with an accordion grouped by the three CPD categories (Measuring Outcomes / Review of Performance / Education); rows open the existing activity view dialog. PLR categories are not surfaced as sections.#7547, #7525Matt selected Option C on #7525 — the fixed-height scrolling grid was hard to read on the dashboard. PLRs are not CPD categories, so unrecognised activities fall into a neutral "Other" group rather than an invented PLR section. The full sortable grid stays on /cpd-activities.
2026-05-26Annual CPD Reflection tile is now HIDDEN outside its Nov–Dec window unless a reflection was already submitted, instead of rendering a locked "Opens in November · N months away" countdown year-round. Added ACs cpd-home.reflection.hidden-out-of-window, .visible-in-window, .submitted-always-shows and .compliance-tracks-year-round; modified cpd-home.reflection.november-only to reflect the hide-rather-than-lock behaviour. Removed the dead monthsUntilReflection helper.#7529, #7522Rob (2026-05-26): "...take up the space with Annual CPD Reflection for 12 months when it is only available at the end of the year." The reflection tile should not occupy CPD Home sidebar space for ~10 months a year when the feature is only fillable Nov–Dec. The CpdComplianceTile continues to track the reflection requirement year-round, so the compliance condition stays visible even when the tile is hidden.
2026-05-26Fixed the CPD Home wheel total (was ~197h): excluded the synthetic "Combined (MO + RP)" rollup from the breakdown total/aggregation/donut so MO+RP are no longer double-counted, and scoped the wheel to the CURRENT CPD year (annual 50h view) instead of summing every year. Restored the per-arc hover tooltips and the per-category colour legend (MO / RP / EA) on the wheel.#7523, #7511, #7514Rob-reported on the 2026-05-26 session: the annual wheel showed ~197h for a ~127h dataset (two stacked bugs — Combined double-count in computeCpdScoreBreakdown + a getCPDData query with no dateRange summing all years), and the wheel had lost its arc tooltips and Matt's designed per-category colour legend (moreton-vs-uat #img-designed-3). New ACs cpd.home.wheel.current-year-only, cpd.home.wheel.excludes-combined-rollup, cpd.home.wheel.arc-tooltips and cpd.home.wheel.category-legend cover the corrected behaviour, each with @regression BDD scenarios.
2026-05-26PPP becomes the user's official CPD Home provider by default on registration, plus a supportive away/low-involvement nudge cadence (friendly, never punitive).#7503, #7295Matt 2026-05-19 (#6362) — "Once a doctor registers with PPP we become their official CPD home unless they inform us otherwise. The doctors have a whole year to reach compliance. If they have low involvements or extended time away we can send a friendly reminder." The AHPRA assumed-non-compliance escalation is deliberately left on the existing human-gated path (#7007); threshold/tone remain for-discussion.
2026-05-26Flipped built ACs from ⏳ Specified to ✅ — cpd.home.plr.four-separate-ticks (four distinct AMC PLR ticks, Professionalism and Ethical Practice unlinked, #7010) and cpd.home.suggested-plan.hides-when-plan-exists (Suggest-a-Plan CTA hidden when hasCpdPlan === true), with real src: citations.#7474, #7313SGD "make the spec tell the truth" pass — these ACs were already implemented in CPDHomeV2 but the spec still showed them as pending. Left cpd-home.compliance.non-upload-is-non-compliance (#7295), the Combined MO+RP segment (#7468), and post-MVP items (APHRA escalation, audit report) untouched.
2026-05-26Annual CPD Plan tile implementation note clarified — hasCpdPlan now means an established (non-draft) plan exists (ne(status, 'draft')) and is the single canonical signal shared by the tile, the onboarding checklist and the CPD Plans tab. A bare draft row no longer counts as "has a plan" on any surface.#7471, #7346Bug #7346: the onboarding widget ticked the CPD-plan step COMPLETE off any row (including a bare draft), while CPD Home and the CPD Plans tab only counted a finalised plan — so the three surfaces disagreed for a user who started but never locked a plan. The fix aligns onboardingService.getOnboardingStatus and dashboardService/cpd.getCPDData on the same ne(status, 'draft') filter. Only draft and locked are reachable today (submit auto-advances to locked, #4839), so behaviour is unchanged for end users — no acceptance criterion changed; the implementation note wording was updated to match the canonical signal and a @regression @issue-7346 scenario was added to cpd-dashboard.feature.
2026-05-26Re-added the Combined (MO + RP) 25h tile to the CPD Home Hour-category breakdown. Derived from summing MO + RP hours against the 25h hard AHPRA minimum; non-filtering (scroll-only) card with a cpd-category-card-combined testid. AC cpd.home.combined-tile.#7468, #7357The Combined tile was wrongly removed on the 29 Apr call. Matt re-confirmed Option A on #7357 (2026-05-26: "Option A. I think this was misinterpretation on what needed to be removed"), so it is reinstated.
2026-05-22PPP provider accreditation badge design approved — light + dark PNG variants committed to brand kit and email-assets path.#7257, #6167AMC confirmed they do not issue badges to CPD Homes; PPP creates its own badge (horizontal pill, PPP emblem + "PPP ACCREDITED / CPD HOME PROVIDER") to grant to vetted external providers. Engineering wiring (enabling EMAIL_AMC_BADGE_ENABLED flag in Doppler) tracked in #6281.
2026-05-21Annual Reflection tile locked outside November–December window; fix comment (said October) and meta label (said "November only" → "Opens in November"); add smoke BDD scenarios for AC cpd-home.reflection.november-only.#7159, #7006, #6360AC was specified (⏳) but missing BDD coverage. Comment and locked-tile label were misleading — the 2-month window (Nov–Dec) was correct in code but not in the user-visible string or inline documentation.
2026-05-21BDD scenarios added for AC cpd-home.compliance.non-upload-is-non-compliance — registration enrols user as official CPD Home; low-engagement triggers supportive nudge, not a punitive flag.#7148, #7008AC was ⏳ Specified (no scenarios). Adds @smoke and @regression coverage traceable to Dev Session 2026-04-23 §CPDHomeRegulator (~00:57:53) and Matt's confirmation on #6362.
2026-05-21AC cpd-home.compliance.escalation-human-gate marked ✅ — BDD @smoke scenarios added confirming no AHPRA notification fires without a super-admin pre-notification review step. Implementation already existed via cpd_aphra_pre_notification table, assertPreNotificationWindowElapsed server-side gate, and CpdAphraPreNotificationPanel SA UI (#5960).#7007AC was ⏳ Specified with no BDD coverage. Closes the spec gap; traces to Dev Session 2026-04-23 §ComplianceEscalation (~00:55:31) and Matt's confirmation on #6361.
2026-05-21Removed "fee, waivers" from the cpd-home.provider-framework.public-page AC. The how-to-apply process now reads "email, timeframes" only.#6968, #6964PR #6956 removed the hardcoded $330 provider fee and fee-waiver rows from /cpd-provider-framework. The spec was drifting from the rendered page — this aligns the AC with the implementation.
2026-05-20Verified AC cpd.home.compliance.wheel-full-does-not-imply-compliant — flipped ⏳ → ✅#6363, #5954Negative AC already satisfied by CpdComplianceTile (#5954). deriveStatusSentence in CpdComplianceTile.tsx:53-65 only emits a "compliant" sentence when compliance.isCompliant is true, and deriveComplianceState in CPDHomeV2/index.tsx:516-527 requires all three of hours, plan, and reflection independently — so hitting 50h on the wheel cannot flip the user to compliant. Regression test at CpdComplianceTile.test.tsx:74 ("NEVER says compliant when only hours are met") guards this. Linked existing BDD smoke scenarios in cpd-compliance.feature with @issue-6363.
2026-05-19Close gap #6366 — cpd.home.resources.appeal-form-distinct flipped ⏳ → ✅. "Appeal program level" was already delivered as its own standalone form under #5687 (instances/ppp/src/modules/Support/CPDSupport/components/AppealForm.tsx, rendered via the dedicated requestReviewAppeal modal section with its own heading, Decision Reference + Grounds for Appeal fields, and own Submit button — fully separate from ExemptionForm.tsx / the requestExemption card). Spec-drift only: AC marked complete; added @regression @issue-6366 BDD scenario in cpd-home.feature proving the appeal program level form renders distinctly with its dedicated fields.#6585, #6366Implementation pre-existed (#5687) but the cpd-home AC was still ⏳ and #6366 (gap-analysis follow-up) was open. No new product code. Mailbox routing (form type "appeal" → appeals@professionalperformanceportfolio.com) is enforced server-side in complianceFormService and unit-covered.
2026-05-19Close gap #6365 — cpd.home.resources.exemption-form-distinct flipped ⏳ → ✅. "Request an exemption" was already delivered as its own standalone form under #5687 (instances/ppp/src/modules/Support/CPDSupport/components/ExemptionForm.tsx, rendered via the dedicated requestExemption modal section and its own grid card, fully separate from AppealForm.tsx / the requestReviewAppeal card). Spec-drift only: AC marked complete, added @regression @issue-6365 BDD scenario in cpd-home.feature proving the exemption form renders standalone with no appeal-program-level fields.#6570, #6365Implementation pre-existed (#5687) but the cpd-home AC was still ⏳ and #6365 (gap-analysis follow-up) was open. No new product code. Mailbox routing (form type "exemption" → exemptions@professionalperformanceportfolio.com) is enforced server-side in complianceFormService and unit-covered in api/backend-ppp/src/services/complianceFormService/index.test.ts; documented in docs/features/super-admin.md.
2026-05-19Close gap #6364 — cpd.home.resources.link-checker flipped ⏳ → ✅. The weekly resource-library link health-check was already delivered under #5681 (resourceLinkCheckService + run-resource-link-check.ts job on cron 0 22 * * 0, migration 0070 + validate.sql, infra wiring in api/infra-azure/src/index.ts). Spec-drift only: AC marked complete, added @regression @issue-6364 BDD scenario in cpd-resource-library.feature.#6498, #6364Implementation pre-existed (#5681) but the cpd-home AC was still ⏳ and #6364 (gap-analysis follow-up) was open. No new code — every active ppp_resources URL is HEAD-checked weekly; non-2xx/unreachable links raise a resource_link_broken super_admin_todos row, idempotent per ISO week. Unit coverage: api/backend-ppp/src/services/superAdminService/resourceLinkCheckService.test.ts.
2026-05-19Resolve 3 on-hold gap issues: (1) Annual Reflection window extended to November–December (2-month window, not Nov-only); (2) AHPRA escalation human-gate confirmed, framework documented in PPP CPD Home Information & Policies GDrive doc; (3) non-upload compliance refined — supportive prompts first (friendly nudges when low engagement), escalation only after persistent non-engagement.#6480, #6360, #6361, #6362Matt confirmed answers on 2026-05-19 via GitHub comments on #6360, #6361, #6362.
2026-05-13Confirm reminder channels and copy: in-app banner (primary) for all 5 reminder windows (Jan plan, rolling pro-rata, 1 Oct, 1 Dec, 17 Dec final); push/email noted as future scope. Engineering draft copy approved. Section moved from Post-MVP to Scheduled.#6216, #6165Product owner approval received 2026-05-13. Channel decision: in-app banner only for this iteration. AMC does not prescribe cadence; PPP product decision covers all 5 windows.
2026-05-06Tag AMC reciprocal API integration as out of scope for the Investor Demo 14 May 2026; deferred until AMC approval lands.#TBDDemo readiness — AMC reciprocal API was a "may adjust once approval lands" forward-looking note; explicit demo-scope tag prevents it being treated as in-flight work.
2026-05-06Drift re-baseline — per-PR changelog fragments added for #5702 (reminder banner) and #5703 (FAQ moderation) to close changeLogIssueRefs drift check.#5834, #5719Issue #5719 flagged that both issues were referenced in spec ACs as ✅ but had no corresponding Change Log fragments. #5702 reminder-banner AC and BDD scenarios shipped; #5703 FAQ-moderation AC marked ✅ with @wip BDD scenarios gating the unimplemented backend. Fragments added to close the changeLogIssueRefs drift check.
2026-05-06Mark HLSR block AC as ✅ built — HlsrBlock component implemented in CPDHomeV2 replacing "coming soon" placeholder.#5834, #5600HlsrBlock was already implemented (specialty-gated, read-only tick, ANZASM activity path). Q10 tick threshold resolved as "all assigned forms must be complete; zero-assigned = auto-pass" (cpd.md Q7). AC promoted from ⏳ to ✅ and Status table updated accordingly.
2026-05-06Reminder banner display on CPD Home — in-page banner surfaces unread CPD reminders with type, deficit/milestone, dismiss + CTA buttons; multiple reminders stack; user-dismissible per-reminder.#5729, #5702AMC CPD compliance UX — surfaces deficit/milestone prompts directly on CPD Home so users act promptly without leaving the page.
2026-05-06Lock dashboard layout & hierarchy — 50h header above PLR, EOY heading above CTA, PLR as h2 section heading, HLSR as h3 section heading, wheel centred and keyboard-clickable.#5700Matt called out these 5 layout invariants on the 5 May call. Drift now caught by @smoke/@regression BDD scenarios, not in production.
2026-05-06Add User Guide link at the bottom of CPD Home — overrides earlier exclusion note; link navigates to /guide.#5832Issue #5832 — Matt requested a User Guide link at the bottom of CPD Home. Earlier spec excluded it based on audience-gating assumption; this issue explicitly overrides that decision.
2026-05-05FAQ moderation — user-submitted FAQ entries default to draft state; public FAQ surface renders approved entries only; Super Admin console has approve/reject/edit actions with audit log per moderation action.#5738, #5703Content safety — unmoderated FAQ entries risk incorrect or harmful clinical guidance reaching users; gating on Super Admin approval mirrors the pattern established for User Guide audience-gated rendering (#5683).
2026-05-055 May call sweep — AMC provisional approval noted; Dashboard layout & hierarchy AC block (50h above PLR; EOY heading above its CTA; PLR heading larger; HLSR heading for consultants only; wheel centred + clickable); Suggested-Plan visibility AC (hides when plan exists); WCAG 2.1 AA contrast AC; Resource Library & Compliance Forms section (link-checker, FAQ moderation, distinct exemption + appeal forms); PLR block unlinks Professionalism from Ethical Practice (now 4 ticks); new Open Question Q11 for non-surgeon Procedural Log Book widget content.Apply Matt's 5 May call decisions plus the deltas surfaced against the existing Notion brief and 23 Apr session. PLR went from 3 labels (Professionalism + Ethical Practice combined) to 4 separate ticks per Matt's explicit request.
2026-05-05Transcript audit 2026-05-05 — §LinkedPractices classified R (requirement); 1 new AC added (cpd.home.plr.four-separate-ticks); 1 @wip BDD scenario added; Status table updated from ⚠️ Drift → ⏳ Specified. All other §§ were CONFIRM (already captured in cpd-home.md, cpd.md, or super-admin.md from prior sessions).#~§LinkedPractices (~00:07:01) of the 2026-05-05 Dev Session transcript ("CPD Home approval granted — billing enabled; dashboard, activities report, admin") confirmed that "Professionalism" and "Ethical Practice" must be rendered as two separate, individually- labelled ticks within the four AMC Program-Level Requirement items (Cultural Safety · Addressing Health Inequities · Professionalism · Ethical Practice). The prior Status table entry (⚠️ Drift, 5 May) documented this decision but no AC bullet existed in the Acceptance Criteria section — AC cpd.home.plr.four-separate-ticks now closes that gap. All other R/F passages (suggested-plan, WCAG, dashboard layout, activities report, file-upload MIME, resource library, exemption/appeal forms, logbook rename) were already captured in this or companion specs.
2026-04-29Documented HLSR/ANZASM data path from code archaeology: tick is driven by logged 'ANZASM Surgical case form' CPD activities (no external API needed). Added Q10 (tick threshold). Fixed duplicate HLSR heading. Updated code-paths. Corrected Evidence Integrity Rule HLSR row. Undeferred HLSR AC as #5600.#~, #5600Deep-dive on #5600 revealed that ANZASM activity types and specialty mapping already exist in the codebase (constants/cpd-activities.ts, settingsServices/ speciality.ts, CPDSpecialistAreas/data.ts). The data path does not require a separate ANZASM API integration — it reuses the existing CPD activity log. Only the tick threshold (≥1 form vs. all-forms-assigned count) needs Matt's confirmation (Q10).
2026-04-29Resolved Q4 (reminder cadence is a PPP product decision; proposed calendar windows documented). Updated escalation AC to PPP Super Admin breach list (#5604). Q5 updated with confirmed escalation mechanism.#5606, #5604Matt confirmed ~22 Apr 2026 that APHRA notification is PPP Super Admin initiated. AMC does not prescribe reminder cadence — engineering resolved Q4 with proposed windows (1 Oct, 1 Dec, 17 Dec).
2026-04-29Spec reorg — moved HLSR business logic, specialty mapping, ANZASM implementation details, and Q7/Q9/Q10 to cpd.md. Removed stale CAPE rows from Evidence Integrity table (rejected scope, 29 Apr).#5606cpd-home.md is the dashboard spec; cpd.md owns compliance rules and business logic. HLSR mapping, ANZASM activity types, tick logic, and the three business-rule questions were misplaced in the dashboard spec.
2026-04-29Built V2 CPD Home (CPDHomeV2 module) — wheel + Plan/Reflection tiles + per-category cards + activities table. Removed CAPE/PLR groups, RACS 65h consultant target, and "Combined" 4th category from spec and code. HLSR deferred until rules detailed.#5588Matt rejected CAPE/PLR/RACS scope on the 29 Apr catchup as items engineering had silently introduced from docs/compliance/RACS_CPD_FRAMEWORK.md rather than from his briefs. He re-stated the wheel rule simply — "if 50 hours have been reached, the progress wheel should be full, but the other requirements need to be ticked as well". Annual Reflection is November-only. Single long-lived feature branch shipping CPD Home V2 + PPP Dashboard CPD panel update together to UAT today.
2026-04-29Transcript audit 2026-04-29 — 3 R passages; all CONFIRM. CPD progress wheel specifics (50hrs = full, annual reflection Nov-only, consultant specialist requirements) are already in cpd-home.md from prior sessions. Prototype scrapped (process decision). Long-lived branch introduced (process). Apple developer DocuSign (operational). Out-of-scope items removed (AMC guidelines, "Kate groups", RSCS rules) are F (feedback on incorrect AI inference) — confirm existing cpd-home.md scope is authoritative.#~§CPDWheel (~00:11:26): "if 50 hours reached, wheel is full; other requirements must also be ticked" — CONFIRM (cpd-home.md has 50hr target and multi-requirement model). §AnnualReflection (~00:12:38): "Annual Reflection can only be filled in November" — CONFIRM (cpd-home.md). §ConsultantReqs (~00:12:38): "dashboard should reflect high-level specialist requirements for a consultant user" — CONFIRM (cpd-home.md specialist requirements AC). §OutOfScope (~00:02:46): Matt rejected "Kate groups", "RSCS rules", and AMC guidelines cross-reference as not agreed scope — F (confirms existing spec boundary; no new AC needed, but validates that cpd-home.md must not reference AMC guidelines unless Matt explicitly authorises). §PrototypeScrapped (~00:18:08): dev process decision, no product AC. §LongBranch (~00:24:20): operational/process.
2026-04-22Transcript audit 2026-04-22 — 4 R passages identified; all CONFIRM against existing specs. CPD progress wheel (one wheel with shading), WHO-5+PPP Pulse overlay, Timesheet widget (fortnightly, 10 default, submit-from-home), and Onboarding wizard priority are all already captured in cpd-home.md, wellness.md, dashboard.md, and timesheets.md from prior sessions. Documentation process (docs = source of truth, Notion = working thread) and B2B/B2C market definition are process/strategy — no product ACs. Multi-currency deferred is a product decision already reflected by AU-first builds throughout specs.#~§CPDWheel (~00:45:14): "simplify from multiple tiles to one wheel with shading to show minimum requirements" — CONFIRM (cpd-home.md has the one-wheel-with-shading AC from prior audit). §WHO5 (~00:39:14): "PPP Pulse widget overlaid with WHO-5 weekly questionnaire for trend analysis" — CONFIRM (wellness.md + dashboard.md). §TimesheetWidget (~00:48:47): "show entries completed for a fortnight (default 10), button to submit from home screen" — CONFIRM (timesheets.md / dashboard.md). §Onboarding (~00:35:01): "onboarding wizard is critical to ensure users know how to use the platform" — CONFIRM (onboarding.md). §B2BvsB2C (~00:27:08): "public user for B2C; enterprise user for B2B with admin seats" — strategy context, relevant to subscription + enterprise specs. §MultiCurrency (~00:54:00): "build for Australia initially, defer ability to split currencies" — CONFIRM (product decision; AU-first is already the default build approach). §DocProcess (~00:08:41): docs as fixed source of truth, Notion as working thread — C (process).
2026-04-21Transcript audit 2026-04-21 — all passages C or CONFIRM. No new ACs. Session was a post-Australia debrief covering SGD formally adopted as development model, 250 open issues identified, 4–7 week target, demo roadmap defined (CPD Home #1, Org Dashboard #2, Wellness #3). All product priorities already in specs. SGD adoption is a process decision, not a product AC.#~§SGD (~00:25:55): "Specification-Governed Design — build everything from specifications that clearly explain in English how the product will be built and tested; prevents code drift" — C (process decision, foundational methodology; the SGD protocol docs/_sgd-audit-protocol.md captures this). §DemoRoadmap (~00:29:03): "demo focus: CPD home, compliance with national prevocational framework, organisational insights, PGY1/PGY2 and unaccredited cohorts" — CONFIRM (already in cpd-home.md, organisational-dashboard.md). §IssueClustering (~00:07:53): "250 open issues, shift to grouped clustering" — C (operational). All other paragraphs are C (travel/jet lag, business engagement, Apple developer account, design tooling/Figma, schedule).
2026-04-15Transcript audit 2026-04-15 (08:07 BST) — all passages C or CONFIRM. No new ACs. Session was a strategic debrief after the Queensland Health CMO call (~$3.5M contract potential). The three product differentiators identified (CPD Home, Org Dashboard, Wellness algorithm) are already prioritised in their respective spec files. Demo scope planning and documentation strategy are process decisions, not product ACs.#~§QHEngagement (~00:07:56): "CPD home is the area of most interest to Queensland Health; securing the contract could generate ~$3.5M annually" — C (business context; CPD Home was already priority #1 in cpd-home.md). §DemoScope (~00:15:26): "three main points of differentiation: CPD home, organisational dashboard with insights, wellness data/algorithm" — CONFIRM (already captured as feature priorities across cpd-home.md, organisational- dashboard.md, wellness.md). All other paragraphs are C (funding extension, demo planning, documentation tooling, feature comparison analysis).
2026-04-22Spec created by splitting CPD Dashboard content out of dashboard.md. Placeholder pending 23 Apr scope call#5322Matt confirmed PPP Dashboard and CPD Home are two separate features on the 22 Apr call
2026-04-23Enriched from 23 Apr catchup: MB-gap list, MVP cut, APHRA escalation post-MVP, automations split to own specthis PR23 Apr deep-dive; CPD Automations split to cpd-automations.md
2026-04-28Added cpd.wheel-verified-pastel and cpd.list-verified-single-colour ACs; documented CPD_WHEEL_PALETTE.*.verifiedPastel tokens#4958Matt 28 Apr: verified hours use a lighter pastel palette in the wheel only — the list keeps a single category colour and signals verification via the existing status chip

Internal documentation — org members only