Kishore Raja AnumulaLet’s talk

Hello Doctor

Reach a doctor. Stay in control.

An English/Telugu healthcare-access concept for people with lower digital confidence. Book directly, or choose help preparing a concern.

Role
Product concept, PRD, UX/UI and prototype
Designed
Booking → consultation → visit records
Year
2026

Prototype changes · Preserved visit context on return; separated prescription status from an available action.

01 /From the first choice to the visit record1:15

Scripted concept, with AI-assisted prototyping and review. No live AI, payments or calls; not yet tested with patients or clinically validated.

01 / THE BRIEF

Make care reachable without mandatory AI.

THE DESIGN CHALLENGE

Offer help.
Keep the choice.

Hypothesis: lower digital confidence may make care harder to navigate. Help describing a concern should be optional.

English / Telugu · Direct or assisted · Separate visit records

EXISTING PROTOTYPEHOME · DETAIL
Original Home close-up: Find a doctor and Prepare with AI optional are separate entry choices
Two visible routes from the same Home screen.Open the full Home screen
FROM REVIEW TO REPAIR

Two fixes, shown in the interface.

Review method: screen inspection and scenario-based walkthroughs of saved prototype actions.

REPAIR 01 / RETURN CONTEXT

Going back should
keep the visit.

Review issue: saved prototype actions cleared the current visit on return.

Changed: preserve patient, visit and released recap.

REPAIRED PROTOTYPERELEASED RECAP
Repaired original visit recap for fictional Sita, Doctor approved Version 1, with Back and Back to visits controls
1

Patient + approved version.

2

Return without a reset.

Repaired recap · Fictional recordSaved return actions retain the visit context.
REPAIR 02 / PRESCRIPTION STATUS

Only available records
look actionable.

Review issue: the no-prescription state used a chevron and tap action.

Changed: remove its chevron and action; keep issued prescriptions actionable.

REPAIRED PROTOTYPETWO RECORD STATES
NO PRESCRIPTION
Original repaired current demo visit: No prescription issued is a static status with no chevron
Static statusNo chevron. No dead-end tap.Full screen
PRESCRIPTION ISSUED
Original repaired fictional Visit 101: Issued View prescription in blue with a chevron
Available actionBlue label, chevron, whole-card target.Full screen

Two fictional records after repair. Tap to enlarge.

02 / PATIENT JOURNEY

From doctor choice to a visit record.

01

Choose a route, language and patient

Both routes require phone verification, then a saved patient or continuation without a saved profile.

DIRECT

Find a doctor

No AI intake or concern summary required.

OPTIONAL ASSISTANCE

Prepare a concern

Agree → speak or type → review, edit and confirm.

  1. 02

    Choose a doctor

    Compare language, sample fee and time. Sharing a reviewed summary is optional.

  2. 03

    Book a time

    Review doctor and time, then complete simulated payment.

  3. 04

    Join the call

    AI notes start off; capture requires patient and doctor agreement.

  4. 05

    Return to Visits

    Find the correct patient, visit and separately labelled records.

Existing doctor profile with English and Telugu, a selected appointment time, no intake summary and an illustrative feeView full-size screen
EXISTING PROTOTYPE

Before booking

Direct booking shows doctor, language, time and fee without a summary.

Existing scripted consultation with optional AI notes switched offView full-size screen
EXISTING PROTOTYPE

During the call

Requesting AI notes waits for doctor approval; the call can continue without notes.

Existing fictional visit showing separate prescription, doctor note and approved AI recap sectionsView full-size screen
EXISTING PROTOTYPE

After the visit

Prescriptions, doctor notes and approved AI recaps remain distinct. All clinical content is fictional.

Demo controls simulate appointment readiness, doctor permission and recap release. A facilitator operates these external events during a walkthrough.

03 / CHOICES & TRADE-OFFS

Keep help optional and control explicit.

CHOICE 01

Keep a direct route

People can book without explaining a concern to AI.

Trade-off: Two routes to maintain and explain.

Next test: Can someone find direct booking unaided?

CHOICE 02

Make comparison explicit

Language, fee and time make the booking choice inspectable.

Trade-off: More reading on a phone.

