High Availability Ready
Deploy redundant application instances and supporting services for resilient production environments.
MedPACS™ is an enterprise-grade PACS Server for secure DICOM ingestion, storage, routing, query/retrieve, and DICOMweb access. Built for hospitals, diagnostic networks, teleradiology providers, and healthcare technology platforms, MedPACS™ can run on-premise, in the cloud, or in hybrid environments without locking your organization into a proprietary viewer.
Designed for the core PACS responsibilities enterprises care about: interoperability, resilience, scalability, storage control, security, routing, and operational visibility.
Deploy redundant application instances and supporting services for resilient production environments.
Scale ingestion, query, routing, and application services as imaging volumes and users grow.
Use standards-based DICOM and DICOMweb integration without tying the archive to one viewer or modality vendor.
Support hospitals, branches, imaging centers, and remote radiology networks through centralized or distributed deployments.
Monitor ingestion, routing, storage, queue health, connectivity, failures, and application status.
Support encrypted transport, controlled application access, network isolation, and auditable operations.
Expose imaging workflows to viewers, RIS, AI applications, portals, and enterprise integration services.
Deploy with Docker or orchestration platforms across public cloud, private cloud, on-premise, or hybrid environments.
Connect modalities, viewers, RIS, AI services, external PACS, and enterprise archives using established imaging protocols and web-native access patterns.
Receive imaging studies from compatible modalities, gateways, PACS nodes, and external DICOM systems.
Support standards-based study discovery and retrieval workflows across connected imaging systems.
Use C-ECHO connectivity checks for node validation and operational troubleshooting.
Enable modern browser, application, and API access patterns using web-native imaging interfaces.
Query studies, series, and instances from compatible DICOMweb clients and applications.
Retrieve DICOM objects and imaging content for zero-footprint viewers and downstream services.
Support web-based ingestion of DICOM objects from compatible applications and services.
Route studies or objects to downstream destinations based on defined enterprise workflow rules.
Keep PACS services independent from the underlying object storage strategy so your archive can evolve with performance, retention, and cost requirements.
DICOM modalities, gateways, external PACS, upload services, and imaging applications.
Validate, index, organize, route, and expose imaging studies through enterprise services.
Use local object storage, enterprise object platforms, or cloud object storage according to deployment needs.
Design archive storage around scalable object storage instead of relying only on local file systems.
Align imaging retention with clinical, operational, contractual, and regulatory requirements.
Use hot, cool, or archive tiers where supported by your storage platform to balance access and cost.
Integrate infrastructure backup, replication, and disaster recovery strategies around your enterprise archive.
MedPACS™ can operate independently of the viewer and integrate with clinical, operational, AI, and imaging applications across your organization.
Modalities, DICOM gateways, external PACS, upload tools, and partner imaging systems.
Centralize imaging ingestion, storage coordination, indexing, routing, query, retrieval, and DICOMweb access.
Viewer, RIS, AI, teleradiology, patient portal, VNA, analytics, and third-party applications.
Connect study lifecycle and operational context with scheduling, worklist, reporting, and workflow systems.
Serve studies to zero-footprint diagnostic viewers through DICOMweb and standards-based interfaces.
Expose imaging studies to compatible AI pipelines and receive downstream results into enterprise workflows.
Integrate metadata, study status, workflow operations, and supporting services into surrounding applications.
Trigger downstream workflows when studies are received, processed, routed, or changed.
Connect with enterprise archives, partner PACS systems, and downstream DICOM destinations.
Separate ingestion, API, indexing, routing, and storage responsibilities so services can scale according to workload.
Multiple hospitals, centers, modalities, gateways, and remote locations.
Deploy multiple application instances behind enterprise load balancing and orchestration layers.
Scale storage capacity and downstream applications independently from ingestion services.
Distribute API and service traffic across multiple instances.
Support orchestrated deployment patterns such as Kubernetes where required.
Use background processing and queue-based patterns for long-running or high-volume imaging tasks.
Integrate service health checks and operational telemetry into infrastructure monitoring workflows.
Install MedPACS™ alongside your existing modalities, storage, viewer, RIS, and enterprise integration services.
Run PACS services using containerized infrastructure.
Set AE Titles, ports, storage, routing, access, and environment-specific configuration.
Register modalities, viewers, RIS, gateways, PACS nodes, and DICOMweb consumers.
Configure network controls, identity, encryption, secrets, and audit policies.
Monitor ingestion, storage, routing, service health, and production workloads.
services:
medpacs-api:
image: <your-registry>/medpacs-api:<version>
environment:
- DATABASE_URL=<database-connection>
- OBJECT_STORAGE_ENDPOINT=<storage-endpoint>
- AUTHORITY_URL=<identity-provider>
medpacs-dicom-service:
image: <your-registry>/medpacs-dicom-service:<version>
ports:
- "11112:11112"
medpacs-dicomweb-service:
image: <your-registry>/medpacs-dicomweb-service:<version>
ports:
- "8080:80"Example only. Production service names, image names, ports, environment variables, topology, and deployment instructions should be provided in the official MedPACS™ deployment package.
Deploy according to clinical, networking, performance, data residency, and IT governance requirements.
Run PACS services with cloud compute, managed databases, object storage, and enterprise networking.
Deploy into organization-controlled infrastructure with isolated networking and storage.
Operate close to modalities and local imaging infrastructure inside hospitals or diagnostic centers.
Combine local DICOM services and storage with centralized cloud applications or archives.
Use standardized deployment and observability patterns to run imaging infrastructure consistently across development, UAT, and production.
Package PACS services consistently across environments.
Manage storage, DICOM nodes, routing, authentication, and environment configuration outside application binaries.
Integrate logs, metrics, tracing, and health checks into enterprise monitoring platforms.
Capture operational events, errors, connectivity issues, and service activity for troubleshooting.
Use versioned container releases and controlled rollout strategies for production upgrades.
Fit PACS services into your backup, replication, recovery, and business continuity architecture.
Designed to work within enterprise network, identity, audit, encryption, and operational governance controls.
Deploy behind enterprise firewalls, private networks, VPNs, or other approved network boundaries.
Protect web APIs, DICOMweb, and application communications using encrypted channels where supported.
Keep database, storage, certificates, and service credentials outside application source code.
Support operational traceability across ingestion, routing, access, and system activity.
PACS vendors, healthcare software companies, and imaging technology providers can use MedPACS™ as the DICOM and archive engine behind their own products.
Talk to the RadpicsAI team about
standalone PACS deployment, DICOM integration,
storage architecture, multi-site rollout,
Docker/Kubernetes deployment, APIs,
and OEM integration.