Practice Hub

Practice Hub is a full-stack web application that serves as a centralized credentialing profile hub for licensed therapists in private practice. The clinician builds and maintains a single, structured master profile containing every piece of information that credentialing bodies and insurance panels repeatedly ask for: NPI number, practice addresses, active state licenses with expiration dates, professional liability insurance details, educational degrees, contracted insurance panels, and a professional vitae. From this master profile, the application generates platform-specific templates — formatted, copy-paste-ready documents tailored to major platforms like Headway, Alma, and TherapyNotes/Unite Native, as well as smaller group practices and EHR-based organizations. Additionally, Practice Hub exports a standardized, machine-readable data file (JSON and/or PDF) that can be handed directly to a credentialing coordinator at a new organization, eliminating the back-and-forth of credentialing packets. The application is built on a React and Vite frontend, an Express 5 REST API backend, PostgreSQL with Drizzle ORM, and Clerk for per-therapist authentication and data isolation, with the full API defined in an OpenAPI 3.1 specification from which TypeScript client hooks are auto-generated.

The credentialing process is one of the most significant and least-discussed administrative burdens in mental health private practice. A therapist seeking to join a single insurance panel — Headway, Alma, or a smaller regional EAP group — may be asked to submit essentially the same information dozens of times across dozens of application forms: their NPI number, taxonomy code, practice address, mailing address, each active state license number and expiration date, professional liability carrier name and policy limits, CAQH profile number, educational history, and often a formatted CV or professional bio. This information almost never changes, yet therapists are routinely asked to re-enter it from scratch because no single tool exists to hold it in a structured, reusable way. The result is hours of redundant administrative labor every time a clinician wants to expand their practice by getting paneled on a new service — labor that directly reduces clinical capacity and creates error-prone manual transcription. Practice Hub is motivated by the observation that this is fundamentally a data management and templating problem, not a technical integration problem. A well-designed profile and export system, requiring no external API access whatsoever, could eliminate the majority of this burden.

The capstone team's central objective is to build Practice Hub from its current infrastructure foundation into a complete, production-quality credentialing profile and template generation system.

• A comprehensive therapist profile editor with multi-step form flows for entering credentials, licenses, insurance details, education history, and professional vitae
• Automated template generation for major platforms (Headway, Alma, TherapyNotes/Unite Native) and custom exports
• JSON and PDF export functionality for credentialing coordinators
• User authentication and data isolation using Clerk
• A well-documented REST API with OpenAPI 3.1 specification and auto-generated TypeScript client hooks
• A normalized PostgreSQL schema managed through Drizzle ORM

• Working knowledge of TypeScript or JavaScript;
• Experience building forms and data entry interfaces in React, including multi-step or wizard-style form flows appropriate for a complex profile with many fields;
• Understanding of REST API design and relational database concepts at the level of defining normalized schemas with multiple related tables;
• Comfortable with Git-based collaboration workflows.

Students should understand how to handle file uploads (for the document vault feature) and have basic familiarity with PDF generation from code

• Experience with react-hook-form, Zod, or similar form validation libraries, as the credentialing profile form is extensive and validation is critical — an expired license date that slips through is a meaningful error in this domain;
• Familiarity with a document generation library such as pdf-lib, Puppeteer PDF rendering, or React-PDF;
• Prior work on data export features (CSV, PDF, or JSON);
• Experience with Drizzle ORM or a comparable TypeScript ORM;
• Exposure to the OpenAPI specification and codegen workflows.

An interest in UX design for data-heavy professional tools is highly valuable — the profile editor involves many fields, and the team will need to think carefully about progressive disclosure, section grouping, and completion state tracking so the experience does not feel overwhelming.

Prior exposure to healthcare administration, insurance billing, or clinical operations is a meaningful differentiator given the domain-specific vocabulary involved.