Development criteria
It turns the relationships and states of patients, appointments, and records, key user flows, recovery paths, and completion conditions into an implementable specification.
HEALTHCARE PROMPTS
How should a Healthcare site be designed? Model the relationships and states of patients, appointments, and records first, then treat privacy, plain language, and urgency as a primary risk. Each service guide below combines an implementation specification with design standards.
10 REAL SERVICES
Development prompts and DESIGN.MD for 10 real services designed around health information and access to care.
ANSWER GUIDE
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
It turns the relationships and states of patients, appointments, and records, key user flows, recovery paths, and completion conditions into an implementable specification.
Start from A portal interface for Healthcare, centered on patients, appointments, and records, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Treat privacy, plain language, and urgency as a primary design risk and define loading, empty, error, partial-data, and success states.