Designing a Modern Appointments Experience for 10X Health

Healthcare

WebApp

Company

10X Health is a growing healthcare company with strong marketing momentum, and I was hired to design their new patient portal. Known for its cutting-edge genetic testing and personalized health programs, 10X Health operates clinics across the U.S. and is currently in a stage of expansion.

Challenge

Before this project, patients didn’t have a centralized place to view upcoming visits, past appointments, or telehealth details within the new 10X portal. Information existed, but it lived across emails, manual clinical workflows, and a complex backend.

As 10X moved toward a more unified digital experience, leadership wanted appointments to become one of the first pillars of the portal. My work involved understanding the data structure, defining what should be patient-facing, and coordinating across clinical, legal, engineering, and architecture to ensure the experience was accurate, compliant, and technically feasible.

Team

VP of Clinical Operations
VP of Technology
Principal Architect
Product Manager
4x Developers
Senior Clinicians

Skills

UX & Interaction Design
UI Design
EHR & Backend Discovery
Cross-Functional Collaboration
Healthcare Workflows

UX Leadership

As the sole designer on the project, I collaborated with clinical, marketing, development & C level executives to gain alignment.

UX Leadership

As the sole designer on the project, I collaborated with clinical, marketing, development & C level executives to gain alignment.

UX Leadership

As the sole designer on the project, I collaborated with clinical, marketing, development & C level executives to gain alignment.

Clinical Understanding

Working closely with clinical staff, I learned their current workflow challenges and how it can affect patients.

Clinical Understanding

Working closely with clinical staff, I learned their current workflow challenges and how it can affect patients.

Clinical Understanding

Working closely with clinical staff, I learned their current workflow challenges and how it can affect patients.

Backend Exploration

I examined our SalesForce and Electronic Health Record databases in-depth to understand limitations and constraints.

Backend Exploration

I examined our SalesForce and Electronic Health Record databases in-depth to understand limitations and constraints.

Backend Exploration

I examined our SalesForce and Electronic Health Record databases in-depth to understand limitations and constraints.

Understanding the Problem Space

I began my discovery process with engineering who pointed out that our Electronic Health Record (EHR) data may not be currently fit for clear patient-facing use. I interviewed 5 members of the clinical team who operate within the EHR daily, to understand what the patient data looks like and challenges they may face.

01 Clinical Considerations:

• Without a patient facing portal to access telehealth links and appointment summaries, clinicians would frequently get requests to resend these links via email. This created a tedious workload and was not the most secure option

02 Patient Considerations:

• Without a patient facing webpage with appointment history, patients needed to call in for necessary documents and information

The EHR showed all times in EST, regardless of the patient's own timezone

• There is an opportunity to give patients upcoming procedure details about their appointments within the portal. For example, if they need to fast or not. This would help bolster patient safety and appointment success

03 Data Flow Considerations:

• Clinical staff created internal-use appointment reminders inside the EHR with patients assigned to them; showing all raw appointments to patients within the portal would lead to confusion

The EHR only supported two appointment types (“In-clinic” and “Telehealth”), while 10X offered a third — Concierge, which could not be represented to patients

• Patient-facing location names did not match internal naming used by clinical and marketing

• Appointment statuses were numerous, and most were not relevant to patients

Data Structure Exploration

I explored the clinical EHR with a UAT account and the clinical team. The goal was to determine what information was technically accessible and how reliable it was.

Key Findings

• Providers, locations, time, duration, and basic visit details were available and accurate
• Telehealth links could be retrieved via API
• Appointment history was available but querying too far back would be resource-heavy and need to be paginated within the UI

Core Problems

From the discovery phase, these core issues emerged:

Appointment timezones are only in EST

User Impact:

Severe

User Experience

Within the EHR, the appointment timezone is stored only EST, despite many appointments taking place in other timezones across the country. To avoid confusion for patients, this must be changed to their own timezone.

Appointment timezones are only in EST

User Impact:

Severe

User Experience

Within the EHR, the appointment timezone is stored only EST, despite many appointments taking place in other timezones across the country. To avoid confusion for patients, this must be changed to their own timezone.

Appointment timezones are only in EST

User Impact:

Severe

User Experience

Within the EHR, the appointment timezone is stored only EST, despite many appointments taking place in other timezones across the country. To avoid confusion for patients, this must be changed to their own timezone.

