A prototype Next.js application that demonstrates how automation, AI-supported risk scoring, and structured intake workflows can modernize healthcare revenue cycle management. The project powers the live demo on Vercel and serves as a foundation for further experimentation.
- Multi-surface experience – landing page, dashboard, intake form, backlog, claims review, workflow map, and vision narrative all share a consistent visual language powered by Tailwind CSS and Radix UI.
- Automation storytelling – mock data pipelines (see
lib/get-claims.ts) showcase how claim risk scores, KPI cards, and charts could surface automation opportunities. - Design references included – the
docs/promptsdirectory stores the V0 design prompts and system notes that guided the build so future contributors can understand the original intent.
- Next.js 16 with the App Router
- React 19 and Server Components
- Tailwind CSS 4 with custom design tokens
- Radix UI Primitives and lucide-react for accessible UI elements
- Recharts for dashboard visualizations
- Vercel Analytics ready for deployment insights
app/ # Route groups (landing page plus nested dashboard, intake, claims, etc.)
components/ # Shared UI primitives (cards, buttons, navigation, charts, footer)
docs/prompts/ # Exported V0 prompts and design-system notes
hooks/ # Reusable React hooks for theme and UI state
lib/ # Helper utilities and mock data (e.g., getClaims)
public/ # Static assets (logos, illustrations, favicons)
styles/ # Tailwind configuration helpers
- Install dependencies
pnpm install
- Run the development server
Open
pnpm dev
http://localhost:3000in your browser to view the app. - Create a production build
pnpm build && pnpm start
Node version: Next.js 16 requires Node.js 18.18+ or 20+. The project was tested with Node 20 on Vercel.
| Command | Description |
|---|---|
pnpm dev |
Start the local Next.js dev server |
pnpm build |
Create an optimized production build |
pnpm start |
Run the production server after pnpm build |
pnpm lint |
Execute ESLint across the repository |
The repo is configured for Vercel. After pushing changes:
- Ensure the project builds locally with
pnpm build. - Connect the GitHub repo to Vercel (if not already connected).
- Vercel will detect Next.js automatically and handle build output + serverless deployment.
Design references live in docs/prompts:
design_system_full_markdown.md– high-level design tokens, spacing rules, and typography guidelines.v_0_prompt_markdown.md– the original V0 generation prompt.landing_page_update_prompt.md– iteration notes for the landing page.about_page_additions_prompt.md– copy and layout guidance for the About page.
These files explain why the UI looks the way it does and are helpful when collaborating with design partners or generating new V0 iterations.
Distributed under the terms of the MIT License.