Skip to main content

System Requirements and Operational Considerations

This section outlines important operational, compatibility, workflow, and environmental considerations for safe and effective use of the AdvaView viewer platform.


DICOM SOP Class Compatibility

AdvaView supports viewing and interaction with a defined subset of DICOM SOP Classes commonly used in enterprise imaging workflows.

Support may vary depending on:

  • Browser capabilities
  • Transfer syntax
  • PACS/VNA configuration
  • DICOM conformance
  • Workstation performance
  • Viewer licensing and enabled features
Important

Support within AdvaView refers to viewing and workflow interoperability capabilities only.

AdvaView does not function as the authoritative storage archive or system of record for DICOM objects.


Fully Supported Viewing SOP Classes

The following SOP Classes are supported for standard viewing workflows within AdvaView.

General Imaging​

Modality / Object TypeSOP Class NameSOP Class UID
CTCT Image Storage1.2.840.10008.5.1.4.1.1.2
Enhanced CTEnhanced CT Image Storage1.2.840.10008.5.1.4.1.1.2.1
MRMR Image Storage1.2.840.10008.5.1.4.1.1.4
Enhanced MREnhanced MR Image Storage1.2.840.10008.5.1.4.1.1.4.1
UltrasoundUltrasound Image Storage1.2.840.10008.5.1.4.1.1.6.1
PETPositron Emission Tomography Image Storage1.2.840.10008.5.1.4.1.1.128
XAX-Ray Angiographic Image Storage1.2.840.10008.5.1.4.1.1.12.1
XRFX-Ray Radiofluoroscopic Image Storage1.2.840.10008.5.1.4.1.1.12.2
CRComputed Radiography Image Storage1.2.840.10008.5.1.4.1.1.1
DXDigital X-Ray Image Storage — For Presentation1.2.840.10008.5.1.4.1.1.1.1

Mammography and Breast Imaging​

SOP Class NameSOP Class UID
Digital Mammography X-Ray Image Storage For Presentation1.2.840.10008.5.1.4.1.1.1.2
Breast Tomosynthesis Image Storage1.2.840.10008.5.1.4.1.1.13.1.3
Breast Projection X-Ray Image Storage — For Presentation1.2.840.10008.5.1.4.1.1.13.1.1
Mammography Regulatory Note

Diagnostic mammography and tomosynthesis workflows require additional regulatory clearance, workstation validation, monitor calibration, and Hanging Protocol configuration depending on regional regulatory requirements.

danger

At this time Mammography and Breast Tomosynthesis Is for investigational use only AdvaView should not be used for diagnostic interpretation of Mammography or Breast Tomosynthesis


Secondary Capture and Clinical Images​

SOP Class NameSOP Class UID
Secondary Capture Image Storage1.2.840.10008.5.1.4.1.1.7
Multiframe Secondary Capture Storage1.2.840.10008.5.1.4.1.1.7.1 – .7.4 (Single Bit / Grayscale Byte / Grayscale Word / True Color)
VL Photographic Image Storage1.2.840.10008.5.1.4.1.1.77.1.4
Endoscopic Image Storage1.2.840.10008.5.1.4.1.1.77.1.1
Microscopic Image Storage1.2.840.10008.5.1.4.1.1.77.1.2

Structured Reports and Documents​

SOP Class NameSOP Class UID
Basic Text SR1.2.840.10008.5.1.4.1.1.88.11
Enhanced SR1.2.840.10008.5.1.4.1.1.88.22
Comprehensive SR1.2.840.10008.5.1.4.1.1.88.33
Encapsulated PDF Storage1.2.840.10008.5.1.4.1.1.104.1

Conditional or Limited Support

The following object types may have limited support depending on browser compatibility, transfer syntax, workflow configuration, or enabled extensions.

SOP Class NameSOP Class UIDNotes
DICOM Video Objects1.2.840.10008.5.1.4.1.1.77.1.1.1 / .77.1.2.1 / .77.1.4.1 (Video Endoscopic / Microscopic / Photographic)Browser codec support required
Encapsulated PDF1.2.840.10008.5.1.4.1.1.104.1Certain embedded object types may not render
Collaboration SessionsN/A — not a DICOM SOP ClassNetwork conditions may affect synchronization

Unsupported SOP Classes

The following SOP Classes are not currently supported for diagnostic viewing workflows within AdvaView.

Examples include:

  • ECG Waveforms
  • Hemodynamic Waveforms
  • Audio Waveforms
  • MR Spectroscopy
  • RT Dose
  • RT Plan
  • Whole Slide Microscopy
  • Presentation States
  • Spatial Registration Objects
  • Surface Segmentation Objects
Additional Compatibility Information

Unsupported SOP classes generally do not appear within study metadata or study structure. However, in some cases, an unsupported SOP class may still appear as a thumbnail.


Ultrasound Limitations​

While AdvaView supports the Ultrasound Image Storage and Ultrasound Multi-frame Image Storage SOP classes for standard ultrasound viewing, the following ultrasound-specific capabilities are not currently supported.

Echo-Specific Acquisition Modes​

The following echocardiography acquisition modes are not supported for diagnostic viewing:

  • M-mode
  • Color Doppler
  • Pulsed-Wave (PW) Doppler
  • Continuous-Wave (CW) Doppler
  • Tissue Doppler Imaging (TDI)
