healthcare-ui-design
Clinical-grade UI/UX patterns for healthcare applications across web (Bootstrap 5/Tabler + PHP) and Android (Jetpack Compose + Material 3). Covers patient records, vital signs, medication safety, care plans, scheduling, telemedicine, dashboards, patient portals, and clinical communication. Enforces HIPAA compliance, WCAG 2.2 AA accessibility, medical safety workflows, and role-based interfaces for clinicians, nurses, patients, and administrators. Use when building or reviewing EMR/EHR systems, hospital management, clinic apps, telemedicine platforms, patient portals, health dashboards, or any healthcare-related interface.
Best use case
healthcare-ui-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Clinical-grade UI/UX patterns for healthcare applications across web (Bootstrap 5/Tabler + PHP) and Android (Jetpack Compose + Material 3). Covers patient records, vital signs, medication safety, care plans, scheduling, telemedicine, dashboards, patient portals, and clinical communication. Enforces HIPAA compliance, WCAG 2.2 AA accessibility, medical safety workflows, and role-based interfaces for clinicians, nurses, patients, and administrators. Use when building or reviewing EMR/EHR systems, hospital management, clinic apps, telemedicine platforms, patient portals, health dashboards, or any healthcare-related interface.
Teams using healthcare-ui-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/healthcare-ui-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How healthcare-ui-design Compares
| Feature / Agent | healthcare-ui-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Clinical-grade UI/UX patterns for healthcare applications across web (Bootstrap 5/Tabler + PHP) and Android (Jetpack Compose + Material 3). Covers patient records, vital signs, medication safety, care plans, scheduling, telemedicine, dashboards, patient portals, and clinical communication. Enforces HIPAA compliance, WCAG 2.2 AA accessibility, medical safety workflows, and role-based interfaces for clinicians, nurses, patients, and administrators. Use when building or reviewing EMR/EHR systems, hospital management, clinic apps, telemedicine platforms, patient portals, health dashboards, or any healthcare-related interface.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Required Plugins
**Superpowers plugin:** MUST be active for all healthcare UI work — design decisions, component generation, accessibility audits, and compliance checks.
**Frontend Design plugin:** Required for all web and Android UI generation.
**Companion skills:** Load `webapp-gui-design` for web implementations, `jetpack-compose-ui` for Android implementations. Always load `vibe-security-skill` — healthcare demands zero-compromise security.
# Healthcare UI Design Standards
## Design Philosophy
Five non-negotiable principles for healthcare interfaces:
1. **Clinical Safety First** — UI decisions can impact patient outcomes. Never auto-select medications, never hide allergies, always require confirmation for critical actions. A confusing dosage field can be fatal.
2. **Calm Under Pressure** — Users are stressed, sick, or overwhelmed. Use clean layouts, soft palettes, generous whitespace, and predictable navigation. Reassure, never overwhelm.
3. **Role-Specific Experiences** — Clinicians need rapid-scan dashboards. Nurses need task-oriented workflows. Patients need plain language and large touch targets. Admin needs analytics. Never build one-size-fits-all.
4. **Compliance by Design** — HIPAA, WCAG 2.2 AA, ADA are embedded in every component, not bolted on. Every screen logs access, enforces timeouts, and protects PHI.
5. **Context-Aware Density** — Show the right amount of data for the situation. Triage screens are dense. Patient portals are spacious. Emergency views strip to essentials.
## Tech Stack Integration
| Platform | Stack | Pattern |
|----------|-------|---------|
| **Web** | Bootstrap 5 / Tabler + PHP | Clone seeder-page, use `webapp-gui-design` patterns, extend with healthcare components |
| **Android** | Jetpack Compose + Material 3 | Follow `jetpack-compose-ui` standards, extend with healthcare composables |
| **API** | REST (PHP) | Follow `api-error-handling` + `api-pagination` skills, add HIPAA audit headers |
| **Auth** | Dual Auth + RBAC | Use `dual-auth-rbac` skill with healthcare role extensions |
## Quick Reference
| Domain | Reference File | When to Use |
|--------|----------------|-------------|
| **Colors, Typography, Spacing** | [`references/design-tokens.md`](references/design-tokens.md) | Starting any healthcare screen, theming, token setup |
| **Patient Lookup & Records** | [`references/patient-records-ui.md`](references/patient-records-ui.md) | Patient lists, profiles, medical history, timeline views |
| **Vitals, Meds, Care Plans** | [`references/clinical-workflows-ui.md`](references/clinical-workflows-ui.md) | Vital sign entry, medication admin, care plan builders |
| **Scheduling & Telemedicine** | [`references/scheduling-telemedicine-ui.md`](references/scheduling-telemedicine-ui.md) | Appointment booking, provider search, video/chat consults |
| **Dashboards & Analytics** | [`references/dashboards-analytics-ui.md`](references/dashboards-analytics-ui.md) | Admin dashboards, KPIs, bed occupancy, risk scores |
| **Patient Portals** | [`references/patient-portal-ui.md`](references/patient-portal-ui.md) | Patient-facing self-service, lab results, payments |
| **Communication & Outreach** | [`references/communication-outreach-ui.md`](references/communication-outreach-ui.md) | Secure messaging, campaigns, health bots, notifications |
| **HIPAA, WCAG, Security** | [`references/compliance-accessibility.md`](references/compliance-accessibility.md) | Compliance audits, accessibility checks, security UI |
| **Web (Bootstrap/Tabler)** | [`references/web-implementation.md`](references/web-implementation.md) | PHP/Bootstrap-specific healthcare components |
| **Android (Compose)** | [`references/android-implementation.md`](references/android-implementation.md) | Kotlin/Compose-specific healthcare composables |
## Core Healthcare Color System
Use semantic clinical colors across both platforms:
| Token | Hex | Usage |
|-------|-----|-------|
| `clinical-primary` | `#2563EB` | Primary actions, headers, navigation |
| `clinical-secondary` | `#0F766E` | Secondary actions, supporting elements |
| `clinical-surface` | `#F8FAFC` | Page backgrounds, card surfaces |
| `clinical-critical` | `#DC2626` | Critical alerts, abnormal vitals, allergies |
| `clinical-warning` | `#D97706` | Warnings, approaching-threshold vitals |
| `clinical-success` | `#059669` | Normal ranges, completed tasks, confirmations |
| `clinical-info` | `#0284C7` | Informational, educational content |
| `clinical-muted` | `#64748B` | Secondary text, metadata, timestamps |
See [`references/design-tokens.md`](references/design-tokens.md) for complete token system.
## Essential Patterns
### Patient Card (Universal Component)
Every healthcare screen that displays a patient must show this minimum context:
```
┌─────────────────────────────────────────────┐
│ [Avatar] John Doe, M, 45y MRN: 1234567 │
│ Allergies: Penicillin ⚠️ Blood: O+ │
│ Primary: Dr. Smith │ Last Visit: 2026-02-20 │
│ ┌─────────┐ ┌──────────┐ ┌───────────────┐ │
│ │ Vitals │ │ Records │ │ Medications │ │
│ └─────────┘ └──────────┘ └───────────────┘ │
└─────────────────────────────────────────────┘
```
**Rules:** Allergy banner is ALWAYS visible (red background if severe). Blood type visible on clinical views. MRN searchable and copyable.
### Clinical Alert Hierarchy
Four-tier alert system — consistent across web and mobile:
| Level | Color | Icon | Behavior |
|-------|-------|------|----------|
| **Critical** | Red bg `#DC2626` | Shield-exclamation | Blocks workflow, requires acknowledgment |
| **Warning** | Amber bg `#D97706` | Triangle-exclamation | Prominent banner, dismissible after read |
| **Info** | Blue bg `#0284C7` | Info-circle | Inline notification, auto-dismiss 10s |
| **Success** | Green bg `#059669` | Check-circle | Toast/snackbar, auto-dismiss 5s |
### Vital Signs Display Pattern
```
┌──────────────┬──────────────┬──────────────┐
│ ❤️ HR: 72 │ 🫁 SpO2: 98% │ 🌡️ Temp: 37.1│
│ bpm [Normal] │ [Normal] │ °C [Normal] │
├──────────────┼──────────────┼──────────────┤
│ BP: 120/80 │ RR: 16 │ Pain: 3/10 │
│ mmHg [Normal]│ /min [Normal]│ [Mild] │
└──────────────┴──────────────┴──────────────┘
```
**Rules:** Color-code each value (green/amber/red) based on clinical thresholds. Show units ALWAYS. Show trend arrows (↑↓→) when historical data exists. Never rely on color alone — include text labels.
### Medication Safety — 5 Rights Check
Before any medication administration, enforce UI verification:
1. **Right Patient** — Display patient name + MRN + photo, require confirmation
2. **Right Medication** — Show drug name + form + strength, barcode scan option
3. **Right Dose** — Display calculated dose with weight-based verification
4. **Right Time** — Show scheduled time vs current time, flag if outside window
5. **Right Route** — Display route (oral/IV/IM/SC), require selection confirmation
Block administration if any check fails. Log all overrides with reason.
## Screen Layout Principles
### Web (Tabler/Bootstrap)
```
┌─────────────────────────────────────────────┐
│ Top Bar: Facility │ Ward │ Shift │ User │ 🔔│
├──────┬──────────────────────────────────────┤
│ Nav │ Context Bar: Patient/Ward/Date │
│ Side │ ┌──────────────────────────────────┐ │
│ bar │ │ Main Content Area │ │
│ │ │ Cards / Tables / Forms │ │
│ │ │ │ │
│ │ └──────────────────────────────────┘ │
│ │ ┌────────────┐ ┌────────────────┐ │
│ │ │ Quick Panel│ │ Activity Feed │ │
│ │ └────────────┘ └────────────────┘ │
└──────┴──────────────────────────────────────┘
```
### Android (Compose)
```
┌─────────────────────────┐
│ TopAppBar: Screen Title │
│ Patient Context Strip │
├─────────────────────────┤
│ │
│ Scrollable Content │
│ (LazyColumn/Grid) │
│ │
│ Cards, Forms, Lists │
│ │
├─────────────────────────┤
│ BottomNav: Home│Patients│
│ Schedule│Chat│Profile │
└─────────────────────────┘
```
## Healthcare-Specific DO's and DON'Ts
### DO
- Display allergies on EVERY screen that shows patient context
- Use confirmation dialogs for all medication and order actions
- Show data source attribution (manual entry vs wearable vs lab)
- Log every patient record access in audit trail
- Differentiate human-entered vs device-captured vitals visually
- Show measurement units on ALL numeric values
- Support offline mode for bedside data entry (sync when connected)
- Use `aria-live` regions for real-time vital sign updates
- Provide undo/cancel within 10s for non-critical actions
- Enforce session timeout (15min inactive) with save-state recovery
### DON'T
- Never auto-select medications from search results
- Never hide the allergy banner for any reason
- Never display PHI in URLs, page titles, or browser notifications
- Never use color alone to convey clinical status — always pair with text/icons
- Never skip confirmation for orders, prescriptions, or discharge actions
- Never store PHI in localStorage, sessionStorage, or unencrypted cookies
- Never show full SSN/ID — mask to last 4 digits
- Never allow copy-paste of patient data without audit logging
- Never use placeholder text as the only label on medical forms
- Never auto-dismiss critical alerts
## Integration with Existing Skills
```
healthcare-ui-design (this skill)
├── webapp-gui-design ──→ Web layout, Tabler components, DataTables
├── jetpack-compose-ui ──→ Android Compose, Material 3, state management
├── vibe-security-skill ──→ HIPAA security, encryption, XSS prevention
├── dual-auth-rbac ──→ Clinical role-based access control
├── mobile-rbac ──→ Android permission gates for clinical modules
├── api-error-handling ──→ Standardized clinical API error responses
├── api-pagination ──→ Patient list pagination (cursor-based)
├── image-compression ──→ Medical image upload optimization
├── photo-management ──→ Patient photo capture and storage
└── report-print-pdf ──→ Clinical report PDF generation
```
## Workflow: Building a Healthcare Screen
1. **Identify role** — Who uses this screen? (Clinician / Nurse / Patient / Admin)
2. **Select layout** — Read platform-specific reference (`web-implementation.md` or `android-implementation.md`)
3. **Apply tokens** — Use `design-tokens.md` for colors, typography, spacing
4. **Build components** — Use domain reference (patient-records, clinical-workflows, etc.)
5. **Add compliance** — Apply `compliance-accessibility.md` checklist
6. **Validate** — Run WCAG checker, test with screen reader, verify HIPAA audit loggingRelated Skills
http-api-design
Design and implement lightweight, ergonomic JSON HTTP APIs for machine-to-machine communication. Use this skill whenever the user is designing API endpoints, writing OpenAPI specs, building REST or HTTP API routes, defining request/response schemas, implementing error handling for APIs, or discussing API contracts.
graphql-api-design
GraphQL schema design, type systems, resolver patterns, DataLoader optimization, pagination, subscriptions, and query complexity management. Use when building GraphQL APIs, designing schemas, migrating from REST, or optimizing query performance.
gemini-frontend-design
Create distinctive, production-grade frontend interfaces using Gemini 3 Pro for design ideation. Use this skill when you want Gemini's creative perspective on web components, pages, or applications. Generates bold, polished code that avoids generic AI aesthetics.
Frontend Responsive Design Standards
Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that works across all screen sizes. Use this skill when creating or modifying UI layouts, responsive grids, breakpoint styles, mobile navigation, or any interface that needs to adapt to different screen sizes. Apply when working with responsive CSS, media queries, viewport settings, flexbox/grid layouts, mobile-first styling, breakpoint definitions (mobile, tablet, desktop), touch target sizing, relative units (rem, em, %), image optimization for different screens, or testing layouts across multiple devices. Use for any task involving multi-device support, responsive design patterns, or adaptive layouts.
frontend-design
Create distinctive, mobile-first Next.js interfaces with high design quality. Use when building pages, components, or layouts. Generates polished code that avoids generic AI aesthetics.
frontend-design-vue
Create distinctive, production-grade Vue 3/TypeScript frontends with exceptional design quality
frontend-design-ultimate
Create distinctive, production-grade static sites with React, Tailwind CSS, and shadcn/ui — no mockups needed. Generates bold, memorable designs from plain text requirements with anti-AI-slop aesthetics, mobile-first responsive patterns, and single-file bundling. Use when building landing pages, marketing sites, portfolios, dashboards, or any static web UI. Supports both Vite (pure static) and Next.js (Vercel deploy) workflows.
frontend-design-pro
Creates jaw-dropping, production-ready frontend interfaces AND delivers perfectly matched real photos (Unsplash/Pexels direct links) OR flawless custom image-generation prompts for hero images, backgrounds, and illustrations. Zero AI slop, zero fake URLs.
frontend-design-2
Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.
feature-sliced-design
Apply Feature-Sliced Design (FSD) v2.1 architectural methodology to frontend projects. Use when organizing code structure, decomposing features, creating new components or features, refactoring existing codebases, or when users mention "FSD", "Feature-Sliced", layers, slices, or frontend architecture patterns.
distinctive-frontend-design
Creates distinctive, production-grade frontend interfaces that avoid generic AI aesthetics. Guides bold aesthetic direction, typography, color, motion, and spatial composition for memorable UI. Use when building frontend components, pages, applications, or interfaces, or when the user asks for UI/UX design, styling, or visually striking interfaces.
dev-api-design
Production-grade API design patterns for REST, GraphQL, gRPC, and tRPC. Covers API architecture, OpenAPI/Swagger specs, versioning/deprecation, authentication/authorization, rate limiting, pagination, error models, contract testing, and developer documentation.