+HealthConnect

Australian healthcare · Mobile product design

Find care with clarity and confidence.

HealthConnect helps adults compare suitable doctors, understand availability and cost, book in-person or telehealth care, and manage appointments in one calm experience.

Product strategyUX/UI designContent designAccessibility

Project note: This is a self-directed product design project based on an Australian healthcare scenario. It does not represent a live service or claim measured outcomes.

9:41
+ HealthConnectEC

Good morning, Emily

Here is what is happening with your care.

HealthConnect is not for emergencies. Call 000 if you need urgent help.
Action requiredComplete your patient form

Complete it before your appointment tomorrow at 10:30 am.

Next appointmentView all
Appointment with Dr Maya Chen

Annerley Medical Centre

Appointment offered
AUG18
Recent activityDetails
New pathology request

Added yesterday · Available in health records

View the document when you are ready.

01 · Product definition

A focused patient service for finding, booking and managing everyday healthcare—not an all-purpose clinical platform.

Primary userAn adult managing their own healthcare, often while busy or anxious.
Core needClear availability, location, consultation type and cost before choosing.
Business goalSupport suitable bookings and reduce avoidable booking administration.
Safety boundaryNo diagnosis, emergency triage or clinical advice.

02 · Role, evidence and constraints

A transparent self-directed project, with assumptions made visible.

The project demonstrates product framing, interaction design and service thinking without claiming access to live clinical systems, patient data or measured service outcomes.

RoleSolo Product Designer
ResponsibilitiesProduct framing, user flows, information architecture, interaction design, UI system, prototype and evaluation planning.
Project typeSelf-directed Australian healthcare scenario.
ToolsFigma, FigJam and HTML/CSS prototype.
Evidence inputs

Review of Australian digital healthcare conventions, healthcare-booking information patterns, Medicare cost communication, WCAG interaction and content considerations, and the original HealthConnect concept.

Known limitation

No direct access to patients, clinicians, provider systems or service analytics. Clinical, policy and technical assumptions require validation.

Decision standard

Each proposal is labelled as an observation, an explicit assumption or a hypothesis requiring validation.

In scope for the MVP

  • Secure account access
  • Find and compare providers
  • Select appointment type, date and time
  • Review fees and policies before confirmation
  • Manage appointments and limited shared documents

Out of scope

  • Diagnosis or clinical advice
  • Emergency triage
  • Prescribing and direct clinician messaging
  • Full medical-record management
  • Payments in the first release

Prioritisation decision: the MVP favours a complete, high-frequency service journey over a broad collection of disconnected healthcare features.

03 · Business and user alignment

Make the right care choice easier to complete.

The experience balances service efficiency with informed patient choice. It does not reduce workload by hiding information or support.

User question

Is this doctor right for me?

Show speciality, services, languages, location, consultation format and clear provider information.

User question

When can I be seen?

Expose real availability early and let users move between in-person and telehealth options.

User question

What will it cost?

Explain the estimated fee, Medicare rebate and likely out-of-pocket amount before confirmation.

User question

Can I change it later?

Keep appointment details, rescheduling and cancellation rules easy to find after booking.

Business goal
Design response
Intended outcome
Increase suitable bookings
Relevant filters and comparable provider details
Patients choose with better context
Reduce booking abandonment
Show availability and cost before review
Fewer late surprises in the flow
Reduce administration
Structured booking and self-service management
Fewer avoidable calls and corrections
Build trust
Plain English, privacy reassurance and transparent fees
Patients understand what they are agreeing to

04 · Core service flow

One connected journey, with decisions made at the right time.

Each stage answers a specific question and prepares the user for the next decision.

1Find careChoose a service, need or provider.
2Compare resultsFilter by access, time, format and cost.
3Review doctorUnderstand suitability before selecting.
4Select appointmentChoose type, date and time.
5Review and confirmCheck details, fees and policies.
6PrepareSee confirmation and required tasks.
7ManageView, reschedule or cancel safely.

05 · Assumptions and risk

Senior design decisions include what could invalidate the solution.

The interface can only be considered feasible when the underlying data, policy and service operations are reliable.

Assumption or risk
Why it matters
How it would be validated
Provider availability is current
Stale availability could create failed bookings and loss of trust.
Confirm integration, refresh rules and failure handling with engineering and provider operations.
Medicare estimates can be displayed
Incorrect rebate information could mislead patients.
Review eligibility language, calculations and disclaimers with policy, finance and legal SMEs.
Users understand telehealth
Unclear terminology may exclude less digitally confident users.
Test comprehension and provide a plain-language description of what is required.
Cancellation is self-service
Clinic policies and exceptions may differ.
Map policy variants, cutoff times, fees and escalation paths with service operations.
Documents can appear in one service
Permissions, consent and interoperability may vary.
Confirm data ownership, consent, retention and access controls with privacy and technical teams.

06 · Key design decisions

Three decisions demonstrate hierarchy, trade-offs and validation intent.

