ORT Solutions

Cloud-Based PACS, Suite, Hub.

One deployment converges your DICOM archive, viewer, radiology workflow, and multi-site oversight — instead of stitching four vendors together yourself.

See how it converges

Deployed and running in under fifteen minutes.

Built For Every Screen

Read on whatever's in your hand.

The same reading workflow, full fidelity, on a workstation, a tablet, or a phone — no degraded experience just because the screen got smaller.

The Principle

Convergence, not integration.

WHY IT'S DIFFERENT

Most radiology IT stacks are assembled after the fact: a DICOM server from one vendor, a viewer from another, a reporting system bolted on by whoever was available. Every added piece is another point of failure and another support contract to chase when something breaks.

ORT Solutions starts from the deployment, not the integration. The DICOM archive, the viewer, the reading workflow, and fleet oversight ship and version together, as one system, on infrastructure you control.

What Ships Together

Three systems. One platform.

Each one runs standalone in the same deployment — no separate contracts, no separate logins to keep track of.

PACS

Archive & viewer

A full Orthanc DICOM server paired with the OHIF viewer. Every modality in your building sends studies straight to it — C-STORE, C-FIND, C-MOVE, and WADO, all supported out of the box.

SUITE

Reading & reporting

The radiology workflow layer: worklist, reading modes built for throughput, custom PDF report templates, e-signatures, and role-based access for admins, radiologists, technicians, and viewers.

HUB

Fleet oversight

One dashboard across every site you run. See modality throughput, pending studies, and system health for each location without logging into each server separately.

What It's Built On

Open engine, open viewer. No black box.

The DICOM server and the viewer aren't ours to lock you into — they're open-source, field-proven, and the reason there's no format lock-in anywhere in this stack.

Orthanc — The DICOM Engine

Open Source, Vendor-Neutral
The same open DICOM engine trusted by hospital archives running at multi-terabyte scale — not a proprietary format trap.
DICOMweb-Native
Modern, web-standard DICOM transport, built in from the ground up — not bolted on after the fact.
Actively Maintained
A large open-source community drives continuous hardening — not a single vendor's roadmap and renewal cycle.

OHIF — The Viewer

Zero Footprint, 100% Browser
Opens directly in a browser tab on any device — nothing to install, license, or push out fleet-wide.
No Per-Seat Licensing
Open source means no viewer license negotiation, ever — for one radiologist or a hundred.
Tuned To The Workflow
Because it's open, it's shaped around how our radiologists actually read — not a rigid off-the-shelf shell we had to work around.

Orthanc is used under its GPLv3+ / AGPLv3+ open-source license (© University Hospital of Liège, Osimis S.A., Orthanc Team SRL, UCLouvain) and OHIF Viewer under the MIT license (© Open Health Imaging Foundation) — both unmodified, exactly as published.

What It Becomes

One workflow. Every center.

The engine and the viewer become a full radiology department in Suite — and a fleet of them in Hub.

The Suite

One Workflow, Start To Finish
RIS and PACS converged into a single system — worklist, viewing, and reporting in one place, one login.
Every View Logged
Structured reporting and a PHI access audit trail ship together — not an add-on someone has to remember to enable.
Built For Desktop & Mobile
The same reading workflow, full fidelity, on a workstation or a phone.

The Hub

Every Center, One View
One login for radiologists reading across every center a group runs, one dashboard for owners overseeing all of them.
Read Without Switching Systems
A Hub instance embeds each Suite instance directly — no second login, no separate tool to check.
Scales With You
One clinic today, a multi-center hospital group tomorrow — same platform either way.
Inside Suite

Built for the read, not just the archive.

Every row here shipped because a radiologist asked for it, not because a feature list needed filling.

OHIF Viewer
Full diagnostic-grade DICOM viewing built into the workflow itself — no separate viewer license, no second login.
Reading Modes
Distinct desktop and mobile reading layouts, so a radiologist can read from a workstation or a phone without a degraded experience.
Quick Normal
One tap finalizes a normal study straight from the viewer toolbar — built after radiologists asked to stop opening a side panel for the highest-volume study type.
Study Auto-Link
Matches incoming DICOM studies to the right worklist entry by name, date of birth, and institution — deliberately not Patient ID, which imaging-center consoles assign inconsistently. A manual fallback catches anything auto-link can't resolve, so nothing sits unmatched.
PDF Reports
Structured, templated report output — consistent formatting every time, no manual cleanup before it goes out.
Image Print
Key DICOM images embedded as report pages, with patient name and exam date burned directly into the pixels — no mismatch risk after export.
Filters & Custom Fields
Status and date-range filtering for fast triage on high-volume days, plus configurable structured fields that adapt to a practice's own reporting conventions — no code change required.
Role Restrictions
Per-role login IP confinement — a real access-control lever for hospital IT and compliance-conscious buyers, not just a login screen.
PHI Access Audit Trail
Every view of a study or report is logged — not just logins. When a compliance reviewer asks who looked at a record and when, there's a real answer.
Protocol Support

Speaks DICOM natively.

No middleware, no translation layer — your modalities connect directly.

