Integration-led architecture

Designed to work with the hospital technology landscape.

HealthZon is intended to connect pathway management with patient, radiology, imaging, identity and communication systems through locally agreed interfaces.

PAS

Patient registry / iPortal

Read-only or bidirectional access to approved demographics, identifiers and pathway context.

CF

Careflow

Referral acceptance, workflow status and locally agreed patient-management interactions.

CRIS

CT scheduling

Booking status, scan completion and DNA notifications to support rebooking and safety-netting.

PACS

Sectra imaging

Study context, reports, viewer launch and appropriate access to CT imaging.

SSO

Microsoft Entra ID

Single sign-on, organisational identity and role-based access control.

MED

Medisec / correspondence

Standardised patient and GP letters after scans, MDT decisions and significant actions.

Architecture principles

Built to reduce lock-in and support local requirements.

01

API-first

Structured service interfaces and clear separation between the user experience and integration layer.

02

Configurable

Local endpoints, credentials, workflows and interface behaviour managed per environment.

03

Auditable

Integration activity, clinical actions and system changes designed to be traceable.

04

Resilient

Retry, monitoring, idempotency and exception handling planned for production interfaces.

05

Minimal duplication

Use existing source systems and avoid unnecessary data migration, with HealthZon acting as the operational pathway view.

06

Standards-aware

REST APIs, HL7/FHIR-compatible patterns and DICOM-aware imaging integration where locally supported.

Integration status

Specific integrations are subject to discovery, local system capability, supplier access, information governance and Trust approval. The public website does not claim that any named interface is already live.

Technical discussion

Talk to us about your local systems and pathway.

Discuss Integration