How would you configure a new intake form for a dermatology clinic in Phreesia?

• A. Create a new template or clone existing, add specialty-specific fields (rash history, sun exposure), set required fields, implement conditional logic, test with internal staff, publish to production
• B. Delete the form after creation
• C. Use the standard form without changes
• D. Only add fields after production

Answer: (A)

When configuring a dermatology intake, start by creating a new template or cloning a proven one, then tailor it with specialty-specific fields such as rash history, sun exposure, lesion duration, and prior treatments. Mark essential questions as required so you don’t miss critical information during the visit. Use conditional logic to adapt questions based on patient responses—for example, if a patient reports a rash, prompt for its location, onset, progression, and associated symptoms; if sun exposure is relevant, ask about sunscreen use, SPF, and tanning history. Testing the form with internal staff helps catch unclear wording and ensures the conditional paths work smoothly before patients see it. Once everything flows correctly, publish the form to production so it’s active for patient visits.

Other options fall short because deleting the form after creation discards the tailored setup you built. Using the standard form without changes misses dermatology-specific data that clinicians rely on. Adding fields after production can disrupt workflows and lead to missing or inconsistent data, whereas building, validating, and then publishing ensures the right information is captured reliably from the start.