Veona Portal (Staff View)

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

What this is

Veona Portal has two sides. This page documents the staff side — how your team manages the patient portal from inside the EHR. It covers confirming the booking requests patients submit (which materialise into real appointments), releasing results to patients, replying to secure messages, sending broadcasts, and owning the portal’s branding.

The patient's own experience — passwordless sign-in, viewing results, self-booking, joining telehealth — is documented separately under **For Patients**.

Who uses it

Verified in apps/api/src/auth/rbac/permissions.ts:

• Portal Coordinator (portal_coordinator) — the portal-ops role. Confirms self-service bookings, releases or holds results to patients (the PHI-release gate), sends broadcasts, owns branding and settings, and reads/replies to/shares secure messages.
• Clinician — the ordering clinician can release their own patient’s results to the portal and confirm bookings, and handles the secure-message inbox end to end (read, reply, share documents).
• Nurse — can confirm bookings, read portal queues, and triage/reply to patient messages (no PHI document-release authority).

Editions

Veona Portal is included in the Hospital and Network editions.

Screens

The Veona Portal staff work surfaces (from apps/web/src/modules/portal/ModuleTabs.tsx):

Overview · Bookings · Results Delivery · Messages · Patients · Broadcasts · Branding · Reports · Settings.

Confirm a portal booking request

When a patient self-books on the portal, they create a PortalBooking in the Requested state. Staff confirmation turns it into a real appointment.

1. Open Overview (/portal) or Bookings (/portal/bookings) to see incoming requests.
2. Review the requested type, provider and date for a Requested booking.
3. Choose Confirm (portal.booking.manage). The booking materialises into a real Appointment stored in the same Appointments table — it now appears on the front-desk schedule, check-in ready.

Note

The full path from patient request to a check-in-ready appointment is documented in Workflows → Patient Portal Booking.

Release results to a patient

Releasing a result is the PHI-release gate — it is the deliberate decision to make a clinical result visible to the patient.

1. Open Results Delivery (/portal/results).
2. Find the released lab or imaging result awaiting portal delivery.
3. Release it to the patient (portal.result.release — Portal Coordinator, or the ordering Clinician for their own patient). The patient can now view and download the branded PDF on their portal.
4. You can also hold a result so it is not yet visible — useful for results a clinician wants to discuss first.

Reply to secure messages

1. Open Messages (/portal/messages) to see the secure staff-patient message inbox.
2. Read a patient message and reply (portal.message.reply — Portal Coordinator, Clinician or Nurse).
3. A Clinician or Portal Coordinator can share a document into the thread (portal.message.share); nurses can reply but not share documents.

Broadcasts and branding

• Broadcasts (/portal/broadcasts) — send a portal-wide announcement to enrolled patients (portal.broadcast). Broadcasts are PHI-safe.
• Branding (/portal/branding) — configure the facility’s portal logo, colours and identity (portal.manage).
• Patients (/portal/patients) lists the patients enrolled in the portal; Settings configures portal behaviour.