Skip to content

CPD Provider Recognition ​

Feature Overview ​

PPP already committed to the Australian Medical Council (AMC), in its accepted CPD Home accreditation submission, a formal three-pathway model for assessing CPD activities and a structured process for recognising CPD providers — including a CPD Advisor role, a paid provider-recognition application with fee waivers, and Education and Training Committee oversight. This spec turns that already-approved policy (submission attachments ATT43, ATT52, ATT53) into a build plan: the assessment pathways, the provider recognition application lifecycle, and AI-assisted evidence-gathering tooling that supports — but never replaces — the human CPD Advisor's decision.

Sources & Recordings ​

Audited against PPP's own submitted AMC CPD Home accreditation attachments — the policy PPP committed to, not a call transcript. Citations appear as † hover tooltips on each AC bullet.

TypeDocumentSession DateLast Audited
AMC Submission AttachmentATT43 — Assessment and Recognition of CPD Activity Policy2026-01-222026-07-15
AMC Submission AttachmentATT52 — Published Assessment Criteria for Members2026-01-222026-07-15
AMC Submission AttachmentATT53 — Pre-Approved CPD Activities List and Provider Recognition Process2026-01-222026-07-15

Open Questions ​

#QuestionProposed answer / statusRef
Q1The $330/year provider recognition fee has no canonical capability-model home — Payments/billing concern not yet modelled (unmodelled_spec_capabilities, OQ-CM2 in docs/vision.md).Flagging for Matt/Rob — does this fold into an existing Payments concern, or warrant its own capability-model entry? Not blocking the rest of this spec.OQ-CM2
Q2Should the AI-assisted evidence pre-fill run per-application (on submit) or batched (e.g. monthly, per Rob's original ask in #7915)?Proposed: per-application, triggered on submission — the ATT53 process is application-driven, not calendar-driven; a batch job doesn't map onto the 30/90-business-day SLA. Needs Matt/Rob confirmation before build.—
Q3Attachment 51 (the Provider Recognition Application Form template, referenced by ATT53) has not yet been pulled/read this session.Fetch ATT51 from the same GDrive submission-attachments folder before building the application form UI, to match the exact fields AMC has on file.—
Closed Questions (0) — click to expand
#QuestionResolutionRef

Acceptance Criteria ​

Three-Pathway Activity Assessment Model (ATT43) ​

  • ⏳ cpd-provider-recognition.pathway.classification — every submitted CPD activity is classified into exactly one pathway: A (pre-approved provider), B (individual assessment), or C (audit, applies to all). †
  • ⏳ cpd-provider-recognition.pathway-a.expedited — Pathway A activities receive basic verification only; recognition decision is immediate, member notified within 2 business days. †
  • ⏳ cpd-provider-recognition.pathway-b.cpd-advisor-assessment — Pathway B activities are assessed by the CPD Advisor against the ATT52 four criteria within 14 business days. †
  • ⏳ cpd-provider-recognition.pathway-b.four-criteria — the four assessment criteria are Educational Quality, Relevance, Appropriateness, and AHPRA/AMC Alignment. †
  • ⏳ cpd-provider-recognition.pathway-b.notification-states — Pathway B members are notified of exactly one outcome: Approved, Approved with Conditions, or Not Approved, each with a plain-language reason. †
  • 🟡 cpd-provider-recognition.pathway-c.audit-sampling — 5% of members are randomly selected annually; every activity in a sampled member's record is reviewed for evidence quality and category accuracy. The draw and its persistence are now live (#11054): runAnnualAuditSample is scheduled as a yearly maintenance job (Annual member audit (5% sample), Jan 15 22:00 UTC, api-container.ts / scripts/run-annual-member-audit.ts) — previously written but never called by anything. Each selected member gets one cpd_annual_member_audits row per audit year (idempotent on the user_id+audit_year unique index), carrying the four published compliance outcomes (Compliant / Compliant with Minor Issues / Not Compliant – Rectifiable / Not Compliant – Non-Rectifiable) plus pending, and the sampling frame was corrected from "members with at least one classified activity" to the full active CPD-Home member roster (getEligibleAuditPopulation). Remaining: excluding members with an approved exemption/variation from the frame — deferred to #11048, which is where that approved-exemption state first becomes readable; documented inline at the call site. † †
  • ⏳ cpd-provider-recognition.member-self-assessment — members can search the pre-approved provider list and self-check pathway eligibility before submitting an activity. †

Provider Recognition Application (ATT53) ​

  • 🟡 cpd-provider-recognition.application.form — a provider not on the pre-approved list can submit a recognition application with evidence of educational quality, quality-assurance processes, evaluator mechanisms, AU-practice relevance, delivery track record, indemnity insurance, and organisational stability. The intake is delivered end-to-end on the backend (#11041): submitProviderRecognitionApplication (applicationIntake.ts) validates through the S4 gate and persists an accepted application to cpd_provider_recognition_applications, published as the unauthenticated trpc.ppp.cpdProviderRecognition.submitApplication mutation on the sensitive rate-limit tier. Before this, nothing wrote to the table at all, so the published provider list rendered empty for every visitor. Remaining: the applicant-facing form UI — and per Q3, ATT51 (the AMC application form template) should be fetched and reconciled against the seven shipped evidence areas before that form is built. †
  • ⏳ cpd-provider-recognition.application.fee-and-waiver — a $330/year (ex GST) fee applies to commercial/for-profit applicants; non-profit health orgs, AU specialist colleges, universities, and Indigenous health orgs are fee-waived on request. †
  • 🟡 cpd-provider-recognition.application.delegated-approval — the CPD Advisor has delegated authority to directly approve standard applications within 30 business days. The decision path is delivered end-to-end on the backend (#11647, AC2 of #11041): decideProviderRecognitionApplication (applicationDecision.ts) transitions a submitted/cpd_advisor_review/resubmitted application to approved / conditionally_approved / declined, recording the reason and deciding user, published as trpc.ppp.superAdmin.providerRecognitionDecision.decide (there is no dedicated CPD Advisor role yet, so this delegated-authority action is gated by requireSuperAdmin, same as the AI-assist evidence trigger). An approved or conditionally_approved outcome is what makes the row eligible for getPublicProviderList's WHERE status IN ('approved', 'conditionally_approved') read (widened from approved-only by #11043 AC2, alongside a required conditions field on any conditionally_approved decision) — before this, nothing could ever populate the published list even after #11642's intake. A policy_question committee-referral trigger and single-free-resubmission enforcement (isFreeResubmissionEligible) were also added by #11043 AC5/AC3. The CPD Advisor review screen UI (#11739) is now built: a Super Admin queue at /admin/provider-recognition-review listing applications awaiting a delegated decision, surfacing the 30-business-day decideByDate window, with a decision dialog wired to providerRecognitionDecision.decide. Remaining: a dedicated CPD Advisor role distinct from Super Admin, and #11043's still-open AC1 (90 vs 100 business days), AC4 (fee-waiver university category). AC6 (decision-status spelling) is resolved: pathwayB.ts's PathwayBOutcome used a standalone 'not_approved' value for the same "not approved" concept application.ts's persisted DelegatedDecisionOutcome/providerRecognitionApplicationStatus already spelled 'declined' — both now use 'declined' (TypeScript-only rename; the Pathway B outcome is a pure-function return value, never itself persisted, so no migration was needed). †
  • ⏳ cpd-provider-recognition.application.committee-referral — complex applications (novel format, quality concerns, provider reconsideration request, conditional approval, precedent-setting, high-risk) are referred to the quarterly Education and Training Committee; decision within 90 business days total. †
  • ⏳ cpd-provider-recognition.application.recognition-validity — approved recognition is valid for 12 months; providers must renew annually with updated evidence and fee payment. †
  • ⏳ cpd-provider-recognition.committee.quarterly-oversight — the Education and Training Committee receives a quarterly report of all applications and reviews a sample of at least 10% (or 5, whichever is greater) of approved applications. †
  • 🟡 cpd-provider-recognition.provider-list.public-searchable — the pre-approved provider list is published and searchable by name, activity type, specialty, and location, updated within 5 business days of new approvals. The public serving surface is delivered (#10704): the S6 read layer (getPublicProviderList, #10664/#10700) is published over the rate-limited public read tier (trpc.ppp.cpdProviderRecognition.getPublicProviderList) and rendered on the public /cpd-provider-list page (instances/ppp/src/modules/cpd/provider-list/), linked from /cpd-provider-framework — mirroring the sibling public AMC pages and served as a public route inside the PPP app (Rob greenlit Option A, 2026-07-22). The page's "recently added" marker consumes the server-computed 5-business-day freshness flag. The CPD Advisor decision screen UI (#11647 shipped the backend transition to approved) is now built (#11739). Remaining: a dedicated CPD Advisor role. †
  • 🟡 cpd-provider-recognition.provider-badge.issued-and-revocable — approved providers are issued a "provider recognition badge" (ATT53 §7), and the badge is withdrawn automatically alongside recognition status (#11062). MVP built as a derived field, not new persisted state: getPublicProviderList (providerListSearch.ts) attaches hasProviderBadge, computed from the exact same isPubliclyRecognised window check (status IN ('approved','conditionally_approved') and inside recognitionValidFrom/recognitionValidUntil) that already gates public-list membership — so the badge can never outlive recognition (AC2's "worse than no badge" concern), because the recognition expiry job (expiry.ts, #11065) that flips a lapsed application to expired is what already revokes it, with no separate badge flag to drift out of sync. Rendered on /cpd-provider-list as a PPP Recognised Provider chip next to the provider name, using the existing InfoHint primitive (#9331) so the explanation is visible on mobile touch, not tooltip-only. Remaining: a dedicated badge image asset (SVG/PNG) a provider could embed on their own site — deferred pending a design-system primitive decision (no such asset exists in docs/features/design-system.md today); a magic-link/provider-facing surface to retrieve it (the recognition application flow has no such screen yet). †

AI-Assisted Decision Support (advisor-support only) ​

  • ⏳ cpd-provider-recognition.ai-assist.evidence-prefill — on application submission, an AI agent gathers evidence against the ATT52 criteria (ABN/ASIC business-registration lookup, web presence, professional/college affiliation signals) and attaches it to the CPD Advisor's review screen. †
  • ⏳ cpd-provider-recognition.ai-assist.confidence-labelled — every AI-gathered evidence item is labelled with its source and a confidence indicator; nothing is presented as a verified fact. †
  • ⏳ cpd-provider-recognition.ai-assist.human-gate — the AI agent never sets application status; only the CPD Advisor (Pathway B) or Education and Training Committee (referred applications) can approve, condition, or decline. †
  • ⏳ cpd-provider-recognition.ai-assist.non-goal-no-autonomous-approval — automated/autonomous approval of any provider or activity is explicitly out of scope for this spec; PPP's own AMC submission scopes it to a future phase. †

Migration — supersedes admin.md #6688 ​

  • 🟡 cpd-provider-recognition.migration.admin-vetting-checklist — the informational 6-item ATT43/ATT53 vetting checklist and ABN/org-type fields from the superseded admin.md CPD provider queue AC are rebuilt here as the Pathway B / recognition-application assessment screen, now backed by the AI-assist evidence and a real approve/condition/decline gate (not informational-only). The structured checklist definition + org-type fields + decision-gate outcomes are implemented in instances/ppp/src/modules/CpdProviderApplication/vettingChecklist/ (#10674); wiring into the S2 advisor-queue screen (#10660) completes it. †
Current Status ​
Sub-featureStatusNotes
Three-pathway assessment model❌ Not startedATT43 — pathways A/B/C, CPD Advisor role
Provider recognition application + fee❌ Not startedATT53 — form, $330 fee, waivers
Delegated-authority approval + Committee❌ Not startedATT53 — 30/90 business-day SLAs
AI-assisted evidence pre-fill❌ Not startedAdvisor-support only, human-gated
Public criteria disclosure page✅ BuiltAlready shipped — see cpd-home.md (ATT52 criteria)
Operational vetting/verification plumbing✅ BuiltAlready shipped — see cpd.md / super-admin.md
Downstream References ​
FeatureField / event usedConsequence
cpd-home.mdcpd-home.provider-framework.public-pageThe public ATT52 criteria page should link to this spec's application flow
cpd.mdcpd.provider-vetting.*Stage-1 vetting mechanics this spec's Pathway B/application flow plugs into
super-admin.mdsuperadmin.cpd.ppp-verification-queueStage-2 activity verification queue; unaffected, referenced as plumbing
Open GitHub Issues ​

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

Closed Issues (0) — click to expand
#Title / AC deliveredClosed
Change Log ​
DateChangePR/IssueReason
2026-10-05The recognition expiry sweep is now registered as a daily maintenance job (04:30 UTC) so lapsed recognitions move to expired. Backend pathways A/B/C, fee and waiver, committee referral, AI assist and renewal are built; only the provider application form (frontend) and the quarterly committee oversight report surface remain unbuilt.#11192, #12960Task 8 reachability check of 5 Oct 2026 (items 13, 14, 15): the spec review wrongly listed the backend as missing.
2026-09-20Collapsed the two "not approved" spellings within cpdProviderRecognitionService to a single ''declined'' value (AC6) — pathwayB.ts''s PathwayBOutcome previously used ''not_approved'' while application.ts''s DelegatedDecisionOutcome/persisted providerRecognitionApplicationStatus already used ''declined'' for the same concept.#12356, #11043Third of #11022's audit-flagged divergences to close (after #11876's AC2/AC3/AC5). TypeScript-only rename — the Pathway B outcome is a pure-function return value, never itself persisted, so no DB migration was required. AC1 (90 vs 100 business days) and AC4 (fee-waiver university category) remain open pending Rob/Matt.
2026-08-29Add the CPD Advisor review-screen UI for delegated-approval decisions — a Super Admin queue listing applications awaiting decision plus a decision dialog wired to the existing decide mutation.#11963, #11739#11647 shipped the backend decision transition with no UI to call it from, leaving "the CPD Advisor review screen UI" as an explicit Remaining item on this spec.
2026-08-29Issue a revocable provider recognition badge on the public provider list, derived from the existing recognition-window state.#11944, #11062Provider Recognition Policy July 2026 § 7 promises approved providers a "provider recognition badge"; nothing issued, rendered, or verified one — found by the policy-to-code conformance audit (#11022), split from #11042. Sequenced after #11041 (recognition intake + approval workflow) shipping.
2026-08-28Schedule the ATT43 5% annual member audit sample and add its outcome model.#11877, #11054runAnnualAuditSample was written but never called (zero schedulers/routers invoked it), had no per-member-per-year record or outcome column, and drew its sampling frame from members with a classified activity rather than the full active roster — found by the policy-to-code conformance audit (#11022).
2026-08-27Widened getPublicProviderList to include conditionally_approved providers (required conditions on that outcome), enforced single free resubmission, and added a policy_question committee-referral trigger.#11876, #11043Policy-to-code conformance audit (#11022) found 3 of 4 named divergences in #11043 fixable without a further product decision; the remaining 3 (90 vs 100 business days, fee-waiver university category, decision-status spelling) need Rob/Matt to resolve first.
2026-08-23Added the CPD Advisor's delegated-approval decision path — the ATT53 §1 write half AC2 of #11041 was still missing after #11642's intake. New service applicationDecision.ts (decideProviderRecognitionApplication) reads an application's current status, runs it through a new pure gate buildDelegatedDecision (application.ts), and transitions it to approved / conditionally_approved / declined, recording the decision reason, timestamp and deciding user. Exposed as trpc.ppp.superAdmin.providerRecognitionDecision.decide; gated by requireSuperAdmin since there is no dedicated CPD Advisor role yet (same pattern as the AI-assist evidence trigger, #10701). The gate refuses to re-decide an application already decided or referred to the Committee, and requires a non-blank reason. An approved outcome is what makes a row visible to getPublicProviderList's WHERE status = 'approved' read, so the published /cpd-provider-list page can finally populate. No migration — the status enum and decision columns already existed on cpd_provider_recognition_applications.#11724, #11647, #11041Closes the remaining AC2 gap from #11041 (fully resolved by the policy→code conformance audit, #11022). #11642 shipped the application intake (AC1) and the empty-state fix (AC3), but explicitly left AC2 — "approved providers appear on the published list" — for a follow-up, because nothing could transition a row to approved without the CPD Advisor's delegated-decision path, a separate ATT53 slice. Scoped to the backend decision transition plus its persistence contract: the CPD Advisor review-screen UI and a dedicated CPD Advisor role (rather than borrowing requireSuperAdmin) remain follow-ups, and Committee-referral persistence (the escalation path for complex applications) is a separate slice — committeeReferral.ts already has the pure referral/window logic but no DB wrapper yet.
2026-08-18Added the provider recognition application intake — the missing write half of the ATT53 application lifecycle. New service applicationIntake.ts (submitProviderRecognitionApplication) is the first production caller of the S4 submission gate buildApplicationSubmission (#10662): it validates through that gate and persists the accepted row to cpd_provider_recognition_applications with status submitted, so a rejected application performs no write at all. Exposed as trpc.ppp.cpdProviderRecognition.submitApplication, an unauthenticated mutation on the sensitive rate-limit tier (10/min) rather than the 30/min public read tier, since an applicant provider is by definition not yet a PPP member and ATT53 publishes the form on the PPP website. Optional URL/AHPRA fields parse through cpdProviderRecognitionApplicationInsertSchema per the contract application.ts records, and feeWaiverCategory derives its enum from the service's own FEE_WAIVER_CATEGORIES. Also fixed the public provider list's empty state (AC3), which told every visitor "No pre-approved providers match your search" even when nothing had been recognised yet. No migration — the table, view and Zod schemas already existed.#11642, #11041Closes the gap found by the policy→code conformance audit (#11022). The ATT53 schema, submission gate and published searchable list were each built, but nothing ever wrote to cpd_provider_recognition_applications — buildApplicationSubmission had no production caller and the recognition router held a single read query — so the list, which reads WHERE status = 'approved' from that table, rendered empty for every visitor. Takes AC1's primary branch (build the intake); the alternative branch of amending the policy to describe the email process actually in use would rewrite an AC sourced to ATT53 in the accepted AMC CPD Home accreditation submission, an external commitment that needs Matt and AMC visibility rather than an implementer's edit. Scoped to the backend intake plus the empty-state fix: the applicant-facing form remains a follow-up, and the spec's unresolved Q3 (ATT51, the AMC form template, has never been fetched) means the field set should be reconciled against ATT51 before that form is built — this slice builds to the seven evidence areas already in the shipped, tested schema.
2026-07-22Served the pre-approved CPD provider list as a public route inside the PPP app — new public page /cpd-provider-list (mirroring /cpd-activities-list) that renders the S6 read layer via a rate-limited public procedure (trpc.ppp.cpdProviderRecognition.getPublicProviderList, wrapping getPublicProviderList from #10664/#10700), searchable by name/activity type/specialty/location with a server-computed "recently added" freshness marker, linked from the public /cpd-provider-framework page. Un-@wip'd the three cpd-provider-recognition.provider-list.public-searchable BDD scenarios (tagged @issue-10704). No new auth surface — reuses the established rateLimitedPublicProcedure tier.#10844, #10704Delivers the ATT53 cpd-provider-recognition.provider-list.public-searchable serving surface. Rob (CTO) greenlit Option A on 2026-07-22 — a public route inside the PPP app rather than a separate marketing microsite — matching the sibling shipped public AMC pages (#6769) and how ACCME/AMC publish their registers on their own primary site. The read/query layer was already built and unit-tested (#10664); this adds only the serving surface, so no requirement changed (additive fulfilment of an existing AC). The endpoint is a plain unauthenticated read and is reusable as-is if the list is later surfaced on the marketing site instead (only the caller changes) — noted because Rob flagged a possible "Kristin email" requesting marketing-site placement.
2026-07-16Replaced the no-signal affiliation stub with a real named-practitioner AHPRA affiliation check. The applicant nominates one practitioner behind the provider (name + AHPRA registration number, new optional fields on cpd_provider_recognition_applications); the ad-hoc evidence run resolves that practitioner's AHPRA registration/specialist status via the existing AHPRA public-register scraper and attaches it as an advisory-only, medium-confidence affiliation signal on the CPD Advisor review screen.#10741, #10728Rescoped by Rob (2026-07-16) from the original per-college/AMC register scraping (too large, one integration per differently-published register, low signal) to a named-practitioner check reusing the existing @ppp-org/ahpra-scraper infra (fetchAhpraDetail / ahpraDetailScraperInvoker). The ai-assist.evidence-prefill AC already names professional/college affiliation as an evidence source, so this completes that source for real applications without changing any stated requirement. Graceful degradation mirrors isAbrConfigured (no nominated practitioner / malformed AHPRA number / scraper disabled or unavailable → explicit no-signal, never a throw); the AHPRA number is validated at the Zod layer and redacted in logs. The human gate is untouched — the signal is unverified evidence a human CPD Advisor confirms. Migration 0208 adds the two columns (0207 is taken by open PR #10739).
2026-07-16Added an applicant-supplied provider_website field to recognition applications and wired it through the ad-hoc evidence run, so the SSRF-guarded web-presence evidence check (#10719) runs its HEAD reachability probe against DB-loaded rows instead of no-opping.#10736, #10729The ai-assist.evidence-prefill AC already names web presence as an evidence source, but loadPendingApplicationsForEvidence had no provider_website column to load, so the web-presence port silently no-opped for every DB row (ABN lookup ran off providerName only). Adding the column completes that AC for real applications. The URL is validated http/https at the Zod input layer; the SSRF guard re-validates at fetch time and remains the security trust boundary. Optional field — an applicant is never forced to supply a website.
2026-07-16Added a first-class, structured location on the provider recognition application — optional Suburb/Town + State (AU states select), stored as nullable columns on cpd_provider_recognition_applications. The public pre-approved provider list search (S6) now surfaces "<suburb>, <state>" when the structured fields are present and falls back to the existing organisation_details free text otherwise, so S6 search never regresses for applications predating the field.#10706, #10703Follow-up to S6 (#10664) — the ATT53 provider-list.public-searchable AC names location as a search dimension but no structured column existed. Proceeds under Rob's recorded assumption (issue #10703 comment 4988942155): structured optional Suburb/Town + State, no geocoding, no backfill, location kept optional so a doctor adding a provider faces no friction (the provider can confirm/update it later via their recognition magic-link screen). Additive fulfilment of an existing AC (governance verdict MATCHES_EXISTING) — no requirement changed. Backend + schema only; the tRPC create procedure and application form / magic-link capture UI are not yet wired, so BDD scenarios stay @wip.
2026-07-16Wired the real ABR (Australian Business Register) fetcher behind the S5 evidence-gatherer ports, plus a Super Admin ad-hoc trigger and a graceful "not configured" degradation state. Web-presence is a real HEAD reachability check; affiliation-signal lookups ship as an explicit no-signal stub (per-college integration deferred).#10701, #10663, #7915Follow-up to #10663 (S5), which shipped gatherEvidencePrefill as injected ports with no live HTTP. This slice adds the real gatherers and resolves the cadence Open Question (Q2). Q2's proposed per-application-on-submit answer is SUPERSEDED by Rob's 2026-07-16 decision — the pre-fill is NOT a per-application auto-trigger and NOT a recurring cron. One initial backfill run ships with the integration; thereafter a Super Admin runs it ad-hoc from the console (~quarterly rhythm). This diverges from the ai-assist.evidence-prefill AC wording ("on application submission"): the trigger is now a superAdminProcedure console action, not a submission hook. The ABR web-services GUID (ABR_GUID) is read from env (Doppler in uat/prd) and is not yet issued (registration in progress); when unset the fetcher degrades gracefully — no ABN lookups, no crash, no retry storm — and the console surfaces a clear not-configured state with the trigger disabled. All S5 guardrails are unchanged: the human gate stays, AI never sets status, every evidence item remains source/confidence-labelled and presented as unverified.
2026-07-15S4 — ATT53 provider recognition application decision layer — evidence-set validation + $330/waiver fee resolution, CPD Advisor 30-business-day delegated decision, Education & Training Committee referral (90 business days total), and 12-month recognition validity / annual renewal / free-resubmission logic.#10699, #10662, #10656Turns the AMC-committed ATT53 provider-recognition lifecycle into governed, unit-tested backend decision logic (application/feeWaiver/committeeReferral/renewal) over the #10658 enabler schema. Backend slice only; the application form UI and tRPC procedures are a tracked follow-up, so the ATT53 application ACs stay ⏳ until the vertical slice completes.
2026-07-15S5 — AI-assisted evidence pre-fill service (ABN/ASIC lookup, web-presence, affiliation signals) against the ATT52 criteria, with confidence labelling and a structural human gate.#10698, #10663Implements the spec's AI-Assisted Decision Support ACs (evidence-prefill, confidence-labelled, human-gate, non-goal-no-autonomous-approval). Built as an injected-port service so it is deterministic and unit-testable with no live HTTP or new API keys; the returned bundle is structurally incapable of carrying a status/decision so the AI can never auto-approve — honouring PPP's AMC submission commitment that autonomous approval is out of scope until a future phase.
2026-07-15Implemented Pathway C annual audit sampling (ATT43) — a deterministic seeded draw selects 5% of members per audit year and flags every activity in a sampled member's record for evidence-quality and category-accuracy review.#10697, #10661Builds the previously-unimplemented AC cpd-provider-recognition.pathway-c.audit-sampling (S3 vertical slice of the decomposed #10656 epic). The draw is seeded on the audit year so a year's sample is reproducible and can be re-derived for audit, and unit-tested with exact assertions.
2026-07-15Rebuilt the informational 6-item ATT43/ATT53 vetting checklist + ABN/org-type fields from the superseded admin.md CPD provider queue as a structured, reusable definition (stable ids, ATT52-criterion mapping, decision-gate outcomes) under instances/ppp/src/modules/CpdProviderApplication/vettingChecklist/.#10695, #10674, #6688AC cpd-provider-recognition.migration.admin-vetting-checklist — the checklist is no longer informational-only; each item now carries a stable id and maps to one of the four ATT52 criteria so the Pathway B assessment screen can drive a real approve / approve-with-conditions / decline gate.
2026-07-15New spec authored — ATT43/52/53 CPD provider recognition + assessment pathway model, plus AI-assisted decision support.#10656, #7915, #6688PPP already committed this model to AMC in its accepted CPD Home accreditation submission; formalising it as a governed spec so it can be decomposed and built, rather than left as an open-ended discussion on #7915.
2026-07-15Implemented the Pathway B individual-assessment decision logic (S2) — the 14-business-day CPD Advisor assessment window, the ATT52 four-criteria assessment shape, and the three ATT43 member notification states (Approved / Approved with Conditions / Not Approved), each with a plain-language reason.#0, #10660Second vertical slice of #10656 (parent), building the not-yet-built Pathway B ACs (cpd-provider-recognition.pathway-b.cpd-advisor-assessment / four-criteria / notification-states) as pure, unit-tested decision-shaping functions on top of the S1 enabler. Backend logic only — tRPC procedures and AdvisorQueue UI land in a later slice, so BDD scenarios stay @wip.
2026-07-15S6 — public pre-approved provider list search (name / activity type / specialty / location, recognition-window gated, 5-business-day freshness marker) and Education & Training Committee quarterly oversight report (all applications + a ≥10%-or-5 QA sample of approved applications), backend query/service layer with exact-assertion unit tests.#10664, #10656Delivers the ATT53 provider-list.public-searchable and committee.quarterly-oversight acceptance criteria as the read/query layer over the recognition applications the enabler/S4 slices persist.

See docs/features/.changelog/cpd-provider-recognition/ for change fragments (per #5273 — never edit this table inline).

Internal documentation — org members only