Next test: Can someone confirm the intended doctor, fee and time?

CHOICE 03

Ask at each boundary

Sharing a concern does not imply permission to capture a call.

Trade-off: More choices to understand.

Next test: Can someone explain each permission?

PROPOSED REFINEMENT

Let a failed summary lead back to care.

Editing should not become a barrier to doctor discovery.

01 / ORIGINAL

Review or edit

Original concern summary screen with Use this summary and Edit summary actionsView full-size screen
The existing screen has no explicit “continue without summary” action.
02 / PROPOSED

Continue without a summary

Preserve patient and language; clear summary sharing. Draft retention remains a service decision.

Three permission boundaries

BEFORE

Share the concern

Share only a reviewed summary, by choice.

DURING

Capture AI notes

Both parties agree. Stopping capture keeps the call running.

AFTER

Release the recap

Only the exact clinician-approved, released version is readable.

04 / RECOVERY

Make the next action clear.

Existing simulated payment-declined screen with Review payment and Back to feeView full-size screen
EXISTING PROTOTYPE

Confirmed payment failure

Review payment or return to the selected fee. “No charge” applies only to confirmed failure.

Existing call interruption screen with Reconnect and Leave callView full-size screen
EXISTING PROTOTYPE

Interrupted call

Reconnect or leave. Scripted checks cover visit finalisation without granting AI-note permission.

Existing recap pending screen saying the patient can leave and check Visits laterView full-size screen
EXISTING PROTOTYPE

Review pending

Leave and check Visits later; an unapproved AI draft stays unavailable.

PROPOSED REFINEMENT

A timeout is not a confirmed failure.

Check the existing transaction before retrying. Preserve doctor and time, show whether the slot is held, and confirm booking only after payment and availability are verified.

Other scripted recovery checks
  • Microphone unavailable: type instead; preserve patient and language.
  • Slot unavailable: choose again; never silently substitute.
  • Patient changed: clear the previous concern and encounter permissions.
  • Notes declined: continue with capture off.

05 / NEXT VALIDATION

Test the complete task with intended patients.

PROPOSED STUDY · NOT YET RUN

Start with a small formative round.

A proposed first round would include five intended users spanning English/Telugu and lower digital confidence. Use fictional concerns and a Telugu-fluent moderator. Record wrong turns, help requests and misunderstandings.

  1. Start without AI.Reach doctor choice unaided.
  2. Correct or abandon a summary.Explain what will be shared.
  3. Book and recover.Confirm patient, doctor, fee and time; handle an unknown payment result without paying twice.
  4. Explain permissions and find the visit.Say when capture starts, who releases the recap and how to return after interruption.

Redesign trigger: mistaking AI for a doctor, assuming capture starts before both agree, or treating pending notes as approved.

UNRESOLVED PRODUCT FLOWS

What needs design before a live pilot

  • Clinical routing: validate symptom-based matching; define clinician-reviewed urgent-care routing and its operational owner.
  • Booking changes: cancellation, rescheduling, missed visits and refund rules.
  • Patient access: family permissions, retained drafts and withdrawal of earlier capture.
  • Service delays: payment reconciliation and overdue clinician review.

SUPPORTING DETAIL

Evidence and interface foundations.

Original Telugu patient-selection screen with saved profiles, create-profile and continue-without-profile choicesView full-size screen
EXISTING PROTOTYPE

The same task in Telugu

Original patient-selection screen. English and Telugu are active; Hindi, Tamil and Kannada are unavailable previews.

Translation and comprehension have not yet been reviewed with intended users.

Evidence and limits

Exports and documented reviews dated 7–8 October 2026 support the existing screens and repairs. Checks establish intended routes, visibility and simulated state preservation, not live runtime behaviour or patient outcomes.

The journey map, trade-off explanations and two static proposals are portfolio additions. Profiles, fees, availability and clinical records are illustrative. Native-language fluency, assistive technology and production services remain untested.

Icons: Uicons by Flaticon.

Visual system

Figma specifies SF Pro and Noto Sans Telugu, blue actions, grouped surfaces and four main destinations. Responsive text and screen-reader behaviour require device testing.

Explore the original prototype.

Try direct booking and the optional assisted route.

Open Figma prototype