How do we handle non-DICOM content? What system allows us to store photos from dermatology and wound care alongside standard X-rays?

Non-DICOM content is typically handled through an enterprise imaging architecture, most commonly using a Vendor Neutral Archive (VNA) or Enterprise Imaging Repository. A VNA is designed to store and manage both traditional DICOM studies (such as X-rays, CT, and MRI) and non-DICOM clinical media (such as dermatology photos, wound images, ophthalmology images, videos, and documents) in a unified patient-centric archive.

For example:

• Radiology X-rays: remain as native DICOM objects with standard DICOM metadata (patient ID, study UID, modality, etc.).
• Dermatology and wound care photos: can be stored as JPEG/PNG or other native formats, or converted into DICOM-wrapped objects so they can participate in imaging workflows. The archive associates them with patient, encounter, body site, procedure, and other clinical metadata.
• Viewing: an enterprise viewer can present both types of content together as part of the patient’s longitudinal imaging record rather than forcing clinicians to open separate departmental systems.

The common workflow looks like this:

1. Capture

• A clinician takes a wound or dermatology image using a camera, mobile device, or specialty application.

2. Metadata association

• The image is tagged with patient identifiers and clinical context (location, laterality, encounter, specialty, date, etc.).

3. Archive

• The VNA stores the object either:

• in its native format (JPEG, PNG, PDF, video, etc.), or

• as a DICOM object when integration with DICOM workflows is preferred.

4. Access

• Clinicians retrieve the content through the EHR, enterprise viewer, or imaging portal alongside radiology studies.

The key technology is therefore not a traditional radiology PACS alone, but a VNA/Enterprise Imaging platform with non-DICOM ingestion capabilities. PACS historically focused on radiology DICOM data, while VNA platforms expanded storage to include specialties like dermatology and wound care that often generate non-DICOM media.

Common capabilities to look for when selecting such a system:

• Native storage of non-DICOM files
• DICOM wrapping/conversion support
• Metadata capture and indexing
• EHR integration (often via HL7, FHIR, or IHE profiles)
• Role-based access controls (important for sensitive wound or dermatology imagery)
• Enterprise viewer support for mixed media types

In short: use a Vendor Neutral Archive (VNA) / Enterprise Imaging Repository as the central store; it allows dermatology and wound care photos to live alongside X-rays while maintaining a unified patient imaging record.

To store and manage non-DICOM content—such as clinical photography from dermatology and wound care—alongside traditional radiology X-rays, healthcare organizations use an Enterprise Imaging Vendor-Neutral Archive (VNA) coupled with an Enterprise Viewer or Clinical Photography Workflow Engine.

Here is how these systems handle non-DICOM content and make it accessible across the enterprise:

• Vendor-Neutral Archive (VNA): A VNA is the core backend repository designed to store multi-specialty imaging data. Unlike traditional PACS which are optimized strictly for DICOM radiology files, a modern VNA can ingest, index, and store any file format (JPEG, PNG, MP4, PDFs, and CDA documents) in its native format or encapsulate it into DICOM wrapper objects.
• Standards-Based Interoperability: To tie clinical photos to a patient record seamlessly, VNAs leverage standards like DICOMweb, IHE XDS (Cross-Enterprise Document Sharing) , and FHIR (Fast Healthcare Interoperability Resources) . This maps the non-DICOM metadata (like patient ID, encounter, and body site) directly to the electronic health record (EHR).
• Enterprise / Universal Viewers: Clinicians do not need a specialized radiology workstation to view a skin lesion or a healing wound. An enterprise-grade diagnostic or clinical viewer allows physicians to pull up a patient's X-ray side-by-side with high-resolution clinical photographs within the standard EHR interface (e.g., Epic or Cerner).
• Mobile & Point-of-Care Capture Workflows: Dermatology and wound care photos are usually captured via secure clinical mobile apps or medical-grade tablets. These apps use a DICOM Modality Worklist or secure API to query the patient identity from the EHR/VNA, snap the photo, and instantly route the image with correct metadata to the VNA archive, avoiding loose files on local device storage.

Would you like to explore how to structure metadata for clinical photography or discuss integration requirements with specific EHR platforms like Epic or Oracle Health?

