RIS · PACS · AI — on-premise or cloud

All of radiology.
In one browser.

From scheduling to reimbursement by CNAS (Romania's national health insurance house): worklist, diagnostic viewer, AI-assisted voice dictation in Romanian, teleradiology, patient portal and billing — one platform, not a single install on any workstation.

0 workstation installsAutomatic CNAS claims — no SIUI desktopAI: dictation · triage · report assistPACS isolated per institution
ZenView — non-contrast head CT 3 series · 84 images
Brain CT slice, brain window IONESCU M. · 58Y · fictitious data W 80 · L 40 · IM 15/28 scroll — slices · drag — contrast · click the series
live series

A real CT study (anonymized), rendered straight from the ZenPACS archive — exactly what it looks like in the browser.

A classic RIS comes with installs on every workstation, hardware dongles, counted licenses and five vendors who don't talk to each other.

ZenRIS comes with one URL.

The life of a study

The phone rings at 08:52.
By 10:13 the report is signed and the claim is ready.

Follow a head CT through ZenRIS — from booking to payment. Every step, one module. All of it, one system.

08:52ZenPlan

Booking

The front desk sees every location, scanner and physician in real time. The patient gets confirmation and prep instructions by SMS — and if an earlier slot opens up, the waiting list offers it on its own.

09:41Modality integration

Acquisition

By appointment time, the patient's details are already on the scanner console, via DICOM worklist. Nobody retypes anything: zero identity errors, zero lost studies.

09:44ZenPACS + ZenFlow

Arrival and triage

Images land in the institution's archive within seconds. Routing does its job on its own: prior studies attach themselves for comparison, and AI moves urgent cases to the top of the list — before anyone even has to ask.

09:52ZenView

Reading

The radiologist opens the study in a tab: MPR, 3D, comparison with prior exams, hanging protocols that arrange the series exactly the way they like. In the browser — at the hospital, or from home, on call.

10:05ZenReport + ZenVoice

Reporting

They speak. The report writes itself, in Romanian, on the department's template. AI structures the text and suggests the conclusion; signing takes one click, and every version stays in the history.

10:13ZenPortal + ZenBill · ZenAgent

Delivery and reimbursement

The patient and the referring physician get a secure link with the images and the report — no CDs, no trips back to the clinic. In the background, the services are already priced, and the CNAS claim goes out automatically: no SIUI (the legacy desktop reporting app), no exports.

Multi-institution · isolation

One platform. Any number of institutions.
Zero data mixing.

ZenRIS is built for clinic chains, hospitals and teleradiology networks. Each institution lives in its own PACS archive, with its own users, templates and billing — not “logically separated” by a filter on a shared database, but separated at the level of architecture.

Clinic A own PACS archive Hospital B own PACS archive Center C own PACS archive ZenRIS one platform, one tenant radiologist pool

Click an institution: only its path lights up. Between institutions there is no path at all — the ✕ isn't decoration.

“Isolation isn't a setting.
It's the architecture.

  • Its own PACS, per institution. One clinic's data has no way to end up in another — they are separate archives, not filtered rows.
  • Pools across boundaries. A radiologist sees exactly the studies assigned to them, from any number of clinics. The clinics never see each other. Ever.
  • A new institution, the same day. Its own archive, users, report letterhead, price list — without touching the rest of the platform.

On-premise · cloud

Your servers or ours.
The product is the same.

There is no “cloud version” and “on-premise version” — there is one ZenRIS. The choice is about where the data lives and who runs the hardware, not about what the platform can do.

your institution's perimeter

Data never leaves the institution. Modalities connect directly on the local network, control is total, and access is still through the browser — including from home, over a secured channel. For hospitals and groups with strict data policies.

On-premiseCloud
Where the data livesInside your institutionIn the EU, in certified data centers
Who runs itYour IT team, with our supportWe do, with an SLA
How you startInstall on your existing infrastructureNew account, same day

Same version. Same features. Same browser. And if you change your mind along the way, migration is a plan — not a rewrite. See the architecture in detail →

Security · compliance

Every view, logged.
Every access, by name.

In medical imaging, security isn't a marketing paragraph — it's a checklist. Ours is short, concrete, and verifiable at the demo.

  • Complete audit trail — who viewed which image and which report, when and from where; exportable for your DPO and for inspections.
  • Granular roles + two-factor authentication for every account.
  • Institutional SSO — Active Directory / LDAP / SAML/OIDC.
  • Encryption in transit and at rest, across every component.
  • Automatic backup and a recovery plan that is tested, not just declared.
  • Per-institution isolation — the architecture described above, not a checkbox.
  • GDPR — legal basis, patient rights, and an access log for each patient's data.
  • EU/Romania hosting for the cloud option.
  • Class I medical device, registered with ANMDMR (Romania).
excerpt from the audit log · fictitious data
10:13  Dr. Ionescu M.  opened      head CT #2026-0412
10:14  Dr. Ionescu M.  signed      report v2
10:19  patient portal  downloaded  signed report
       (link has since expired)

Ask us for the full list of controls at the demo. Or better yet — bring your IT team and let them ask.

See ZenRIS on your own studies.

Book a 30-minute demo — or bring your own anonymized DICOM files and watch them cross the platform: from arrival, to report, to portal.

The demo runs in your browser. Obviously.