OHIF extension and customization
Implement OHIF modes, panels, commands, and extensions for your product workflow. Document how custom modules are registered and tested so your team can update them alongside the viewer.
ACANIO / Specialized engineering
OHIF Viewer Development & Customization
Your imaging product needs workflow behavior beyond a stock viewer. ACANIO adapts OHIF modes, extensions, and data sources, delivering maintainable custom modules, integration tests, and an upgrade plan for your chosen version.
Discuss your project ↗ Explore who we help →Engineering capabilities
Viewport tools and hanging protocol workflows
Adapt viewport layouts, image tools, and hanging protocols to the studies users review. Test study navigation, priors, and layout behavior against agreed modality and series combinations.
DICOMweb and identity integration
Configure archive search, metadata retrieval, and image access through DICOMweb data sources. Integrate identity and authorization with the host application, including expired sessions and inaccessible studies.
Performance, testing, and deployment architecture
Investigate loading time, memory use, and rendering behavior with representative studies. Deliver regression checks and deployment configuration that reflect your browsers, network limits, and supported OHIF version.
When OHIF needs to fit your product
Customer problems
This service fits a team adding a reading tool, changing a viewport layout, connecting an archive, or maintaining an existing OHIF customization. We first separate configuration changes from extension work and changes that would require maintaining a fork.
What we need to begin
Start with your OHIF version or commit, custom extension source, build configuration, supported browsers, archive interface details, and synthetic studies. Access to a test environment and the owners of authentication and deployment helps define the integration boundary.
Adding a review panel without losing the upgrade path
Illustrative approach: add a study review panel to an existing OHIF application. Scope, version support, and acceptance criteria are agreed for the actual product.
- Map the current behavior. Reproduce the workflow on the pinned viewer version. Record registered modes, extensions, custom patches, and dependencies before choosing where the new panel belongs.
- Define the extension boundary. Implement the panel and its commands as an extension, then compose it into the required mode. Keep archive access in the data source and document any dependency on platform internals.
- Exercise the workflow. Load a synthetic study, navigate series, change layouts, and switch between studies. Confirm panel state follows the current study and handles missing metadata or inaccessible images.
- Rehearse maintenance. Run the same checks against the proposed upgrade version in a separate branch. Record API changes, dependency conflicts, and migration work so the product owner can choose the release scope.
Deliverables and acceptance checks
A scoped engagement can deliver an extension or mode, configuration changes, automated workflow checks, a compatibility record, and maintenance notes identifying any remaining core patches.
- A missing extension or incompatible API produces a diagnosable failure in testing rather than silently removing a tool.
- Study switching clears stale panel state, and denied archive access leaves a usable recovery path.
- The agreed version builds reproducibly; the upgrade rehearsal records which custom behavior passes and what still needs migration.
For a public source to inspect, ACANIO’s Nextcloud DICOM viewer walkthrough points to its OHIF-based viewer. The repository exposes extensions, modes, and platform code, and the Nextcloud App Store listing makes the application discoverable.
Questions to scope the work
- Which version must remain supported? Identify the current release, any fork, and the intended upgrade window.
- What should change for the user? Provide a workflow sketch and representative study types so we can distinguish configuration from custom tools.
- Who will maintain the extension? Agree repository ownership, review responsibilities, and regression checks before handover.
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.