Meytal Dahan
Partners
Back to products

Healthcare

Ichilov Hospital's Movement

A corporate health checkup app for Ichilov hospital. Designed for employees of organizations that subscribe as a benefit.

Type

B2B2C

Role

Product Designer

Scope

  • Mobile UX
  • Dashboard design
  • Form design
  • Patient flows

Movement is the patient-facing app for Ichilov Hospital's corporate health-checkup service. Employees of subscribing organizations use it to fill out self-assessment questionnaires, see which treatments their results recommend, book appointments, view test results, and read post-visit summaries - the entire arc of a checkup in one calm, consumer-grade interface instead of a clinical portal.

01 · Section

The service

Ichilov runs the checkup as a B2B benefit: organizations buy access for their staff, and the app is each employee's point of contact with their own care. That distribution shapes the brief. Users aren't sick - they're checking in. The product has to feel like a benefit worth opening, not a clinical portal worth dreading, while still holding the depth of a real care flow: questionnaires that drive treatment recommendations, scheduling, results, summaries, and body measurements over time.

02 · Section

The dashboard

The home screen answers one question: where am I in my care, right now? It surfaces only what actually changes day-to-day - the checkups the user has purchased, the next appointment, the latest body measurements, and quick paths into recent results. Everything deeper sits one tap below. The goal was glance-able, not encyclopedic.

03 · Section

Questionnaires

Self-reported answers are what make the rest of the checkup accurate, so completion rate becomes the key metric - yet no one opens a healthcare app excited to fill out a questionnaire. I designed the questionnaires to feel experiential: colorful, inviting, rich with icons, generous spacing, and large, easy tap targets, paired with short, conversational phrasing. The form needed to feel less like a clinical intake and more like a brief, friendly check-in - easy to start, easy to continue, and possible to complete in a single sitting.

04 · Section

Mobile First

The majority of users access the product via mobile, so the entire experience was designed mobile-first - not as a scaled-down version of desktop, but as the primary interaction model. Every flow was defined for small-screen behavior first, with progressive enhancement on larger devices.

Next product

Beehive

A high-end platform for financial services

Insights

More on Ichilov Hospital's Movement.

View all insights
Movement
Studio & Agency

Augmenting Your Outsourced Workforce for HealthTech Projects: Expert Support for Studios With No Medical Background

Studio leaders, a HealthTech project can look intimidating – medical regulation, terminology, doctors. But it's also a market with big budgets. My experience with Ichilov's Movement app lets me come in Plug & Play – to communicate with doctors, document medical edge cases, and deliver ready-made outputs to your studio. Don't pass up the project – bring in an expert.

Read
Movement
CEOsSpecific Feature ROI

What One Glance-able Dashboard Actually Returns

The dashboard in Movement (Ichilov's corporate checkup app) wasn't a 'nice to have' — it was the business case. In a B2B2C benefit, a product nobody reopens isn't a benefit, it's a cost that gets cut at renewal. So I designed the home screen to answer one question on open: where am I in my care right now? Purchased checkups, next appointment, latest measurements, recent results. The most expensive feature isn't the complex one — it's the one that drives downloads but no return visits, because you pay acquisition twice. Retention is the ROI. Design for the moment of reassurance, not screen time.

Read
Movement
Engineering LeadersProject-Specific Data Visualization

Visualizing Body Measurements and Results Without Pretending to Diagnose

Movement shows real body measurements and checkup results, to people who are checking in, not being treated. That boundary drove the engineering. The hard part of data viz isn't the chart, it's the data contract: reference ranges, units, result states, and graceful handling of pending or missing values across many orgs. Visualize for orientation, model for truth, and never let the chart claim more than the data honestly supports. Liability and clarity in one decision.

Read
Movement
Engineering Leaders

Edge Cases in Health Systems: How Do You Design Error Screens and Critical Health Alerts?

Engineering leaders on health apps, edge cases aren't a "Nice to Have" – they're an existential requirement. In a medical system, an unclear error screen = a possible misdiagnosis. In Ichilov's Movement project, we documented every exceptional state from day one with a dedicated UI component. Require your designers to document edge cases before you write any code.

Read
Movement
FoundersAI Strategy in the Product

Where AI Belongs in a Checkup App, and Where It Doesn't

Founders want an AI story. Here's the precise version for Movement (Ichilov's checkup app): users aren't sick, they're checking in — it has to feel like a benefit, not a diagnostic engine. That rules out the flashy temptation: an AI that interprets results and plays doctor. In a clinical-adjacent product, an overconfident explanation isn't a feature, it's a liability. Where AI could earn its place is the experiential layer — the self-assessment questionnaires, where completion rate is everything. Adaptive, conversational flow that lifts completion without overstepping scope. Don't aim AI at your riskiest surface to look modern. Aim it at the metric you live or die by, and keep clinical truth with the people qualified to deliver it.