Appointments are created in the EHR for internal use

User Impact:

Severe

User Experience

As an example, a clinician may create an appointment as a reminder to contact a certain patient, and the patient will be linked to that appointment. Without certain API parameters - that patient could see internal appointments that are linked to them, which would cause confusion.

Appointments are created in the EHR for internal use

User Impact:

Severe

User Experience

As an example, a clinician may create an appointment as a reminder to contact a certain patient, and the patient will be linked to that appointment. Without certain API parameters - that patient could see internal appointments that are linked to them, which would cause confusion.

Appointments are created in the EHR for internal use

User Impact:

Severe

User Experience

As an example, a clinician may create an appointment as a reminder to contact a certain patient, and the patient will be linked to that appointment. Without certain API parameters - that patient could see internal appointments that are linked to them, which would cause confusion.

Patients are being emailed appointment summaries

User Impact:

Severe

User Experience & Business

Appointment summaries were delivered only via email, which patients frequently misplaced. This led to manual follow-ups by clinicians and highlighted the need for a simple, secure way for patients to access summaries on demand.

Patients are being emailed appointment summaries

User Impact:

Severe

User Experience & Business

Appointment summaries were delivered only via email, which patients frequently misplaced. This led to manual follow-ups by clinicians and highlighted the need for a simple, secure way for patients to access summaries on demand.

Patients are being emailed appointment summaries

User Impact:

Severe

User Experience & Business

Appointment summaries were delivered only via email, which patients frequently misplaced. This led to manual follow-ups by clinicians and highlighted the need for a simple, secure way for patients to access summaries on demand.

EHR appointment types do not match what 10X offers

User Impact:

Moderate

User Experience

The EHR supports only “In-person” and “Telehealth” appointment types, while 10X offers in-clinic, in-home concierge, and telehealth services. Mapping all non-telehealth visits to “In-person” would misrepresent the patient experience, and could even cause confusion.

EHR appointment types do not match what 10X offers

User Impact:

Moderate

User Experience

The EHR supports only “In-person” and “Telehealth” appointment types, while 10X offers in-clinic, in-home concierge, and telehealth services. Mapping all non-telehealth visits to “In-person” would misrepresent the patient experience, and could even cause confusion.

EHR appointment types do not match what 10X offers

User Impact:

Moderate

User Experience

The EHR supports only “In-person” and “Telehealth” appointment types, while 10X offers in-clinic, in-home concierge, and telehealth services. Mapping all non-telehealth visits to “In-person” would misrepresent the patient experience, and could even cause confusion.

Location naming conventions are not uniform

User Impact:

Moderate

User Experience & Business

Location names differed between the EHR and patient-facing marketing materials. Without alignment, patients could see unfamiliar or misleading clinic names in the portal.

Location naming conventions are not uniform

User Impact:

Moderate

User Experience & Business

Location names differed between the EHR and patient-facing marketing materials. Without alignment, patients could see unfamiliar or misleading clinic names in the portal.

Location naming conventions are not uniform

User Impact:

Moderate

User Experience & Business

Location names differed between the EHR and patient-facing marketing materials. Without alignment, patients could see unfamiliar or misleading clinic names in the portal.

Design Process

To ensure the final appointments experience was both patient-friendly and technically feasible, I followed a structured design process that explored stakeholder preferences, defined development and EHR constraints and iterated on feedback from multiple departments to ensure this feature's success.

My process:

• Confirm “Core Problems” & constraints with team
• Clearly outline patient facing appointments & necessary procedure details associated with them
• Early Wireframes & feedback
• High Fidelity Wireframes
• Clinical & Tech Team Reviews
• Polished Specifications

My process:

Lorem ipsum

My process:

Lorem ipsum

My process:

Lorem ipsum

My process:

Lorem ipsum

Solutions

Displays appointment time in the user’s local timezone

Based on the user's device settings, we will show the appointment day, time and timezone. We had considered using the patients stored address, but there is always a risk of the address being outdated or visiting our clinic on vacation, which does happen (!).

UI Result:

Appointments are always seen in the user's timezone.

Displays appointment time in the user’s local timezone

Based on the user's device settings, we will show the appointment day, time and timezone. We had considered using the patients stored address, but there is always a risk of the address being outdated or visiting our clinic on vacation, which does happen (!).

