What this prompt does
This prompt directs Claude or ChatGPT to design a telehealth video consultation interface end to end. You set the [product_name] and [platform_type], then provide clinical context through [specialties], [consultation_types], [session_length], and [compliance_requirements], plus the [framework] you'll build in. The model designs the waiting room, the provider video call view, the clinical notes panel, prescription writing, the post-consultation flow, the patient mobile view, and the framework implementation.
It works because it bakes in healthcare-specific design rules — calming colors, 16px minimum body text, no jarring animations for anxious patients — and threads [compliance_requirements] like HIPAA and HITECH through every view. By naming [specialties] and [consultation_types], the model tailors flows: a 15-minute primary care visit gets different pacing than a 45-minute mental health session. The [framework] variable shapes the WebRTC and encrypted-recording notes at the end.
When to use it
- You're scoping a telehealth or virtual-care product and need a full screen-by-screen design.
- You want the waiting room, call interface, SOAP notes, and e-prescribe flow designed together rather than bolted on.
- You need a HIPAA-aware design that surfaces consent indicators and encrypted recording requirements.
- You're designing both a provider desktop view and a patient mobile-first view in one pass.
- You want clinical tools (drug interaction lookup, ICD-10 search) placed sensibly inside the call.
- You need a starting point for WebRTC implementation decisions like TURN fallback and offline note queuing.
Example output
The model returns a layered design document covering each view in order, from the pre-consultation waiting room to the framework implementation notes. Each section lists concrete UI elements — movable picture-in-picture video, a collapsible patient chart panel, a SOAP note template with auto-save, drug interaction alerts as red blocking modals — and the states and consent indicators around them. The closing [framework] section translates this into WebRTC, encrypted media, responsive layout, and offline-resilience concerns. Expect a thorough spec, not deployable code.
Pro tips
- Be specific with
[specialties]; mental health, dermatology, and urgent care imply different intake fields and session pacing. - Use
[session_length]to communicate pacing — short urgent visits and long therapy sessions need different timer and notes behavior. - Keep
[compliance_requirements]accurate to your region; HIPAA plus state telehealth rules change consent and recording UI. - Set
[framework]to your real video stack (a WebRTC SDK like Daily.co) so the implementation notes are usable. - Ask for the patient mobile view separately if you need large-control, accessibility-first detail for elderly users.
- The prompt designs UI, not a compliance program — have a real privacy and security review before shipping anything clinical.
