Where we're going
This platform is built in the open, shaped by the healthcare professionals using it. Here's what's shipped and what we're working toward.
Foundation & Community
The core platform: professional discussions, AI-assisted privacy, and clinical case sharing. Live since February 2026.
- ✓Professional profiles with discipline and verification status
- ✓Multidisciplinary discussion threads
- ✓AI-powered discussion summaries (Claude)
- ✓AI anonymization checker with privacy gate
- ✓Discipline filtering across feed
- ✓Code of conduct & privacy framework
- ✓Invite-only registration with server-controlled lifecycle
- ✓Structured case posting with clinical categories
- ✓Body region diagram for pain/symptom marking
- ✓Password reset / forgot password flow
- ✓API authentication & input validation
- ✓Security headers (XSS, clickjacking, HSTS, CSP)
- ✓Email notifications on new responses
Quality, Trust & Foundation-Laying
A broad pass to tighten what exists, improve surfaces, and lay groundwork for what comes next. Shipped March 2026.
- ✓Global error boundary - component crashes no longer white-screen
- ✓Skeleton loading states across feed, threads, and profiles
- ✓Toast notification system for user feedback
- ✓Member profile pages (/members/[id]) with recent contributions
- ✓Hover cards on professional names for quick trust-building
- ✓New disciplines: Dietitian, OT, Social Worker, Speech Therapist, Podiatrist
- ✓RIZIV/INAMI format validation (soft, non-blocking)
- ✓Response helpful upvotes persisted server-side (Supabase)
- ✓View Transitions for smoother page navigation
- ✓Notification delivery defaults established for private beta
- ✓Accessibility: ARIA labels, keyboard navigation, prefers-reduced-motion
- ✓Security audit: console cleanup, auth verification, error sanitization, and RLS access-control baseline
- ✓Shared timestamp utilities - consistent relative/absolute dates everywhere
- ✓TypeScript strictness improvements across touched files
Trust & Clinical Intelligence
Deeper verification, server-side persistence, and the first steps toward clinical evidence integration.
- ○Upvote abuse safeguards and moderation signals
- ○Notification preferences stored server-side (moving from local beta storage)
- ○RIZIV verification Tier 2 - cross-reference with Belgian registry
- ○Supabase Row Level Security (RLS) follow-up hardening and policy tests
- ○Rate limiting on all public-facing API endpoints
- ○Automatic PubMed evidence surfacing per case
- ○Similar past cases surface automatically
- ○Smart routing - right experts notified for right cases
- ○GDPR & EU AI Act compliance review
Collective Intelligence
AI that learns from the growing knowledge base to surface patterns and insights at scale.
- ○AI pattern detection across cases
- ○Evidence strength scoring
- ○Outcome tracking - what worked, what did not
- ○Institution accounts (clinics, hospitals, universities)
- ○Multi-language support (NL/FR/EN)
- ○International expansion beyond Belgium
Built transparently
PATH B is built by a physiotherapist with feedback from clinicians. Most shipped features now run server-side. During private beta, account-level notification preferences still use local browser storage while server-side controls are finalized.
Have a suggestion?
This roadmap is shaped by the community. If something is missing or wrong, reach out directly.
pathbcareplatform@gmail.com