Skip to content

CPD Activities ​

Feature Overview ​

Logging, categorising, and verifying individual CPD activities: the master-activity-driven add form, the four AMC Program-Level Requirement categories, provider email verification, supervisory (multi-user) credit, and the activities list. Split out of cpd.md on 2026-05-27.

Open Questions ​

#QuestionWhy it is openRef
Q1Should the 16 "maximum per year" caps on the activities master list block a doctor from logging more hours for that activity, given the published July 2026 activities table has no maximum column?On the 29 Jul Dev Session (~00:28:01), going through the master list, you counted 16 activities with a value in the "maximum per year" column and agreed caps should be put in. Rob then checked the published table column by column (11 Aug): it has no maximum column. On 20 Sep, engineering stopped blocking submissions at the cap as an interim default (PR #12355), waiting for your decision. #11039 was closed by that PR, so the question had no tracker until now. The answer also decides the auto-scoring caps (cpd-automations.md Q7, #12742).#11039, transcript-2026-07-29

Acceptance Criteria ​

  • ✅ Master activity list drives the form — selects pre-fill fields

  • ✅ Activities categorised to match college CPD framework

  • ✅ cpd.categories.professionalism-ethical-split — the four AMC Program-Level Requirements (PLRs) are tracked as distinct, individually-tickable categories: (1) Culturally Safe Practice, (2) Addressing Health Inequities, (3) Professionalism, (4) Ethics. "Professionalism" and "Ethics" must never appear combined. Compliance rule: every doctor must complete at least one CPD activity aligned with each of the four PLRs to be compliant; doctors may complete more than one per PLR if they wish. Wording corrected by #12150 (2026-09-01) — previously "Cultural Safety" / "Ethical Practice" per #6369; Matt's 2026-09-01 comment quoted AMC's actual published wording and reversed that, superseding #6369. † †

  • ✅ cpd.activity.master-list-is-the-published-table — the master activity list the Add CPD Activity form offers, and that the activities list renders, is the published CPD Activities by Category and Hours (July 2026) table: the same 101 activities, under the published spelling of each name, each selectable only for the category columns the published table marks it in, with its points and point system taken from whichever one of the two published hours columns carries a value. A doctor can therefore never be offered an activity the published table does not list, nor be blocked from claiming one under a category the published table permits — notably Surgical Meetings including M&M, Multidisciplinary etc, which is published in all four category columns and so counts toward the Measuring Outcomes minimum. Where a rename is needed to restore the published spelling it is applied as a rename of the existing row, never a delete-and-recreate, so activities a doctor has already logged keep pointing at the same master-list row and no logged CPD is orphaned. Enforced by test against a verbatim transcription of the published table, not by review — the guard pins the in-app constant, the marketing copy, lookups.json and (since #11089) the UAT deploy seed scripts/seedCpdActivities.ts. (#11040, #11057, #11089) † † † † ‡

  • ✅ cpd.activity.plr-claim-provider-confirms — when a doctor tags a submitted CPD activity with a PLR claim (one of the four PLRs: Culturally Safe Practice / Addressing Health Inequities / Professionalism / Ethics — wording corrected by #12150, 2026-09-01), the CPD provider must explicitly confirm the PLR claim during email verification — not just confirm attendance. The provider verification email surfaces the claimed PLR alongside the activity title, date, and attendee; the provider's verification action explicitly accepts or rejects the PLR tag as part of the same one-click flow. A rejected PLR claim does not invalidate the activity itself (it can still count toward general hours) but it removes the PLR tick from the doctor's compliance dashboard. † (#6476) (#7011) (#7296) (#7847) ‡

  • ✅ cpd.activity.status-model-unverified — a provider-linked CPD activity follows a three-stage status model: pending → unverified → verified. pending = the verification email has been sent and the activity is with the provider awaiting their reply; unverified = the provider has replied (consumed the approval token) and the activity is now with PPP awaiting super-admin verification; verified = a PPP super-admin has verified it. Self-certified activities (no provider) have no email round-trip and start directly at unverified (revised by #11044 — see cpd.activity.self-directed-no-provider below; previously documented as never entering unverified, which left them permanently pending with no route to verification). On the widgets, pending and unverified both count as unverified hours; only verified counts as verified hours — see cpd-home.md § cpd.home.verified-unverified-split. The provider reply moving an activity from pending to unverified records the PLR confirmations but does not light the compliance tick — the tick only lights once the activity is fully verified, preserving the anti-gaming guarantee of cpd.activity.plr-claim-provider-confirms. PPP verification of an activity tagged with a high-level requirement also sets the doctor's per-year HLSR attestation (year = the activity date's year), the only route that lights the CPD Home HLSR tick (#11192, Matt #8715). † (#8765) ‡

  • ✅ cpd.activity.pre-approved-provider-auto-verify — an activity nominating a provider that is already pre-approved for the submitting doctor specifically is created directly at verified, with no approval email sent and no pending/unverified stop-over — matching the published policy's promise that pre-approved-provider activities "receive automatic verification". "Pre-approved for this doctor" means BOTH cpdActivityProviders.isApproved = true (the provider joins this list globally after its first successful token-consumption anywhere, see super-admin.md's approved-authorizers audit trail, #5779) AND this doctor already has a prior activity with that same provider — the same (userId, providerId) relationship the "approved authorizers" dropdown (getApprovedAuthorizersForUser) already establishes. isApproved alone is a global flag shared by every doctor in the system; checking it without the per-doctor relationship would auto-verify an activity naming a provider that only ever approved a different doctor's submission, with no confirmation from the provider about this doctor at all — found during PR #11743 review and fixed before merge. An activity nominating a provider that is not pre-approved for this doctor is unaffected and still goes through the full pending → unverified → verified email round-trip. † (#11044) ‡

  • ✅ cpd.activity.self-directed-no-provider — the CPD activity form offers a "Self-directed (no provider)" option alongside "New Provider", so a doctor can log self-directed learning (journal reading, an online course not from a pre-approved provider) without nominating any third party to email — closing the gap where the only routes required a provider name and email. Submitting with no provider creates the activity with providerId: null and no email is sent; the activity starts at unverified (not pending, since there is no provider who could ever reply) so it surfaces immediately on the PPP super-admin unverified-activity queue and counts toward the doctor's unverified hours rather than being stuck at pending indefinitely. † (#11044) ‡

  • ✅ cpd.activity.plr-claim-tag-not-category — a PLR is a tag/claim on a MO/RP/EA activity, not a category of its own. The activity form offers a PLR multi-select (zero or more of the four PLRs) writing to cpdUserActivities.plrClaims; a PLR never appears as a selectable activity category. † (#7525) (#7646) ‡

  • ✅ cpd.activity.plr-tick-from-claims — the CPD Home PLR compliance tick derives from the activity's plrClaims tag (gated by the provider not having rejected it), not from category-name matching; a category-name fallback is retained until the PR2 data migration removes the legacy PLR category rows. † (#7525) (#7646) ‡

  • ✅ The Add/Edit CPD Activity form no longer shows the legacy classId "Is this activity related to any program requirement below?" radio group — it duplicated PlrClaimsSection's PLR multi-select and confused doctors about which control to use. classId itself is a separate, already-vestigial field (optional end-to-end, read by no compliance-tick logic) and is unaffected; the PR2 cpd_categories/cpd_classes data migration referenced above is still outstanding. (#12659; code:instances/ppp/src/forms/ManualCPDForm/ManualCPDFormView.tsx)

  • ✅ cpd.activity.plr-claim-field-label — the per-activity PLR claims checkbox label reads "Does this activity address any Program-Level Requirements?", without an "(optional)" suffix. The field itself remains optional at the per-activity level (a single MO/RP/EA activity legitimately claims zero PLRs; cpd.activity.plr-claim-tag-not-category is unchanged) — but "(optional)" read as "PLRs don't matter", which is no longer true once annual PLR coverage became a required condition of the compliance verdict (cpd.home.compliance.plr-required-for-verdict in cpd-home.md). (2026-08-23) (#11046) † ‡

  • ⏳ Support hours-based AND points-based colleges — per-regulatory-body

  • ✅ cpd.activity.submitted-vs-verified-style — CPD items have distinct visual treatment for submitted vs verified states: submitted uses a light-light colour with a hashed/hatched pattern; verified uses a solid light colour. Both states meet WCAG 2.1 AA contrast standards. †

  • ✅ cpd.activity.card-pastel-colours — CPD activity cards use a lighter pastel colour palette consistent with the application's visual aesthetic and the colours used on the PPP marketing site's CPD activities page; no saturated or dark category colours on activity cards †

    • Submitted (light) · Verified (lighter) · Rejected (distinct hue)
  • ✅ cpd.activity.auto-select-category — when the user picks an activity, PPP auto-selects the CPD category; the add-activity form defaults to the category with the fewest recorded hours †. Rule:

    1. If the activity maps to exactly one category, that category is the auto-pick
    2. If the activity maps to two or more categories, auto-pick the one with the fewest hours logged this year by the current user (encourages a balanced plan; deficit-driven)
    3. If two or more candidates are tied on hours, auto-pick the first in the activity's category list (deterministic fallback)
    4. The auto-picked category is editable — the user can change it before saving
  • ✅ Null CPD Category / Provider render as em-dash

  • ✅ Description 255-char DB limit enforced with client maxLength

  • ⚠️ ApproveCPD shows success for invalid/expired tokens

  • ✅ ApproveCPD points input accepts fractional hours

  • ✅ OCR-detected hospital matched against user's linked hospitals

    • Single confident match → auto-assign with confirmation
    • Multiple/no match → user picks or adds hospital
    • Mapping persisted for future OCRs of same string
  • ✅ cpd.ocr.dob-extraction — OCR sticker scanner consistently extracts the date-of-birth field from scanned documents, in addition to existing extracted fields.† The vision prompt and structured-output schema include dob; the extracted value is normalised to day-first DD/MM/YYYY and validated (rejects impossible and implausible dates — e.g. a future DOB or an out-of-range year); when no DOB is detected the field returns empty without breaking the URN/gender extraction; the extracted DOB pre-populates the logbook-case dobPatient form field for user confirmation. (26 May 2026)

  • ✅ cpd.activity.selector.defaults-all-activities — default activity-selector mode is "All Activities"; the activity list reflects all activities, not just the plan; the legacy "Your Plan" filter is removed; Master List link remains visible † (5 May)

  • ✅ cpd.activity.master-list.responsive-on-mobile — the static Activities Master List (CPDActivitiesTable) does not horizontally scroll on a mobile viewport. The 6–7 column table hard-coded minWidth: 650, which forced horizontal scroll inside the fullScreen guidance modal on a phone; on xs it now renders a stacked card list (one card per activity — name, the categories it satisfies as chips, and its hours), mirroring the MobileList pattern used by the API-backed master list. The desktop table (with the existing minWidth: 650) is unchanged at sm+, so the standalone /cpd-activities page, the guidance modal, and the Manual CPD form all keep their desktop rendering. † ‡ (#8937)

  • ✅ cpd.activity.sticky-save-mobile — on a phone, the Add / View CPD activity form's Save / Submit action bar stays pinned and reachable above the on-screen keyboard while editing the last fields. The CPD Add and View dialogs open with scroll="paper" (bounded scroll container) and the ManualCPDFormView action row is sticky. Implements the shared design-system.form-actions.sticky-mobile behaviour for CPD.†‡ (#9324)

  • ✅ cpd.activity.upload.mime-allowlist — file uploads accept image/* and application/pdf only; other MIME types return a friendly toast "Only images and PDFs are supported" † (5 May)

  • ✅ cpd.activity.hlsr-mapping-integrity — regression test asserts every activity flagged as ANZASM (or required by an HLSR row) maps to its specialty's HLSR rule; CI fails on drift (5 May)

  • ✅ cpd.activity.superadmin-filter.unverified — super admin can filter the activities list to show only unverified entries †; on /settings/provider-details, the activity list has status filter checkboxes (not a dropdown); default view shows all statuses; one checkbox per status (Verified = DB verified, Pending Verification = DB pending); selecting one filters the list to that status only; radio-style behaviour (one active at a time). DB enum values: pending | unverified | verified | archived (the unverified stage — provider replied, awaiting PPP — added in #8765, see cpd.activity.status-model-unverified). (6 May 2026)

  • 🅼 cpd.activity.master-list.single-source — all entry points must point to a single master activity list; legacy code pointing to different lists must be removed †; audit confirmed the two activity list procedures serve different purposes (activities = user logbook records; cpdActivities = master type lookup); no duplication exists. (6 May 2026) (closed — false premise)

  • ✅ cpd.activity.getall.user-scope — activities.getAll tRPC procedure must be either deleted (no frontend caller exists) or scoped to the authenticated user's own records; currently returns all system records with no userId filter — data exposure risk. (12 May 2026)

  • ✅ cpd.activity.types.superadmin-management — Super Admin has a dedicated settings screen to manage the master list of CPD activity types (separate from individual user activity records); each type can be created, edited, and deactivated; each type is classifiable by category (e.g. Education, Research, Teaching, Clinical) and college mapping (e.g. AMC, ANZASM); deactivated types are hidden from the doctor-facing activity form but retained on existing records; changes propagate immediately. (12 May 2026)

  • ✅ cpd.activity.provider-declined.notify-user — user receives a notification when a submitted activity is not authorised by the provider †; the magic link page for provider activity verification includes a "Decline" button with a mandatory reason field; on submission: (1) activity status transitions to rejected (requires DB migration — rejected not yet in cpd_user_activity_status enum); (2) an in-app notification is sent to the submitting doctor including the provider's reason; (3) the doctor can resubmit the activity after a rejection; (4) Super Admin can filter the activity list by rejected status to see all provider-declined activities. No email — in-app notification only. (6 May 2026) (verified #6373 — implemented end-to-end by #5952: declineByProvider procedure → declineCpdUserActivity → recordCpdDeclineTokenConsumption fires the cpd_activity_provider_declined in-app notification with provider name + reason)

  • ✅ cpd.activity.provider-approved.notify-user — when a provider successfully consumes the approval token (activity marked verified), an in-app bell notification is sent to the submitting doctor confirming the activity has been verified, including the provider's name and the allocated hours. In-app notification only — the existing confirmation email (recordCpdApprovalTokenConsumption in cpdUserActivities/recordTokenConsumption.ts) is retained; this AC adds the in-app notification alongside it. (6 May 2026)

  • ✅ cpd.provider-approval.approver-identity — the CPD provider approval page asks the approver for their full name (required to Verify or Decline; pre-filled from the name last typed for that provider email) and the token-consumption audit row is written as an external actor — typed name, the provider email the link went to, IP address, browser and time — instead of under the doctor's user id. The doctor-attributed row remains the fallback when no provider email is on record. † (#12530) ‡

  • ✅ cpd.activity.view-details.provider-email — the View Details form for a CPD activity displays the provider's name and email address together (e.g. "Royal Australasian College of Surgeons — rob@professionalperformanceportfolio.com"), so the doctor can confirm which address the verification request was sent to without leaving the form. The email is already returned by the getByFilter API (provider: getTableColumns(cpdActivityProviders)); no backend change was needed — only a view-mode branch in ManualCPDFormView.tsx mirroring the pattern used for the Activity and Category fields. † (#8659) (16 Jun 2026)

  • ✅ cpd.activity.hours.accumulation-rule — CPD hours accumulate as decimals in the backend. The wheel and all compliance displays round to the nearest whole hour using the AMC auto-scoring formula (Math.round(minutes ÷ 60) — the same formula used for auto-scored activities); e.g. 12.7h displays as 13h, 12.4h displays as 12h. Residual fractional hours are preserved in the DB and contribute to the next rounding boundary. The current toFixed(1) decimal display in CPDProgressWidget.tsx must be updated to use Math.round. (23 Apr 2026)

  • ⏳ cpd.activity.no-hard-annual-cap-pending-matt — engineering default pending Matt's confirmation, NOT a ratified policy change. Submitting CPD hours for an activity is no longer hard-blocked at that activity's maxPerYear value, for either the "per activity" or "per hour" point system. The published CPD Activities by Category and Hours (July 2026) table — the same authoritative table cpd.activity.master-list-is-the-published-table pins the master list to — carries no cap/maximum-per-year column at all; a doctor reading the published policy has no way to know a yearly ceiling exists, so hard-blocking submission against one risked under-reporting genuinely-earned CPD hours against their AHPRA obligation. A separate internal "Activities Master List" screen still displays maxPerYear on 16 activities, but that screen is not the authoritative document practitioners are shown, and maxPerYear itself is not removed from the data model — it still drives the "X of Y remaining this year" helper-text copy on the Add CPD Activity form — so enforcement can be reinstated without a migration if Matt confirms the master-list caps should be published and enforced going forward. Open Question: should any of the 16 maxPerYear-configured activities' caps ever be published and enforced? Tracked on #11039 (issue kept open, for-discussion, pending Matt). Correction (2026-10-03, Task 8 refresh): #11039 was closed when PR #12355 merged (2026-09-20), so the question is now tracked as Open Question Q1 above. The newest Matt statement is the other way: on the 2026-07-29 Dev Session, with the activities master list on screen, Matt counted "1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 there that are in the final column maximum per year" and agreed caps should be put in for them. That predates Rob's 2026-09-20 interim default, and that default rests on a fact Matt wasn't shown (the published table has no maximum column). So this stays ⏳ pending Q1, not ✅. † † ‡

  • ✅ cpd.activity.master-list-from-activities-tab — the Activities Master List can be opened from the CPD Activities tab (/cpd-activities) as well as from CPD Plans. The doctor doesn't have to know it sits under Plans or start adding an activity to find it. † Built in #12743: a visible "Activities Master List" button in the page header opens the same GuidanceModal as the CPD Plans button, without starting an Add Activity flow. ‡

  • ✅ cpd.activity.points-server-side-bounds — the points field on a CPD user activity is server-side bounded to 0 <= points <= 1000 on every write path of the cpdUserActivities router — doctor create, doctor update, and the provider's verifyByProvider email-link reply — not just guarded by the client's own >0 UI check, which a direct API call bypasses entirely. This does not cover the separate cpd.meetings auto-credit path, which writes to the same points column via a different service and is tracked as a same-bug-class follow-up on #12415. This is a single-activity sanity bound distinct from the annual maxPerYear policy question tracked on cpd.activity.no-hard-annual-cap-pending-matt/#11039 — it does not reinstate that hard annual cap and is not a ratified policy figure; 1000 is a conservative engineering ceiling (~33x the highest points/hours value or maxPerYear cap in the published master list, which tops out at 30) chosen to comfortably clear any real activity while still rejecting non-physical input. † (#12361) ‡

  • ✅ cpd.activity.meeting-credit-shows-title — a CPD activity auto-credited from a meeting has no linked master-list activity, so the Activities table (and its mobile card list) shows the meeting title held in description in the activity-name column instead of a blank cell — the same activity name, else description fallback the dashboard row uses. A linked activity name still wins over the description. (#12462)

Multi-user CPD credit (collaborative cases) ​

  • ✅ When a surgical logbook case involves multiple clinicians (e.g. a registrar as primary operator and a consultant as supervisor), both the registrar and the consultant independently receive CPD credit for that case, calculated according to their respective roles — the registrar earns credit for performing/assisting; the consultant earns credit for supervising. † — a case naming a distinct supervisor generates an independent derived CPD credit record owned by that supervisor (activities.derived_from_activity_id self-FK, participant_role = 'consultant'), so the supervising credit lands in the supervisor's own compliance total; the derived record is re-synced on update and removed when the supervisor is cleared. The supervisory point/hour rules for that derived record are tracked separately in #7457.
  • ✅ Supervisory CPD credit is triggered automatically when a consultant is named as supervisor on a logbook case; the consultant's CPD plan records the appropriate hours/points for their supervisory role without the consultant having to log the activity separately.† — builds on #7456's derived-credit record model: when syncDerivedSupervisorCredit generates the supervisor-owned derived row it now scores it via computeSupervisoryCredit (api/backend-ppp/src/services/multiClinicianCreditService/supervisoryCredit.ts), writing supervisoryHours/supervisoryPoints (operative-time-driven, 1 point/hour, capped at the confirmed 15h supervised-training requirement) plus an auto-generated provenance flag (attributes.derivedCredit = true) so the entry is visibly distinguishable from manually-logged activities; un-naming the supervisor voids the derived entry.
  • ✅ cpd.multi-user.self-loi-credit — a NEW trigger path alongside the named-supervisor one: when the logging doctor selects a Level of Involvement that earns CPD credit for their own role on their own surgical logbook case, they automatically derive their own supervising/teaching CPD credit — no separate logging, no named supervisor required. † Sibling of syncDerivedSupervisorCredit: syncSelfSupervisionCredit (api/backend-ppp/src/services/cpd/selfSupervisionCreditService/) derives a cpd_user_activities credit row owned by the logging doctor (derived_from_activity_id links the source case), re-synced on every create/update and removed on delete; the activity (Supervision of Surgical Trainees vs Teaching to Trainees / Undergraduates) is chosen per case by the existing deficit-driven auto-bucket resolver selectOptimalCpdActivity — reused, not reimplemented. To prevent double credit, the legacy verification-gated flat-1pt TaT branch in cpdUserActivityHandler defers whenever the own-role LoI is flagged earns_cpd_credit. ‡ (#9200)
  • ✅ cpd.multi-user.self-loi-credit.qualifying-lois — the Levels of Involvement that earn this credit are data-driven off the per-LoI loi_label_overrides.earns_cpd_credit flag (#10760, super-admin adjustable on /admin/level-of-involvement), seeded from Matt's ratification: non-consultant TaT: Training another Trainee ONLY (S-TU/S-TS "Trainer (unscrubbed)"/"Trainer (scrubbed)" explicitly do NOT), and consultant PPT: Performed in part by non consultant, S-S: Supervising (scrubbed), S-U: Supervising (in theatre) (S-H "Supervising (in hospital)" and PCC "Performed with consultant colleague" explicitly do NOT). † The four YES flags ship as a data-backfill migration seeding earns_cpd_credit = true, so the decision ships but stays admin-adjustable without a deploy. (#9200)
  • ✅ cpd.multi-user.self-loi-credit.minute-banking — supervising/teaching CPD converts per whole hour but every operative minute is logged and accumulates: a case's operative minutes join a single per-(doctor, CPD year) pool; each whole hour the pool crosses credits one CPD hour and the sub-hour remainder is banked and rolls forward across cases (e.g. a 125-minute case credits 2 hours + 5 minutes banked; a later case that pushes the pool across the next 60-minute boundary credits a further hour). The banked remainder persists in cpd_supervision_minute_bank. † ‡ (#9200)

Activities List Default Filter ​

The /cpd-activities list is the user's primary view of their logged activities. It must align with the AMC CPD calendar-year cycle: by default, surface only the current year's activities. This matches the dashboard widget default scoping and the closed historical context that activities relate to the current season.

  • ✅ cpd.activities.list.default-current-year — first visit to /cpd-activities with no ?year= query param shows only activities whose activityDate falls in the current calendar year
  • ✅ cpd.activities.list.all-years-toggle — a single-click toggle (segmented control) switches between current year and All years; no extra confirmation dialog
  • ✅ cpd.activities.list.filter-persists-in-url — the chosen filter is reflected in the URL via ?year=YYYY (specific year) or ?year=all; reloading or sharing a deep-link reproduces the same filter state
  • ✅ Empty state copy when the selected year has no activities reads exactly "No CPD activities logged for yet." — the placeholder is the resolved year label, e.g. "2026" or "All years"
  • ✅ Existing column-width and provider-list behaviour from is preserved
Open GitHub Issues ​

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

Change Log ​
DateChangePR/IssueReason
2026-10-04The CPD provider approval page (/approve-cpd-activity/:token) requires the approver's full name before Verify or Decline, pre-filled from the name last typed for that provider email. recordTokenConsumption and recordDeclineTokenConsumption write the token-consumption audit row as an external actor (typed name, provider email, IP address, browser) instead of under the doctor's user id; the doctor-attributed row remains the fallback when no provider email is on record or the identity write fails. No migration (reuses external_approvers / audit_trail from #12528).#0, #12530Rob 2026-10-04 (#12528-#12531 sprint). The name-capture AC is new and still awaits Matt's confirmation per the issue; built name-only.
2026-10-03The CPD Activities page (/cpd-activities) header now has an "Activities Master List" button that opens the same GuidanceModal as the CPD Plans header button, without starting an Add Activity flow. AC cpd.activity.master-list-from-activities-tab flipped from drift to built.#12743Matt (Dev Session 2026-07-29): the master list "also needs to be added to the activities tab at the top". It was scope point 3 of #11039, dropped when PR #12355 closed that issue with only the cap enforcement.
2026-10-03Task 8 spec refresh. New AC cpd.activity.master-list-from-activities-tab, marked drift (#12743). It is Matt's 2026-07-29 ask, which was dropped when PR #12355 closed #11039. cpd.activity.no-hard-annual-cap-pending-matt now records Matt's newer 2026-07-29 statement that the 16 master-list caps are real and should be put in, and fixes the stale claim that #11039 is still open. That decision has moved to new Open Question Q1. Status set to partial-drift.#11192, #11039, #12743Async Task spec refresh (#11192). The newest dated Matt statement wins (2026-07-29 Dev Session ~00:27:05–00:28:01). It conflicts with Rob's 2026-09-20 interim default, which rests on a fact Matt wasn't shown (the published table has no cap column), so it goes to Matt as an Open Question rather than either side being picked. Spec-only, no BDD (the scenario requirement is on #12743).
2026-10-01The Add/Edit CPD Activity form no longer shows the legacy classId "Is this activity related to any program requirement below?" radio group alongside PlrClaimsSection's checkboxes — removed ProgramRequirementSection.tsx and its wiring in ManualCPDFormView.tsx. The cpd_categories/cpd_classes rows and the category-name read fallback (#7646 PR2 territory) are untouched.#12659Found during the Async Task 8 CPD Home Lifecycle audit (#11192): the two parallel PLR-tagging controls confused doctors about which to use. Live-confirmed #7646 PR2 has not shipped (legacy rows still present, the category-name fallback still live, last patched 2026-09-14 #12225) — so the fix is narrower than "wait for PR2": classId itself is a separate, already-vestigial field (optional end-to-end, read by no compliance-tick logic, empty across a live persona''s logged activities), so only the duplicate UI control is removed, not the legacy data path.
2026-09-21The points field on a CPD user activity is now server-side bounded (0 &lt;= points &lt;= 1000) on create, update, and the provider's verifyByProvider reply — new AC cpd.activity.points-server-side-bounds.#12361The shared points schema fell through to the drizzle-zod NUMERIC(8,2) default (a bare z.number()), letting negative values and values up to 999,999.99 pass server-side validation. Found during security review of #12355/#11039. This is a single-activity sanity bound only, not a reinstatement of the separate annual maxPerYear policy cap tracked on #11039 pending Matt's confirmation.
2026-09-20Submitting CPD hours no longer hard-blocks at an activity's configured maxPerYear cap, for either the "per activity" or "per hour" point system — new AC cpd.activity.no-hard-annual-cap-pending-matt.#11039The published "CPD Activities by Category and Hours" table carries no cap/maximum-per-year column, so hard-blocking submission against an undisclosed internal cap risked under-reporting genuinely-earned CPD hours against the doctor's AHPRA obligation. Engineering default (Rob's Option B decision) pending Matt's confirmation of whether the master-list caps should ever be published/enforced — issue kept open with for-discussion.
2026-08-23Pre-approved providers now get automatic verification, scoped to providers already approved FOR THE SUBMITTING DOCTOR specifically (skip the email round-trip); a "Self-directed (no provider)" route lets a doctor log self-certified CPD without nominating a third party, landing on unverified instead of stuck at pending. Reviewed on PR #11743: the auto-verify branch originally checked the global provider.isApproved flag alone, which would have let any doctor auto-verify against a provider only ever approved by a different doctor; fixed to also require this doctor's own prior activity with that provider. Also fixed a status-clobber regression that would have downgraded auto-credited logbook/PPP360 activities from verified to unverified.#11743, #11044Found by the policy-conformance audit (#11022) — neither route the published "Assessment and Recognition of CPD Activity Policy July 2026" describes actually worked. §1's "automatic verification" for pre-approved providers never checked provider.isApproved; §2's self-directed learning route required a provider name+email for every submission, and even the backend's null-provider concept would have been stuck at pending forever.
2026-07-29Adds the missing step definitions for the four published-table conformance scenarios #11082 merged with none (steps/cpd-published-table.steps.ts), and tags those scenarios @wip @known-issue-11153 until the BDD generator can run them. The steps are source-inspection, asserting the in-app cpd-activities.ts constant against the verbatim published transcription — the 101-row exact set, the absent off-list duplicate, the restored college references, the casing/hyphenation fidelity an export depends on, and the Surgical Meetings mapping to Measuring Outcomes. Scope note added during review: this checks the in-app constant only, not the live Add CPD Activity Autocomplete or the DB seed it actually renders from — see #11156.#11155, #11153, #11040, #11057, #11025Reported by the #11112 lane and verified against uat: the four scenarios were @regression with no @wip and no step definitions. Two independent causes let this land green rather than red: playwright.bdd.config.ts sets missingSteps: 'skip-scenario' (#5155), so an undefined step is silently skipped rather than failed, and separately bddgen aborts in loadSteps on a mixed CJS/ESM step file, so the suite generates nothing and runs zero scenarios (#11153) — either alone would already have masked the defect. Two of the steps could not simply reuse the existing 'I am on the Add CPD Activity form': that step is browser-driven, and while only 4 of the 11 scenarios that use it carry @requires-backend, redefining the step here would have been a duplicate definition regardless. They now open on a master-list Given instead — which, per review, reads the in-app constant rather than the live picker's data source; #11156 tracks closing that gap. The scenarios stay @wip rather than shipping as apparently-enforced guards that cannot execute; the step assertions were proven correct against the real constants via a throwaway harness in the meantime.
2026-07-29Reverses the genericisation this PR applied a day earlier: the eight college-referencing activity names go back to Kristin's published wording — "ANZASM surgical case form", "ANZASM first line assessment", "ANZASM second line assessment", "MALT with peer review", "Examiner - RACS, AMC, university", "Teaching on RACS courses / workshops", "Participation in ASERNIP-S review …" and "Attendance at College provided courses / workshops" — across the in-app constant, the verbatim transcription, the marketing copy, the /information policy pages, lookups.json, the CD seed script and the conformance fixtures, which now pin Kristin's strings rather than the genericised ones. The rename migration (renumbered 0222 → 0226 for a collision with uat's orthopaedic backfill) drops its seven genericisation pairs and renames for case and punctuation fidelity only; its first-apply validator no longer asserts the college names are stale. verify-policy-fidelity.mjs loses its INTENTIONAL_SOURCE_SUBSTITUTIONS map entirely and scores all 13 policies at 100% against the unmodified source documents.#11082, #11025, #11040, #11057Matt narrowed his own 29 April RACS/CAPE ruling on the 2026-07-29 Dev Session call (#11025): it governs what PPP calls its own products and features — CAPE is the proprietary term he flagged — and college references in CPD activity materials are correct to carry ("they're references… we're happy to reference"). The genericisation applied that ruling to a surface it was not written for. Restoring the verbatim wording also restores the fidelity gate to demanding it, which is exactly what the removed substitution map's own comment anticipated, and removes a standing regulatory risk: activity names are the strings on an exported CPD record, so a genericised name gave a regulator reconciling an export against the published list no exact match. Nothing was written to any database — #11105 changed only instances/marketing/src, so had the migration's genericisation pairs shipped, this PR would have been what first wrote the wrong spellings into cpd_activities_list.
2026-07-28Re-points the published-table conformance guards at the post-#11105 published table. Eight activities carry their genericised published spelling — "MALT with peer review" becomes "Morbidity audit with peer review", the three "ANZASM …" rows become "Surgical mortality audit …", "Examiner - RACS, AMC, university" becomes "Examiner - specialist college, AMC, university", "Participation in ASERNIP-S review …" becomes "Participation in a surgical research review …", "Attendance at College provided courses / workshops" and "Teaching on RACS courses / workshops" both gain "specialist college" — across the in-app constant, the transcription, lookups.json, migration 0222 and the CD seed script. The specialist HLSR table's surgical-mortality row now reproduces the published wording verbatim in both copies, and its conformance exemption is deleted rather than re-pointed.#11082, #11040, #11057, #11025#11105 (issue #11025) landed Matt's 29 April RACS-naming ruling on the published documents these constants are pinned to, so the guards added earlier in this PR went red — correctly. They were pinning the product to a transcription of the RACS-named table, which would have re-entrenched the banned terminology behind a passing test, exactly as #11105 warned when it flagged the sequencing conflict. Every row still describes the same activity and the master-list row id never changes, so no doctor loses claimable CPD and no logged activity is orphaned. The specialist row's exemption was justified solely by "#11025 owns this row"; with that hold released the row conforms like the other 24, and re-pointing the exemption at the new text would have preserved a deviation that no longer has a reason.
2026-07-27Adds cpd.activity.master-list-is-the-published-table: the master activity list the Add CPD Activity form offers is the published "CPD Activities by Category and Hours (July 2026)" table — the same 101 activities, under the published spelling, each selectable only for the category columns the published table marks it in. "Surgical Meetings including M&M, Multidisciplinary etc" is published in all four categories and now counts toward the Measuring Outcomes minimum; the off-list 102nd row is gone. Renames are applied as renames of the existing row, never delete-and-recreate, so already-logged activities are not orphaned.#11082, #11040, #11057A policy-to-code conformance audit (#11022) found the offered list had drifted from the published table. The live harm (#11040) was that Measuring Outcomes carries a hard 5-hour minimum and the mark had been dropped from the one row published in all four categories, so routine surgical M&amp;M could not be claimed toward it. The list also offered an activity the published table does not list, awarding hours for it, and gave practitioners two indistinguishable choices for the same thing.
2026-07-22Self-logged supervising/teaching Level of Involvement now earns the logging doctor their own derived CPD credit, scored per operative hour with minute banking and the auto-bucket resolver choosing Supervision vs Teaching.#10825, #9200Matt ratified on #9200 (2026-07-21) which LoIs earn credit (non-consultant TaT only; consultant PPT/S-S/S-U), that hours convert per whole hour but every minute accumulates, and that credit maps to both target activities via the existing "select lowest bucket" resolver. TaT re-added to the selectable non-consultant list.
2026-06-17Added the unverified status to the CPD activity lifecycle: provider-linked activities now follow pending → unverified → verified (AC cpd.activity.status-model-unverified). DB status enum extended via migration 0162.#8768, #8765Operational provider-approval flow Matt greenlit 2026-06-16 (split from on-hold #7915). The provider reply now lands the activity in 'unverified' (with PPP) so doctors can tell a provider has already replied versus still awaiting the provider; only PPP-verified activities count as verified hours.
2026-06-17Remove spurious 1-hour cap on per-activity CPD activities without a maxPerYear limit; fix zero-hours guard; correct stale BDD scenario.#8752, #8670The hours validation was capping entry at the CPD award value (points) instead of recognising that points is an award amount, not a time limit. A doctor may spend 3 hours at a 1-CPD-point event. The stale scenario at issue-4598 asserted the old wrong behaviour and was updated to scope it to activities with a configured maxPerYear. The zero-hours guard was tightened to reject 0 as meaningless for CPD logging.
2026-06-16Show provider name and email together in View Details disabled TextField#8691, #8659Doctor could not confirm the verification email destination without leaving the form. Provider email was already returned by getByFilter; only a view-mode branch in ManualCPDFormView.tsx was needed.
2026-06-02PLRs become a tag/claim on a MO/RP/EA activity — activity form gains a PLR multi-select writing to plrClaims, and the CPD Home PLR tick derives from plrClaims (category-name fallback retained until the PR2 migration).#8091, #7646, #7525Matt confirmed on #7525 that a PLR is a claim/tag on an activity within MO/RP/EA, not a category of its own. PR1 of 2 — behaviour only; PR2 removes the legacy PLR category rows and the fallback.
2026-06-01Provider must explicitly confirm a tagged PLR claim during email verification — AC cpd.activity.plr-claim-provider-confirms flipped to met.#7875, #7847, #6476, #7011, #7296Anti-gaming control (#6369) — the provider, not the self-tagging doctor, is the trusted source for PLR alignment. The email surfaces the claimed PLR, the one-click verification page presents a per-PLR confirm/reject control, the decision is persisted, and a provider-rejected PLR removes the compliance tick (activity still counts toward general hours).

Internal documentation — org members only