Skip to content
2026

A scribe that follows the clinician

Helping clinicians capture documentation without returning to the workstation.

0:00 / 0:00
Role
UX Design
Timeline
June – July 2026
Team
Solo — individual exploration
Skills
UX DesignSystems ThinkingInteraction DesignClinical Workflow

Read this case study as

What is CARE?

CARE is a hospital information system that helps clinicians manage patient care and clinical workflows.

CARE — the open healthcare platform

Many moving parts. One connected system.

  • Patient records

    Patient history, profile & ongoing care

  • Clinical encounters

    OPD, inpatient & emergency workflows

  • Documentation & clinical notes

    Structured clinical documentation

  • Orders, labs & pharmacy

    Investigations, medications & services

  • Tasks & care plans

    Coordinate ongoing care

  • Referrals

    Connect care across teams

  • Billing & reporting

    Support hospital operations

  • AI & integrations

    Extend workflows with connected tools

Jo at a laptop, thinking: “So many pieces, but all in one place.”

My role

I explored the clinical workflow around CARE Scribe, looking beyond the existing product experience to understand where it breaks down in real-world use.

I looked at how doctors work during consultations, explored different ways to capture conversations, and went beyond the interface by speaking with the team, reviewing existing device work, exploring alternatives, and prototyping the experience.

A doctor's day

The consultation doesn't always happen at the desk.

1

At the desk

Clear audio. Better context.

2

Away from the desk

Capture starts to break.

The doctor moves. The documentation doesn't.

How AI Scribe helps today

AI Scribe listens to the consultation and turns it into clinical notes. But the experience is still tied to the workstation.

0:00 / 0:00
AI Scribe in action — a real consultation turned into structured notes.Footage: a routine OPD consultation at JNIMS, shared by Shivank Kacker on LinkedIn · Click here to see the full video →

The gap

AI Scribe can capture the conversation, but the doctor still needs to stay near the workstation.

What if documentation could follow the doctor?

Exploring a wearable

The team was already exploring a wearable pendant mic that could move capture with the clinician, beyond the workstation.

Concept visual: a doctor wearing an imagined pendant microphone device
AI-generated concept image illustrating the wearable exploration. Not a CARE product.

Questions that came up

As I explored the wearable direction, a few practical questions surfaced.

  • Could existing devices support this workflow?

  • What would it take to deploy dedicated hardware?

  • How would maintenance and replacement work?

  • What operational overhead would dedicated hardware introduce?

The wearable solved the capture problem, but introduced a hardware problem.

Exploring mobile capture

What could mobile capture look like?

The phone is already something doctors carry and use every day. I started exploring whether it could also support conversation capture, without introducing another device into the workflow.

Why the phone?

01

Already with the doctor

No extra device to carry during a consultation.

02

Familiar to use

Works with something doctors already know and use.

03

Easier to maintain

No separate hardware to distribute, charge, pair, or replace.

04

Can work beyond connectivity

Audio could be stored temporarily and uploaded when a connection is available.

Two exploration directions

01

Mobile as the documentation tool

  1. Consultation
  2. Record
  3. AI transcribes
  4. Review & update on mobile

Outcome

Mobile becomes another place to complete documentation.

Jo weighing the two mobile directions
02

Mobile as the capture companion

  1. Consultation
  2. Record
  3. AI transcribes
  4. Sync to CARE
  5. Review & update on desktop

Outcome

Mobile captures the conversation. CARE remains the place for documentation.

Solution

Mobile as the capture companion

I moved forward with the second direction: mobile as a capture companion.

It keeps capture with the doctor, while CARE Desktop remains the place for review and documentation.

The mobile workflow

Scroll
Documentation that follows the consultation — the mobile app flow: Today's Patients, Prepare, Record, Capture, Pause, Review, Synced

Beyond voice capture

Capture more than conversations. Attach clinical documents directly to the encounter.

Scroll
Beyond voice capture — the mobile companion scanning clinical documents and handwritten notes and attaching them to the encounter, synced with CARE Desktop

Reflection

Thinking in Systems

Great experiences don't come from isolated features—they come from how those features fit into existing workflows, products, and mental models.

Design Around Workflows

The goal isn't to add another screen. It's to make technology support the clinician's workflow while staying out of the way.


This concept was proposed as part of my contributions to CARE as a Design Contributor and is currently under discussion with the CARE team.

Workflow DesignSystems ThinkingAI ExperienceProduct Design