Skip to content

Veona Pulse

import { Steps } from ‘@astrojs/starlight/components’; import { Aside } from ‘@astrojs/starlight/components’;

Veona Pulse is the analytics engine. It reads live data from every module — census, queue flow, revenue, clinical KPIs (Key Performance Indicators) — and presents it as dashboards, then lets you build, schedule and export custom reports.

Verified in apps/api/src/pulse/pulse.permissions.ts:

  • Pulse Analyst (pulse_analyst) — read dashboards, build saved reports, and export. Does not see the revenue-assurance / anti-leakage surface and cannot change settings.
  • Pulse Admin (pulse_admin) — full analytics control including the revenue-assurance surface (pulse.revenue) and settings. The leadership / facility-admin / internal-audit persona. Also reads the audit log.

Most clinical roles hold read-only analytics on their own domain. The revenue-leakage view names approvers and cashiers, so it is held to leadership/audit (Pulse Admin) only.

Veona Pulse is included in the Hospital, Network and Public Health editions.

The Veona Pulse work surfaces (from apps/web/src/modules/pulse/ModuleTabs.tsx):

Dashboards · Clinical Operations · Diagnostics · Pharmacy & Supply · Revenue & Finance · Front-Desk & Flow · Workforce · Revenue Assurance · Operational · Group Benchmarking · Statutory · ICD-11 · Report Builder · Reports · Settings.

  1. Open Dashboards (/pulse) for the cross-facility overview (census, queue, revenue, clinical KPIs).
  2. Drill into a domain board — Clinical Operations, Diagnostics, Pharmacy & Supply, Revenue & Finance, Front-Desk & Flow or Workforce — for that area’s metrics.
  3. Revenue Assurance (/pulse/revenue) is the anti-leakage surface and requires both pulse.read and pulse.revenue (Pulse Admin).
  4. Group Benchmarking compares facilities within a network; Statutory and ICD-11 support regulatory and diagnosis-coded reporting.
  1. Open Report Builder (/pulse/builder).
  2. Choose the metrics, filters and grouping for the report; preview the result against live data.
  3. Save the report — it appears under Reports (/pulse/reports).
  4. From a saved report, set a schedule so it runs automatically and is delivered on a cadence (pulse.manage).

Saved reports and dashboard views can be exported (pulse.export — Pulse Analyst or Pulse Admin). Export honours the same permission scope as the dashboard, so a user only exports data they may already see.

Open Settings (/pulse/settings) to configure saved-report defaults and the analytics surface (pulse.settings — Pulse Admin).