Service Design

Designing seamless patient and provider journeys across touchpoints
View as Markdown

Service design in healthcare is about designing the entire experience — not just the digital interface, but every interaction a patient or provider has with your product across time and touchpoints.

Patient Journey Mapping

Map the end-to-end patient journey:

  • Awareness — How do patients find your solution?
  • Onboarding — How do they sign up and get started?
  • Engagement — How do they use your product day-to-day?
  • Escalation — What happens when things go wrong?
  • Discharge/Transition — How does the relationship end or evolve?

For each stage, document:

  • User actions
  • Touchpoints (app, web, phone, in-person, email)
  • Emotional state
  • Pain points and opportunities
  • Clinical touchpoints

Service Blueprints

Service blueprints extend journey maps by showing the behind-the-scenes work:

LayerDescriptionExample
Physical evidenceTangible artifactsApp UI, email, prescription, device
User actionsWhat the patient doesLogs symptom, books appointment
FrontstageVisible employee actionsNurse reviews alert, doctor calls patient
BackstageInvisible employee actionsTriage algorithm runs, data syncs to EHR
Support processesInfrastructureCloud infrastructure, compliance monitoring

Omnichannel Health Experiences

Patients interact across multiple channels. Design for continuity:

  • Mobile app — Daily engagement, monitoring, messaging
  • Web portal — Detailed information, account management, billing
  • Voice — Medication reminders, hands-free check-ins
  • Wearable — Passive data collection, activity tracking
  • In-person — Clinical visits triggered by digital insights
  • Email/SMS — Reminders, summaries, follow-ups

Front-Stage and Back-Stage Workflows

A common mistake in health tech is designing only the patient-facing experience without considering what happens behind the scenes:

  • Alert workflows: Who sees an abnormal reading? How is it escalated?
  • Clinician dashboard: What does the provider see? How do they take action?
  • Data reconciliation: How is patient-generated data validated and integrated?
  • Billing workflows: How is the encounter coded and billed?