Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire UI/UX Designer for Hospitals
Senior, direct, no layers

The realistic outcome is more completed journeys from the same traffic: more bookings, more form completions, and fewer drop-offs at the step where customers currently give up..

15+
Years Experience
100+
Projects Delivered
6
Countries Served
$25M+
Revenue Enabled
Hospitals — UI/UX Designer

A UI/UX Designer for Hospitals

Hospitals run on coordination: referrals in, appointments out, beds, clinics, imaging, and follow-up, all across departments that often use different systems and different vocabularies. When that coordination breaks down, the symptoms are familiar — phones backed up, referrals lost between departments, patients no-showing because nobody confirmed, and clinicians spending evenings on documentation and inbox work.

The fix is rarely a new system. It is usually the unglamorous work of connecting what already exists, removing duplicate data entry, and giving patients one clear path to book, prepare, and follow up. That is where this engagement starts.

A UI/UX Designer for hospitals works inside hospital reality: procurement and IT review, clinical governance, and the fact that anything patient-facing must be right, not just fast. Scope is agreed with the department that owns the workflow, and clinical decisions always stay with clinicians. Book a free discovery call and we will test the fit before any scope is agreed.

What you get

What this engagement covers for Hospitals

  • A redesign of the journeys that matter: finding a service, booking, ordering, or contacting you.
  • Wireframes and prototypes tested with real users before visual design is finalised.
  • Mobile-first layouts, because that is where most customers arrive.
  • Clear calls to action, readable forms, and fewer steps between interest and enquiry.
  • Accessibility basics: contrast, text size, keyboard navigation, and clear structure.
  • A design system for the pages that follow, so future pages stay consistent without redesigns.
Working in Hospitals

Built for how Hospitals actually operate

Most hospitals run an electronic health record such as Epic, Oracle Health (formerly Cerner), or MEDITECH, with athenahealth or Veradigm in some ambulatory settings. Around the EHR sit scheduling, revenue cycle, workforce tools such as Workday and UKG, and clinical communication tools such as Vocera and TigerConnect.

New work is built to that landscape: integrations use the EHR's published interfaces such as HL7 and FHIR where available, patient-facing tools are kept out of the clinical record unless a proper integration is approved, and every workflow is documented so hospital IT can support it after handover.

Hospital work involves protected health information and, in many cases, clinical safety considerations. Access controls, audit trails, and a business associate agreement where required are part of every engagement, and clinical content is reviewed by the hospital's own clinicians. Nothing here is legal or medical advice, and no tool built here makes clinical decisions.

How it works

From kickoff to delivery for Hospitals

  1. Research the journeys

    Analytics, enquiry data, and a few real user conversations show where people actually get stuck.

  2. Prototype the fix

    Wireframes and a clickable prototype for the core journeys, tested before visual design.

  3. Design and build

    Visual design applied to the tested structure, with development handover notes.

  4. Measure the change

    Completion rates before and after, so the redesign is judged on behaviour, not taste.

Outcomes

What changes for Hospitals

The realistic outcome is more completed journeys from the same traffic: more bookings, more form completions, and fewer drop-offs at the step where customers currently give up.

Hospital engagements start with the department that owns the workflow and a conversation with hospital IT about interfaces, access, and review timelines. A small working slice is shown early so the department can judge it on real work, and wider rollout waits for IT and governance sign-off rather than running ahead of it.

Why Omer

Why hire Omer

  • Journeys first, decoration second.
  • Tested with real users before design is finalised.
  • Mobile-first layouts as the default.
  • Fewer steps between interest and enquiry.
  • Judged on completion rates, not on taste.
FAQ

Questions, answered

Can you integrate with Epic, Oracle Health, or MEDITECH?
Where the hospital's EHR team approves it and a published interface exists — typically HL7 or FHIR — yes. The first step is a conversation with hospital IT about what interfaces are available, because that decides what is genuinely possible.
How do you handle protected health information?
Patient data stays in the hospital's own systems wherever possible, access is limited to the fields a job actually needs, activity is logged, and a business associate agreement is put in place where one is required. Hospital IT and compliance review data handling before anything goes live.
Can you work within hospital procurement and IT approval?
Yes. Hospital engagements are scoped to fit procurement, security review, and clinical governance timelines, and work is staged so a department can see a working slice before committing to a wider rollout.
Is a redesign worth it if our site already looks fine for Hospitals?
Looks are not the test; completion is. If analytics show drop-offs on booking or contact steps, a journey redesign pays. If completion is already strong, smaller fixes are the honest recommendation.
Will you work with our developers?
Yes. Designs are delivered with handover notes, components, and states, so your developers can build them without guesswork.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.