SAP vs Unomed Cloud PACS

Confronta SAP e Unomed Cloud PACS su capacità, giurisdizione, garanzie e idoneità per acquirenti europei.

Entrambi elencati come alternative a: Microsoft Azure

SAP

Germany· Cloud Computing

Needs review

Shortlist SAP when you need S/4HANA-class ERP breadth under a German parent entity and can fund a structured implementation. Skip when you want lightweight self-serve finance SaaS without a transformation partner. Consider Salesforce when CRM is the system of record, or a Microsoft Dynamics / Azure-centric stack when identity and productivity are already standardised on Microsoft.

EU-operatedFull ERP suiteS/4HANA CloudISO 27001 (claimed)B2B DPA published

Vedi scheda Visita il sito web

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

Vedi scheda Visita il sito web

Le righe evidenziate differiscono tra i due prodotti.

SAP vs Unomed Cloud PACS: Sintesi
Caratteristica	SAP	Unomed Cloud PACS
Paese di origine	Germany	Switzerland
Categoria	Cloud Computing	Cloud Computing
Open source	No	No
Self-hosted	Sì	No
Sede	Germany	Switzerland
Soggetto giuridico	SAP SE, Dietmar-Hopp-Allee 16, 69190 Walldorf (Mannheim HRB 719915)	Unomed AG
Legge applicabile	German entity; order forms may name local SAP affiliates	Non indicato
Capogruppo / controllo USA	Nessuna capogruppo USA nota	Nessuna capogruppo USA nota
Esposizione CLOUD Act (indicativa)	Medio	Medio
Stato di hosting UE	Parziale	Parziale
Hosting / residenza	Mixed: SAP-operated data centers (including Walldorf / St. Leon-Rot, Germany) plus Enterprise Cloud Services documented on AWS, Microsoft Azure, Google Cloud Platform, or customer data centers. Product-specific subprocessor lists are primarily on My Trust Center for customers.	Vendor 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.
Riassunto	German-headquartered enterprise ERP suite (SAP Cloud ERP / S/4HANA) for finance, supply chain, procurement, and HR.	Swiss cloud PACS and vendor-neutral archive for storing, viewing and sharing DICOM medical images in the browser, integrated with existing medical practice workflows.
Tag	erp enterprise s4hana gdpr cloud	pacs dicom medical-imaging healthcare cloud-pacs switzerland vna

A colpo d'occhio: SAP vs Unomed Cloud PACS
A colpo d'occhio	SAP	Unomed Cloud PACS
HQ	Walldorf, Germany	Zurich, Switzerland
Legal entity	SAP SE (HRB 719915 Mannheim)	Unomed AG (CHE-374.858.885)
Product focus	Cloud ERP / S/4HANA	Non indicato
Commercial model	Enterprise subscription and licences (quote-based)	Non indicato
Open source	No	Non indicato
Product type	Non indicato	Cloud PACS / VNA SaaS
Self-hosted	Non indicato	No (local connector only)
Default viewer	Non indicato	OHIF (not for diagnosis per GTCs)
Data residency regions	Customer-selectable; Americas, Europe, Asia Pacific (incl. SAP DE sites and hyperscalers)	Switzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy
Compliance certs (claimed)	ISO 27001, SOC 1/2, BSI C5, plus regional attestations via Trust Center	Non indicato

Key capabilities: SAP vs Unomed Cloud PACS
Key capabilities	SAP	Unomed Cloud PACS
EU-operated	Sì	Sì
Full ERP suite	Sì	Non indicato
S/4HANA Cloud	Sì	Non indicato
ISO 27001 (claimed)	Sì	Non indicato
B2B DPA published	Sì	Non indicato
Cloud PACS / VNA	Non indicato	Sì
DICOM archive	Non indicato	Sì
Browser viewer	Non indicato	Sì
PIS overlay	Non indicato	Sì

SAP

