Skip to content

AMC Yearly Review — Super Admin Runbook ​

Owner: PPP Super Admin Cadence: Annual, triggered by the super-admin-amc-review Container Apps Job on Feb 1 each year (after AMC's typical Jan publication cycle). Spec: super-admin.md § AMC Yearly Review · cpd.md Q5 (Answered Questions)

This runbook is the manual checklist the Super Admin walks through when the annual AMC review todo fires. The todo persists until it is closed with either "Mark reviewed — no change" or a link to a merged PR.

Step 1 — Pull the AMC source page ​

  1. Open the AMC CPD Home framework page (current URL is configured in the Super Admin console row; if it has changed, update the URL in super_admin_todos.metadata.amcUrl)
  2. Save a PDF snapshot to the audit folder: gdrive://PPP — Compliance/AMC Reviews/AMC-Framework-YYYY-MM-DD.pdf
  3. Note the publication date AMC shows on the page header

Step 2 — Diff against last year's PPP source-of-truth ​

Compare against the four files in this repo:

FileWhat to check
docs/features/cpd.md § Specialist High-Level RequirementsIs every AMC-listed specialty present? Any new specialties? Any HLSR text edits?
packages-shared/ppp/src/schema-groups/identity-profile/speciality.ts (requirements JSONB seed)Same — code-side mirror of the spec table
api/backend-ppp/src/services/admin-and-org/dashboardService/cpd/index.ts (CPD_CATEGORIES constant)Category minimum hours — has AMC changed any of MO/RP/Education/Combined minima?
docs/site/compliance/racs-cpd-framework.mdHas AMC moved off the RACS reference? Has the source URL changed?

Step 3 — One of the following ​

Option A — No change found ​

  1. Click "Mark reviewed — no change" on the Super Admin console todo
  2. The system writes one audit row: userId, action: 'amc-review-noop', amcUrl, amcPdfHash, timestamp
  3. The next Feb 1 job creates the next year's todo

Option B — Changes found ​

  1. Raise a single PR titled chore(amc): YYYY annual review — sync seed data
  2. PR contents:
    • Updated cpd.md Specialist High-Level Requirements table
    • Updated specialty.ts seed JSONB
    • Updated CPD_CATEGORIES constant if minima changed
    • A new fragment in docs/features/.changelog/cpd/YYYY-MM-DD-prN.md describing what AMC changed and why
    • Migration if requirements JSONB shape changes
  3. Once the PR is merged, close the todo with the merged-PR URL — the system writes the audit row with action: 'amc-review-pr' and the PR number

Step 4 — Communicate ​

  • Post a brief in #engineering on the team channel: "AMC YYYY review complete — no change" or "AMC YYYY review complete — see PR #N for details"
  • If any change affects user-visible compliance (e.g. category minima drop), notify Matt (PO) before merging

Why this is manual ​

  • AMC has no public API
  • HTML scraping breaks silently and would create a hidden compliance liability
  • Manual review + versioned code edits keep the audit trail clean and reviewable
  • The annual cadence aligns with AMC's own publication rhythm — more frequent review wastes effort

Internal documentation — org members only