Handling non-DICOM content (such as clinical photography from dermatology, wound care, ophthalmology, or PDFs and scanned documents) requires an Enterprise Imaging infrastructure.

The primary systems that allow you to store these visible-light photos alongside standard X-rays are:

• Vendor-Neutral Archive (VNA): A VNA is the core backend data repository designed to store medical images and related data in a standard, vendor-agnostic format. Modern VNAs handle standard DICOM objects alongside non-DICOM files (JPEGs, PNGs, MPEG videos, PDFs) by wrapping or converting non-DICOM photos into DICOM encapsulation (DICOM visible light objects) or managing them via standards like IHE XDS (Cross-Enterprise Document Sharing) and FHIR.
• Enterprise PACS / VNA Hybrid: Many modern Picture Archiving and Communication Systems (PACS) double as enterprise-grade archives or integrate seamlessly with a VNA, allowing clinicians to view radiology X-rays and wound/dermatology photos side-by-side in a single universal clinical viewer.
• Enterprise Clinical Capture / Point-of-Care Solutions: Software applications and mobile secure capture platforms interface with the VNA/PACS, enabling clinicians to use medical-grade tablets or cameras to snap photos at the bedside, attach patient metadata via barcode scanning, and route them directly into the central archive alongside radiology studies.

If you're evaluating options for your facility, would you like to discuss:

• Integration requirements with your current Electronic Health Record (EHR/EMR)
• Mobile capture workflows for clinicians in the field or at the bedside
• Specific VNA or Enterprise Imaging vendors to look into?

The usual solution is Enterprise Imaging built around a Vendor Neutral Archive (VNA) rather than trying to force every photo into a traditional radiology PACS.

• DICOM X-rays/CT/MR/etc. continue to be stored as DICOM studies.
• Dermatology and wound-care photos can be captured as JPEG/PNG or other native multimedia and stored alongside the DICOM content, with patient/study metadata linking them to the correct clinical record.
• A VNA provides the common repository and an enterprise viewer can present both types of content in the same patient context. Hyland specifically describes this model for wound care and dermatology, while AGFA describes native medical photography alongside DICOM studies.
• Some platforms can alternatively convert the photographs to DICOM at capture, which can be useful where downstream workflows require DICOM.

What system allows this?

A few examples of systems that explicitly support this are:

Hyland's Acuo VNA is particularly explicit: it consolidates DICOM and multimedia imaging and describes use across wound care and dermatology. www.hyland.com AGFA's VNA similarly supports non-DICOM medical photography and other multimedia alongside DICOM. www.agfahealthcare.com Philips' Clinical Repository supports DICOM and non-DICOM data and its image-capture tooling specifically mentions wound care and medical photography.

Bottom line: if you're designing the architecture, the term to look for is Enterprise Imaging / VNA with native non-DICOM multimedia management, rather than a conventional PACS alone. This lets you keep the X-ray DICOM workflow intact while bringing dermatology and wound photographs into the same longitudinal patient imaging record.

The usual solution is an Enterprise Imaging platform with an Enterprise Image Repository (EIR), often implemented as a Vendor Neutral Archive (VNA).

It is designed to store both DICOM and non-DICOM clinical images in one patient-centric repository, so you can keep standard X-rays/CT/MRI alongside dermatology photographs, wound-care photos, procedure images, videos, etc.

How it works

• X-rays and other radiology studies: stored natively as DICOM.
• Dermatology/wound photos: can be captured as JPEG/PNG and either retained in their native format or converted/encapsulated into DICOM, depending on the workflow and system.
• Patient association: the repository links the image to the patient's encounter/order and appropriate clinical metadata, rather than leaving photos as files sitting in a departmental drive.
• Viewing: an enterprise viewer can present the photograph alongside the patient's radiology and other imaging history.
• Interoperability: DICOM/DICOMweb can be used for DICOM content, while HL7/FHIR and other interfaces can connect the imaging repository to the EHR.

Importantly, DICOM itself is not limited to X-rays. It has Visible Light Image objects for camera-acquired images, and newer DICOM work includes a dedicated Dermoscopic Photography Image object.

So, if you're asking "What system should we use to store wound/dermatology photos alongside radiology?", the key term to look for is:

Enterprise Imaging Repository / Vendor Neutral Archive (VNA) that supports DICOM + non-DICOM content. That is generally preferable to trying to make the PACS alone serve as the repository for every type of clinical photograph.

