Keep medical images with the documents that explain them
A case file can include a referral letter, a PDF report, and a set of medical images. When each attachment opens in a different tool, the person reviewing the case has to keep finding their place.
The Doconut DICOM Plugin brings DCM and IMA files into Doconut's browser viewer. For developers building a .NET document portal, it offers a way to present medical images alongside the supporting documents already in the application.
If browsing documents on Doconut.app has made you consider embedding a viewer in your own product, this plugin is an extension to explore on Doconut.com. The integration described here belongs to your own Doconut-powered application.
What the DICOM plugin adds
The plugin supports opening DICOM files with the .dcm and .ima extensions. It can present multi-frame files as an animation, individual frame pages, or a combination of the two. Rendering settings let developers adjust image resolution, animation timing, and repeat behavior. These capabilities are described on the official DICOM product page.
That choice of presentation matters. A short animated overview can help a user understand that an attachment contains a sequence, while individual pages make it easier to return to a particular frame. A portal can choose the presentation that fits its review process instead of treating every attachment as one static picture.
Doconut positions the plugin for web viewing workflows; it is not presented as a clinically certified PACS replacement. That distinction helps a team define a useful, realistic scope for its integration.
Start with one clear portal workflow
Consider an internal case-management screen. It already lists a report, correspondence, and associated attachments. Adding a DICOM preview could follow this flow:
- The user opens a case they are authorized to access.
- The application lists the associated attachments with clear filenames and file types.
- Selecting a medical-image attachment opens the embedded viewer.
- The user navigates the available frames, then returns to the case details.
The application should maintain the relationship between the attachment and its case. Clear navigation and a visible document name are small details that can make a mixed-document screen easier to use.
For the remaining attachments, consult Doconut's supported file formats. Use that catalog to decide which files your portal will accept and preview.
Choose a display mode during evaluation
Build a small evaluation set with both single-frame and multi-frame files. Use samples approved for development, and include the variations your application expects to receive.
For each example, decide whether users need an overview, frame-by-frame navigation, or both. Compare the result at the viewer size used in your actual portal. A large standalone demo can hide layout problems that become apparent when the viewer sits beside case details.
Also measure the first preview and subsequent navigation with representative file sizes. Record the behavior before changing rendering settings so that you can judge the effect of each adjustment.
These are application acceptance checks, not a claim that every DICOM dataset will behave identically.
Connect the plugin to your .NET application
The DICOM integration documentation explains package installation, registration, licensing, and rendering configuration. Select the documentation for your target framework and keep the plugin version aligned with the corresponding Doconut viewer package.
Plan access to the original attachment and to rendered output as part of the same application workflow. Authentication, authorization, retention, and any audit trail depend on the surrounding application and its deployment. Adding a viewer does not define those policies for you.
A focused first milestone is enough: open an authorized sample, show the intended frame presentation, and return to the case without losing context. Expand the integration once that path works with your representative files.
Explore DICOM viewing with Doconut
The most useful reason to add DICOM viewing is to make medical-image attachments accessible within the document workflow your users already follow.
Visit the Doconut DICOM Plugin page to review the feature set and licensing options. Then use the official integration guide to evaluate it in your .NET portal, with the files and navigation patterns your team actually needs.