Integrations

PACS-friendly by design.

Verityn is built to work alongside the infrastructure already in place. Standard DICOM and HL7/FHIR connections, results in the viewer the radiologist already uses, and no requirement to change the workflow.

Standards-based

The standards your site already runs.

Verityn does not require proprietary gateways or custom middleware. Integration is built on the protocols your PACS, RIS, and EHR already speak.

DICOM C-STORE and C-FIND

Studies are received and queried over standard DICOM. No proprietary connector is required on the sending system.

HL7 and FHIR

Orders and results are exchanged with the RIS and EHR using the messaging protocols the site already runs: HL7 v2 or FHIR R4.

Modality worklist

Verityn sits alongside the existing worklist and returns prioritisation flags without disrupting the existing task queue.

Secondary capture and structured report

Results return as a DICOM secondary capture or a Structured Report. They sit beside the original study in the existing viewer.

Integration points

Where Verityn connects.

Each connection point uses a standard that radiology infrastructure already supports, so nothing new needs to be installed on the sending side.

DICOM C-STORE and C-FIND

Receive and query studies over standard DICOM, no proprietary gateway.

Modality worklist

Sit alongside the existing worklist and return prioritisation without disruption.

Secondary capture and SR

Return flags as a secondary capture image or a DICOM Structured Report beside the original.

HL7 and FHIR

Exchange orders and results with the RIS and EHR using the messaging your site already runs.

PACS viewers

Overlays and heatmaps render in your current viewer. No new screen for the radiologist to learn.

Audit and export

Structured export of every study, flag, confidence value, and human decision for governance.

Study flow

How a study moves through the system.

From arrival to radiologist decision, the path is transparent, standards-based, and leaves no step outside the audit log.

01

Study arrives via DICOM

A completed study is sent to Verityn via a standard DICOM C-STORE from the modality or the PACS. No proprietary gateway is required.

02

Second read runs automatically

The computer vision model processes the study and produces flags with confidence values, bounding regions, and plain-language reasons.

03

Flags returned to the worklist

Results are written back as a secondary capture image or a DICOM Structured Report, visible in the existing worklist alongside the original study.

04

Radiologist reviews in their current viewer

The radiologist opens the study in the viewer they already use. Heatmaps and bounding regions are overlaid without requiring a new screen or tool.

05

Clinician decides. Action is logged.

The radiologist agrees or dismisses each flag. The decision, timestamp, and clinician identifier are recorded in the audit log.

06

Radiologist writes the report

The report is written by the radiologist as it always was. Verityn does not contribute to report text.

No rip-and-replace

Your PACS stays. Your viewer stays.

The most common concern in radiology IT is that a new clinical tool requires replacing infrastructure, retraining staff on new screens, or long vendor negotiations. Verityn is designed to avoid all of that.

Because results are returned as a secondary capture or a structured report over standard DICOM, the radiologist sees Verityn's output in the viewer they have always used, without needing to open a second application.

Worklist prioritisation is applied through the existing worklist interface. There is no new queue, no new portal, and no new login for the reader. The tool is there when they need it and absent when they do not.

No new viewer for the radiologist
No proprietary gateway on the modality
No change to report writing workflow
No new worklist screen
No patient data moved without consent
No autonomous clinical decisions
Security and deployment

On-premise or private cloud. Your choice.

For sites where identifiable patient data must not leave the local environment, Verityn can be deployed on-premise or in a private cloud tenancy. Processing occurs within the site's own network boundary, and no image data is transmitted to shared infrastructure.

Data is encrypted in transit and at rest. Access is authenticated, logged, and audited. The deployment architecture is documented as part of the data processing agreement.

Deployment

On-premise or private cloud

Transit

Encrypted in transit and at rest

Audit

Full access and decision log

Compliance

DSPT, ISO 27001 aligned

Ready to connect Verityn to your PACS?

Talk to our integrations team about your site's infrastructure. We can assess compatibility and walk through the connection process before any commitment.