Partner portal

Charity

Charity sponsors: sponsorship decisions, validation summaries shared with charity under consent, charity-tagged cases on patient journeys.

Implementation status: requirements documented — authenticated workflows not built (blocked on backend).

Intended users

  • Charity sponsors making sponsorship decisions on patient cases.

Authentication & access

  • Invitation-based; charity shell shares org/billing/users with employer/insurer shells (OPS handoff).

Onboarding

  • Charity organisation profile and sponsor permissions.

Navigation & screens (Figma)

  • CHR-04 Sponsorship decision (pending/approved/rejected).

  • Validation summaries shared with charity under consent (FR-CHR references).

Workflows

  • Case flagged for charity → charity reviewer decision → patient journey updates.

Permissions boundary

  • Charity users see only consented case summaries for their programme.

  • Cannot access expert clinical editor or provider quotations.

Backend capabilities needed (no API paths in repo)

  • Sponsorship decision API with audit trail.

  • Consent-scoped case summary delivery.

UI states to implement

  • No pending decisions

  • Decision submitted

  • Expired case

  • 403

Acceptance criteria

  • CHR-04 decision screen reflects live case state and persists decision.

  • No PII beyond consented fields.

Figma references

← All categories