CONTEXT & PROBLEM FRAMING
Patient intake is often the first interaction a patient has with a healthcare system, yet it’s frequently inefficient and frustrating—traditionally relying on paper forms or fragmented digital solutions. EngageCare Patient is a digital intake experience designed to replace manual workflows with a guided, mobile-first process that allows patients to complete personal, medical, and insurance information before or during their visit.
Problems with traditional patient intake
Paper-centric and poorly digitized
Time consuming for both patients and clinics
Inconsistent in data capture and UX clarity
The business goal was to transform this into a more efficient, flexible, and delightful digital experience that could be branded for multiple clients yet require minimal configuration on their part.
DESIGN CHALLENGES
• Needed to support many different workflows depending on practice type and data needs
• UX had to be neutral yet brandable
• Must reduce cognitive load for diverse patients
• Ensure consistency across devices with limited UI access
DESIGN STRATEGY
The design strategy focused on creating a guided, patient-friendly intake experience that could support a wide range of clinic workflows without introducing unnecessary complexity. Because the product needed to be configurable across practices, the interface emphasized clear hierarchy, progressive disclosure, and familiar patterns rather than highly customized screens.
Each step in the flow was designed to collect only what was necessary at that moment, helping patients move through the process confidently while reducing downstream administrative effort for staff. Throughout the work, design decisions were made with technical feasibility and scalability in mind, ensuring new workflows and components could be reused and extended as the platform evolved.
PROCESS HIGHLIGHTS
The process centered on close collaboration with clinical staff to translate complex intake requirements into clear, buildable user flows. Rather than designing a single linear experience, I focused on defining flexible flow structures that could support conditional paths while remaining easy for patients to understand. Interactive prototypes were used early to validate behavior, edge cases, and technical feasibility, helping align the team before implementation. This approach reduced ambiguity during development and ensured design intent carried through to production, even as scope evolved.
KEY DECISIONS & TRADEOFFS
Key product decisions were informed by technical constraints and carefully weighed tradeoffs, helping keep the experience consistent, scalable, and trustworthy within an outcome-sensitive healthcare environment.
Consistent intake patterns
Less clinic-specific customization
Predictable experience patients
learn once
Advanced controls hidden by default
Reduced cognitive load during completion
Configuration over custom builds
Fewer edge-case optimizations
Faster implementation and easier scaling
Conservative interactions
Higher trust in a regulated environment
IMPACT
The original intake experience was fragmented and inconsistent, creating friction for patients and limiting the usefulness of submitted data. I restructured the flow around standardized patterns and clearer progression, which made it easier for patients to learn the system more quickly and move through it predictably, even as new complexity was introduced.
I expanded the intake flows, capturing more comprehensive patient data, including medical history and condition-specific information upfront—equipping care teams with stronger context, reducing the need for follow-up clarification which supported more informed clinical decision-making. These structural changes strengthened downstream clinical workflows by increasing the completeness and contextual depth of patient-submitted information.
REFLECTION
Clarity is earned through structure
Early in the project, there was pressure to accommodate clinic-specific variations in how intake information was collected. As intake expanded to capture more comprehensive patient data, complexity naturally increased. The challenge wasn’t simply adding fields, it was introducing more depth without increasing friction for patients or overwhelming care teams downstream. Customization initially felt like the user-centric choice, but it quickly became clear that scaling those variations would introduce inconsistency, increase maintenance overhead, and fragment the experience across teams. Rather than solving each request in isolation, I focused on creating a coherent system using hierarchy and progressive disclosure to manage complexity while preserving operational clarity.
That tension reshaped how I think about scale. In high-stakes environments like healthcare, consistency builds trust, and restraint enables sustainability. Designing for scale means balancing usability with feasibility and long-term maintainability - aligning early with technical and operational realities so solutions remain durable as the system evolves.
