CPD Remediation
Feature Overview
Support for practitioners who are at risk of not meeting their CPD requirements, or who are referred for remediation by AHPRA/AMC. The Remediation and at Risk of Not Meeting CPD Requirements Policy July 2026 describes an intake, a tailored remediation plan tracked in the platform, scheduled advisor check-ins, and a referral-notification path.
#11673 built the enabler: the intake/referral records, the remediation plan entity, and the Member Dashboard form behind a new Remediation tile on the CPD Support page. Consultation scheduling, activity-to-area mapping, timelines/checkpoints, fortnightly check-ins, escalation, and regulator (AHPRA/AMC) intake remain unbuilt — see Current Status.
Sources & Recordings
Audited against the full published policy source text (not just the partial quotes in issue #11051) — no Dev Session transcript exists for this feature yet. Citations appear as † hover tooltips on each AC bullet.
| Type | Document | Session Date | Last Audited |
|---|---|---|---|
| Published Policy | Remediation and at Risk of Not Meeting CPD Requirements Policy July 2026 (Policy ID #09, Last Updated July 2026) | — | 2026-08-19 |
This spec is authored directly from the full policy source text at instances/marketing/scripts/policy-sources/remediation-policy.txt (the extracted-text fixture pinned by marketing's verify-policy-fidelity gate against the rendered Information page) — not only the partial quotes reproduced in issue #11051's body, which omitted the Employer/Supervisor referral source, the Consultation/Goal-Setting step, and the entire Escalation section. No Dev Session transcript discusses remediation. Every AC below traces to a specific policy passage; nothing is inferred beyond what the policy states.
Scope note: the policy document also has a second, distinct half — "At Risk of Not Meeting CPD Requirements" (dashboard visualisation, automated risk-flagging, routine reminders, proactive communication) — which is a different mechanism from remediation (early-warning vs. active-plan) and is not covered by this spec. See Open Question 6.
Open Questions
| # | Question | Proposed answer / status | Ref |
|---|---|---|---|
| 1 | Build the full platform workflow (the Intake through Escalation acceptance criteria below), or amend the policy to describe remediation as an email-initiated, advisor-run process with no platform surface? | Rob's 2026-08-11 decision on #11051: build to match the published policy. Recorded here as the swing decision this spec is scoped against. | #11051 |
| 2 | What are the exact fields captured on the "Request Support for Remediation" online form? | Not specified in the policy text quoted so far — the policy names the form but not its fields. | — |
| 3 | What triggers a remediation plan to be marked complete / exit criteria for the plan? | Still not stated in the policy. #11673 therefore makes completion explicitly manual: a CPD Advisor sets completed via markPlanComplete, stamped with completed_by_user_id. Nothing infers completion from activity progress — inventing an automatic exit criterion the policy does not define would be a requirement, not an implementation detail. | #11673 |
| 4 | Who can view a practitioner's remediation plan besides the practitioner and their CPD Advisor (e.g. Super Admin, Hospital Admin)? | Answered (Rob, 2026-08-19, #11673): practitioner + CPD Advisor + Super Admin only. Hospital Admin must NOT see remediation records. Enforced in one place — assertCanViewRemediation — and pinned by mutation-verified tests. See also Open Question 7 (no CPD Advisor role exists). | #11673 |
| 5 | Escalation to AHPRA — is CPD compliance reporting to AHPRA (mentioned in Escalation) the same mechanism as the existing PPP→AHPRA integration referenced elsewhere in the codebase, or a distinct remediation-specific report? | Policy says "CPD compliance is reported by PPP to Ahpra" as a standing fact, not a remediation-specific new integration — likely the existing mechanism, but not explicitly confirmed. | — |
| 6 | Is the "At Risk of Not Meeting CPD Requirements" half of the policy (dashboard visualisation, automated risk-flagging with named thresholds, routine 3/2/1-month reminders, proactive communication) in scope for this spec, a separate spec, or already covered by cpd-reminders.feature? | Not decided. Distinct mechanism from remediation (early-warning vs. active-plan) — recommend a separate spec/issue rather than folding into this one, since #11051 (this spec's source issue) scoped only the remediation half. | — |
| 7 | There is no "CPD Advisor" role in the user model. Roles are boolean flags on users (is_super_admin, is_hospital_admin, is_hospital_super_admin); "CPD Advisor" exists only as a status value (cpd_advisor_review) elsewhere in CPD. Should a real advisor role/flag be introduced? | Surfaced by #11673, not decided. That build follows the existing cpd_provider_recognition_applications.decided_by_user_id precedent: the Advisor is identified per-record by an FK, and advisor-tier actions gate on Super Admin. Consequence: every CPD Advisor today must also be a Super Admin. Introducing a real role is a user-model change needing Matt's sign-off, so it was not smuggled into an enabler. | #11673 |
| 8 | Employer/supervisor referral has no employer-facing login. Should employers get a self-service surface, and if so, what authenticates them? | #11673 ships Rob's agreed stopgap: a Super Admin enters the referral on the practitioner's behalf, with referral_source = 'employer' and submitted_by_user_id = the entering admin, so the record still reflects who actually referred. Employer self-service (magic link? verified org domain?) is a separate future design. | #11673 |
Closed Questions (0) — click to expand
| # | Question | Resolution | Ref |
|---|
Acceptance Criteria
Intake and initiation
- ✅
cpd-remediation.intake.self-referral— practitioner can self-refer for remediation support. † ‡ (#11673) - ✅
cpd-remediation.intake.employer-referral— a practitioner's employer or supervisor can request/refer remediation on their behalf. † ‡ (#11673) - ⏳
cpd-remediation.intake.regulator-referral— AHPRA/AMC referral is a distinct intake source from self- and employer-referral. † - ⏳
cpd-remediation.intake.regulator-notification-sla— practitioner is notified of a regulator referral within 7 business days, via platform and email. † - ✅
cpd-remediation.intake.dashboard-form— an online form on the Member Dashboard lets a practitioner request remediation support. † ‡ (#11673) - ✅
cpd-remediation.intake.email-channel— a support email address is offered as an alternative intake channel to the form. † ‡ (#11673) - ✅
cpd-remediation.intake.initial-assessment— CPD Advisor reviews the practitioner's CPD record, area(s) of underperformance, and any referring-authority feedback before consultation. † ‡ (#11673)
Consultation and goal setting
- ✅
cpd-remediation.consultation.virtual-session— CPD Advisor arranges a virtual consultation with the practitioner using a structured goal-setting framework. † ‡ (#11674) - ✅
cpd-remediation.consultation.nominate-supervisor— practitioner can nominate a supervisor/mentor to participate in the remediation process. † ‡ (#11673, #11674)
Plan development
- ✅
cpd-remediation.plan.entity— a remediation plan is a distinct, persisted entity tracked within CPD Home Platform. † ‡ (#11673) - ✅
cpd-remediation.plan.activity-mapping— CPD activities in a remediation plan are mapped to specific remediation areas. † ‡ (#11674) - ✅
cpd-remediation.plan.timelines-checkpoints— a remediation plan records timelines, checkpoints, and documentation requirements. † ‡ (#11674)
Monitoring
- ⏳
cpd-remediation.checkin.fortnightly— a fortnightly check-in with the practitioner's CPD Advisor is scheduled while a remediation plan is active. † - ⏳
cpd-remediation.checkin.reviews-logged-progress— each check-in reviews progress the practitioner has logged in the platform dashboard. † - ⏳
cpd-remediation.checkin.seeks-supervisor-feedback— each check-in seeks feedback from the practitioner and any nominated supervisor/mentor. † - ⏳
cpd-remediation.plan.adjustable— a remediation plan can be adjusted based on practitioner progress, new/clarified goals, or additional AHPRA/AMC concerns. † - ✅
cpd-remediation.outcome.unsuccessful-noted— where PPP's attempts to assist a practitioner get back on track have been unsuccessful, this is noted for future reference and auditing purposes, covering both terminal exit paths (a plan setdiscontinued, or an intakeclosedwithout ever reaching a plan). † ‡ (#11059)
Escalation
- ⏳
cpd-remediation.escalation.non-compliance-notice— a practitioner whose remediation is not progressing is notified of the requirement to comply. † - ⏳
cpd-remediation.escalation.joint-meeting— a joint meeting involving the practitioner, advisor, and nominated supervisor/mentor may be held as an escalation step. † - ⏳
cpd-remediation.escalation.statement-withheld— if remediation is still not progressing after escalation, PPP may withhold the CPD Statement of Completion for that CPD year. † - ⏳
cpd-remediation.escalation.ahpra-compliance-reporting— CPD compliance status is reported by PPP to AHPRA as part of the escalation path. †
Marketing / public accessibility
- ✅
cpd-remediation.marketing.no-dead-navigation— the published policy page does not name a Dashboard navigation path that doesn't exist. † ‡ (#11662) - ✅
cpd-remediation.marketing.information-page-title-is-h1(#11177) — the public Information page (/information, which renders this policy) has exactly one<h1>, and it is the page title. Its title previously rendered as an<h3>with no h1 on the page; only the heading element changed (SectionHeadingas="h1"), so the policy wording and theverify-policy-fidelitygate are untouched. Covered by the marketing e2e test that every secondary page has exactly one h1. † ‡
Current Status
| Sub-feature | Status | Notes |
|---|---|---|
| Marketing dead-link removal | ✅ Built | #11662 merged — removed the false Dashboard navigation claim |
| Intake — self-referral, dashboard form, email channel, initial assessment | ✅ Built | #11673 — Remediation tile + form, cpd_remediation_intakes (migration 0231) |
| Intake — employer referral | 🟡 Stopgap | #11673 — Super-Admin-entered on the practitioner's behalf; no employer login (OQ 8) |
| Intake — regulator (AHPRA/AMC) referral + 7-day notification SLA | ❌ Not started | Out of scope for the #11673 enabler; referral_source has no regulator value yet |
| Consultation and goal setting | ❌ Not started | No virtual-consultation scheduling or supervisor nomination mechanism |
| Remediation plan entity | ✅ Built | #11673 — cpd_remediation_plans, manual completion by a CPD Advisor |
| Remediation plan activity mapping + timelines/checkpoints | ❌ Not started | Deliberately not pre-empted by the enabler's plan shape |
| Fortnightly check-in scheduling + monitoring | ❌ Not started | No scheduling mechanism exists |
| Escalation (non-compliance notice, joint meeting, statement withholding) | ❌ Not started | No escalation record or CPD-Statement-of-Completion gating exists |
| Regulator referral notification SLA | ❌ Not started | The only existing AHPRA integration runs the opposite direction (PPP → AHPRA) |
Downstream References
| Feature | Field / event used | Consequence |
|---|---|---|
| cpd | Practitioner's CPD record, read by the CPD Advisor during Initial Assessment | A remediation plan build must read from the existing CPD activity/plan schema rather than duplicating it |
Implementation / Architecture
Decomposed from #11051 into an enabler (#11673) plus independent story issues (#11674–#11677: consultation/goal-setting, activity-to-area mapping and timelines, fortnightly check-ins, escalation and regulator intake).
Enabler (#11673) — shipped. Two tables in the CPD bounded context (packages-shared/ppp/src/schema-groups/cpd/cpdRemediation.ts, migration 0231): cpd_remediation_intakes (referral source, free-text area of concern, optional nominated supervisor email) and cpd_remediation_plans (distinct from the ordinary annual cpd_plans row; manual completion). Business logic sits in remediationService, the tRPC surface in routers/procedures/cpd/remediation, and the practitioner-facing form behind a new Remediation tile on SupportSectionGrid.tsx.
Two constraints worth carrying forward into #11674–#11677:
- Visibility has exactly one definition —
assertCanViewRemediation(practitioner / assigned CPD Advisor / Super Admin; never Hospital Admin). New remediation reads must route through it rather than re-deriving the rule, and it refuses withNOT_FOUNDso a record's existence is not confirmed to an unauthorised caller. - There is no CPD Advisor role (Open Question 7). Advisor-tier actions currently gate on Super Admin, following the
cpd_provider_recognition_applications.decided_by_user_idprecedent. If a real advisor role lands, the gate inassertIsAdvisoris the one place to change.
Two gating footguns for #11674–#11677, both deliberate choices here:
- Do not swap
assertIsAdvisorfor~ppp-api/utils/adminProcedurejust because both checkis_super_admin.adminProcedureshort-circuits onctx.internal, so a batch or scheduled job bypasses the check entirely — acceptable for admin CRUD, not for a practitioner's clinical-support record. Keeping the gate in the service also keeps it under service-method unit tests, which is what allows the visibility rule to be proven by mutation. - Do not follow
orgAdminProcedure's pattern. It readsctx.identity.userPersona, butPppIdentity(utils/entrypoint.ts) only populatesemail,pppUserId,userId, andprofileIncomplete— so that persona check readsundefinedand admits only super admins in practice. Queryusers.userPersonafresh from the DB (ascheckIsHospitalAdmin.tsdoes) if a remediation surface ever needs a persona-tier check.
Open GitHub Issues
Open issues on label:feature:cpd-remediation — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Closed Issues (1) — click to expand
| # | Title / AC delivered | Closed |
|---|---|---|
| #11662 | cpd-remediation.marketing.no-dead-navigation — removed the false Dashboard remediation navigation claim from Info11.tsx | 2026-08-19 |
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-09-24 | Information page title renders as an h1 instead of an h3 (SectionHeading as="h1"); policy wording and the verify-policy-fidelity gate are untouched. | #12430, #11177 | #11177 click-through audit found secondary pages had no h1. instances/marketing/.../Information/index.tsx is a cpd-remediation code path, so the spec records the change (cpd-remediation.marketing.information-page-title-is-h1). |
| 2026-09-20 | Added an outcome-note column to both remediation exit paths — discontinuedReason on cpd_remediation_plans and outcomeNote on cpd_remediation_intakes (migration 0250) — required at the service layer when a CPD Advisor sets the terminal discontinued/closed status via new discontinueRemediationPlan/closeRemediationIntake procedures. New AC cpd-remediation.outcome.unsuccessful-noted. | #11059 | #11059 found the Records Policy's "noted in the user's profile for future reference and auditing purposes" promise had no data behind it — only a binary terminal status existed, no narrative. AC1 of #11059, scoped to cover both exit paths on 2026-09-20 after #11051's schema landed unblocked it. |
| 2026-09-15 | Built consultation scheduling/goal-setting, CPD activity-to-remediation-area mapping, and plan timelines/checkpoints (cpd-remediation.consultation.virtual-session, cpd-remediation.consultation.nominate-supervisor, cpd-remediation.plan.activity-mapping, cpd-remediation.plan.timelines-checkpoints). | #11674 | Second of five issues decomposing #11051's remediation policy build (#11673 enabler, #11674 consultation/plan-development). Supervisor nomination is captured on the intake (already built by #11673) and read via the plan's linked intake — no duplicate field added to the plan. |
| 2026-08-19 | OQ1-4 resolved (Rob: build, not amend-copy; intake form fields; plan exit criteria; plan visibility). Decomposed into 5 tracking issues (#11673 enabler, #11674 consultation/plan, #11675 monitoring, #11676 escalation, #11677 regulator intake). | #11681, #11673, #11674, #11675, #11676, #11677 | Feature is too large for one PR; each story issue is independently buildable once the enabler lands. Supersedes the abandoned #11678, which double-picked #11665's already-merged spec authoring and could not merge cleanly. |
| 2026-08-19 | code-paths: re-pointed from Info11.tsx to Information/index.tsx — Info11.tsx was deleted as unreferenced dead code, superseded by the July 2026 policy set (#11022), along with 8 other orphaned Info*.tsx files. | #11058 | #11030's code-paths-live gate requires every glob to still resolve; the glob would otherwise match zero tracked files. Re-point rather than delete, per CLAUDE.md. |
| 2026-08-19 | Spec authored — first governing spec for remediation, per SGD gate on #11051. Authored against the full policy source text (not only #11051's partial quotes), adding intake employer-referral, consultation/goal-setting, and the escalation section (non-compliance notice, joint meeting, CPD Statement of Completion withholding, AHPRA compliance reporting) that the issue's quotes omitted. | #11051 | #11022's policy→code audit found zero code coverage for a fully-published policy; CLAUDE.md requires a governing spec before implementation begins |