BeamIt Health DICOM Conformance Statement

1. Introduction

This DICOM Conformance Statement applies to the BeamIt Health medical image sharing platform. BeamIt provides cloud-hosted DICOM storage, retrieval, and sharing services accessible via DICOMweb RESTful APIs and traditional DICOM network services.

2. Table of Contents

1. Introduction
2. Table of Contents
3. Networking
4. Supported SOP Classes
5. Supported Transfer Syntaxes
6. DICOMweb Services
7. Security
8. Character Sets
9. Configuration
10. Support

3. Networking

3.1 Implementation Model

BeamIt operates as a cloud-based DICOM Service Class Provider (SCP) and Service Class User (SCU). The primary integration method is via DICOMweb RESTful APIs. Traditional DICOM networking (C-STORE) is available for on-premise PACS integration via a secure gateway.

3.2 AE Titles

3.3 Network Services

4. Supported SOP Classes

4.1 Storage SOP Classes (SCP)

4.2 Query/Retrieve SOP Classes

5. Supported Transfer Syntaxes

6. DICOMweb Services

BeamIt implements DICOMweb (DICOM PS3.18) as the primary integration method. All DICOMweb endpoints require authentication via Bearer token or API key.

6.1 QIDO-RS (Query)

Supports all standard QIDO-RS query parameters including PatientName, StudyDate, ModalitiesInStudy, AccessionNumber, and StudyInstanceUID.

6.2 WADO-RS (Retrieve)

Supports Accept headers: application/dicom, multipart/related, and application/dicom+json for metadata.

6.3 STOW-RS (Store)

Accepts multipart/related content with application/dicom parts. Maximum instance size: 500 MB.

7. Security

7.1 Transport Security

• All communications encrypted with TLS 1.2 or higher
• TLS 1.3 preferred when supported by client
• Strong cipher suites only (AES-256-GCM, ChaCha20-Poly1305)
• HSTS enforced with 1-year max-age

7.2 Authentication

• OAuth 2.0 with PKCE for user-context integrations
• API key authentication for server-to-server communication
• JWT tokens with configurable expiration
• Multi-factor authentication available for admin accounts

7.3 Data at Rest

• AES-256 encryption for all stored DICOM data
• Google Cloud KMS for key management
• Automatic key rotation
• Separate encryption keys per tenant (enterprise)

7.4 Audit Logging

• All DICOM operations logged with timestamp, user, IP, and action
• Audit logs retained for minimum 6 years (HIPAA requirement)
• Immutable audit trail — logs cannot be modified or deleted
• Export capability for compliance audits

8. Character Sets

UTF-8 (ISO_IR 192) is the recommended character set for all new integrations. BeamIt handles character set conversion automatically when displaying data in the viewer.

9. Configuration

BeamIt is a cloud SaaS platform. The following parameters are configurable per integration:

• AE Title: Custom AE Title for your institution's DICOM gateway
• Accepted SOP Classes: Configurable per integration to restrict accepted modalities
• Maximum Instance Size: Default 500 MB, configurable up to 2 GB
• Retention Period: Configurable data retention (default: indefinite)
• Auto-routing Rules: Automatic forwarding based on modality, institution, or custom tags
• Webhook Endpoints: Custom notification URLs for DICOM events

10. Support