Prototyped a clinic intake form and need fresh eyes on the flow
Helping a small physio clinic ditch their paper intake forms. They see about 20-30 new patients a month, so nothing huge, but the paper stack is driving them crazy. The brief was simple: a web form that patients fill before arriving, covering history, consent, and basic pain assessment. Reception should be able to read it at a glance.
Used Runable to test the flow before going custom. Took about 4 hours to wire it up. The flow starts with the patient picking an appointment time, then fills in personal and medical history (about 5 fields), signs a consent waiver, and finally sees a summary page that shows their name, history notes, and consent status in a clean card layout.
Form logic held up on mobile and desktop, the summary view is actually readable, and editing copy and fields was quick. But I had to fix a few things manually. The consent text was way too generic so I rewrote it for their specific policies. Mobile spacing needed tweaks. And calendar integration is still manual, they just copy paste the time.
The clinic owner wants consent before history. I think after. Which order makes more sense to someone walking in already in pain? Also curious about the consent language. Too formal or too simple? I keep second-guessing it.
Posted Jun 23, 2026, 5:57 PM UTC