Skip to content
LIVERun 001 capturing

planned / v1.0.0

Clinic Patient Journey System

A patient journey system covering enquiry, appointment, visit, diagnosis, follow-up, reminder, review, and return visit.

Open exact prompt

Overview

Evaluate a model's ability to implement Clinic Patient Journey System as a bounded, evidence-backed product challenge.

Capabilities tested

  • timelines
  • consent
  • operations

Required outcome

A patient journey system covering enquiry, appointment, visit, diagnosis, follow-up, reminder, review, and return visit.

Requirements

functional

  • A patient journey system covering enquiry, appointment, visit, diagnosis, follow-up, reminder, review, and return visit.

ux

  • Responsive, readable interface
  • Keyboard-accessible core controls

technical

  • Production build succeeds
  • No secrets or private data in the artifact

Constraints

Allowed

  • Local sample data
  • Established framework utilities

Forbidden

  • Automated model execution
  • Unreviewed private data
  • Unsupported production claims

Acceptance criteria

  • The primary workflow is complete and observable
  • Core controls change real local state
  • Failure or empty states are visible
  • The narrow viewport remains usable

Evidence required

  • Production build output
  • Desktop and mobile screenshots
  • Core-flow recording
  • Known-bug list

Exact prompt

prompts/challenges/clinic-patient-journey.md
# BuildArena Challenge

Role: Senior product engineer.

Project: Clinic Patient Journey System v1.0.0

Objective: Evaluate a model's ability to implement Clinic Patient Journey System as a bounded, evidence-backed product challenge.

Required outcome: A patient journey system covering enquiry, appointment, visit, diagnosis, follow-up, reminder, review, and return visit.

Functional requirements:
- A patient journey system covering enquiry, appointment, visit, diagnosis, follow-up, reminder, review, and return visit.

UX requirements:
- Responsive, readable interface
- Keyboard-accessible core controls

Technical requirements:
- Production build succeeds
- No secrets or private data in the artifact

Constraints:
- Allowed: Local sample data; Established framework utilities
- Forbidden: Automated model execution; Unreviewed private data; Unsupported production claims

Build order: Inspect the environment; establish the smallest vertical slice; verify the central workflow; add secondary requirements; run production validation.

Evidence to return: Commands, test results, screenshots, core-flow recording, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.

Claims prohibited without proof: complete, production-ready, fully working, bug-free, accessible, responsive, performant.