Sign-up & Registration
Split from Onboarding (2026-09-29, Rob's decision). The 3-step sign-up flow, the registration fields and sign-up-time payment are their own async task (Task 6, #11187), with their own review cycle, separate from the dashboard onboarding checklist (Task 7, #11189). The guided tour and SSO profile completion stay in onboarding.md under that same decision, even though SSO sign-up shares this flow's 3 steps. That was Rob's call, not an architectural necessity. The regulator lookup itself (AHPRA/GMC green tick, autofill, consultant derivation) has its own spec, Medical Registration Verification.
The 2026-09-29 source file never reached git; it was restored on 2026-10-03 (Rob's decision) and reconciled with Task 6's refresh of the sign-up ACs. AC IDs and question numbers (Q1–Q4, Q9, Q10) are kept as they were in onboarding.md, so existing references still resolve.
Feature Overview
A new doctor passes through a lean 3-step sign-up: verify their medical registration (AHPRA for Australia, GMC for the UK), pay, and pick a CPD plan. They then complete the rest of their setup on the dashboard (see Onboarding and Onboarding Checklist). There is no separate Phase 2 Setup Wizard.
- Sign-up (3 steps) is deliberately lean: just enough to verify the doctor and take payment.
- CV upload, immunisations, wearables, supervisors/placement and CPD cadence are intentionally not part of sign-up. They are completed after sign-up on the dashboard (see Onboarding).
Sign-up Flow (3 steps)
Sign-up at /signup-process is a 3-step flow (instances/ppp/src/modules/identity-profile/signup/RegistrationForm.tsx — const steps = ['Registration', 'Payment', 'CPD Plan']). The SSO variant (SsoProfileCompletion.tsx) substitutes Profile Details for Registration but is otherwise the same 3 steps. SSO's own completion behaviour (step-0 gating, persisting accountAccess, the already-onboarded redirect) is specified in Onboarding — SSO profile completion.
- Registration — the primary registration number (AHPRA/GMC) is the first field (top-left, with the regulatory-body selector beside it on the same row), so the register lookup + autofill runs at the very start of the step; followed by name, DOB, email, country, graduate year + medical degree + awarding university (optional; pre-populated on confirmed GMC match — see Medical Registration Verification), registered-specialist flag, speciality confirmation, job role. (See the authoritative field list in Matt's 17 Apr 2026 Notion Brief.)
- Payment — Stripe checkout (CPD or PPP Full, tax-inclusive — see Q4), priced in the doctor's country currency (
onboarding.signup.price-matches-country); current prices in the pricing table. - CPD Plan — initial CPD plan selection.
3 steps is the confirmed design (Rob, 2026-05-26). CV upload, immunisations, wearables, supervisors/placement and CPD cadence are intentionally not part of sign-up — they are completed after sign-up on the dashboard onboarding checklist (supervisors/cadence via My Profile, CV managed in the PPP Passport (#9196) — not My Profile, immunisations via the PPP Passport, wearables via Wellness Data Sources) so sign-up stays minimal-friction. (Originally these lived in the Phase 2 Setup Wizard, removed in #8027.)
Open Questions
| # | Question | Source | Status |
|---|---|---|---|
| Q9 | Sign-up currency: country field, or regulatory body? On 2026-04-21 Matt said prices should match the user's country "IP address and or registration body (AHPRA Aus, GMC UK)", adding that "if registration body then locks user to their primary place of practice and probably most appropriate and less risk of error?". The shipped Payment step takes the currency from the Country of Primary Practice the doctor types on Registration, not from the AHPRA/GMC body or IP. Should the regulatory body lock the currency (so an AHPRA doctor always sees AUD), or is the Country field enough? | #5255 (2026-04-21) | Open — for Matt |
| Q10 | Enterprise-discount billing sub-questions left over from Q4. On 2026-05-03 Matt raised three commercial points alongside the tax-display call. Rob deferred them to a call, and they were never answered on this spec. (a) How does an enterprise token apply at sign-up? This has since been answered in business-models.md Q1 (#8175): a per-contract signed magic-link invite. (b) Billing-cycle differences: the AU working-year changeover in February versus the UK December subscription changeover. Pro-rata, or one anniversary for everyone? (c) If a doctor enters an enterprise token after paying, do they get a refund, or a credit at renewal? (b) and (c) are still open. | notion-signup-doctor-brief (2026-05-03) | Open — for Matt |
Question numbers are carried over from onboarding.md so existing references stay valid; Q5–Q8 are onboarding questions and remain there.
Matt's 17 Apr 2026 Notion Brief — Requirements Update
Source: Sign up — doctor Notion brief.
Purpose
Confirm eligibility, collect needed information, and take payment with minimum friction while maintaining the highest quality of verification and privacy.
Fields collected (authoritative)
- Name
- Date of Birth
- Country of Primary Practice
- Graduate Year + Medical Degree (verification process) — derives current PGY
- Primary Registration number (AHPRA / GMC / etc.) + verification check — this should auto-determine whether the user is a Consultant or Non-Consultant profile (note: GPs = Consultants). Second jurisdiction can be added later in Profile (e.g. AHPRA + GMC for a dual-jurisdiction doctor).
- Registered-specialist flag (if AU and registered specialist, drives CPD High-Level Requirements)
- Speciality confirmation → translates to working Department (note: some users may span two departments — rare, more common in physician specialities)
- Job Role (one of the eight from Profile (Doctor): Consultant Physician; Consultant Surgeon; Non-Consultant Physician; Non-Consultant Surgical; Critical Care Consultant; Critical Care Non-Consultant; General Practice Consultant; General Practice Non-Consultant)
- CV upload (can be deferred — not required at sign-up)
Screenshots / UX changes called out by Matt
- docs.professionalperformanceportfolio.com — Sign up doctor journey: the screen doesn't show the complete sign-up process — confirm fidelity with the field list above.
- Confirm behaviour: temporary password is sent to the user's email; on first login, the user is prompted to change it.
Acceptance Criteria
Registration (sign-up step 1)
- ✅ Medical registration verification (AHPRA/GMC) — see Medical Registration Verification.
- ✅ The primary registration number is the first field on the Registration step, with the regulatory-body selector beside it. ‡
- ✅ Registration fields are password-manager & autofill friendly: the Date of Birth control is a native date input that accepts a full pasted/typed/autofilled value verbatim (carries
autocomplete="bday") rather than a masked picker that reordered digits (12/03/1975 → 03/12/2005); the primary registration field is labelled "Medical Registration Number" withautocomplete="off"andinputmode="text"so password managers stop offering vehicle-registration values; and the name/email fields carrygiven-name/family-name/emailautocomplete tokens. Validation and the register-lookup behaviour are unchanged. ‡ - ✅ Date of Birth field displays and accepts dd/mm/yyyy for AU/UK users. ‡
- ✅
onboarding.signup.additional-specialities-prompt— Built in #12746. A doctor's secondary department or speciality is not captured at sign-up; it is added later on Profile. The sign-up Speciality step shows a prompt telling the doctor that more departments or specialities can be added later through their Profile. Profile does support more than one speciality. †‡
✅ Delivered — issues closed (collapsed)
All verified closed; kept for traceability. Issue numbers are in the Closed Issues table at the bottom of this file.
- ✅ Sign-up form validation (date entry, payment)
- ✅ Server-side speciality resolution layer maps regulator-reported labels to PPP
specialityId - ✅ Sign-up Speciality field is pre-selected from the resolved
specialityIdwhen GMC verification succeeds - ✅
MyProfileregistration edit flow runs the same resolution and prompts the user before overwriting a stored speciality - ✅ Unmapped regulator labels leave the field unset, log a structured warning, and raise an admin notification
- ✅ Canonical PPP speciality list broadened to cover physician, surgical, anaesthesia/critical-care, obstetric, paediatric, diagnostic, psychiatric, and primary-care specialties
- ✅ CPD requirement triggers remain correct after the broadened list lands
- ✅ Empty email on registration shows "Email is required", not "Invalid email format"
- ✅ "Registered specialist?" required field shows validation error when unselected
- ✅ AHPRA "Verified" badge replaced with honest copy while in format-only mode
- ✅ Welcome email failure surfaces a resend path rather than silent failure
- ✅ Scheduled cleanup removes stale quarantine/signup uploads
- ✅ Sign-up CV (PII — name, contact details, employment history) is uploaded privately to the dedicated
ppp/cv_uploads/prefix via the unauthenticated signup endpoint (no auth token exists yet at sign-up), not the co-mingled, formerly-"public"cpd_activity_files/bucket. The blob is never anonymously reachable — storage containers are provisionedallowBlobPublicAccess:false/publicAccess:Noneand reads are served only via short-lived SAS-signed URLs (storageClient.get→getSignedReadUrl). Signup-failure rollback honours both the new and legacy prefixes so no orphan leaks during the transition. ‡ - ✅ Sign-up flow displays a prominent warning callout (not a subtle nudge) recommending a personal email over a hospital email, explaining that work emails can be switched off on changing employer and offering a work email as a backup sign-in later. The bold "Use a personal email address" heading is an accessible MUI Alert (
severity="warning",role="alert", theme warning palette — no hardcoded hex) so the warning is announced to assistive tech. †‡ - ✅ Sign-up "Are you a registered specialist?" → when the user selects "Yes" but the registration body has not confirmed consultant/specialist status, a "Consultant Verification Required" warning is shown for both GMC and AHPRA (previously GMC only). Consultant status is enforced server-side from the AHPRA/GMC lookup regardless of this UI hint — see Medical Registration Verification. ‡
Payment (sign-up step 2)
- ✅
onboarding.signup.price-matches-country— the sign-up Payment step (step 2) shows prices in the doctor's country currency: AUD for Australia, GBP for the UK. The currency is taken from the Country of Primary Practice entered on the Registration step, and it sets the Stripe billing-country default. Figures come from the canonical pricing table: PPP Full Platform is A$1,699 incl. GST from 2026-08-20 (Matt, WhatsApp), and CPD Home is A$299. Q9 asks whether the regulatory body should lock the currency instead of the Country field.Sign-up Step 3 pricing shows AUD only in v1 — GBP deferred to UK launch per Q4.Superseded: the "AUD only in v1" wording conflicted with Matt's 2026-04-21 direction ("Im ok with the GBP prices as they are outlined for Uk users") and with the shipped country-based currency (#5255, #5863). It also named the wrong step. †‡ - ✅ AUD prices are shown GST-inclusive with
tax_behaviorleft unset — GST is embedded in the displayed price, not added via Stripeautomatic_tax, and no Stripe Tax dashboard config is required. GBP tax handling is deferred to UK launch. (Matt's 2026-05-05 decision; this supersedes the rejectedautomatic_tax-exclusive option from the 28 Apr proposal.) ‡ - ✅
payment_intent.succeededwebhook tolerates firing before the user row exists.
The ongoing billing lifecycle (refunds, upgrades/downgrades, the Customer Portal, /billing reachability) is out of this spec's scope — see Onboarding — Payments lifecycle and Payment.
CPD Plan (sign-up step 3)
- ✅ CPD plan list items are clickable during sign up.
- ✅ The sign-up "Suggested CPD Plan" dialog exposes a "Use this plan" action that pre-fills the CPD Plan step with the suggested activities, matching the in-app
/cpd-plansflow. At sign-up it merges the suggested activities into any the doctor has already picked on the CPD Plan step (their picks are never dropped), and suggested activities are matched to the activity list by normalised name so none is silently skipped (#12766). ‡
Current Status
| Sub-feature | Status | Notes |
|---|---|---|
| AHPRA / GMC validation | ✅ Built | Mar 2026 — own spec, Medical Registration Verification |
| 3-step sign-up flow | ✅ Built | Registration number first field |
| Registration fields | ✅ Built | Additional-specialities prompt added (#12746) |
| Sign-up payment (step 2) | ✅ Built | AUD/GBP by Country of Primary Practice; Q9 asks about locking to the body |
| Sign-up CPD plan (step 3) | ✅ Built |
Open GitHub Issues
Open issues on label:feature:signup-registration — issue data unavailable at build time.Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Original Vision
Registration & Medical Verification
- AHPRA validation (Australia) — live lookup against the public AHPRA register via our own client (
ahpraRegistrantService/ahpraScrapeClient.ts), not PCA ✅ - GMC validation (UK) — integrated (#3939). Licence-status enforcement (active licence allow-list) is specified in auth.md — GMC Licence Status Enforcement (#5069).
- Email-based registration
Speciality resolution & canonical list (#4613)
The server-side speciality-resolution layer (regulator label → PPP canonical specialityId), the unmapped-label handling, profile-edit overwrite prompt, and the broadened canonical speciality list are specified authoritatively in Medical Registration Verification — that spec owns the regulator-integration detail so it lives in one place. The delivered ACs are tracked in the ✅ Delivered block under Registration above; this section is a cross-reference only to avoid duplicating (and drifting) the narrative.
Closed Questions (4) — click to expand
| # | Question | Source | Status |
|---|---|---|---|
| Q1 | Auto-determine Consultant vs Non-Consultant from registration number — which data source gives us the cleanest signal in AU and UK? | Primary Registration field | Resolved 5 May (code audit + Matt's 3 May "need more clarity here"). Both regulators are wired up and surface what we need. AU/AHPRA: PCA FHIR client (ahpraRegistrantService/pcaClient.ts) returns a qualifications[] array per practitioner — e.g. ["Medical Practitioner", "Specialist General Practitioner"] for a GP, ["Medical Practitioner", "Specialist Anaesthetist"] for an anaesthetist. In AU's data model GP is a Specialist Registration sub-type (specialty = General Practice), not a separate register — there's no AHPRA equivalent of UK's GP Register. Our hasEndorsedSpecialty derivation flags any "Specialist *" qualification as Consultant — captures GPs correctly. UK/GMC: gmcRegistrantService/validateConsultantStatus.ts already returns separate flags isConsultant (Specialist Register), isOnGpRegister, and specialistRegisterEntries[] (e.g. ["General surgery"]). Engineering proposal: in v1 keep the binary Consultant/Non-Consultant for userType (drives feature gating in CPD Home, WBA permissions, etc.); also persist a display-only specialty field surfaced in profile/UI. Q for Matt to ratify: OK to ship binary + display-specialty for v1? |
| Q2 | Two-department users — capture both at sign-up, or defer the secondary department to Profile? | Speciality confirmation | Answered 2026-05-03 (Matt): Yes — defer secondary to Profile; add a sign-up prompt saying "You can add additional departments/specialities later via Profile." The prompt became onboarding.signup.additional-specialities-prompt (2026-10-03), built in #12746. Follow-up Matt raised: check whether Consultant flag activates additional high-level specialist requirements in CPD Home. Engineering 5 May: yes — the Consultant-vs-Non-Consultant flag drives the CPD plan target hours and required category split (cpdPlanService/index.ts + cpdPlanSuggestionService/index.ts); see cpd.md for the role-target matrix. Adding specialty in v1 does not change required hours (same CPD Home target by Consultant/Non-Consultant), but the specialty label is surfaced in the dashboard widgets per dashboard.md. Resolved. |
| Q3 | Temp password flow — current platform UX, confirm it matches current build | Screenshots commentary | Answered 2026-05-03 (Matt): Yes — temp password emailed; force change on first login. Matches current build. Resolved. |
| Q4 | Stripe VAT/GST for AUD and GBP — display tax-inclusive, enable Stripe automatic_tax, or defer? (#5140) | Payments drift rebaseline | Resolved 5 May (legal constraint). Matt 3 May proposed ex-GST/ex-VAT display; engineering legal-checked and ex-tax display is unlawful for B2C in AU and inadvisable in UK — see ACCC § 48 / Component Pricing (mandatory single tax-inclusive figure when offering to consumers; ex-GST permitted only B2B) and the UK DMCCA 2024 Part 4 Ch 1 pricing-transparency duty for services. v1 decision: public pricing page (B2C, individual doctors) shows a tax-inclusive single price (the canonical AUD figures GST-incl; GBP at UK launch VAT-incl). automatic_tax = on for AUD now and GBP at UK launch.tax_behavior unset, no automatic_tax (see the Payment ACs). Enterprise B2B contracts (hospitals/Networks) may show ex-GST/ex-VAT line items in the contract since that audience is B2B — separate from the public pricing page. The three commercial sub-questions Matt raised alongside this (enterprise token, billing cycle, refund) are tracked as open Q10. |
Closed Issues (16) — click to expand
| # | Title / AC delivered | Closed |
|---|---|---|
| #4613 | Server-side speciality resolution layer, unmapped-label handling, broadened canonical list | 2026-04-15 |
| #4620 | CPD plan list items clickable during sign-up | 2026-04-28 |
| #4792 | AHPRA "Verified" badge replaced with honest copy in format-only mode | 2026-04-23 |
| #4894 | Empty email shows "Email is required", not "Invalid email format" | 2026-05-19 |
| #4903 | "Registered specialist?" required-field validation error | 2026-05-19 |
| #5140 | AUD prices shown GST-inclusive, tax_behavior unset | 2026-05-20 |
| #5183 | Scheduled cleanup removes stale quarantine/signup uploads | 2026-05-19 |
| #5189 | Welcome email failure surfaces a resend path | 2026-05-19 |
| #5255 | Sign-up Payment step priced in the doctor's country currency (fixed by PR #5863) | 2026-05-07 |
| #7021, #7301, #7852 | Sign-up displays warning recommending personal over hospital email | 2026-06-01 |
| #7640 | Registration number moved to the first field of the Registration step | 2026-05-27 |
| #7643 | "Consultant Verification Required" warning for unconfirmed specialist claim | 2026-05-27 |
| #7720 | Registration fields password-manager & autofill friendly | 2026-05-27 |
| #7728 | Suggested CPD Plan dialog "Use this plan" action | 2026-05-27 |
| #7761 | Date of Birth field dd/mm/yyyy for AU/UK users | 2026-05-27 |
| #9194 | Sign-up CV upload moved to private prefix, SAS-signed URLs | 2026-06-29 |
Change Log
| Date | Change | PR/Issue | Reason |
|---|
| 2026-10-04 | Sign-up "Use this plan" now merges the suggested activities into what the doctor has already picked on the CPD Plan step instead of replacing it, and matches suggested activities to the activity list by normalised name (trim, collapse spaces, ignore case) so none is silently dropped. Not done yet — the "X hrs still to plan" message and the sign-up BDD scenario (the payment step cannot be completed on a local stack). | #12766 | UAT practice run (Rob, 2026-10-03) lost manual picks after "Use this plan" and applied only 2 of 4 suggested items. The public suggestion endpoint carries no activity ids, so the exact-name lookup dropped rows whose stored spelling differed. | | 2026-10-04 | The CV attachment on sign-up step 1 is optional. The field is no longer marked required and Next proceeds without a file; a CV that is attached is still type- and size-checked. The profile/onboarding nudge to upload a CV later is NOT built — there is currently no post-sign-up CV upload surface (the Passport CV tab only displays an uploaded file). | #12783, #12876 | signup-registration.md field list says "CV upload (can be deferred — not required at sign-up)" and states CV is completed after sign-up on the dashboard. Reported by Rob on UAT 2026-10-03. Remainder (upload surface + checklist nudge) filed as #12876. | | 2026-10-04 | Sign-up step 1 reserves space for the async messages under the registration number (GMC specialty hint, verification error, GMC prompt) and under the specialist radios (suggested user type banner), and the CPD-consent checkbox is spaced clear of the "English is a second language" checkbox. A BDD scenario asserts the consent checkbox does not move when the GMC lookup completes. | #12784 | UAT run-through (Rob, 2026-10-03) — a click aimed at the consent checkbox landed on the ESL checkbox after the lower form shifted, and the ESL value persisted on the new account. | | 2026-10-03 | The sign-up Speciality field now shows the prompt "You can add additional departments/specialities later via Profile." as its helper text (replaced by the validation error when one is shown). It adds no required field. | #12746 | Matt (Notion Sign up - doctor, comment 2026-05-03, answering Q2) asked for a prompt saying other departments/specialities can be added through Profile. Profile already supports more than one speciality (userSpecialities, RoleSpecialtySection). | | 2026-10-03 | Restored this spec in git (Rob's 2026-10-03 decision) from the surviving generated copy of the 2026-09-29 split, in source shape with archival material at the bottom. Moved — not copied — every sign-up AC out of onboarding.md, with Task 6's 2026-10-03 refresh winning wherever the two disagreed. AC IDs kept unchanged (onboarding.signup.price-matches-country, onboarding.signup.additional-specialities-prompt), as were question numbers (closed Q1–Q4, open Q9 and Q10). New github-label feature:signup-registration; #12746 re-labelled to it. code-paths: claims instances/ppp/src/modules/identity-profile/signup/**; onboarding.md now claims only the SSO completion files inside it. Status is partial-drift (#12746). | #11187, #12746, #12627, #5255, #5863 | The 29 Sep copy said "AUD only in v1" for sign-up pricing, had no Open Questions, and had no additional-specialities AC. Task 6's dated Matt sources supersede all three: Matt accepted GBP for UK users on 2026-04-21 (#5255), the 2026-05-03 prompt requirement is not built (#12746), and Q9/Q10 are open. The 29 Sep copy was right that #9194 is closed (2026-06-29); the "stays open" note carried in onboarding.md was stale and is dropped. Closed issue numbers moved out of the visible AC text into a Closed Issues table, following the 2026-09-29 template rules (#12627). Closed Q4's "Stripe automatic_tax = on" wording is struck through, superseded by Matt's 2026-05-05 GST-inclusive decision (#5140). | | 2026-09-29 | Split out of onboarding.md as its own spec (Rob's decision) — the 3-step sign-up flow, registration fields and sign-up-time payment. Guided tour and SSO profile completion stay in onboarding.md. | #11187, #11189 | Task 6 ("Sign up and Registration") and Task 7 ("Onboarding") are reviewed as separate async tasks with separate videos and sign-off; the spec structure now matches, closing the scope ambiguity found while reviewing Task 7. The source file from this split never reached git (only a gitignored generated copy survived); see the 2026-10-03 restore entry. |## Sources & Recordings
| Source | Notes |
|---|---|
| https://www.notion.so/Sign-up-doctor-344b6928417380baba76cf6efd075bb2 | Matt's Sign up - doctor brief + 2026-05-03 comment thread (last edited 2026-05-26) |
| https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6E | Description pending SGD audit |
| https://docs.google.com/document/d/1YhgQSFL9iOlQLoTrQYSwxRNXH4Dg4wefkItcwljQZmo | Description pending SGD audit |