Making AED readiness visible, actionable, and easier to manage.

A high-stakes administration experience for HeartSafe, helping teams oversee Automated External Defibrillator readiness, inspections, sites, users, and role-based access from one connected platform.

At a glance

Readiness states and urgent device issues surfaced early

One system

Sites, users, devices, and settings brought together

Traceable

Inspection records and device events kept in context

Role-aware

Access structured around operational responsibilities

HeartSafe AED readiness dashboard showing device states, urgency, and the device list in one operational view.

The operational challenge

Readiness is more than knowing where a device is

An Automated External Defibrillator can be installed and still be unavailable when it is needed. Battery condition, pad expiry, connectivity, self-test results, inspection history, and location details all affect whether a device is truly rescue ready.

The experience needed to help administrators understand device state quickly, identify what required attention, and move from organisation-level oversight into a specific record without losing context.

Design principle

“Make readiness visible before asking people to investigate, then keep the next action close to the evidence.”

Platform architecture

A clear home for organisation, user, and device administration

The admin portal organises the wider HeartSafe ecosystem into understandable areas: organisation management, user management, application settings, audit tools, device readiness, AED management, and event review.

HeartSafe Admin Portal overview with quick links, sites, users, and contact information — Admin Portal overview with quick links, organisation summaries, user information, and a clear route into readiness and AED management.

Readiness at a glance

Prioritise what needs attention before opening a device

The dashboard separates device states into clear operational categories such as not ready for use, needs attention, offline, and rescue ready. Summary metrics, search, filters, and flexible list or card views support both rapid scanning and deeper investigation.

Device records & inspection workflows

Keep current condition, history, and maintenance action together

The device detail experience brings readiness status, battery and pad condition, connectivity, self-test information, location details, inspection records, event activity, and the new inspection form into one working area.

HeartSafe AED detail screen with readiness status, inspection records, events, and inspection form — Device detail view combining readiness evidence, historical records, event activity, and a focused inspection-entry workflow.

Sites & AED operations

Scale from locations to individual devices without changing mental models

Site and AED management use consistent search, card, and view patterns so administrators can move between location-level oversight and device inventories without relearning the interface.

HeartSafe site management screen with searchable medical-centre cards — Site management with searchable location cards and direct access to site details.

HeartSafe AED management screen with searchable device cards — AED management with a consistent device inventory pattern and list or grid controls.

Roles & access management

Make responsibility visible as the platform grows

Role cards make the available responsibility areas explicit, including readiness administration, AED administration, event review, maintenance, and hospital administration. The structure gives administrators a clearer foundation for assigning access by operational need.

HeartSafe role management screen with readiness, AED, event review, maintenance, and hospital roles — Role management showing distinct operational responsibilities and the product areas associated with each role.

Design reflection

High-stakes products do not need to feel alarming everywhere. They need a calm structure that makes urgency unmistakable when it appears. The HeartSafe experience uses repeated interaction patterns, clear device states, and contextual records to support confident administration without turning every screen into an emergency.

01
Readiness before detailSurface the operational state first, then provide the evidence and actions behind it.
02
Consistency reduces frictionSearch, cards, lists, and management patterns repeat across sites, devices, and roles.
03
History belongs beside actionInspection and event records are most useful when the next maintenance action is available in the same context.