C-STORE
Receive images from modalities
C-FIND
Query for patients and studies
C-MOVE
Retrieve images to workstations
WADO
Web access to DICOM objects
REST API
Custom integrations with your existing tools
Referring & Care Team Access

One link, not one more login.

Hub is the lightweight companion for people who need to check on a study, not read it — referring physicians, care coordinators, front-desk staff.

Installable, Not Downloaded
Added to a phone or desktop home screen like a native app — no app-store distribution, no update prompts to manage.
Role-Aware From First Login
Admins land on Study Management, viewers land on the Viewer, radiologists get their own routing — nobody sees a screen built for someone else's job.
Modality Dashboard
A live breakdown of studies by modality and priority, so a referring physician can see volume and urgency at a glance, not just a list.
Cross-Cloud By Design
A Hub instance embeds a Suite instance the same way whether that Suite runs on the Global Fleet or a Local Zone deployment — the backend differs by region, the experience doesn't.
Every Center, One Login
A radiologist group running multiple centers gets one login across every one of them, and owners get a supervisory view of every center's activity at a glance — one clinic today, a multi-center group tomorrow, same platform either way.
Administration & Fleet

What runs when you're not looking at it.

Every customer gets a fully isolated instance — Portal is how we operate a fleet of them without operating on any one of them by hand.

Dedicated Instance Per Customer
Its own VM, its own database. No customer's data ever shares a database with another's.
Managed Release Pipeline
Versioned, fleet-wide rollout with canary/fallback pinning — an update that regresses gets caught and reverted automatically, not discovered by a customer.
Elastic Sizing
Instance and storage resize after deployment as a customer's study volume grows, without a migration.
Cold Archive, On Request
Hot/cold tiering of DICOM and PDF data to object storage, for customers who want to control on-instance storage growth over time. Proven in production, not a blanket default — so storage cost stays predictable for everyone else.
Configurable Retention
Auto-purge windows for DICOM data, set per customer's own policy, not ours.
Monitoring & Reliability

How we know before you do.

Most vendors can't answer "how do you know if something breaks?" We can, in one dashboard.

System Check
A standing, multi-dimensional health audit of every instance in the fleet: service uptime, backup validity, disk and storage, RAM and load, open ports, security posture, database health, version drift, DICOM traffic.
Portal Health Monitor
A dedicated check on the management layer itself, not just the customer instances it manages.
Automated Alerting
A recurring correlation job surfaces issues fleet-wide with the actual remediation step attached, not just a red dot.
Deliberate Version Pinning
The imaging engine is pinned to a known-stable version fleet-wide, by policy — predictability over bleeding-edge.
Security & Compliance

Isolation is the whole strategy.

No shared database, no shared blast radius. Everything below is standard on every deployment, not an upgrade tier.

Encrypted Credentials At Rest
Sensitive secrets are encrypted (Fernet, per-instance key derivation) across both clouds.
SSH Hardening & Intrusion Prevention
Fail2ban and a hardened SSH configuration ship with every deployment automatically — not a step someone can forget.
HTTPS Everywhere
HSTS enforced, with a locked-down Content-Security-Policy — no open wildcard framing.
Role-Based IP Restriction
Confine specific roles to specific network locations — a real lever for hospital IT and compliance reviewers.
In-Country Data Residency
The Local Zone deployment path keeps data inside the Philippines, for government and public-health facilities that require it.
Designed With HIPAA-Aligned Controls
Encryption, access restriction, audit-relevant logging, and tenant isolation are built into every layer of the platform.
Deployment Options

Same platform. Two places to run it.

Global Fleet

Best For
Clinics and hospitals anywhere, fastest to provision
Current Scale
12 live customer instances
Codebase
Same unified Suite/Hub codebase as the Local Zone deployment

Local Zone (Philippines)

Best For
Philippine government and public-sector facilities with in-country data residency requirements
Current Scale
1 live customer instance — pilot-proven, ready to scale
Codebase
Same unified Suite/Hub codebase as the Global Fleet deployment
Built For

Running in production across the Philippines.

Deployed by hospitals, diagnostic imaging centers, teleradiology services, and medical research groups — each running SSL-secured, DICOM-compliant infrastructure with 24/7 uptime.

Independent Clinics
Fast setup, no vendor lock-in, mobile-friendly reading and referring workflows.
Hospitals & Health Systems
Isolated per-tenant architecture, role-based access control, fleet monitoring with proactive alerting.
Government & Public Health
In-country data residency via our Local Zone deployment, hardening baked into provisioning, HIPAA-aligned controls.
Resellers & Partners
One codebase, automated provisioning — onboarding a new customer doesn't need bespoke engineering per deal.
Track Record

Continuous hardening, not a one-time build.

303
SUITE RELEASES
SINCE V1.0
44
HUB RELEASES
SINCE V1.0
13
LIVE DEPLOYMENTS
ACROSS 2 CLOUDS
0
CUSTOMERS SHARING
A DATABASE
99%
UPTIME
ACROSS THE FLEET

Ready to converge your stack?

Tell us about your setup and we'll reach out to plan your deployment.