ACANIO / Specialized engineering

PACS & DICOM Integration Services

A viewer or clinical application is only useful if it can reliably reach the right imaging studies. ACANIO connects your PACS and archive interfaces, delivering tested data exchange, deployment configuration, and recovery procedures for the agreed environments.

Discuss your project ↗ Explore who we help →

What we build

Engineering capabilities

↗

DICOM and DICOMweb interfaces

Implement the query, retrieval, and storage operations your workflow needs over DIMSE or DICOMweb. Confirm supported operations and transfer syntaxes against each system’s conformance statement and test real interface behavior.

↗

PACS integration and archive connectivity

Connect your viewer or service to existing PACS and archive endpoints. Address network access, credentials, routing, and retrieval failures, with configuration and integration tests for each agreed environment.

↗

Metadata and study workflow design

Map patient, accession, study, series, and instance identifiers across system boundaries. Define how new, updated, and incomplete studies become available, including duplicate and reconciliation handling.

↗

Authentication, auditing, and deployment

Apply agreed access controls and audit events to imaging exchange. Document credential handling, network boundaries, deployment configuration, and operational recovery without embedding secrets in browser code.

Scope and prerequisites

Resolve the boundary between application and archive

Customer problems

This service fits new viewer connectivity, archive migration, cloud access, or exchange between systems with different DICOM capabilities. We establish which system owns the images and metadata, then define the required query, retrieval, and storage behavior.

What we need to begin

Bring archive and viewer versions, conformance statements, endpoint or AE configuration, supported SOP classes and transfer syntaxes, synthetic datasets, and expected study sizes. An approved test route, test credentials, and an archive administrator are needed to exercise authentication, network, and storage behavior.

Follow the illustrative technical walkthrough ↓

Engineering in detail

Connect a viewer to an existing archive

Illustrative approach: enable study search and image retrieval from an archive while retaining the existing image store. Storage is included only when the workflow needs it.

Establish access. Confirm network reachability, TLS and authentication requirements, and the operations exposed by each endpoint. Test access from the intended application environment before changing the viewer.
Prove a representative dataset. Search for a synthetic study, retrieve its series metadata, and load images. Check identifiers, image counts, multiframe data, and transfer syntax support against the agreed dataset matrix.
Define transfer behavior. For storage or forwarding, record per-instance outcomes and how a partially transferred study is reconciled. Agree retry and duplicate behavior with the receiving archive rather than assuming every repeat transfer is harmless.
Repeat under operating constraints. Exercise large studies, limited bandwidth, session expiry, and an interrupted transfer. Capture actionable errors and document how an operator resumes or investigates the exchange.

Deliverables and acceptance checks

Deliverables can include an archive adapter or viewer data source, endpoint configuration templates without secrets, a supported-dataset matrix, integration test fixtures, and an operational runbook.

Denied access and expired credentials cannot be mistaken for an empty study list.
Each agreed image type loads with the expected identifiers, dimensions, and frame count; unsupported data produces an explicit error.
Partial transfers expose failed instances and can be reconciled under the agreed retry policy.
Loading and transfer checks meet performance criteria agreed for representative study sizes and networks.

Technical reference: DICOM PS3.18 web services, alongside each vendor’s conformance statement.
The DICOMweb viewer walkthrough covers the application side of this boundary.

Planning an engagement

Questions to scope the work

Which operations and systems are in scope? Identify the archives, viewers, query and retrieve paths, and whether writing or migration is required.
What data must work at launch? Agree modalities, image types, transfer syntaxes, and representative volumes.
Who owns operational recovery? Identify the people who manage credentials, archive configuration, failed transfers, and acceptance sign-off.

Explore engagement options ↗

Explore related expertise

Connected engineering services

Have a project in mind?

Tell us what you are building and which systems need to work together.

Discuss your project ↗

Please do not send patient information or other sensitive health data.