Skip to content

Plans Index

Ankit Upadhyay edited this page Aug 25, 2026 · 2 revisions

Design Docs & Plans

Engineering plans and implementation guides live in docs/plans/ in the repo — each is the design brief for a feature or workstream. This section groups them by theme, summarizes each, and tracks status. The repo file is canonical; these pages exist so you can browse the plans without cloning.

There is also a broad, living PIMS architecture guide (docs/guide/pims-architecture.md) that is the source of truth for new module design across the clinical workflow (appointments, SOAP, vitals, prescriptions, treatment plans, inventory, finance, discharge, and more). The plans below are the deeper, per-workstream briefs.

Plans by theme

All 18 files currently in docs/plans/ map into these theme rows (multi-file workstreams such as currency and companion history are grouped into a single row).

Theme What it covers Repo file(s)
Payments and Currency Multi-currency (EUR/USD/GBP) across backend, web, mobile; invoice linking for mobile-booked appointments. currency-backend-stripe-implementation-guide.md · currency-frontend-web-implementation-guide.md · currency-mobile-implementation-guide.md · backend-invoice-linking-for-mobile-booked-appointments.md
Authentication SuperTokens migration (ADR-0003); passkeys, MFA/2FA for the web PIMS. supertokens-migration.md · supertokens-frontend-handover.md · supertokens-mobile-handover.md · pms-web-passkey-mfa-2fa-implementation-guide.md
Support Chat A Stream-based support channel connecting PMS/mobile users to Superadmin support. backend-support-chat-engineering-guide.md · pms-mobile-support-chat-guide.md · superadmin-support-chat-from-scratch-guide.md
Companion and Clinical History A unified, org-scoped medical-history timeline (backend + frontend). companion-history-backend-guide.md · companion-history-frontend-guide.md
Clinical Terms / SOAP Inline clinical-term autocomplete in the SOAP form. clinical-terms-soap-frontend-guide.md
PMS Documents Carry newly captured document metadata through the create path. pms-document-backend-guide.md
Mobile App Update Remote force/optional app-update policy. mobile-app-update-backend-guide.md
Super Admin A production-grade multi-tenant governance/admin app. Superseded - the shipped SuperAdmin app diverged from this design (Next.js + SuperTokens rather than the plan's stack); the plan is kept as a historical design document. super-admin-production-grade-plan.md
Frontend Convergence Normalize the design system and converge web/mobile tokens. frontend-platform-convergence-plan.md

How these relate to the roadmap

Plans are the how; the Roadmap is the when/what. Many plans map directly to an active workstream or epic (e.g. the SuperTokens plan ↔ epic #1672, payments ↔ #1659). Developer-platform designs (data API, MCP server, AI agent, website builder) are captured under Developer Portal and ADRs 0004/0005.

Related

Product & Domain
Architecture
Applications
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Roadmap
Operations
Meta

Canonical code & docs: main repo · Auto-generated companion: DeepWiki

Clone this wiki locally