Back to projects
Internal Tools

Internal Healthcare Operations Platform

Swing Therapeutics · Lead Software Engineer / Lead Hands-on Engineer

Swing Therapeutics | Internal Tools / Healthcare Operations

Led hands-on development of a React, Next.js, and TypeScript internal healthcare operations platform supporting staff workflows, documentation, messaging, reporting, and visual workflow automation behind SSO and role-based access.

ReactNext.jsTypeScriptViteFirebaseReact FlowTanStack QueryTailwind CSS
Abstract architecture diagram — no product screenshots

Overview

Modern React and Next.js web application engineering for an internal healthcare operations platform. The staff-facing application supported clinical and operations workflows spanning documentation, messaging, reporting, and visual workflow automation behind Google SSO and role-based access. Firestore backed console data directly, while healthcare-adjacent systems were reached through a separate API platform. The stack also included Vite for related frontend tooling. This case study is NDA-safe and omits private workflows, screenshots, and internal identifiers.

My Contribution

  • Built and maintained complex React and Next.js web experiences for internal clinical and operations teams, including permission-aware workflows, reporting, messaging, and automation tooling
  • Implemented Google SSO, allowlisted staff access, route-level authorization, and fine-grained RBAC
  • Built a React Flow–based visual workflow builder that publishes graph definitions to an external execution platform
  • Delivered reporting and export tooling with calculated fields, table filtering, and spreadsheet output
  • Integrated external healthcare operations, messaging, support, and care-pathway systems through a centralized API client
  • Supported multi-environment and multi-brand deployments through Firebase Hosting and configuration-driven navigation

Technical Architecture

  1. Staff authenticate with Google via Firebase Auth
  2. Allowlist, workspace access checks, and RBAC
  3. Permission-aware navigation into operational modules
  4. Firestore for console application data
  5. TanStack Query for server-state and reporting data
  6. Centralized API client to healthcare-adjacent systems
  7. React Flow builder publishes graphs to an external execution platform
  8. Reporting and spreadsheet exports
  9. Firebase Hosting for multi-environment deployments

Engineering Challenges

  • Large internal SPA surface with permission-aware navigation
  • React Flow graph transformation and safe publication to an external execution system
  • Multiple healthcare-adjacent integrations behind one API client layer
  • Workspace and multi-brand configuration without fragmenting the codebase
  • Reporting and export complexity with limited automated coverage

Reliability, Privacy, and Security Considerations

Staff tooling required SSO, allowlisting, and RBAC before exposing operational modules. Secrets and environment configuration stayed outside the client bundle. This portfolio omits private workflows, screenshots, patient data, and internal resource names.

Engineering Outcomes

  • Centralized multiple internal workflows into one staff platform
  • Improved consistency of permission-aware access
  • Enabled visual configuration of internal automations
  • Supported repeatable multi-environment deployments
  • Gave operations teams consolidated reporting and export tools

Technologies

  • React, Next.js, TypeScript, Vite, React Router, Tailwind CSS, TanStack Query, TanStack Table
  • Firebase Auth, Firestore, Firebase Hosting
  • React Flow, Radix UI, React Aria, React Hook Form, Zod, SheetJS, TipTap, Vitest
  • Integrations: Google Identity, external healthcare operations API, EHR-adjacent integration, Iterable, Awell, Zendesk, Slack, Auth0 for consumer-user administration