Read
Movement
Engineering LeadersR&D Collaboration

Designing Movement With R&D, Not At Them

Movement, Ichilov's checkup app, pulls real hospital data into a glance-able dashboard. I learned fast that what the dashboard *can* show is an engineering question before it's a design one. So I brought R&D in early — data availability and freshness shaped the layout more than any visual idea I had. The best design constraint is the one your engineers hand you before you've drawn the wrong thing.

Read
Movement
Engineering LeadersDesign Systems

Why a Design System Was Infrastructure, Not Decoration, for Movement

A Design System isn't a style guide your engineers tolerate. On Movement, Ichilov's checkup app, it was the cheapest way to keep a dashboard, questionnaires, booking, and results from drifting into four separate codebases. Same card, same tap target, same status state, defined once. The win CTOs feel: predictable estimates, fewer regressions, accessibility solved in the component instead of re-audited per screen. Build it as infrastructure or pay maintenance tax forever.

Read
Movement
CEOs

Digital Health as an Organizational Growth Engine: The ROI of Improving Medical Service Through an App

CEOs of healthcare institutions, digital apps aren't a "nice to have" – they're new revenue channels. Ichilov's Movement opened up a B2B2C model that generates a recurring revenue stream from subscribing organizations. Quality UX turns customers into ambassadors who push HR managers to sign on for additional services. It's a strategic investment, not an expense.

Read
Movement
Project ManagersDelivery & Handoff to Development

A Handoff That Doesn't Bounce Back

On Movement, the handoff covered a dashboard, booking, results, summaries, and questionnaires — a lot of surface for one app. My rule at delivery: development shouldn't have to guess, and the states most likely to break should be documented before anyone asks. Edge cases are where handoffs bounce back as rework. Spell them out up front and your burndown stops lying to you.

Read
Movement
FoundersFrom MVP to Full Version

What We Shipped First, and Why It Was the Dashboard

Founders always ask how to scope an MVP. On Movement (Ichilov's checkup app) the easy answer was 'ship the whole journey' — booking, questionnaires, results, summaries. I pushed back. We led with one surface: the glance-able dashboard. If you open the app and instantly see your checkups, next appointment, and latest results, the product already earns its spot on your home screen. Then we expanded — the experiential questionnaires next, because completion rate is what makes the clinical side work and it deserved real craft, not a rushed slice. Don't ship a thin slice of everything. Ship the one surface worth reopening, nail it, then grow from proven value.

Read
Movement
Product ManagersMicro-interactions & Animation

Micro-interactions Were My Completion-Rate Lever in Movement's Questionnaires

Completion rate is the metric our health questionnaires live on. So I didn't treat animation as polish, I treated it as the lever. A tap that responds instantly. A selection that confirms with a small motion. A clean transition to the next question. Each one whispers 'you're making progress' and that's what stops people abandoning a health form halfway. Micro-interactions make a long questionnaire feel short, and perceived effort kills completion long before real length does.

Read
Movement
Product ManagersTypography & Visual Hierarchy

Typography Did the Triage on Movement's Dashboard

Our dashboard had to answer one question at a glance: where am I in my care right now? Purchased checkups, next appointment, measurements, results, all fighting for the fold. I didn't add screens. I used typography. Size and weight decided what reads first, so the next appointment wins and results sit calm beneath it. Hierarchy is the cheapest roadmap lever a PM has: reorder attention before you build more UI.

Read
Movement
Engineering LeadersIndustry-Specific Accessibility

Accessibility in Health Isn't WCAG Theater

In a health product, accessibility isn't WCAG theater. Movement (Ichilov's checkup app) is used by a broad working population — not digital natives, and not always calm when results arrive. So WCAG was the floor, not the goal. The sharpest case: the self-assessment questionnaires, where completion rate is the metric and every accessibility gap is a drop-off. Large tap targets, friendly high-contrast color, icons that support text rather than replace it, and semantic structure so assistive tech announces 'next appointment' as a real unit. For CTOs: health-domain accessibility is a correctness requirement, not a checkbox. An inaccessible questionnaire directly suppresses the metric your clinical workflow depends on.

Read
Movement
Founders

Cracking the HealthTech Market: How Do You Successfully Run User Testing on a Medical Product?

