Deployment & Security
How Us2.ai is deployed, secured, and integrated for clinical leads, IT committees, procurement officers, and security reviewers.
Predictable Deployment Process
The same four milestones on either path. Cloud needs no hardware procurement, so the milestones can run back to back; on-premise waits for your server. Most of the elapsed time is your own security review and IT scheduling.
Scoping & Assessment
Review infrastructure, DICOM routing, and integration points. Identify cloud or on-premise deployment path.
Installation & Configuration
Deploy Us2.ai server (on-premise) or provision cloud instance. Configure DICOM routing and system connectivity.
Validation & Testing
Run test studies, validate output against your existing workflow, and confirm integration with PACS/CVIS/EMR.
Go Live
Enable production routing. Ongoing monitoring and support. Can be disabled at any time without data migration.
Deployment Options
Choose the deployment model that fits your organization's security and infrastructure requirements.
Minimum Hardware Requirements
Minimum specifications for on-premise deployment. Cloud deployment requires no hardware procurement.
Hosting Regions and Interfaces
The cloud runs on Amazon Web Services. Each site is set up in one region, and its studies and reports stay in that region.
- United States (N. Virginia)
- Canada (Central)
- European Union (Frankfurt)
- India (Mumbai)
- Singapore
- Australia (Sydney)
- Japan (Tokyo)
Where data must not leave the hospital, the on-premise deployment keeps it inside your network.
Interfaces
Security & Compliance
Us2.ai maintains the certifications and compliance standards required for enterprise healthcare deployment.
GDPR & HIPAA
A data processing agreement template for the European Union and United Kingdom, and a business associate agreement for United States customers.
ISO 13485 & ISO 27001:2022
Certified medical-device quality management and information security management systems. Annual audits and continuous monitoring.
SOC 2 Type II
Independently audited security controls for availability, processing integrity, and confidentiality. Report available on request.
MDSAP
Medical Device Single Audit Program: a single audit covering regulatory expectations for the United States, Canada, Brazil, Japan, and Australia.
NHS DSPT & DTAC
Data Security and Protection Toolkit and Digital Technology Assessment Criteria completed for United Kingdom NHS deployments. Cyber Essentials Plus and ICO registration on request.
Regional Data Residency
Cloud data stays in the region the site is set up in, among them Singapore, Australia, Japan, the European Union and the United States. On-premise keeps it inside the hospital.
AES-256 encryption at rest. TLS 1.2+ in transit. Optional customer-managed encryption keys.
Configurable retention policies. Data can be purged on demand. No data is used for model training without explicit consent.
Role-based access control. Audit logging for all system access. SSO integration available.
Cybersecurity Review Scope
Common questions from IT security reviews, answered up front.
Frequently Asked Questions
Common questions about Us2.ai deployment, hosting, and data security.
Where is the Us2.ai cloud hosted?
On Amazon Web Services. Each site is set up in one region, and its data stays there: United States (N. Virginia), Canada (Central), European Union (Frankfurt), India (Mumbai), Singapore, Australia (Sydney), Japan (Tokyo). Where data must stay inside the hospital, deploy on-premise instead.
Does Us2.ai support HL7 and FHIR?
Yes. HL7 v2 carries results out (ORU^R01) and orders and patient updates in (ORM^O01, ADT) over MLLP. Cloud deployments also export each study as a FHIR R4 Bundle, by download, API or outbound webhook. DICOM SR, PDF and DICOMweb are covered in the interfaces table on this page.
Does Us2.ai store patient data?
Configurable. Cloud deployments can process in real-time without persistent storage. On-premise retains data within your facility.
What network ports are required?
LAN: DICOM ports 104/11112 for internal study routing between modalities and the Us2.ai server. WAN: HTTPS 443 for cloud connectivity and management. No inbound internet access required.
Is a VPN required?
Not for cloud. On-premise operates entirely within your LAN. Optional VPN for remote management access.
How are software updates handled?
Cloud: automatic, zero-downtime updates. On-premise: scheduled update packages deployed by your IT team or Us2.ai support.
What happens if Us2.ai goes down?
Your existing workflow continues unaffected. Us2.ai operates as an additive layer: if the service is unavailable, studies route to your normal reporting path.
Can we run a pilot without production risk?
Yes. Parallel processing mode routes studies to Us2.ai while your existing workflow continues. Zero impact to production until you choose to switch.
Security and architecture decisions don't wait for deployment day.
Ready to Start Your Evaluation?
Our team can provide a detailed technical architecture review, compliance documentation, and deployment plan specific to your environment.