SAP S/4HANA Cloud ERP core
Public and private cloud editions cover finance, supply chain, procurement, sales, and related processes on an in-memory data model with role-based UX. Scope and extensibility differ between Public Edition (standardised) and Private Edition (closer to classic on-premises flexibility).
GROW and RISE packaging
SAP GROW targets organisations starting on standardised AI-enabled cloud ERP. RISE with SAP supports existing on-premises customers migrating toward cloud with transformation services. Packaging choice drives implementation shape more than feature marketing slides.
Integration via SAP BTP
SAP Business Technology Platform and Integration Suite provide APIs, iPaaS connectivity, and extension points to link SAP ERP with third-party and legacy systems. Expect integration projects rather than plug-and-play SMB connectors.
Selectable cloud regions and sovereign options
Customers can choose data center regions; SAP documents Americas, Europe, and Asia Pacific availability, including SAP-operated German sites and hyperscaler regions. Sovereign / regulated options (for example German IT-Grundschutz messaging for SAP-owned facilities) exist but must be contracted explicitly.
Trust Center compliance artifacts
SAP publishes ISO 27001, SOC, C5, and other certificates plus DPAs through the Trust Center and customer portals. Audit reports for specific services are often gated to customers rather than fully public PDFs.

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: SAP vs Unomed Cloud PACS
Assurance & compliance	SAP	Unomed Cloud PACS
Independent security / no-logs audit	Not applicable ERP suite; not a no-logs privacy network product. Rely on SOC/ISO/C5 attestations instead.	Not found No public independent security audit report located on unomed.ch.
ISO 27001	Vendor claimed Trust Center lists ISO 27001 certificates for cloud services and publishes certificate finder entries (e.g. Central / Enterprise Cloud Services).	Not found No ISO 27001 certificate or registry entry found on the official site.
SOC 2 / SOC 3	Vendor claimed SOC 1 and SOC 2 reports described on Trust Center; many reports customer-gated via SAP for Me / My Trust Center.	Not found No SOC 2/3 report referenced on public pages reviewed.
GDPR / EU data protection	Vendor claimed EU parent entity; Trust Center privacy pages and DPAs reference GDPR processing terms.	Vendor claimed Swiss FADP (DSG) primary; privacy policy also cites GDPR bases. Confirm DPA/ABV for your use case.
US CLOUD Act exposure (indicative)	Partial German SAP SE parent with no known US parent, but Enterprise Cloud Services explicitly include AWS, Azure, and GCP paths. Medium exposure for hyperscaler-backed tenants. Not legal advice.	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)	Vendor claimed SAP states it signs DPAs; Trust Center hosts Data Processing Agreement documents for cloud, support, and professional services.	Vendor claimed GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider.
BSI C5	Vendor claimed Trust Center lists Cloud Computing Compliance Controls Catalogue (C5) audit reports among EU regional offerings.	Non indicato
EU AI Act	Partial SAP publishes EU AI Act governance materials for Joule Agents and AI features; customer still must assess in-scope AI uses.	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 certification	Non indicato	Partial Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional.

Considerations & known limitations: SAP vs Unomed Cloud PACS
Considerations & known limitations	SAP	Unomed Cloud PACS
Hyperscaler hosting is common	Medium Even with a German parent, many cloud tenants run on AWS, Azure, or GCP. EU region selection does not remove US-group infrastructure operators from the path. Confirm contracted region and subprocessors.	Non indicato
Heavy implementation programmes	Medium S/4HANA and RISE projects typically need partners, data migration, and process redesign. Poor fit if you expected self-serve SaaS onboarding.	Non indicato
Detailed subprocessor lists often customer-gated	Low Public pages confirm lists exist on My Trust Center, but a full anonymous dump was not available in this research pass. Request the list for your exact cloud service before security sign-off.	Non indicato
Catalog category is Cloud Computing, not ERP	Low EuropeanStack has no dedicated ERP category yet. This entry is filed under Cloud Computing as the closest existing slug.	Non indicato
US-group cloud components in the data path	Non indicato	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 diagnosis	Non indicato	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 audit	Non indicato	Medium Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates.
Subprocessor list not published	Non indicato	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.

Idoneità

SAP

Best fit when

Midsize to large enterprises consolidating finance, supply chain, and procurement on one ERP
Organisations that need deep industry process templates and multi-country localisation
Buyers that require a German / EU parent contracting entity plus formal Trust Center attestations
Existing SAP ECC customers planning a RISE or S/4HANA transformation
Teams with budget for partner-led implementation rather than pure self-serve SaaS

Poor fit when

Startups or SMBs needing only simple invoicing without ERP programme overhead
Buyers that require a guaranteed EU-only, non-hyperscaler hosting path without reading the contract region
Teams seeking an open-source ERP they can fork and fully self-operate without vendor lock-in
CRM-first organisations where Salesforce-class customer platforms are the real system of record

Consider instead when

When: Your primary system of record is CRM and revenue operations, not manufacturing or complex finance
Consider: Salesforce
Stronger CRM depth; US parent and different compliance posture.
When: You already standardise on Microsoft identity, M365, and Azure and want ERP in that estate
Consider: Microsoft 365 / Azure-centric Dynamics stacks
Compare total cost of identity + productivity + ERP under one US vendor.
When: You need a smaller European mid-market ERP without S/4HANA transformation scope
Consider: Evaluate EU mid-market ERP vendors outside this catalog (no peer ERP slug listed yet)
Catalog currently lacks a direct European ERP alternative entry.

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

SAP

Which exact cloud service and region would this buyer contract (Public Edition vs Private Edition vs RISE on which hyperscaler)?
Will the order form be with SAP SE or a local affiliate, and which governing law clause applies?
Can the vendor provide the current subprocessor list and SOC/C5 reports for the specific service code without an existing customer login?

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?