Unomed Cloud PACS vs UpCloud

Comparez Unomed Cloud PACS et UpCloud sur les capacités, la juridiction, les garanties et l'adéquation pour les acheteurs européens.

Tous deux listés comme alternatives à: Amazon Web Services (AWS), Microsoft Azure

Logo: Unomed Cloud PACS

Unomed Cloud PACS

Switzerland· Cloud Computing

Needs review

Shortlist for Swiss practices that want a cloud DICOM archive, browser viewing and referrer sharing without replacing their PIS, and that accept a Zurich SaaS vendor with claimed Swiss image hosting. Skip when you need a default CE-marked diagnostic viewer, a fully public subprocessor and audit pack, or a self-hosted PACS you operate yourself. Consider PostDICOM or a classic on-prem PACS plus sharing tool when those constraints dominate.

Swiss-operatedCloud PACS / VNADICOM archiveBrowser viewerPIS overlay
Voir la ficheVisiter le site web

Les lignes surlignées diffèrent entre les deux produits.

Unomed Cloud PACS vs UpCloud: Aperçu
CaractéristiqueLogo: Unomed Cloud PACSUnomed Cloud PACSLogo: UpCloudUpCloud
Pays d'origineSwitzerlandFinland
CatégorieCloud ComputingCloud Computing
Open sourceNonNon
Auto-hébergéNonNon
SiègeSwitzerlandNon indiqué
Entité légaleUnomed AGNon indiqué
Maison mère / contrôle USAucune maison mère US connueNon indiqué
Exposition CLOUD Act (indicative)MoyenNon indiqué
Statut d'hébergement dans l'UEPartielNon indiqué
Hébergement / résidenceVendor claims primary hosting, databases and DICOM storage in Switzerland. Privacy policy lists identity/liveness processing in EU (Ireland) and speech recognition in EU (Denmark). API CSP references AWS S3 eu-central-2 (Zurich) and AWS Rekognition/Cognito eu-west-1; push via Firebase; website may use Cloudflare WAF cookies and Google Analytics. Named subprocessor list on request only.Non indiqué
Résumé

Swiss cloud PACS and vendor-neutral archive for storing, viewing and sharing DICOM medical images in the browser, integrated with existing medical practice workflows.

Finnish IaaS from UpCloud Oy (Helsinki): MaxIOPS block storage, Cloud Servers, managed Kubernetes and databases across 15 global regions with customer-selected residency.

Tags
pacsdicommedical-imaginghealthcarecloud-pacsswitzerlandvna
cloudiaasinfrastructurekubernetesgdprapifinlandmanaged-databases
En un coup d'œil: Unomed Cloud PACS vs UpCloud
En un coup d'œilLogo: Unomed Cloud PACSUnomed Cloud PACSLogo: UpCloudUpCloud
HQZurich, SwitzerlandNon indiqué
Legal entityUnomed AG (CHE-374.858.885)Non indiqué
Product typeCloud PACS / VNA SaaSNon indiqué
Self-hostedNo (local connector only)Non indiqué
Default viewerOHIF (not for diagnosis per GTCs)Non indiqué
Data residency regionsSwitzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policyNon indiqué
Key capabilities: Unomed Cloud PACS vs UpCloud
Key capabilitiesLogo: Unomed Cloud PACSUnomed Cloud PACSLogo: UpCloudUpCloud
Swiss-operatedOuiNon indiqué
Cloud PACS / VNAOuiNon indiqué
DICOM archiveOuiNon indiqué
Browser viewerOuiNon indiqué
PIS overlayOuiNon indiqué

Unomed Cloud PACS

  • Cloud DICOM archive (VNA-style)

    Central archive for studies from in-house modalities and external institutes, with DICOM export so you can take the archive with you. Storage is billed as you grow; long-term statutory retention remains the customer's duty under Unomed's terms.

  • Zero-footprint browser viewer (OHIF default)

    Open studies in the browser with nothing installed on the workstation. OHIF is the default; other viewers can be connected on request. Unomed's GTCs state the standard viewer is not authorised for diagnostic reporting.

  • PACS inbox with assisted patient matching

    Inbound studies land in an inbox; Unomed suggests the matching patient (including fuzzy name matches) and a human confirms. Useful when institutes send studies that do not already carry a clean order from your record.

  • Share via messenger and guest links

    Send studies to colleagues, referrers and patients through Unomed messenger. Recipients without an account get a time-limited guest link; registered users keep the thread in case chat instead of CDs or ad-hoc portals.

  • Cloud Connector, Radiology Bridge and Medical API

    Connect DICOM modalities like a second destination printer, autoroute from an existing institute PACS via Radiology Bridge, or integrate via DICOMweb/Medical API. Keeps on-site PACS investments when you only need outbound routing to Unomed practices.

  • Overlay on existing practice software

    Opens studies from the patient record in supported web-based Swiss practice systems without replacing the PIS. Vendor lists 16+ systems with several official partners; desktop-only software needs a feasibility discussion.

