Built to connect with your existing radiology systems

1 Your existing systems

HubNex connects supported radiology systems to coordinate imaging studies and report return across hospitals. Radiologists keep using familiar viewing and reporting tools. Compatibility, interfaces and configuration are confirmed for each hospital during onboarding.

• PACS: access images through the supported viewing environment.
• RIS: connect requests, worklists and workflow information through the agreed interface.
• Reporting: prepare reports with familiar tools and return them through the agreed route.
• No PACS or RIS on site: imaging modalities can connect directly, so studies are reported by radiologists at partner hospitals and the reports come back to the site.

Support for a standard does not by itself mean every product has been tested, and we do not display vendor logos without a verified relationship. Standards used: DICOM for images, HL7 for orders and, where configured, FHIR for clinical context.

2 The Edge Agent

An Edge Agent runs inside each participating hospital's network and handles both sending and receiving of studies.

• It opens outbound connections only. No inbound firewall ports are opened on the hospital side.
• It is authenticated to the platform over TLS 1.3, with mutual TLS (mTLS) in production deployments.
• It can pseudonymise studies before they leave the hospital network.
• Hospital IT controls where it is placed, its network egress rules and which modalities it accepts.
• If connectivity is lost, it keeps studies in an encrypted buffer and forwards them when the connection returns.

3 What setting up a collaboration involves

Setup includes connecting the hospital's systems, agreeing participation and reporting roles, configuring allocation rules and validating the study and report flow. Integration scope, responsibilities and timing are agreed for each site, including its security and data-protection review.

Pilots progress in stages, each gated by the hospital's sign-off: first synthetic data to validate integration and workflow, then pseudonymised data, and real patient data only after an independent penetration test and pre-go-live hardening are complete.

4 Reporting coordination

HubNex matches studies using the required expertise, radiologist availability and the allocation rules agreed by the participating hospitals. Requests and report return follow the configured workflow. Any tracking, priority or escalation functions are specified for the deployment. HubNex coordinates routing and does not perform diagnostic analysis; integration of external AI tools is not part of the current offering.

• Rules: routing rules are set per deployment, by modality, body region, subspecialty and capacity.
• Priority: the request's priority is read from the order fields (STAT, URGENT, ASAP or ROUTINE).
• Critical findings: flagged by the platform so they can be acted on.
• Records: each routing decision is logged, with the scores behind it.

5 Where data is processed and stored

• Region: the platform is hosted in the EU with an ISO 27001-certified infrastructure provider (Germany or Finland during the pilot). The provider's certification belongs to the provider, not to HubNex.
• Studies: studies shared for reading are transferred from the sending hospital's Edge Agent to the HubNex platform, encrypted in transit and at rest.
• Minimal data: HubNex extracts and retains only what is needed to route a study and return a report. Clinical context from a hospital is reduced to an age band, gender, priority and a coded indication; names and dates of birth are not shared.
• Retention: patient data is kept for the pilot period and deleted within 30 days of its end.

6 Security controls

• Encryption in transit: TLS 1.3 on every connection to the platform; DICOM TLS between the hospital PACS and the Edge Agent.
• Encryption at rest: AES-256 on an encrypted volume holding all application data. The unlock passphrases are held by HubNex, not by the hosting provider. Backups are encrypted separately.
• Access: role-based and least-privilege. Multi-factor authentication is required for administrators. In the pilot, each hospital manages its own clinical users within its existing PACS and identity systems.
• Audit: authentication and authorisation events and actions on studies are recorded in append-only audit logs.
• Network: a single public entry point, default-deny firewall and rate limiting. Hospital IT can restrict platform access to its own network ranges.

7 Certifications and independent testing

We separate what has been achieved from what is planned.

• Available now: a GDPR Article 28 data processing agreement and a DPIA support package for your DPO. A security white paper and security Q&A are available on request.
• Planned: an independent penetration test before any pilot with real patient data, repeated at least annually.
• Targeted: ISO 27001 certification of HubNex itself. This has not yet been achieved.
• Regulatory: HubNex does not currently claim medical-device certification.

Regulatory requirements depend on the country and the workflow, and are assessed with each hospital rather than assumed.

8 Responsibilities and support

Hospitals remain responsible for their own systems, users, clinical decisions and the agreements between participating hospitals. HubNex is responsible for the platform. Support and service levels for the pilot are set out in the pilot agreement. Post-pilot pricing depends on study volume and the services you use; contact us for details. Security researchers can report findings to security@hubnex.net.