note

DICOM objects produced by these acquisition modes may be stored under the Ultrasound Image Storage or Ultrasound Multi-frame Image Storage SOP classes and may be visible within the viewer, but correct rendering and clinical interpretation of these modality-specific formats is not validated or supported.

Duplex and Triplex Format Playback​

Duplex and triplex ultrasound formats — which encode multiple image regions (e.g., B-mode, Color Doppler, and Spectral Doppler) within a single DICOM object using the DICOM Sequence of Ultrasound Regions attribute — are not currently supported.

Specifically, the following are not supported:

  • Duplex and triplex study playback and synchronization
  • Synchronized display of combined image, Doppler spectra, and measurement grids during cine playback
  • Region-aware rendering of multi-region ultrasound objects

Echo-Specific Measurements​

The following echocardiography-specific measurement tools are not currently supported:

  • Velocity measurements
  • Pressure gradient calculations
  • Left ventricular (LV) systolic and diastolic function measurements
note

Standard linear and area measurement tools (Length, Bidirectional, ROI) are available for general use on ultrasound images but are not validated for echo-specific hemodynamic measurements.


Transfer Syntax Considerations

Support for some SOP Classes may depend on the transfer syntax used by the originating modality or PACS.

Examples include:

  • MPEG-4 / H.264 video
  • JPEG2000
  • High-Throughput JPEG2000
  • Browser-native codec support

Browser Compatibility

Certain DICOM object types rely on browser-native rendering capabilities and hardware acceleration.

Validated browser configurations should be used in clinical environments.


Storage and Persistence

AdvaView is a stateless zero-footprint viewer and does not function as a long-term archive or PACS.

Storage and persistence responsibilities remain with the connected PACS, VNA, or enterprise imaging platform.


Measurements, Markups, and Annotations

Measurement Accuracy​

Measurement accuracy may be affected by multiple clinical and technical factors including:

  • Patient positioning
  • Patient motion
  • Acquisition protocol
  • Modality calibration
  • Reconstruction distortion
  • Spatial resolution
  • Contrast resolution
  • Display scaling
  • Browser zoom settings

Users are responsible for verifying measurement accuracy prior to clinical interpretation.


DICOM Calibration Review​

Calibration methods used by imaging modalities should be reviewed and validated prior to clinical use.

This review should also be repeated when:

  • New imaging modalities are introduced
  • Existing modalities are upgraded
  • Modality software changes occur
Calibration Validation

Incorrect image calibration may result in inaccurate clinical measurements.


Measurement Placement​

Users should take care when placing measurement control points.

Measurement precision may be affected by:

  • Zoom level
  • Display scaling
  • Monitor resolution
  • Viewport size
  • Cursor placement accuracy

The user is responsible for confirming measurement validity.


Viewing Considerations

Hanging Protocols​

Hanging Protocols may automatically apply:

  • Image rotations
  • Layout changes
  • Series prioritization
  • Multi-monitor placement rules

Users should understand which Hanging Protocol configurations are active within their environment.


Cine Playback​

When DICOM Cine Module metadata is present, AdvaView attempts to playback the series using the defined frames-per-second (FPS) value.

If Cine metadata is not present, playback defaults to:

  • 30 FPS

Playback indicators may display:

  • Current FPS
  • Target FPS
  • Dropped frame indicators
Performance Note

If workstation or browser performance limitations prevent the requested playback frame rate, playback performance indicators will reflect the actual displayed FPS.


Third-Party Software Requirements

Antivirus Protection​

Client side Endpoint protection or equivalent security controls should be implemented to protect viewer infrastructure from malware and malicious software.


Network Requirements

Network Redundancy​

Healthcare organizations are responsible for implementing:

  • Network redundancy
  • Disaster recovery workflows
  • Downtime procedures
  • Alternate image review workflows

Regulatory Requirements

United States​

Federal law restricts this device to sale by or on the order of a licensed physician or qualified healthcare practitioner.

Organizations outside the United States are responsible for complying with their applicable regional regulations.


Compatibility Requirements

Hardware Requirements​

The workstation environment must meet the minimum supported hardware specifications defined for AdvaView deployments.


Environment Requirements

AdvaView must operate within environments meeting supported:

  • Hardware specifications
  • Browser requirements
  • Network performance requirements
  • Graphics requirements

Software Updates

Organizations should maintain current supported software versions and security updates fora all Client devices utilizing AdvaView.

Software updates are important for:

  • Cybersecurity
  • Stability
  • Compatibility
  • Performance
  • Regulatory compliance

Workstation Configuration Requirements

Desktop Resolution​

Monitors should operate at their native resolution.

Example:

  • A 5MP monitor should operate at full 5MP native resolution.

Display configuration should support clinically appropriate image presentation standards.


Desktop Scaling​

Operating system desktop scaling should not be applied on diagnostic imaging displays.

Diagnostic Display Requirement

Display scaling may negatively affect image presentation accuracy and measurement precision.


Display Bit Depth​

Display bit depth should be configured to:

  • Minimum 32-bit color
  • Or 8-bit grayscale

Graphics Card Configuration​

Browsers should be configured to use the intended high-performance graphics hardware when available.


Browser Zoom​

Browser zoom must be set to:

  • 100%

Hardware Acceleration​

Browser hardware acceleration should remain enabled for optimal viewer performance.