Every hospital on One Click Away.

Every hospital on the platform.

Every application One Click Away supports. Which hospital has which is set from that hospital.

What One Click Away sells, and what each hospital bought. A package is the product level; the commercial status is whether access is valid right now.

The shared shape of this hospital. Every application reads the same facilities, locations, departments and zones.

Select somebody from Users to see their access, shifts and devices.

Registered application installations. A device id identifies an installation, not attested hardware.

What is wrong, who is affected, and what to check next. A snapshot taken when you ask for it — not live monitoring.

Named procedures, defined in source. There is no editor here — a runbook is added in a commit, not from this page.

Operational problems the platform is managing. Separate from support tickets, which are conversations with a hospital.

The external services this platform depends on. Credentials are not stored here and cannot be entered here.

Derived when you ask for them. Nothing is stored, and a figure that could not be read is shown as unavailable rather than as zero.

Which release each application is meant to be running. Assigning a release does not deploy software.

Application settings for this hospital. Source defaults, hospital overrides, and what each application actually reads.

Usage across hospitals.

Every account and hospital change, most recent first.

Issues raised by hospitals.

Device health and push registration per hospital.

Platform-wide scheduled-job health. The selected hospital does not change this result.