apps

As a project that had already passed through several design hands before reaching us, we began by first understanding the business needs, potential endpoints, technical requirements (much of the backend had been already built prior to us entering the project), and any other prior requirements that hadn’t already been met. After interviewing users, reviewing competitor products and assessing clinician needs, we complied our research into documentation. After presenting our findings to the business, we collaborated to develop user flows (aka how a user goes through certain processes—in this case, conducting searches and scheduling appointments).

The result of user research, interviews, and competitive analysis allowed us to devise a solution involving an easy-to-use, three-part search bar. User research broadly indicated that for both insurance reasons and patient expectancy, clinicians and patients were hoping to connect relatively within their locale, supporting the addition of the “Location” input into the search. We created basic sitemaps and lo-fi flow charts; getting the basic flows documented and confirming direction with the business. We then pitched polished versions of the concept to the business in a complete flow, where upon searching, patients would find a list of providers to choose from on a new results page. There they would cycle through and compare the profiles and practices that fit their needs, supported by visual datapoints such as Specialties, Insurance types, Identities, and more.

Along the way, we adopted the client’s branding to inform colors, atoms, components, and overall design direction for the site. We began creating a design system starting with foundational elements and base components, which began to grow based off of the component concepts we were creating for ongoing business review. We evolved everything from typography primitives, spacing guidelines, layout grids, more atomic elements, and eventually reusable components and patterns.

We collaborated through several iterations before landing on a final set of designs. Using the approved mockups and the updated design system, we began preparing views for developer handoff. As developers worked off the mockup, we were able to support them along the way—taking any questions or design feedback.

Today, the web app hosts thousands of provider profiles. We continue to build features that support not just TherapySearch, but integrate directly with the TherapyNotes EHR and TherapyPortal; where even now our design TherapySearch design system is being scaled across the suite—mainly to make the patient experience of going between TherapySearch and TherapyPortal more cohesive, but also to improve the backend experience for providers as well.