Skip to content
View in Notion

Roadmap — National Frameworks & Preset Learning Agreements ​

Priority — superseded 2026-06-28 → 2026-09-22: the AMC PGY1/PGY2 pathway is now the top roadmap priority once baseline infrastructure works. On #9667 (2026-06-28) Matt made the Roadmap / Yearly Appraisal / What's Up Next thread, including an AMC like-for-like pass, the next focus after getting the app working.† On 2026-09-16 he noted the roadmap is "something that we're quoting on the website to be AMC ready".† On 2026-09-22 he called it the integration he is "keen specifically in the road map ... because that's one of our big selling points that I'm plastering everywhere that we don't currently have".† The QLD-Health-specific overlays below (jurisdictional variations, organisational roll-up) are still unscheduled. Matt has not restated those since 22 Apr.

Additional build — not core PPP. Queensland Health requirements and national-framework auto-prefill are a separate commercial engagement, not part of the core PPP delivery roadmap. Do not schedule or implement this spec as part of standard sprint work without explicit direction from Matt. (Decision: Matt Randell, 22 Apr 2026 catchup — #5335. Superseded for the AMC PGY1/PGY2 pathway by the 2026-06-28 / 2026-09-22 statements above.) See docs/features/ppp-roadmap.md for the core roadmap scope.

Direction given (2 Jun 2026, #5522): Matt has explicitly asked for the EPA entrustability ladder in the Q-Health demo. A low-fidelity, presentation-only ladder (static data) is in scope for the demo under this direction. The live data wiring (entrustment source, jurisdiction/PGY gating, framework auto-prefill) remains research-gated on the AMC PDF extraction below and stays a Next-horizon build.

Feature Overview ​

Automatically pre-populate a doctor's PPP roadmap with the milestones, entrustable professional activities (EPAs), CPD hours, and assessments required by their stage of training and jurisdiction, rather than presenting a blank canvas. When a doctor signs up, PPP detects { stage, jurisdiction, specialty } from their profile and applies the matching national framework template.

The goal is compliance-by-default: a PGY1 intern in Queensland sees the AMC 2024 PGY1 framework milestones pre-filled; a PGY2 resident in NSW sees the NSW PGY2 variation; a specialty trainee sees their college's training programme. Each pre-filled item is editable and tagged back to the framework source, and roadmap completeness is tracked as a compliance percentage feeding into the organisational dashboard.

Open Questions ​

  • Does AMC publish the PGY1/PGY2 framework as structured data (JSON/XML/CSV), or must we hand-encode from the PDF?
  • How often does the framework change? Annual? Less frequent? Drives versioning effort.
  • Are there vendor licensing implications of redistributing framework content inside PPP?
  • Clinical Learning Australia — is it a competitor PPP can displace, or a complementary tool that PPP should integrate with?
Original Vision ​

"Once over this first hump we will look at how we can incorporate preset frameworks or learning agreements to auto fill our roadmap feature to comply with stage of learning for doctors according to jurisdiction."

— Matt Randell, email to Rob Duncan, 15 Apr 2026, "Point further research after Q health meeting"

Surfaced during the Queensland Health meeting on 15 Apr 2026. Q Health is already aware of competing initiatives (Clinical Learning Australia) and will compare PPP against frameworks they already use. Auto-filling the roadmap from preset frameworks is both a differentiator and a compliance story for enterprise health service customers.

Matt's PPP Road Map Notion (17 Apr 2026) — intent + visual reference ​

Source: PPP Road Map Notion page. Sub-page of PPP Dashboard.

Intent (verbatim from Matt) ​

  1. Facility to incorporate predetermined learning objectives — outline short-term requirements to achieve long-term outcomes.
  2. Simplify large datasets of outcomes into small achievable goals — "deload the clinician". The explicit purpose is reducing cognitive load, not just compliance.
  3. Compartmentalise as SMART GOALS — Specific / Measurable / Achievable / Relevant / Time-bound.
  4. Map to Enterprise Learning Objectives and give the user a plan.
  5. Tie to existing PPP features — WBAs, Logbook Cases (if relevant), Appraisal. "User needs to achieve goals over short term and then longer." The Roadmap should aggregate activity already captured elsewhere in PPP rather than invent new objective types. Matt calls out the scope creep risk but flags it as valuable for the Queensland Health deal.

Matt's reference — UK ePortfolio style milestone timeline ​

Matt embedded a screenshot of the UK Foundation/IMT/Specialty-training ePortfolio layout (Dr Matthew Randell, North Hampshire Hospital, 03 Sept 2025 – 03 Mar 2026, Curriculum 2021). It captures the visual pattern he wants to emulate:

Structure observed:

                                              [Training History] [My Learning Agreements]
 Progress Summary | Comments

Curriculum 2021 — transitioned 5th October 2024

                    ● MCR              ● MCR               ○ LA Final
                    (mid-point)        (final)             review meeting
                       │                  │                    │
    ●────────●─────────●─────────●────────●─────────●─────────●───── (locked future)
    Select/    LA                 Self-      LA Mid-       Self-
    Edit       Objective-         assess     point         assess
    Lead CS    setting            (mid)      review        (final)
                meeting                       meeting

Design conventions:

ElementVisual
Completed milestoneSolid dark-navy circle with white ✓
Current / active milestoneOutlined navy with chevron arrow
Future / lockedGrey, padlock icon
TimelineHorizontal, left → right
Layout densityAlternating rows above/below the line to avoid crowding
Period scopeOne training period (6 months) per view — zoom out for longer horizons
Quick actions"Training History" + "My Learning Agreements" top-right

Milestone types in the UK model (to consider for PPP equivalents):

UK milestonePPP equivalent (tie to existing feature)
Select / Edit Lead CS (Clinical Supervisor)Profile — supervisor assignment
LA Objective-setting meetingNew — roadmap preset kick-off
Self-assessment (mid-point)Retrospective — reflection entry
LA Mid-point review meetingAppraisal — MCR-mid equivalent
MCR (mid-point)Appraisal — MCR
Self-assessment (final)Retrospective — reflection entry
LA Final review meetingAppraisal — yearly
MCR (final)Appraisal — MCR final

Takeaways for the PPP Roadmap data model ​

  • Roadmap = projection of existing PPP activity onto a timeline, not a separate data store. Every milestone resolves to an existing activity type (WBA, Appraisal, Retrospective entry, Logbook case), so completion signal is already captured in the system.
  • Period scoping matters — the reference shows one 6-month training period, with zoom-out for longer horizons. Matches our 6/12/18/24m + programme tab design.
  • States are ternary: completed (solid tick) / current (outlined arrow) / future (grey lock). Keep these three exact states in PPP.
  • "Learning Agreements" concept from UK — worth adding to the data model as learning_agreement_period spanning a rotation / training period, with milestones nested inside.
  • Scope creep is Matt's call: the Roadmap will cross feature boundaries (WBA + Appraisal + Retrospective + Logbook). He has explicitly accepted this tradeoff for the Qhealth deal.
AMC Prevocational National Framework (PGY1/PGY2) — 2024+ deep-dive ​

Source: Notion page + AMC framework homepage. Three governing PDFs attached to Matt's Notion (Training & Assessment Requirements, Training Environment, Quality Assurance).

Framework shape ​

Three primary documents govern the framework:

  1. Training & Assessment Requirements — prevocational outcome statements, EPAs, record of learning, performance-improvement processes, certification.
  2. Training Environment — national standards for programs and terms (mandatory), experience requirements (replacing fixed term allocations), supervisor training mandates (within 3 years), strengthened Aboriginal and Torres Strait Islander standards.
  3. Quality Assurance — AMC domains for accrediting Prevocational Training Accreditation Authorities; procedures aligned with medical-school/specialty-college accreditation.

Core competency model: Entrustable Professional Activities (EPAs) ​

Not a traditional competency checklist — the framework uses EPAs that describe the key clinical work of PGY1/PGY2 doctors. The set is four EPAs (no EPA 5), adapted from the RACP Basic Training EPAs, identical across PGY1 and PGY2.

The exact EPA titles and the entrustability scale are now sourced and verified against the primary AMC documents (deep-research 2026-06-10, adversarially verified; src: amc-prevocational-epa) — superseding the earlier "engineering reconstruction" caveat. Spike #8277 is resolved by the table below.

The four AMC prevocational EPAs (verbatim) ​

EPAShort titleFull descriptor (AMC Section 2B)Min assessments/yr
1Clinical assessmentConduct a clinical assessment of a patient incorporating history, examination, and formulation of a differential diagnosis and a management plan, including appropriate investigations.4 (≈1/term)
2Recognition and care of the acutely unwell patientRecognise, assess, escalate appropriately, and provide immediate management to deteriorating and acutely unwell patients.2
3PrescribingAppropriately prescribe therapies (drugs, fluids, blood products, inhalational therapies including oxygen) tailored to patients' needs and conditions, either in response to a request by the treating team or self-initiated.2
4Team communicationCommunicate about patient care, including accurate documentation and written and verbal information to facilitate high-quality care at transition points and referral.2

The entrustability scale — THREE rungs, not five ​

The official AMC EPA assessment forms use a three-point entrustability scale (NOT the five-rung Chen/ten Cate "observation → supervises others" ladder, and NOT a two-level binary — a binary characterisation was explicitly refuted in verification). Each rung is defined by how present/contactable the supervisor must be:

LevelLabelDefinition (AMC EPA assessment form)
1Requires direct supervisionThe supervisor needs to be there to observe the interactions and review the work.
2Requires proximal supervisionThe supervisor needs to be easily contacted, and able to provide immediate or detailed review of work.
3Requires minimal supervisionThe supervisor trusts the prevocational doctor to complete the task, needs to be contactable / in the building, and able to provide a general overview of work.

Correction (#5522 demo): the shipped demo (epaLadderData.ts) used a fabricated five-rung scale (Observe only → Supervises others) and four placeholder EPA titles. Matt flagged this as "the info appears untrue" (#5522). Both are wrong — the live build (#8276) uses the four verified EPAs and the three verified rungs above, seeded from epa-framework-config.json.

Not pass/fail — assessment minima + global panel judgement ​

EPA assessment is explicitly not pass/fail and there is no minimum number of EPAs that must reach a given rung. Each prevocational year requires ≥10 EPA assessments: ≥4 of EPA 1 (usually one per term) and ≥2 each of EPA 2/3/4, with ≥2 in any one term. The health service's Assessment Review Panel makes a global end-of-year judgement against the Prevocational Outcome Statements. The doctor-facing ladder must therefore show, per EPA, the latest entrustability rung plus progress toward the per-year assessment minima — never a pass/fail meter.

Assessment instruments (mandated) ​

InstrumentPurposeTiming
Beginning-of-term discussionOrientation + goal settingTerm start
Term Assessment FormFormative feedback against prevocational outcome statementsMid-term
Term Assessment FormSummative decision: satisfactory term completionEnd-of-term
EPA Assessment Forms (×4)Entrustability rating per EPAOngoing / as-observed
Record of LearningComprehensive documentationThroughout year
Panel global judgmentYear-end review of all evidence — PGY1/PGY2 certification decisionYear end
Improving Performance Action Plan (IPAP)Support for trainees strugglingAs needed

Timeline / cadence ​

Term start        Mid-term         End-of-term      Year end
   |                 |                  |              |
   Orientation       Formative          Summative      Panel
   + goals           term assessment    term assessment global
                     + EPA evidence     + EPA evidence  judgment
                                                           │
                                               ┌───────────┼───────────┐
                                          Certified   Improvement    Repeat
                                                      plan required   year

PGY1 vs PGY2 ​

  • PGY1 — implementation began 2024 across most states. Medical Board of Australia approves PGY1 standards; AMC issues Certificate of Completion.
  • PGY2 — ACT and NSW began implementing 2024; remaining states staggered into 2025. AMC issues first PGY2 certificates from August 2024.
  • Both years use the same four EPAs and the same three-rung scale. PGY2 is held to a higher bar on those identical EPAs — greater complexity, responsibility, reduced supervision and context — not a different EPA set or a separate ladder. The assessor records "Was the entrustability rating appropriate for the level of training, given the complexity of the case?" (Yes/No), so PGY is an expectation/complexity context, not a fourth dimension of the ladder. (Verified — src: amc-prevocational-epa; resolves Section 3 Part C extraction.)

Critical difference from previous framework ​

Old framework: mandatory term allocations — 10 weeks surgery, 10 weeks medicine, 8 weeks emergency medical care.

New framework: flexible experience parameters, prioritising quality of learning over fixed time allocations. This means PPP's preset can't simply auto-seed "10 weeks of X" milestones — instead we seed EPA exposure requirements and let the health service configure the rotation sequence.

Things the framework deliberately does NOT mandate ​

  • No minimum case numbers
  • No specific CPD hour requirements (separate from AHPRA Medical Board's 50h/yr CPD; prevocational is a different track)
  • No case-load targets

The framework is experience-based and entrustment-based, not volume-based. This is critical for PPP roadmap modelling — we should not fabricate minimum counts the framework doesn't require.

PPP Roadmap preset — proposed encoding ​

When { pgyYear ∈ {1, 2}, jurisdiction = 'AU' } is detected on the user's profile, auto-seed:

Milestone typeCadenceSource field
beginning_of_term_discussionPer termAMC Training & Assessment Req's
term_assessment_midMid-term (per term)AMC Training & Assessment Req's
term_assessment_endEnd-of-term (per term)AMC Training & Assessment Req's
epa_entrustment_review (×4)Rolling — target each EPA observed within termAMC Training & Assessment Req's
panel_global_judgmentYear-endAMC Training & Assessment Req's
ipap_review (conditional)Triggered if any summative unsatisfactoryAMC Training & Assessment Req's

New entity proposals for roadmap service:

ts
interface FrameworkPreset {
  id: 'amc-pgy1' | 'amc-pgy2' | 'racs-set' | ...
  displayName: string
  jurisdiction: 'AU' | 'NZ' | 'UK' | ...
  appliesToProfile: (p: UserProfile) => boolean
  milestones: FrameworkMilestone[]
  epas?: Epa[]                           // PGY1/PGY2 only
}

interface FrameworkMilestone {
  type: 'term_assessment_mid' | 'term_assessment_end' | 'epa_entrustment_review' | 'panel_global_judgment' | ...
  title: string
  dueRule: 'per_term_mid' | 'per_term_end' | 'year_end' | ...
  assessmentForm?: 'term_assessment' | 'epa_form' | 'ipap'
  requiresEvidence: string[]             // ['record_of_learning_entry', 'supervisor_signoff']
}

interface Epa {
  id: 'epa-1' | 'epa-2' | 'epa-3' | 'epa-4'
  shortTitle: string
  fullTitle: string                      // verbatim AMC descriptor
  minAssessmentsPerYear: number          // EPA1 = 4, EPA2/3/4 = 2
}

// Three-rung AMC prevocational scale (verified) — see #amc-entrustment-scale.
// NOT the 5-rung Chen/ten Cate ladder. Framework-scoped: specialty colleges
// (e.g. RACP, 8 EPAs) define their own scale, so this enum is per-framework,
// not global.
type EntrustabilityLevel =
  | 'direct'                             // Requires direct supervision
  | 'proximal'                           // Requires proximal supervision
  | 'minimal'                            // Requires minimal supervision

Specialty-college EPAs — framework-scoped, not universal ​

The AMC prevocational four are structured by PGY (PGY1/2 junior doctors). Specialty training colleges layer their own, larger EPA sets structured by specialty — so the entrustability ladder must be framework-scoped, never a single fixed list. This is the "Specialty and/or PGY" requirement: a doctor sees the AMC framework while prevocational, then their college framework once in vocational training.

Verified exemplar — RACP Basic Training (8 EPAs) (src: racp-basic-training-epa): clinically assess patients; discuss diagnoses/management with patients & families; document patient progress; prescribe medications tailored to needs; transfer care; choose/organise/interpret investigations; assess and manage acutely unwell patients; plan/prepare/perform/after-care for procedures. The AMC's four prevocational EPAs are an explicit adaptation/subset of these — confirming the lineage and the framework-scoped design.

Phasing: the AMC prevocational framework ships live and gated ({ pgyYear ∈ {1,2}, jurisdiction = 'AU' }) from epa-framework-config.json. RACP and the other colleges (RACS, RANZCOG, RANZCP, ACEM, RACGP, ANZCA) are documented but not seeded live — see Open Questions: their EPA counts/titles and (critically) their entrustment scales are not yet verified, and live gating needs a user→training-program/specialty mapping that does not exist yet (users.specialty is a free string today). The config schema is deliberately framework-keyed so a college framework is a data add, not a code change, once verified.

Wellbeing + external data integration ​

Framework mandates:

  • "Strengthened wellbeing standards" — integrates with PPP Pulse / WHO-5 widget on dashboard
  • "Use and respond to external sources of data (e.g. the Medical Training Survey)" — so the roadmap must be able to surface data from the MTS feed

Quality assurance / accreditation layer ​

The framework also governs how training programs and authorities are accredited. For PPP this is relevant only insofar as:

  • Users' programs are accredited by a PTAA (Prevocational Training Accreditation Authority) — we can display this badge on their profile
  • Supervisor mandatory training completion (within 3 years) is a profile/credential field worth tracking

Open questions for Matt ​

  • Q5 — surface entrustability as a visual ladder in the Roadmap, or keep it in the EPA form only? Resolved — ladder on the Roadmap (#5522); rebuilt on verified data (4 EPAs / 3 rungs) by #8276, seeded from epa-framework-config.json.
  • Q6 — PGY1 → PGY2 transition: does PPP auto-re-seed the roadmap when the user's pgyYear ticks over, or prompt them? (PGY is a context bump on the same EPAs, so the ladder set does not change — only the expectation bar.)
  • Q7 — should the roadmap preset be read-only (health-service owned) or user-editable? The framework is flexible enough that local programs add local requirements on top.
  • Q8 (new) — specialty-college frameworks: confirm the EPA sets and entrustment scales for RACS, RANZCOG, RANZCP, ACEM, RACGP, ANZCA (only RACP's 8 EPAs are verified; none of their scales are). Needed before seeding any college framework live, plus a users.specialty → training-program mapping to gate them.
  • Q9 (new) — where does the doctor's actual entrustability data come from? The AMC EPA assessment is supervisor-completed; PPP needs an EPA-assessment capture path (or import) before the ladder shows real ratings rather than seed/placeholder state. Tracked on #8276.
Scope ​

In scope ​

  • Framework template storage — model the AMC PGY1/PGY2 national framework (2024) as structured data (EPAs, milestones, assessments, required CPD hours)
  • Jurisdictional overlays — capture QLD / NSW / VIC / WA / SA / TAS / ACT / NT variations on top of the national framework
  • Auto-population on signup — detect stage/jurisdiction from doctor profile, pre-fill roadmap with framework items
  • Editable pre-fill — each pre-filled item can be edited, deferred, or marked not-applicable, but retains a tag to its framework source
  • Compliance tracking — roadmap completeness percentage against framework requirements, surfaced on doctor dashboard and rolled up to organisational dashboard
  • Framework versioning — the AMC framework updated in 2024, will update again; support multiple concurrent framework versions with effective dates
  • Competitive positioning — feature matrix vs Clinical Learning Australia so Sales can articulate PPP's differentiation

Out of scope (for now) ​

  • Specialty college training programmes (RACS, RACP, RANZCOG, etc.) — phase 2 after prevocational framework is proven
  • UK equivalents (Foundation Programme, Core Training) — mirror the Australian model once established
  • Automatic sign-off of framework items — supervisors still sign off manually via the existing WBA/appraisal flow

Acceptance Criteria ​

Research phase (prerequisite) ​

  • ⏳ Complete competitive analysis of Clinical Learning Australia (feature set, coverage, integrations, gaps)
  • ✅ Complete structural analysis of AMC PGY1/PGY2 2024 framework (EPAs, milestones, assessment schedule) — resolved #8277: 4 EPAs + 3-rung entrustability scale + assessment minima verified and seeded in epa-framework-config.json (src: amc-prevocational-epa)
  • ⏳ Document jurisdictional variations across all Australian states/territories
  • ⏳ Confirm whether AMC publishes machine-readable framework definitions (or whether we need to manually encode)
  • ⏳ roadmap-frameworks.amc-like-for-like-mapping — every AMC PGY1/PGY2 training and assessment requirement is mapped either to an existing PPP feature (MCR, MSF, 360, WBA, logbook, CPD), noting any tweak needed, or to a new build. Matt confirms the mapping before any preset is seeded.†† Rob posted a first-pass draft on #9667 (2026-07-07) without extracting the three AMC PDFs. Matt's decision is open as ppp-roadmap Q13.

Data model ​

  • ⏳ framework entity — stores framework name, version, effective date range, source authority
  • ⏳ framework_item entity — stores EPAs, milestones, CPD hour requirements, linked to parent framework
  • ⏳ framework_jurisdiction_overlay entity — stores jurisdictional deviations (QLD adds X, NSW requires Y)
  • ⏳ doctor_framework_instance entity — joins a doctor to a framework version at a point in time, with { stage, jurisdiction }
  • ✅ Drizzle schema + migration + .validate.sql per CLAUDE.md pitfall

Auto-population flow ​

  • ⏳ On signup completion, detect { stage, jurisdiction, specialty } and match to framework
  • ⏳ Pre-fill roadmap with framework items, tagged to framework source
  • ⏳ Pre-filled items visible under existing roadmap UI with a "framework" badge
  • ⏳ Doctor can edit, defer, or mark not-applicable on each item (edit audit trail)

Compliance surface ​

  • ⏳ Doctor dashboard shows framework completion percentage
  • ⏳ Organisational dashboard (admin view) rolls up framework compliance across all doctors in the service
  • ⏳ Filter organisational dashboard by framework / jurisdiction / stage

EPA entrustability ladder (verified — #8277 → #8276) ​

  • ✅ AC id roadmap-frameworks.epa-set — the AMC prevocational framework seeds exactly four EPAs with verbatim AMC titles.†
  • ✅ AC id roadmap-frameworks.entrustment-scale — the entrustability scale is three rungs (direct/proximal/minimal), not five.†
  • ✅ AC id roadmap-frameworks.config-seeded — EPAs + scale + assessment minima live in epa-framework-config.json, Zod-validated fail-fast at load.†
  • ✅ AC id roadmap-frameworks.framework-scoped — config is framework-keyed so specialty-college sets (e.g. RACP 8 EPAs) are a data add.†
  • ✅ AC id roadmap-frameworks.pgy-gated (#8276) — the ladder renders only for { pgyYear ∈ {1,2}, jurisdiction = 'AU' }; getEpaLadder returns visible:false otherwise and EpaLadder renders nothing.†
  • ✅ AC id roadmap-frameworks.not-pass-fail (#8276) — the per-EPA view shows the latest awarded rung + "X / Y assessments" progress to the assessment minima, never a pass/fail meter.†

BDD scenarios (before build) ​

  • ⏳ @smoke @feature:roadmap-national-frameworks — happy path: PGY1 in QLD signs up, roadmap pre-filled from AMC 2024 framework with QLD overlay
  • ⏳ @smoke @feature:roadmap-national-frameworks — happy path: doctor edits a pre-filled item, edit persists and retains framework tag
  • ⏳ @regression @feature:roadmap-national-frameworks — framework version updated after doctor enrolled, existing doctor stays on original version until explicit upgrade
Status ​

Partially started; priority raised. The EPA ladder is verified and seeded (#8277 → #8276). The framework data model and auto-prefill are not built. Parked until the Q Health demo is delivered and the CPD home build-out is complete. The AMC PGY1/PGY2 pathway is now the top roadmap priority once baseline infrastructure works (Matt, 2026-09-22 — see the banner above). The next step is the like-for-like mapping (roadmap-frameworks.amc-like-for-like-mapping, ppp-roadmap Q13). Research pointers come from Matt's email (15 Apr 2026). See Notion research page for the competitive and framework links.

Open issues on label:feature:roadmap-national-frameworks — issue data unavailable at build time.Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Dependencies ​
  • Blocks: none directly, but feeds the organisational dashboard compliance story
  • Blocked by: doctor profile must capture { stage, jurisdiction, specialty } reliably — confirm during research that today's signup flow captures enough data
  • Related: cpd.md (CPD hour tracking feeds framework compliance), onboarding.md (signup flow is where framework assignment happens), dashboard.md (compliance surface)
Change Log ​
DateChangeAuthor
2026-10-03The "Additional build — do not schedule" banner (22 Apr, #5335) is struck through for the AMC PGY1/PGY2 pathway and kept visible. Matt's 2026-06-28 (#9667), 2026-09-16 and 2026-09-22 statements make the pathway the top roadmap priority once baseline infrastructure works. New AC roadmap-frameworks.amc-like-for-like-mapping. Status moved from not-started to in-progress, because the EPA ladder is already built (#8276).#11144, #9667 — Async Task spec refresh, Task 1 (#11144). The newest dated statement from Matt wins. The QLD-Health overlays and the organisational roll-up stay unscheduled because Matt has not restated them since 22 Apr.
2026-07-13BDD scenario coverage intentionally deferred — spec is status: not-started (roadmap-only). No @feature:roadmap-national-frameworks scenarios needed yet.#10578, #10572 — Coverage/BDD gap audit (#10572) flagged this spec as having zero BDD tag match. Confirmed roadmap-only per front-matter status:; BDD is written when the feature is built, not while it is unstarted roadmap. This note stops future coverage sweeps from re-flagging the gap.
2026-06-10Resolve spike #8277 — verify + seed the AMC prevocational EPA framework (4 EPAs, 3-rung entrustability scale) from primary AMC sources into epa-framework-config.json.#8449, #8277 — The #5522 demo used a fabricated 5-rung scale + placeholder EPA titles (Matt 'the info appears untrue'). Adversarially-verified deep-research confirmed 4 EPAs + a 3-point scale (direct/proximal/minimal); this seeds the verified data + Zod loader so the ladder rebuild (#8276) uses authoritative, citable values.
2026-04-28CLA research complete - CLA is complement (PGY1-2 mandatory framework). PPP differentiators - CPD tracking, surgical logbook, wellness, career-long portfolio. No code change.#5169 — Research outcome from issue #5169 - clarifies that Clinical Learning Australia is not a competitor but a complementary early-career framework, and confirms PPP's career-long positioning.
2026-04-15Stub created from Matt's email post-Q-Health meeting. Not for now — prioritise after Q Health demo and CPD home.Rob
2026-04-28Cross-referenced from ppp-roadmap.md Delivery Horizons (#5325). Auto-prefill + enterprise overlay sit on the Next horizon, specialty-college presets + framework versioning sit on Later. No new content in this spec — pointer only.Rob
Sources & Recordings ​

No Drive sources confirmed yet — research pending. Entry: (none yet — research pending)

Internal documentation — org members only