UpCloud

  • MaxIOPS Block Storage

    UpCloud's proprietary storage technology delivers up to 100,000 IOPS on read/write operations, verified in benchmarks like those from Cloud Spectator. This enables databases and high-traffic apps to run smoothly without bottlenecks. Storage attaches directly to servers, with snapshots for quick backups. Users benefit from consistent performance across all plans, unlike tiered systems elsewhere.

  • Global Data Centers and Networking

    Choose from 13 locations: eight in Europe (Helsinki, Amsterdam, Frankfurt, London, Madrid, Warsaw, Stockholm, Copenhagen), plus Chicago, New York, San Jose, Singapore, and Sydney. Networking includes free load balancers, VPN gateways, and NAT for private connectivity. No charges apply for ingress or egress traffic, reducing bills for data-heavy workloads.

  • Managed Services and Essentials Package

    Deploy managed PostgreSQL, MySQL, Valkey, or OpenSearch databases with automated scaling and updates. Managed Kubernetes control planes handle etcd and upgrades. The free UpCloud Essentials package bundles daily backups, floating IPs, and basic firewalls at no added cost. API access supports automation for CI/CD pipelines.

Assurance & compliance: Unomed Cloud PACS vs UpCloud
Assurance & complianceLogo: Unomed Cloud PACSUnomed Cloud PACSLogo: UpCloudUpCloud
Independent security / no-logs audit
Not found

No public independent security audit report located on unomed.ch.

Non indiqué
ISO 27001
Not found

No ISO 27001 certificate or registry entry found on the official site.

Non indiqué
SOC 2 / SOC 3
Not found

No SOC 2/3 report referenced on public pages reviewed.

Non indiqué
GDPR / EU data protection
Vendor claimed

Swiss FADP (DSG) primary; privacy policy also cites GDPR bases. Confirm DPA/ABV for your use case.

Non indiqué
US CLOUD Act exposure (indicative)
Partial

Swiss entity / no known US parent, but AWS (S3 Zurich region, Rekognition Ireland) and Firebase appear in public technical/privacy materials. Not legal advice.

Non indiqué
Data processing agreement (B2B)
Vendor claimed

GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider.

Non indiqué
EU AI Act
Not applicable

PACS archive/viewer product; AI is used for assisted patient matching and other suite features, but this entry evaluates the imaging archive, not an AI-centric system.

Non indiqué
Diagnostic viewer certification
Partial

Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional.

Non indiqué
Considerations & known limitations: Unomed Cloud PACS vs UpCloud
Considerations & known limitationsLogo: Unomed Cloud PACSUnomed Cloud PACSLogo: UpCloudUpCloud
US-group cloud components in the data path
Medium

Even with Swiss HQ and claimed Swiss image hosting, AWS and Firebase endpoints appear in public privacy/CSP materials. Procurement should obtain the named subprocessor annex and assess CLOUD Act residual risk.

Non indiqué
Default viewer not for diagnosis
High

If radiologists must report from the included viewer, Unomed alone is the wrong shortlist item unless a certified diagnostic viewer is contracted.

Non indiqué
No public ISO/SOC or independent audit
Medium

Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates.

Non indiqué
Subprocessor list not published
Medium

Privacy policy says processors can be requested at any time but does not name hosting vendors on the page. Blockers for security questionnaires until the annex is shared.

Non indiqué

Adéquation

Unomed Cloud PACS

Best fit when

  • Swiss medical or dental practices that want cloud DICOM archive and sharing without an on-site PACS project
  • Teams that must open imaging from an existing web-based practice system rather than a second patient search
  • Institutes that need to autoroute studies to referring practices while keeping an existing PACS (Radiology Bridge)
  • Buyers who prioritise a Swiss contracting entity and vendor-claimed Swiss image residency under the FADP
  • Workflows that share studies with referrers or patients via links instead of CDs or one-off portals

Poor fit when

  • Organisations that require the included viewer to be a certified diagnostic/reporting workstation out of the box
  • Buyers that need a published named subprocessor list and independent ISO/SOC evidence before first sales call
  • Teams seeking a fully self-hosted open-source PACS they operate themselves
  • Hospitals needing a full RIS/PACS suite beyond practice-oriented cloud archive and sharing

Consider instead when

  • When: You need a European cloud PACS peer outside Switzerland or broader multi-country packaging

    Consider: PostDICOM (Netherlands) or other EU cloud PACS vendors

    Feature parity is not claimed; compare residency contracts and viewer certification directly.

  • When: You primarily need raw cloud object storage or hospital-grade imaging services on a hyperscaler

    Consider: AWS or Azure health/imaging stacks with your own viewer and compliance design

    More infrastructure flexibility; you own more of the clinical workflow glue.

  • When: You must keep all image data on premises under your sole operational control

    Consider: Classic on-prem PACS plus a dedicated sharing portal

    Unomed is cloud SaaS with a local connector, not a self-hosted Unomed server product.

UpCloud

Best fit when

Non indiqué

Poor fit when

Non indiqué

Open questions for due diligence

Unomed Cloud PACS

  • Will Unomed provide the current named subprocessor list (hosting, backup, email, SMS, identity) under NDA or in the ABV annex?
  • Which exact Swiss data-centre operators and certifications cover the DICOM archive?
  • Is a CE-marked / certified diagnostic viewer required for your reporting workflow, and which third-party option will Unomed integrate?
  • What SLA, backup/RPO and export support apply to your Cloud PACS tier?

UpCloud

Non indiqué