UI Result:

Appointments are always seen in the user's timezone.

Displays appointment time in the user’s local timezone

Based on the user's device settings, we will show the appointment day, time and timezone. We had considered using the patients stored address, but there is always a risk of the address being outdated or visiting our clinic on vacation, which does happen (!).

UI Result:

Appointments are always seen in the user's timezone.

Appointment summaries are now accessible within the portal

Patients can now securely view and download appointment summaries directly in the portal. Post-visit emails guide patients to the portal rather than delivering summaries as attachments.

UI Result:

View or download appointment summaries easily.

Appointment summaries are now accessible within the portal

Patients can now securely view and download appointment summaries directly in the portal. Post-visit emails guide patients to the portal rather than delivering summaries as attachments.

UI Result:

View or download appointment summaries easily.

Appointment summaries are now accessible within the portal

Patients can now securely view and download appointment summaries directly in the portal. Post-visit emails guide patients to the portal rather than delivering summaries as attachments.

UI Result:

View or download appointment summaries easily.

Clinical implements a plan to better track concierge appointments

Concierge appointments were tracked inconsistently due to EHR limitations. Raising this issue aligned with a planned clinical restructure, enabling accurate concierge labeling in a follow-up three months after release.

UI Result:

Concierge tag shown on upcoming and completed appointments.

Clinical implements a plan to better track concierge appointments

Concierge appointments were tracked inconsistently due to EHR limitations. Raising this issue aligned with a planned clinical restructure, enabling accurate concierge labeling in a follow-up three months after release.

UI Result:

Concierge tag shown on upcoming and completed appointments.

Clinical implements a plan to better track concierge appointments

Concierge appointments were tracked inconsistently due to EHR limitations. Raising this issue aligned with a planned clinical restructure, enabling accurate concierge labeling in a follow-up three months after release.

UI Result:

Concierge tag shown on upcoming and completed appointments.

Filtering out internal appointments

After working with the clinical team, we found the best path forward was for the API to only pull a certain list of appointment ‘profiles’ - or preset appointments for different procedures. Working with the clinical team, we identified the appropriate appointment profiles to show.

UI Result:

User will see only their real appointments.

Filtering out internal appointments

After working with the clinical team, we found the best path forward was for the API to only pull a certain list of appointment ‘profiles’ - or preset appointments for different procedures. Working with the clinical team, we identified the appropriate appointment profiles to show.

UI Result:

User will see only their real appointments.

Filtering out internal appointments

After working with the clinical team, we found the best path forward was for the API to only pull a certain list of appointment ‘profiles’ - or preset appointments for different procedures. Working with the clinical team, we identified the appropriate appointment profiles to show.

UI Result:

User will see only their real appointments.

Location addresses instead of location names

Although marketing and clinical aligned on naming, those labels were not accessible via API. Instead, appointment addresses were used and integrated with Google Maps, allowing patients to clearly see and navigate to their appointment location.

UI Result:

User has a linked address in their appointment information.

Location addresses instead of location names

Although marketing and clinical aligned on naming, those labels were not accessible via API. Instead, appointment addresses were used and integrated with Google Maps, allowing patients to clearly see and navigate to their appointment location.

UI Result:

User has a linked address in their appointment information.

Location addresses instead of location names

Although marketing and clinical aligned on naming, those labels were not accessible via API. Instead, appointment addresses were used and integrated with Google Maps, allowing patients to clearly see and navigate to their appointment location.

UI Result:

User has a linked address in their appointment information.

Final Designs

Outcomes

The Appointments experience became one of the first foundational features of the new 10X portal. This required careful coordination across clinical, engineering, and leadership to translate EHR data into a secure patient portal, something patients could comfortably rely on in an interface, a challenge the company had not yet faced at the time.

The project also encouraged cross-team alignment:

• Clinical adjusted appointment structures to better support digital use
• Marketing and clinical aligned on naming conventions
• Engineering streamlined how appointment data was returned via API

Patients now have a single place to understand their appointments, and teams have clearer internal structures supporting them. This feature also set the groundwork for future portal capabilities that require consistent patient-facing data.

Contact Me

Reach out, I love to chat.

Chris Godowski © 2026

Contact Me

Reach out, I love to chat.

Chris Godowski © 2026

Contact Me

Reach out, I love to chat.

Chris Godowski © 2026