Home dashboard
Problem
Healthcare dashboards often give equal visual weight to every item.
Decision
Place one time-sensitive action before passive information.
Trade-off
Fewer general shortcuts, but lower risk of missing an important task.
Validation question
Can users identify what requires action within five seconds?
Doctor results
Problem
Users cannot compare providers when key details are presented inconsistently.
Decision
Use a stable card structure for availability, consultation format, distance and estimated cost.
Trade-off
Taller cards, but faster and more reliable comparison.
Validation question
Can users explain why one provider is more suitable than another?
Booking review
Problem
Date, location and fee errors are costly after confirmation.
Decision
Repeat critical details immediately before commitment.
Trade-off
One additional step, justified by error prevention and confidence.
Validation question
Can users correctly restate the appointment and expected fee?

07 · Product solution

Twenty screens across the core journey and key service states.

The set covers secure entry, the full doctor-booking journey and the essential areas patients use after booking. Every screen has one purpose and one prioritised action.

Core booking journeyFind care · Compare doctors · Review provider · Choose appointment · Review booking · Confirmation
Account and ongoing careLogin · Home · Appointments · Appointment details · Records · Profile
Resilience and recoveryPassword recovery · Loading · Empty states · No results · Service error · Reschedule and cancel

08 · Design principles

Purpose before decoration.

Calm and reassuringQuiet surfaces, clear hierarchy and one dominant action reduce cognitive pressure.
Credible and transparentProvider status, fee estimates and service limits are stated before commitment.
Accessible by defaultPlain English, labelled states, 44 px controls and information beyond colour.
Efficient, not rushedProgressive disclosure keeps decisions short without withholding essential context.

09 · System and states

Consistent patterns support safe decisions.

The visual system uses calm healthcare colours, readable typography and predictable interaction patterns to help people act with confidence.

Spacing4 · 8 · 12 · 16 · 24 · 32
Touch targetsMinimum 44 × 44 px
Radius8 · 10 · 14 · 18
Layout14 px mobile inset; clear vertical rhythm

Colour choices

Blue supports clear actions, teal brings a calm healthcare character, and semantic colours communicate status with text or icons so meaning never relies on colour alone.

Action blue#166AA3
Health teal#087E78
Deep ink#183044
Success#167044
Error#AA3434

Typography

Inter is used throughout for familiar letterforms, strong small-screen legibility and a neutral public-service tone.

Heading · 700Clear next steps
Body · 400Understand your appointment before you confirm.
Label · 800Action required
Primary action
Secondary action
Focused field
Error field
Check your password and try again.
Loading state
Loading available appointments…
Empty state
No upcoming appointments.
Find care when you are ready.
Recoverable error
Availability could not be loaded.
Your selections are saved. Try again.
Disabled action

10 · Validation plan

Measure comprehension, completion and service impact.

Evidence note: These are proposed measures and success criteria, not claimed outcomes. No patient research or service data has been fabricated.
Search-to-booking completionCan users find and book suitable care?
Provider comprehensionCan users explain why a doctor suits their need?
Fee comprehensionDo users understand estimates before confirming?
Booking correction rateHow often are details changed after booking?
Self-service managementCan appointments be managed without support?
Accessibility findingsWhat barriers remain across key tasks?
Participants

5–7 adults who have previously booked healthcare online, including people with accessibility needs where feasible.

Core tasks
  • Find a suitable GP available this week
  • Compare two providers and explain the choice
  • Identify the likely out-of-pocket cost
  • Book, then reschedule or cancel
Measures
  • Task completion and time on task
  • Critical and non-critical errors
  • Fee comprehension and confidence
  • Qualitative observations
Proposed success criteria
  • Establish a baseline during moderated usability testing, then agree an acceptable completion threshold with the service team
  • All participants identify that fees are estimates
  • No participant mistakes the service for emergency or diagnostic care

11 · Applied accessibility

Accessibility considerations embedded throughout the experience.

Interaction

44 px targets, visible focus, labelled controls and actions that do not depend on colour alone.

Content

Visible form labels, plain English, clear error recovery and explicit safety boundaries.

Adaptation

Reduced-motion support, responsive reflow and a planned large-text test for key screens.

Production requirements

Implementation would require semantic landmarks, logical heading order, labelled controls, current-page states and programmatic error associations.

Testing still required

VoiceOver, TalkBack, keyboard-only navigation, 200% zoom and testing with assistive-technology users.

Semantic form example

Use the email linked to your account.

12 · Delivery considerations

The service would require coordinated policy, clinical, operational and technical delivery.

Policy and content

Validate Medicare language, service eligibility, cancellation rules and plain-English content.

Clinical safety

Review boundaries, urgent-care messaging and any content that could influence health decisions.

Privacy and security

Confirm consent, data minimisation, access controls, retention and account-recovery requirements.

Service operations

Map contact-centre escalation, clinic exceptions, provider-data ownership and support pathways.

Engineering and data

Confirm availability integrations, update frequency, failure states, analytics and technical constraints.

Accessibility assurance

Include specialist review and user testing throughout delivery rather than as a final compliance check.

Design proposal
Required collaboration
Delivery evidence
Show estimated Medicare rebate before confirmation
Policy SME, engineering, legal, content design and analytics
Validated calculation rules, approved wording, source-of-truth ownership and comprehension test results