By Nick Babich
These eight healthcare app design examples pair patient and clinician screens and annotate what each one shows first and why it works.
Key Takeaways
- Name the person and the status first: the strongest patient screens say whose care it is and what the result or status means in plain words before anything else.
- Say who has reviewed it: a lab result that is honest about being unreviewed, and about when review usually happens, is a better pattern than a silent result or an unexplained warning color.
- Give every wait a status and a way out: a waiting room with a time estimate, a queue position and a phone fallback keeps people from guessing whether the visit is still happening.
- Clinicians need two identifiers and a reason: a patient list that says why each person is on it, and a card that shows name and date of birth, save a chart-reading step.
- End with a dated next step: “Ready Tue, Nov 17, after 2:00 PM” beats “soon,” for patients and for the nurse who needs to know what is pending at 9:00 PM.
Each example covers one task in three screens, from booking a visit to confirming a shift handoff, and the numbered callouts mark the details that make the screen safe to use. All eight products are fictional, with invented names and data, and each was drawn for this article in its own visual style. They are design patterns, not clinical or compliance guidance. If you are planning a product in this space, healthcare UX design teams we compare for patient and clinician apps are listed separately; this page stays on the screens.
On November 15, 2026, I read 20 results across four related web searches for healthcare app design examples and healthcare UX design examples. Five were galleries or template libraries, 11 were case studies or portfolio pieces about a single product, two were roundups of several products and two were critiques of one app. Each is useful, but none that I read pairs patient and clinician screens in one format or says what a health screen must show first, so that is how this page is organized. It covers app and product screens, not hospital or clinic websites. For the regulatory and workflow side of the work, such as HIPAA, FDA oversight, clinical workflows and project scoping, read what compliance, clinical workflows and scoping add to healthcare UX work; none of that is repeated here.
How to Read a Healthcare App Screen
A healthcare screen works when it shows the right first thing for its reader, and patients and clinicians need different first things. The four checks below separate them, and they are the same checks worth asking of work by the UX teams we review for digital health products. They also work on any screen you save from a gallery or your own app.
- 01 Whose is this: a patient screen names the person whose care it is, which matters most when a caregiver acts for someone else, as in Wrenly. A clinician screen shows two identifiers, such as name and date of birth, as in Pelhaven, Oakrill and Hartsong.
- 02 What is the answer: a patient needs the result or status in plain words, as in Alderfen. A clinician needs what changed since last time, as in Hartsong and Pelhaven.
- 03 What happens next: a patient needs a next step with a date or time, as in Marlwick and Sablemoor. A clinician needs what is waiting and the one action to take, as in Oakrill.
- 04 What if it’s wrong or urgent: a patient needs a way to reach a person, as in Dovemere. A clinician needs a visible way to escalate or undo, with who and when logged, as in Pelhaven.
Not every screen answers all four. A waiting room has no result to explain, and a handoff card has no “undo.” When a check does not apply, notice what the screen does with that space instead.
Healthcare App Design Examples at a Glance
Use the table to jump to the pattern closest to your product. Each row records what the screens show for the four checks, taken from the images below.
| # | Product (fictional) | Reader and task | Screens | Whose is this | The answer | What happens next | If it’s wrong or urgent |
|---|---|---|---|---|---|---|---|
| 1 | Marlwick (clinic booking, iOS) | Patient: book a visit | 3 | The patient’s own visit, with the doctor and clinic named | Reason in plain categories; slot in Pacific Time; $30 co-pay | Mon, Nov 16, 11:15 AM PT; bring ID and insurance card | Change free until Sun, Nov 15, 11:15 AM PT; clinic phone |
| 2 | Dovemere (telehealth, Android) | Patient: join a video visit | 3 | Visit with Dr. Tomas Reyes at 2:30 PM | Camera, microphone, speaker and connection each show a result | About 5 minutes; 1 patient ahead | Phone call replaces video; clinic number on screen |
| 3 | Alderfen (patient portal, iOS) | Patient: read a lab result | 3 | Vitamin D result collected Thu, Nov 12 | 24 ng/mL against a lab range of 30 to 100, in one sentence | Review usually within 3 business days | Message, call or book; urgent line stated |
| 4 | Sablemoor (medication, Android, large type) | Patient: take doses, request a refill | 3 | Lisinopril 10 mg and Metformin 500 mg | “Taken at 8:04 AM” | Ready Tue, Nov 17, after 2:00 PM | Undo on a taken dose; approval step named |
| 5 | Wrenly (caregiver access, iOS) | Caregiver: view a parent’s care | 3 | Banner names Walter Haas on every screen | What is shared, area by area; private messages not shared | Check-up Thu, Nov 19, 10:00 AM | Switch to own account; he can end access |
| 6 | Pelhaven (remote monitoring, web) | Clinician: triage monitored patients | 3 | Rosa Delgado, DOB Jun 9, 1959, MRN 004821 | Why she is listed; 143, 146, 148 against a limit of 140 | Retry call at 1:00 PM | Escalate to Dr. Nwosu |
| 7 | Oakrill (secure messages, web) | Clinician: answer a patient message | 3 | Dev Kapoor, DOB Apr 22, 1988, last visit Oct 9 | Reply deadline 10:30 AM; category Symptom | Reply sent 9:41 AM; visit booked 1:30 PM | Edit before send; phone number in the reply |
| 8 | Hartsong (shift handoff, Android, dark) | Nurse: receive a handoff | 3 | Joan Hale, DOB Feb 11, 1951; room shown as location | 3 changes, 1 pending, in three fixed sections | Evening labs 9:00 PM; recheck 10:00 PM | Message the sender, on shift until 7:30 PM |
8 Annotated Healthcare App Patterns
The first five patterns are patient-facing, including one for a caregiver, and the last three are for clinicians. Each uses the same four labels so you can compare them quickly.
1. Marlwick: Book a Visit on iOS
Reader: A patient books an in-person visit with a family doctor, in three screens on iPhone.
What the screens show: The first screen asks what the visit is for with five plain categories, such as “New symptom or concern,” and a line saying details can be added later. The second shows the doctor, real slots for Mon, Nov 16, the words “Times are Pacific Time (PT),” and an estimated $30 co-pay. The button repeats the choice: “Book 11:15 AM PT.” The confirmation lists what to bring, a free change window that ends Sun, Nov 15 at 11:15 AM PT, and the clinic’s phone number.
Why it works: The person is never asked to translate a feeling into a medical term. The time zone and the cost appear where the decision is made, not on a receipt afterward. The confirmation answers two questions that otherwise become phone calls: what to bring and whether the visit can be changed.
Watch for: A time zone label helps only if it is correct for the person. If someone books while traveling, say which time zone the slots use and repeat it on the confirmation. Keep the cost line honest: “estimated” should mean the clinic will explain how the estimate is made.
2. Dovemere: Join a Video Visit on Android
Reader: A patient joins a video visit that starts at 2:30 PM, in three screens on an Android phone.
What the screens show: A setup screen runs four checks, camera, microphone, speaker and connection, and gives each its own result, with a test button for sound. The waiting room says “about 5 min,” shows when the estimate last updated, says one patient is ahead, and puts the clinic’s phone number and a “Switch to a phone call” button on the same screen. If the connection drops, a banner says what is happening, that the visit is still open, and offers to retry or have the doctor call.
Why it works: People in a waiting room do not know whether the system has forgotten them. A time estimate with a freshness stamp and a queue position answer that without a spinner. The phone fallback is visible before anything goes wrong, so a failure becomes a small detour.
Watch for: Do not hide the fallback in a help menu, because the people who need it most are the ones with a weak connection. Decide in advance what the clinician sees when a patient drops, and say it on the patient’s screen so the visit is not treated as a no-show.
3. Alderfen: Read a Lab Result on iOS
Reader: A patient reads a vitamin D result in a portal app, in three screens on iPhone.
What the screens show: The results list says on every row whether the care team has reviewed the result. The detail screen shows 24 ng/mL as a large number, draws it on a scale next to the lab’s range of 30 to 100, and adds one sentence: the result is below the range this lab uses, and a result outside the range does not always mean a problem. A note says the doctor has not reviewed it yet and that reviews usually take up to 3 business days. The last screen offers a message, a call or a visit, and says what to do if the person feels unwell right now.
Why it works: The value, the range and the meaning sit together, so the person is not left to search the web for context. The review note is honest about what the app does not know. The urgent line is on the screen where worried people go to ask a question.
Watch for: Resist color alarms. A red result with no explanation can alarm people more than the number warrants, and a calm sentence below it may not undo that. Also keep the wording of the range sentence reviewed by a clinician at your organization: this article shows a pattern, not text to copy.
4. Sablemoor: Doses and a Refill on Android, Large Type
Reader: A patient takes today’s doses and requests a refill, in three screens on an Android phone with large type.
What the screens show: Today’s list is grouped by time, with the medicine name and dose in large type. A taken dose shows “Taken at 8:04 AM” with a separate Undo link, and an untaken one has a large “Mark as taken” button. The refill screen shows supply as a date, “Enough until Fri, Nov 20,” the pharmacy and “Ready for pickup Tue, Nov 17, after 2:00 PM.” The confirmation says the doctor’s office has to approve the refill first and that the person will be told by Mon, Nov 16 if it is not.
Why it works: Large type and large targets suit people who take several medicines and may have trouble seeing small text. A time on the taken state turns a tap into a record. Showing supply as a date, next to a ready date that comes before it, lets the person see there is no gap.
Watch for: An Undo that sits right next to the taken state invites accidental taps, so keep it visually separate and easy to read. Ask your clinical reviewer what the app may say about doses at all: this screen only records what the person reports.
5. Wrenly: Acting for a Parent on iOS
Reader: A caregiver, Maria Haas, views her father Walter’s care, in three screens on iPhone.
What the screens show: A banner at the top says “Caregiver view, Walter Haas” with a “Switch to mine” button, and it stays in place on every screen. The week view shows his check-up on Thu, Nov 19 at 10:00 AM, a visit summary and a new test result that his care team has not reviewed. A “What you can see” screen lists each area with “See,” “See and book” or “Not shared,” and says Walter chose the settings on Oct 28, 2026. The access record lists when the caregiver opened his appointments, and says he can see the list and end access.
Why it works: A caregiver who also has their own account can lose track of whose records are on screen. The banner removes the guess. Each shared area is a word, not a color or an icon, and the access record shows the caregiver the same boundary the patient set.
Watch for: The banner has to survive deep screens, modals and notifications, not only the home view. Test the case where the caregiver gets a push notification about the patient and taps into the app, and check that the first screen they land on already says whose care it is.
6. Pelhaven: Triage Monitored Patients on the Web
Reader: A nurse reviews patients sending home readings and logs an action, in three screens in a browser.
What the screens show: The list says why each patient is on it in words, such as “Systolic blood pressure above her limit 3 days in a row” or “No reading for 2 days,” with a small trend line and the last action. The patient view puts name, date of birth and record number at the top, then a 14-day chart with the physician’s limit of 140 drawn and labeled, and the last three readings, 143, 146 and 148, listed. The action screen logs “Called the patient” with who, when and what next, and keeps an Escalate button in reach.
Why it works: A list of names makes the nurse open each chart to learn why it was flagged. A reason in words lets the nurse triage at a glance. The limit is drawn on the chart, so the nurse sees at once which readings crossed it. The log records the action and the plan, so the next person does not repeat the call.
Watch for: The only highlight on the chart is the three readings above the limit, because they are the subject. If every point or every row is colored, nothing stands out. Do not let a reason in words be the only signal: a patient with no reading is also a reason, and it has no number to chart.
7. Oakrill: Answer Patient Messages on the Web
Reader: A physician works through patient messages, in three screens in a browser.
What the screens show: The inbox is sorted by reply deadline, and each message carries a category tag, such as Symptom, Scheduling or Billing, and a clock time like “Reply by 10:30 AM.” An opened message sits under the patient’s name, date of birth, record number and last visit. A reply template fills in the specifics, such as the next opening at 1:30 PM and the clinic’s phone number, and stays editable before it is sent. The sent screen says the reply went out at 9:41 AM against a 10:30 AM target and that the message and the booked visit are on the patient’s record.
Why it works: A deadline as a clock time is a plan, where a priority color is a mood. Context sits above the message, so the clinician does not switch screens to learn who is writing. The template saves typing without hiding the text, since the clinician reads and edits it before it goes.
Watch for: Templates drift toward saying the same thing to everyone. Keep them short, let the clinician change every word, and review the wording clinically. Also decide what the deadline measures, a first reply or a resolved question, and say so in the settings screen, because those two numbers are very different.
8. Hartsong: Shift Handoff on Android, Dark Theme
Reader: A night-shift nurse receives a handoff from the day nurse, in three screens on an Android phone in a dark theme.
What the screens show: The unit list shows each patient by name and date of birth, with the room as a smaller line and counts of changes and pending items. A handoff card repeats the identifiers and then uses the same three sections every time: what changed today, pending and watch for, each with a time where there is one. The last screen says “Received at 7:12 PM,” names the sender, who is on shift until 7:30 PM, and offers a button to message them.
Why it works: A fixed order lets a tired reader find the pending item without reading a paragraph. Times on pending items turn a note into a task. A receipt that names the sender gives the receiver a person to ask while that person is still there. The dark theme suits a dim ward, as long as contrast holds for small gray text.
Watch for: Do not let location do the identifying. The Joint Commission’s 2026 National Patient Safety Goals for ambulatory care ask staff to use at least two patient identifiers when giving medicines, collecting specimens and providing treatments, and they state that a room number or physical location is not an identifier. A handoff card is not one of those moments, but showing identifiers the same way everywhere builds the habit.
What the Eight Patterns Have in Common
The eight patterns agree on four habits: they name the person, put the answer in plain words, give a dated next step and keep a human reachable. They also spend their words differently. Patient screens spend them on reassurance and explanation, and clinician screens spend them on context and the reason something is on the list.
- Specifics instead of reassurance: “Ready Tue, Nov 17, after 2:00 PM” and “Reply by 10:30 AM” say more than “We will be in touch soon.”
- Honesty about what the app does not know: Alderfen says the result is unreviewed, and Sablemoor says the refill needs approval.
- A visible way back: a phone number on the waiting room, a switch-back button on the caregiver banner, an Undo on a taken dose and an Escalate button on the action screen.
- One job per screen: each example splits a task into short steps, the same habit you see in single mobile screens grouped by app type.
If you want to see how another high-stakes category handles the same moment of confirming a decision, read eight annotated money flows, from KYC to investing. The checks there are about money; the habits above are about care.
How to Use These Examples in a Design Review
You can use these examples as a short review script: pick one screen from your product, name its reader, and run the four checks on it. A short review of one screen is enough to start, and the screens worth choosing are the ones people reach in a hard moment.
- Pick the hard moment: a first look at an unreviewed result, a wait that has run long, a handoff at the end of a shift, a caregiver landing from a notification.
- Name the reader: a patient, a caregiver or a clinician, and what they did a minute before opening the screen.
- Run the four checks: whose is this, what is the answer, what happens next, and what if it is wrong or urgent. Write the answer on the screen for each, not what you hope the screen implies.
- Find the gap: any check with no answer is a design decision someone has not made yet. Bring it to your clinical reviewer and your compliance owner, not only to the designer.
- Save the whole flow: when you collect examples from other products, capture every screen of the flow, not only the most polished one.
FAQ
What makes a good healthcare app design?
A good healthcare app design shows the right first thing to its reader. For a patient that is whose care it is, the answer in plain words and a dated next step. For a clinician it is who the patient is, what changed and the one action to take. It also keeps a person reachable and says what the app does not know.
What are some examples of healthcare apps?
Common types include appointment booking apps, telehealth and video visit apps, patient portals for results and records, medication and refill apps, caregiver and family access apps, remote monitoring tools for care teams, secure messaging inboxes and shift handoff tools. The eight examples on this page cover each of those with fictional products.
How is designing for patients different from designing for clinicians?
Patients are often reading about their own health, sometimes while worried, so screens spend words on plain language and reassurance with specifics. Clinicians are often interrupted and working through many patients, so screens spend them on identity, change and priority. Both need a clear next step and a way to ask a person.
Are these screens clinical or compliance guidance?
No. They show design patterns using fictional products and invented data. Clinical wording, data handling and regulatory questions need review by qualified people at the organization that builds the product.
Conclusion
The eight patterns look nothing alike, and they agree on the parts that matter: name the person, say the answer in plain words, give a dated next step and leave a human reachable.
When you collect healthcare screens for your next project, pick the one a person reaches in a hard moment and check it against the four checks. That one screen tells you more about a health product than its home tab.