ALL WORK

CASE STUDY · HEALTHCARE PLATFORM · 2019

Dr. 7alan

A mobile healthcare journey for requesting a doctor home visit, backed by an operational dashboard for coordinating demand and providers.

XAPPRIKA SCOPE

  • Mobile application
  • Administrative dashboard
  • Healthcare request workflows

INTERFACE RECONSTRUCTION BASED ON THE DELIVERED PRODUCT.

THE CONTEXT

A home-visit request must capture need, location, and speciality, then make its status clear to patients and operations. Dr. 7alan connects that journey in one service.

THE PATIENT JOURNEY

From needing care to knowing who is coming.

The mobile product turns a home-visit request into explicit states: submitted, matched, underway, and complete. The patient does not have to infer what happens next.

SYNTHETIC DISPLAY DATA · INTERFACE RECONSTRUCTION

THE OPERATIONS LAYER

Every request becomes visible work.

DELIVERED INTERFACES

The product, screen by screen.

Selected captures from the delivered work, contained in a horizontal sequence to keep the story concise. Open any frame to inspect the full-resolution interface.

SWIPE OR DRAG THROUGH 14 INTERFACES

THE PRODUCT RESPONSE

Built around the work people actually do.

  1. 01

    Request care

    The patient journey turns a healthcare need into a structured home-visit request.

  2. 02

    Location-aware operations

    Map and visit views give the operations team geographic context for active demand.

  3. 03

    Visible request states

    Status-based workflows help administrators distinguish new, active, and completed visit requests.

IMPORTANT JOURNEYS

01

Requesting a home visit

NEED — A patient needs a direct path from choosing care to submitting a visit request.

The mobile flow captures the service need, location, and request details in a guided sequence.

WHY IT MATTERS — A stressful healthcare need becomes a clear set of next steps.

02

Coordinating visits on a map

NEED — Operations needs to understand where requests and providers are distributed.

The dashboard combines visit management, status filters, patient and doctor records, and map context.

WHY IT MATTERS — The service can be managed as an operational system, not only a consumer app.

DESIGN / ENGINEERING

DESIGN

Keep the patient journey direct

The mobile experience prioritises the request path over administrative complexity.

ENGINEERING

Separate consumer and operations surfaces

A Flutter patient application and Next.js dashboard serve distinct interaction and information-density needs.

THE RESULT

The delivered product pairs a direct patient request journey with the operational surface needed to coordinate home visits as a service.

VIEW THE PRODUCT

HAVE A SYSTEM TO BUILD?

Let’s make the complex usable.

[ START A CONVERSATION ]