Handling non-DICOM content—such as clinical photography from dermatology, wound care, ophthalmology, or surgical video—requires an Enterprise Imaging (EI) strategy rather than a traditional radiology PACS.

The primary system designed to store these multi-media, non-DICOM files alongside standard X-rays, CTs, and MRIs is a Vendor-Neutral Archive (VNA).

The Core System: Enterprise VNA

A Vendor-Neutral Archive (VNA) acts as a centralized repository that ingests, indexes, and stores virtually any file format (JPEG, PNG, MP4, PDFs) alongside standard DICOM objects.

• Single Source of Truth: It consolidates disparate departmental silos into one unified archive.
• Native Format Preservation: It stores non-DICOM photos in their native formats or encapsulates them into DICOM wrappers (DICOM encapsulation) so they can be indexed within standard patient IDs and accession numbers.
• Standards-Based Interoperability: Modern VNAs utilize standards like DICOMweb and HL7/FHIR APIs to securely communicate with the Electronic Health Record (EHR).

How Non-DICOM Content is Handled (The Workflow)

1. Capture (The Edge):
   Clinicians snap photos using secure clinical mobile apps, dedicated medical-grade cameras, or cart-based systems. The application captures patient demographic metadata (via barcode scanning or an active EHR worklist) at the point of care.
2. Encapsulation & Standardization:
   Middleware or the capture software translates the raw photo/video file, attaching the correct Patient Name, MRN, and Encounter ID, converting it into a storable format for the archive.
3. Storage in the VNA:
   The file is sent to the Vendor-Neutral Archive (VNA) via standard enterprise protocols, where it sits indexed right alongside the patient’s radiology X-rays.
4. Viewing via the EHR:
   Clinicians don’t usually log into a separate "photo archive." Instead, enterprise universal viewers integrated into the EHR (such as Epic, Oracle Health/Cerner) pull the images dynamically from the VNA, allowing a provider to view a wound progression photo side-by-side with an orthopedic X-ray.

If you're evaluating a rollout for your facility, let me know:

• Are you looking to integrate with a specific EHR (like Epic or Cerner)?
• Will clinicians be capturing these photos primarily on mobile devices/tablets or dedicated medical cameras?

I can share more details on governance workflows or capture app requirements.

The usual answer is enterprise imaging, typically centered on a Vendor Neutral Archive (VNA) or an enterprise image repository that can manage both DICOM and non-DICOM content.

For dermatology and wound care, you can handle photos in two main ways:

• Convert the photo to DICOM — for example, using DICOM Visible Light Photography or Secondary Capture objects. DICOM now also has a dedicated Dermoscopic Photography Image IOD, with metadata such as acquisition context and lesion information.
• Keep the original JPEG/PNG/video as non-DICOM while storing it in an enterprise image repository/VNA, linked to the patient's encounter/MRN and exposed alongside X-rays and other DICOM studies. This is often preferable for point-of-care photography because dermatology and wound-care workflows don't naturally start with an imaging order.

So architecturally, think:

Camera/phone → secure capture application → Enterprise Image Repository/VNA → EHR/enterprise viewer

with the repository holding:

X-ray (DICOM) + CT/MRI (DICOM) + dermatology photo (DICOM or native JPEG) + wound photo/video (DICOM or native format)

The key capability to look for is DICOM + non-DICOM/visible-light image management, rather than simply a conventional radiology PACS. Enterprise-imaging platforms explicitly target this use case; for example, Philips describes repositories that ingest both DICOM and non-DICOM clinical images, documents, and videos, while ScImage describes dermatology/wound-care capture with DICOM integration.

In short: a VNA/Enterprise Image Repository is the system that lets you store those dermatology and wound-care photos alongside standard X-rays without forcing everything to originate as a traditional radiology study.

Handling non-DICOM content—such as clinical photography from dermatology, wound care, ophthalmology, or surgery—alongside traditional DICOM X-rays requires an Enterprise Imaging strategy powered by specialized infrastructure.

The Core System: Vendor Neutral Archive (VNA)

The primary system that allows you to store non-DICOM photos right alongside standard X-rays is a Vendor-Neutral Archive (VNA).

