Custom DICOM and web imaging viewers
Build study navigation, image loading, and viewer controls around your product workflow. Deliver an integrated viewer with documented interfaces and tests for the image types your users need.
ACANIO / Specialized engineering
Medical Imaging Software Development
Imaging products need viewers, visualization, and archive connectivity that work together. ACANIO develops and modernizes these components around your product architecture, delivering integrated software, tests, and documentation your team can maintain.
Discuss your project ↗ Explore who we help →Engineering capabilities
Advanced visualization and measurement workflows
Extend image review with MPR, image fusion, segmentation display, and measurement tools using technologies including CornerstoneJS and VTK.js. Check orientation, spacing, and measurement persistence against representative datasets and the agreed review workflow.
DICOMweb, PACS, and cloud integration
Connect archive queries, metadata retrieval, and image loading to your viewer. Address authentication, network boundaries, and archive-specific behavior, with integration tests and deployment documentation.
OHIF customization and extension
Adapt OHIF modes, extensions, panels, and tools for your application. Keep custom behavior organized around extension boundaries and document dependencies so your team can maintain it.
Example engineering scenarios
- Integrate a web viewer into an existing imaging product
- Extend an imaging application with MPR and study navigation
- Connect a viewer to a DICOMweb-compatible archive
- Develop mammography viewing tools around specialized reading workflows
- Integrate ECG waveform viewing into a clinical application
- Develop veterinary imaging viewers and workflows for specialized review
DICOM Viewer for Nextcloud: a source you can inspect
By ACANIO LLC. Based on the public project repository.
Opening medical images from a collaboration platform brings together two concerns: access to shared files and a viewer that understands imaging data. ACANIO’s public Nextcloud DICOM viewer builds on OHIF v3 with additional customizations.
Foundation and boundaries
The repository separates viewer extensions, workflow modes, and platform code. Its documented foundation supports DICOMweb archives and browser-based image review. Those boundaries give a technical team concrete places to inspect data access, tools, and workflow composition.
What you can verify
Review the README, source tree, and history to assess the implementation yourself. The source provides a concrete starting point for discussing extension boundaries, archive connectivity, and maintenance with your engineers.
For a similar integration, the first design questions are how viewing context reaches the application, which component authorizes image access, and where custom behavior belongs. The walkthrough below turns those questions into an integration sequence.
Inspect the public DICOM viewer repository ↗Connecting a DICOMweb archive to a web viewer
A successful image load is only one part of a viewer integration. The application also needs reliable study selection, authorized access, and a useful response when the archive cannot serve an image.
- Agree the interface contract. Identify the archive endpoints, supported image types, study identifiers, and authorization boundary. Start with synthetic test studies that exercise the expected modalities and transfer syntaxes.
- Connect search and retrieval. Configure study search and image retrieval roots in the viewer’s data source. OHIF exposes separate QIDO and WADO configuration; upload needs an agreed storage endpoint and permission. Check returned metadata and frame loading before adding workflow tools.
- Test access, failure paths, and performance. Verify denied access, expired sessions, missing series, partial studies, and slow responses. Optimize image loading and rendering for responsive interaction. Keep credentials out of launch URLs and browser configuration, and ensure errors do not expose patient details.
- Hand over an operable integration. Document endpoint configuration, supported datasets, test results, and recovery steps. Prepare technical documentation to support FDA 510(k) submissions where applicable. Agree performance acceptance criteria against representative study sizes and the intended network.
For the viewer side, explore OHIF customization and extensions.
For archive boundaries and exchange, see PACS and DICOM integration.
Adding model results introduces a separate AI result association and display workflow.
Own the system. Keep the source.
We design around the viewers, archives, and clouds you already run. The repository stays in your control. Where a product is developed in a regulated environment, we can support the engineering record.
- Workflow-first viewers: hanging protocols, priors, labeling, and longitudinal review
- Cloud, on-premise, or hybrid deployment, including networks that cannot reach the public internet
- Legacy modernization, performance, and secure development practices
Domain knowledge meets disciplined delivery.
We begin with your workflow, architecture, and integration constraints. Then we design, implement, review, integrate, and hand over maintainable software. We can collaborate with your internal team or take ownership of a defined engineering workstream.
How we work ↗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.