Skip to content
LynxMediq

Cloud PACS

Shipping in PixelMediq

Cloud PACS: the first LynxMediq portfolio area to ship

The archive and the viewer are where the LynxMediq direction starts, and they are available now in PixelMediq. This page summarises what ships and what the portfolio still plans to add. The product detail lives on pixelmediq.com.

Shipping in PixelMediq

Available today

From the modality port to the read

A summary of what PixelMediq publishes as available for the archive and viewer. PixelMediq also states what it does not do, which is worth reading before you plan around it.

Edge gateway ingestion

An on-premise gateway receives studies from the modalities over DICOM C-STORE, answers C-ECHO, and accepts DICOMweb STOW-RS.

Zero-footprint viewer

Read in the browser with no client to install. The viewer reads from the local gateway on site and from the cloud off it.

DICOMweb access

QIDO-RS, WADO-RS, and STOW-RS expose the archive to viewers and third-party systems over standard web APIs.

Stored as sent

Objects are archived as the modality sent them and identified by content hash. Previews and derived frames sit beside the original.

Prior study context

Relevant priors are presented alongside the current study during a read, with hanging protocols published per department.

Optional de-identification

Off by default and configured per gateway or upload, for teaching and research use.

Shipping in PixelMediq

Storage and archive options

The archive is separate from the storage underneath it

PixelMediq abstracts storage across the backends below, which is what lets the same software run cloud-first, fully on-premise, or hybrid.

Local disk

Keep studies on local storage for a fully on-premise deployment.

Network disk / NAS

Use existing NAS capacity for shared on-premise archival.

S3-compatible object storage

Amazon S3 or any compatible object store for durable long-term archival.

AWS HealthImaging

A managed AWS store built for medical imaging, for cloud-first deployments.

Archive credentials are managed per tenant, and an archive and purge lifecycle governs retention. Studies stay reachable through the same DICOMweb interface wherever they live.

Current product

PixelMediq

The full archive and viewer detail, including the DICOM conformance statement and the transfer syntax matrix, is published on pixelmediq.com.

You buy, deploy, and run PixelMediq. LynxMediq is the portfolio it belongs to, and there is no second product to purchase alongside it.

Roadmap

Portfolio direction

What the portfolio plans to add around the archive

These are planned direction for LynxMediq. They are not available in PixelMediq today, and sequencing can change.

  • Secure, expiring share links for referrers and patients
  • Study routing rules by modality, site, and body part
  • Compression and storage tiering policies you control
  • AI findings overlaid on the image as DICOM SR, SEG, and presentation states
  • Cardiology imaging in the same archive

Evaluate the archive against your own modalities

PixelMediq is the product to test. For questions about where the LynxMediq archive direction goes next, talk to us.