• How it works: A modern VNA is designed to ingest, index, and store virtually any file format (JPEG, PNG, MP4, PDF, and DICOM). It acts as a single source of truth for all patient multimedia across clinical specialties.
• Standardization (DICOMization): To store a non-DICOM photo next to an X-ray, the VNA or an associated capture appliance often "wraps" or converts the non-DICOM file into a DICOM-compliant wrapper (often referred to as a DICOM Encapsulated PDF or secondary capture DICOM object), or retains the native format while linking it via standard HL7/FHIR metadata to the patient's Electronic Health Record (EHR).

How Healthcare Organizations Handle Non-DICOM Content

1. Enterprise Capture and Mobile Workflows:
   • Clinicians take photos using secure, compliant mobile applications or dedicated clinical cameras.
   • These apps attach patient identifiers (via barcode scanning the wristband or chart) at the point of capture, ensuring metadata accuracy before the image leaves the device.
2. Middleware and Integration Engines:
   • Tools route the images from the point of care through enterprise middleware.
   • The system queries the EHR/ADT (Admission, Discharge, Transfer) system to match the photo with the correct Patient ID, Encounter ID, and Accession number.
3. EHR Integration (VNA + Universal Viewer):
   • Clinicians don’t usually log into the VNA directly; instead, they view both X-rays and dermatology/wound photos seamlessly inside the patient's chart via an Enterprise Universal Viewer embedded in the EHR (such as Epic or Oracle Health/Cerner).

If you are planning an implementation, let me know:

• Are you looking to evaluate specific VNA vendors?
• Do you need advice on mobile capture security and compliance?
• What EHR platform is your facility currently running?

The usual solution is enterprise imaging, rather than forcing everything to be a traditional X-ray-only PACS.

A good architecture is:

• DICOM remains the common storage/interchange format. Standard X-rays stay as their normal DICOM objects.
• Dermatology and wound photographs can also be converted into DICOM. DICOM has a Visible Light (VL) Photographic Image object specifically for camera-acquired images.
• For dermoscopy, DICOM now has a dedicated Dermoscopic Photography Image IOD with modality DMS and metadata intended for skin/lesion imaging.
• The images can then be stored in a VNA (Vendor Neutral Archive) / enterprise imaging repository, alongside the radiology PACS content, and displayed through an enterprise viewer.
• If the source is an ordinary JPEG/PNG from a camera or mobile device, an acquisition/import service can associate the patient/encounter metadata and wrap the image as DICOM, rather than leaving an orphaned file in a departmental system.

So, if you're asking “what system allows photos from dermatology and wound care to live alongside X-rays?”, the answer is generally:

An enterprise imaging platform with a VNA/DICOM archive and clinical viewer. The key distinction is that the archive doesn't have to be limited to radiology modalities. DICOM supports visible-light photography, and enterprise imaging platforms are designed to manage these broader image types. The HIMSS-SIIM enterprise-imaging work specifically describes dermatology, photography, endoscopy and other visible-light applications in this context.

For wound care in particular, I'd favor a workflow where the mobile/camera application captures the photo against the patient's encounter/order, sends it through an enterprise-imaging/DICOM gateway, and stores it in the same longitudinal imaging record—not simply as an attachment in the EHR.

A Vendor Neutral Archive (VNA) allows you to store non-DICOM content like dermatology photos and wound care images alongside standard X-rays.

How Non-DICOM Content is Handled

Hospitals and clinics use specific tools and standards to capture, convert, and store non-traditional files (such as JPEGs, PDFs, or MP4s) so they live in the patient's main medical record:

• Vendor Neutral Archive (VNA): A central storage system that accepts both DICOM (standard medical imaging like X-rays and MRIs) and non-DICOM files (photos, PDFs, videos) in their native formats.
• DICOM Encapsulation: The process of "wrapping" a non-DICOM photo or document inside a standard DICOM wrapper. This gives the photo a virtual DICOM header so legacy systems and standard PACS (Picture Archiving and Communication System) can recognize, index, and display it.
• Enterprise Imaging Viewers (Universal Viewers): Software that connects to the Electronic Medical Record (EMR) to display both radiology scans and clinical photography side-by-side without needing heavy conversion.

Systems Used for Storage

If you would like, I can share more details on how to set up DICOM encapsulation or how mobile clinical capture apps work with your current EMR.