Patient registry / iPortal
Read-only or bidirectional access to approved demographics, identifiers and pathway context.
Integration-led architecture
HealthZon is intended to connect pathway management with patient, radiology, imaging, identity and communication systems through locally agreed interfaces.
Read-only or bidirectional access to approved demographics, identifiers and pathway context.
Referral acceptance, workflow status and locally agreed patient-management interactions.
Booking status, scan completion and DNA notifications to support rebooking and safety-netting.
Study context, reports, viewer launch and appropriate access to CT imaging.
Single sign-on, organisational identity and role-based access control.
Standardised patient and GP letters after scans, MDT decisions and significant actions.
Architecture principles
Structured service interfaces and clear separation between the user experience and integration layer.
Local endpoints, credentials, workflows and interface behaviour managed per environment.
Integration activity, clinical actions and system changes designed to be traceable.
Retry, monitoring, idempotency and exception handling planned for production interfaces.
Use existing source systems and avoid unnecessary data migration, with HealthZon acting as the operational pathway view.
REST APIs, HL7/FHIR-compatible patterns and DICOM-aware imaging integration where locally supported.
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