Founders in HealthTech, you can't run A/B Testing on a medical product without putting patients at risk. In Ichilov's Movement project, we built an interactive prototype in Figma that was tested with doctors and nurses before a single line of code. A fix in Figma costs pennies; a fix in code costs thousands of shekels. That's a real Time to Market shortcut.

Read
Movement
Project Managers

Managing a Digital Project in Healthcare: Navigating Regulation, Medical Approvals, and Timelines

Project managers in medical, the secret to hitting your timeline is structured separation between decision layers. In Ichilov's Movement project, the medical team approved "what" the system does while the design team advanced on "how." Instead of endless loops – parallel work with planned merge points. That's how you get through medical regulation.

Read
Movement
Product ManagersFirst-Run Onboarding

First-Run Onboarding When Your Users Came for a Benefit, Not a Hospital

Onboarding problem unique to Movement: the user didn't choose us, their employer did. First run has to reframe fast, you're opening a benefit, not a hospital portal. So I skipped the tutorial wall and got people to a populated dashboard where they can see their own care state. Seeing your next checkup beats any explainer slide. Activation isn't 'finished the tour'. It's reached something meaningful and came back. Prove the benefit, don't explain the product.

Read
Movement
Engineering LeadersInternationalization (i18n)

Designing So i18n Stays a Constraint, Not a Retrofit

For an app like Movement (Ichilov's patient checkup product), i18n is never far off — Hebrew means RTL, and a working-population patient base isn't single-language for long. I won't pretend localization was the headline here, but the design discipline matters: think in logical start/end instead of hard-coded left/right, leave room for text expansion (translations rarely match source length), and keep meaning out of icons. The riskiest surface is the dense, status-driven dashboard — mirrored layouts break alignment there first. The takeaway for engineering leaders: i18n debt is cheapest to prevent at the design-system level. Direction-aware, text-tolerant components turn 'add a language' into a content task, not a re-architecture.

Read
Movement
FoundersColor & Psychology

Color Was the Difference Between a Benefit and a Clinical Portal

Strategic truth about Movement: our users aren't sick. They got Ichilov's checkup as an employer perk. If the app feels like a clinical portal, the whole B2B2C model wobbles, because employers are buying something employees should want to open. Color is where positioning gets real. Warm and confident instead of sterile hospital. It lowers the dread of answering health questions and supports completion. Palette isn't decoration, it's why the contract renews.

Read
Movement
Product Managers

Designing a Health Product Under Time Pressure: How Do You Build a Diagnostics App That Doesn't Stress the User?

Product managers in Digital Health, your users aren't "Users" – they're anxious patients. In the Movement app for Ichilov, we built a User Flow that reduces cognitive load at critical points, with supportive micro-copy that guides the user. The difference between a medical app that gets abandoned and one that gets used – it's in the emotion, not the features.

Read
Movement
CEOsPersonalization & Tailored Models

Personalization That Sells the Renewal

Personalization in Movement (Ichilov's checkup app) isn't a vanity feature — it's what protects the renewal. It's a B2B2C benefit: the organization buys, the employee uses. Two audiences, and personalization is the bridge. The dashboard is effectively a tailored model of one person's care state — their checkups, their next appointment, their latest results — not a generic menu. That specificity is what turns a corporate perk into something that feels like it knows you. And that feeling is the line between a benefit people actually use and one that goes unopened until the contract lapses. Keep the user engaged by meeting them exactly where they are in their journey — that's how you keep the buyer happy.

Read
Movement
Project ManagersDocumentation & Organizational Handoff

Documenting So the Work Outlives Me

Movement lives inside a hospital and reaches users through employers — meaning people who never saw a design review will maintain it for years. So I documented the *why*, not just the screens: why the dashboard answers one anxious question, why the questionnaires are conversational, why mobile is primary. Documentation that captures rationale is how a project survives the person who built it leaving the room.

Read
Movement
Product ManagersUser Research

Researching People Who Don't Feel Sick

On Movement, Ichilov's corporate health-checkup app, my biggest research finding was a reframe: these users aren't sick. They're checking in on a benefit their employer gave them. That one sentence changed what the dashboard had to answer and what we could safely cut. Good user research doesn't just validate features — it defends your roadmap from solving problems nobody actually has.

Read
Movement
Project ManagersUsability Testing

Testing the Questionnaire Before It Costs Us

On Movement, the patient-facing app for Ichilov's checkup service, questionnaire completion was the metric everything rode on. So we tested those flows early and often — small sessions, real taps, real hesitation. The point wasn't to be thorough for its own sake. It was to surface the expensive surprises while they were still cheap to fix. Usability testing is risk management that happens to look like design.

Read