OVHcloud vs Unomed Cloud PACS

Vergleichen Sie OVHcloud und Unomed Cloud PACS nach Funktionen, Rechtsraum, Nachweisen und Einsatzpassung.

Beide als Alternativen zu: 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
OVHcloud vs Unomed Cloud PACS: Überblick
MerkmalLogo: OVHcloudOVHcloudLogo: Unomed Cloud PACSUnomed Cloud PACS
HerkunftslandFranceSwitzerland
KategorieCloud ComputingCloud Computing
Open SourceNeinNein
Self-HostedNeinNein
HauptsitzNicht angegebenSwitzerland
RechtsträgerNicht angegebenUnomed AG
US-Mutter / KontrolleNicht angegebenKeine bekannte US-Mutter
CLOUD-Act-Exposition (indikativ)Nicht angegebenMittel
EU-Hosting-StatusNicht angegebenTeilweise
Hosting / ResidenzNicht angegebenVendor 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.
Zusammenfassung

French cloud and infrastructure group (Roubaix): Bare Metal dedicated servers, OpenStack Public Cloud, Hosted Private Cloud (incl. SecNumCloud), and Web Cloud on OVH-operated datacentres across Europe, North America, and Asia-Pacific.

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

Tags
Auf einen Blick: OVHcloud vs Unomed Cloud PACS
Auf einen BlickLogo: OVHcloudOVHcloudLogo: Unomed Cloud PACSUnomed Cloud PACS
HQNicht angegebenZurich, Switzerland
Legal entityNicht angegebenUnomed AG (CHE-374.858.885)
Product typeNicht angegebenCloud PACS / VNA SaaS
Self-hostedNicht angegebenNo (local connector only)
Default viewerNicht angegebenOHIF (not for diagnosis per GTCs)
Data residency regionsNicht angegebenSwitzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy
Key capabilities: OVHcloud vs Unomed Cloud PACS
Key capabilitiesLogo: OVHcloudOVHcloudLogo: Unomed Cloud PACSUnomed Cloud PACS
Swiss-operatedNicht angegebenJa
Cloud PACS / VNANicht angegebenJa
DICOM archiveNicht angegebenJa
Browser viewerNicht angegebenJa
PIS overlayNicht angegebenJa

OVHcloud

  • Anti-DDoS Protection and Vast Network Capacity

    Every OVHcloud service includes unlimited anti-DDoS mitigation, scrubbing attacks across layers 3, 4, and 7 without downtime fees. The global network exceeds 100 Tbit/s, ensuring low latency and high throughput. No charges apply to outbound traffic, unlike some rivals, which helps control costs for data-intensive apps like streaming or backups.

  • Sustainability with Low PUE and Resource Reuse

    OVHcloud reports a power usage effectiveness (PUE) of 1.28 across its facilities, beating industry averages. It uses 7 times less water than peers and runs on 100% low-carbon energy sources. Servers get repurposed for secondary uses before recycling, targeting zero landfill waste by 2025. This approach reduces operational costs passed to customers.

  • OpenStack Public Cloud and Reversibility

    Built on OpenStack, the public cloud supports pay-as-you-go pricing with API access for automation. Private cloud options avoid lock-in through data export tools and standard formats. Customers retain full control, with no data mining for ads. Features like vRack private networking connect services seamlessly across regions.

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.

Assurance & compliance: OVHcloud vs Unomed Cloud PACS
Assurance & complianceLogo: OVHcloudOVHcloudLogo: Unomed Cloud PACSUnomed Cloud PACS
Independent security / no-logs auditNicht angegeben
Not found

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

ISO 27001Nicht angegeben
Not found

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

SOC 2 / SOC 3Nicht angegeben
Not found

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

GDPR / EU data protectionNicht angegeben
Vendor claimed

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

US CLOUD Act exposure (indicative)Nicht angegeben
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.

Data processing agreement (B2B)Nicht angegeben
Vendor claimed

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

EU AI ActNicht angegeben
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.

Diagnostic viewer certificationNicht angegeben
Partial

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

Considerations & known limitations: OVHcloud vs Unomed Cloud PACS
Considerations & known limitationsLogo: OVHcloudOVHcloudLogo: Unomed Cloud PACSUnomed Cloud PACS
US-group cloud components in the data pathNicht angegeben
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.

Default viewer not for diagnosisNicht angegeben
High

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

No public ISO/SOC or independent auditNicht angegeben
Medium

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

Subprocessor list not publishedNicht angegeben
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.

Passung

OVHcloud

Best fit when

Nicht angegeben

Poor fit when

Nicht angegeben

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.

Open questions for due diligence

OVHcloud

Nicht angegeben

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?