Skip to content
UT Studio
HealthcareNewPreview only

Clinic

Healthcare network site and patient portal built around longer appointments

Preview only — not yet on sale.

Pro licence · what that covers

Latest version
1.0.0
Updated
Difficulty
Intermediate
Licence
Pro
Clinic healthcare homepage introducing the practice and its approach to appointments
Homepage1 of 4

Clinic screens

Homepage1 / 4

Clinic healthcare homepage introducing the practice and its approach to appointments

Clinic healthcare homepage introducing the practice and its approach to appointments

At a glance

Type
Healthcare
Best for
Patient portal · Booking & enquiry · Marketing site
Stack
TypeScript · Next.js · Tailwind CSS
Screens shown
4Captured from the live preview
Areas of care
8Each with its own page
Clinicians
9Across four clinics
Licence
Pro · 1 developer12 months of updates
Availability
PreviewLive preview open now

Built for

What this template is for. Each one is a filter in the catalogue, so the products beside it solve the same problem.

Overview

Healthcare interfaces usually feel rushed because the practice behind them is scheduled to be. Clinic is designed the other way: eight areas of care, named clinicians, four locations and a patient portal where the care plan is something you can read and keep. The tone is the product — calm, specific and free of the stock imagery that makes every private practice look like the same practice.

What's inside

  • Areas of care

    Eight care areas, each linked to the clinicians who actually practise it.

  • Clinicians

    Named clinicians with specialties and locations, joined rather than duplicated.

  • Locations

    Four buildings with the practical arrival detail a patient needs on the morning of a visit.

Explore the experience

Every screen below is the deployed template, captured from its own live preview.

  1. 01

    Areas of care

    Eight care areas, each linked to the clinicians who actually practise it.

    • Linked clinicians
    Clinic specialties page listing the practice's areas of care
    Areas of care
  2. 02

    Clinicians

    Named clinicians with specialties and locations, joined rather than duplicated.

    • Specialty and location
    Clinic clinician directory with names, specialties and locations
    Clinicians
  3. 03

    Locations

    Four buildings with the practical arrival detail a patient needs on the morning of a visit.

    • Visiting information
    Clinic locations page listing the practice's buildings and visiting information
    Locations

What's included

  • The full source archive, with the first release
  • 12 months of updates, kept permanently
  • 1 developer — commercial use, including client work
  • Deployment guides for 3 targets
  • Email support for the length of your update window
  • Redistribution as your own product

Every line above is read from this product’s own licence and release record rather than written beside it, so it cannot promise something the release does not contain.

Architecture

Care pathway as the organising model

Register, first visit, written plan, between visits and annual review are stages of one pathway, and every public page and portal screen is positioned against it. Clinicians, specialties and locations are joined records, so a clinician page lists the right locations without anybody maintaining a second list.

Tech stack

Built with

What the product is implemented in.

Requires

What you must already have. These block installation.

Folder structure

Folder structure
clinic/
├── app/
│   ├── page.tsx
│   ├── specialties/[slug]/page.tsx
│   ├── clinicians/[slug]/page.tsx
│   ├── locations/page.tsx
│   └── resources/page.tsx
├── components/
└── content/

Requirements

Node.js
≥ 22.12LTS or current
Package manager
pnpm ≥ 10npm and yarn also work
Operating system
macOS, Linux, Windows (WSL2)

Installation

  1. Unpack the download

    The archive contains the full source. There is no installer and no post-install script.

    bash
    unzip clinic.zip
    cd clinic
  2. Install dependencies

    bash
    pnpm install
  3. Configure the environment

    Copy the example file and fill in the variables listed under Environment variables.

    bash
    cp .env.example .env

Quick start

  1. Start the development server

    bash
    pnpm dev
  2. Verify the install

    Runs formatting, lint, type-check, tests and a production build.

    bash
    pnpm check

Environment variables

Environment variables
VariableRequiredDescription
DATABASE_URLRequiredPostgreSQL connection string. Use a pooled endpoint in serverless environments.postgresql://user:pass@localhost:5432/app
NEXT_PUBLIC_APP_URLRequiredAbsolute origin of the deployment. Used for canonical URLs and metadata.https://app.example.com
LOG_LEVELOptionaldebug | info | warn | error. Defaults to info in production.

Configuration

    Deployment

    • Vercel

      Zero-config. Set the environment variables listed above and connect the repository.

    • Docker

      A multi-stage Dockerfile is included, producing a standalone image with no build toolchain.

    • Any Node host

      Builds to a standard Node server. Nothing depends on a platform-specific runtime.

    Compatibility

    Framework and runtime versions this product supports
    TechnologyVersionsStatus
    Next.js≥ 15Supported

    What changed in 1.0.0

    Initial commercial release

    • addedInitial commercial release

    Version history

    1. 1.0.0

      Initial commercial release

      • addedInitial commercial release

    Documentation

    Documentation ships with the first release.

    Support

    Frequently asked questions

    Curated by us, not inferred — these are the ones that genuinely pair with it.

    Built with the same stack

    Products that share a framework with this one.

    Further reading

    Documentation and guides that use this template as their example.