RadIVWL
The bridge between entrenched worklist infrastructure and the next generation of AI-native reporting.
A licensed integration platform that lets generative AI reporting platforms slot into InteleViewer Worklist–anchored workflows without ripping anything out. Purpose-built for the reporting migration moment in US radiology.
A migration window the market has been putting off for years.
US radiology practices have anchored on InteleViewer Worklist for over a decade. The workflow is entrenched, staff are trained on it, and the productivity gains from moving to something else have never justified the migration pain.
Reporting, by contrast, is up for grabs. Nuance PowerScribe 360 is reaching end-of-life, forcing thousands of practices to make a reporting decision they've deferred for years. A new generation of AI-native reporting platforms — RadPair among them — is ready to take that market. But the workflow reality is that reports are dictated inside the worklist. And there's been no clean way to connect the two.
RadIVWL is that connection. It's not a worklist replacement, and it's not a reporting platform. It's the integration layer that lets modern AI reporting slot cleanly into an InteleViewer-anchored workflow — without asking your practice to change anything else.
Transcript in, structured report out — inside one radiologist surface.
Here's what the radiologist actually sees inside the Radgentix web host. RadPair's AI-native reporting — a dictation transcript on the left, a live-drafted structured report on the right — running alongside InteleViewer Worklist and the diagnostic viewer. To the radiologist, it's one continuous surface. Everything Radgentix does to make that happen runs quietly in the background.
The point of the integration is that none of this friction shows up to the radiologist. They open a study from InteleViewer Worklist as they always have. The diagnostic viewer opens in parallel. The reporting surface — this one — is right there, drafted by RadPair, ready to review. Sign-off routes back through the existing channels. What changes for the practice is the reporting engine underneath — everything else stays the same.
Two systems, one seamless workflow.
Your practice runs on InteleViewer Worklist, and it works. Modern AI reporting from partners like RadPair is ready to change how radiologists draft, review and sign. What's been missing is the connection between them — one that doesn't disrupt the workflow your radiologists already trust. That's what Radgentix builds.
Nothing to rip out
Your practice keeps InteleViewer Worklist exactly as it is today. No migration project. No retraining. No rebuild of the workflows your team has spent years refining.
One radiologist surface
The radiologist opens a study, and RadPair's AI reporting is already there — same window, same flow. No alt-tabbing between a viewer and a separate reporting app. No second login to remember.
Reports go where they always did
Signed reports return through your existing PACS and RIS pipeline. Your billing, your regulatory reporting, your referring-doctor delivery — none of it needs to change downstream.
One accountable partner
When integration questions come up, Radgentix owns them end-to-end. One relationship for the connection between your worklist and your AI reporting. One team on the hook for keeping the flow live.
From first contact to production go-live.
RadIVWL deployments follow a repeatable pattern. Timelines vary based on customer environment and integration complexity, but the phases below are consistent across engagements.
Scoping and readiness
Confirm the integration target on both sides — worklist version, reporting platform, and any customer-side constraints. Sign the licence agreement and provision cloud tenants.
Environment provisioning
Stand up the cloud control plane, configure the customer tenant, provision test licenses, and prepare the workstation bridge installer for the customer's imaging environment.
Pilot deployment
Deploy the bridge to a small group of radiologist workstations, wire the web host, and run structured pilot workflows. Verify token flow, usage telemetry, and reporting integration end to end.
Rollout and stabilisation
Expand to the full radiologist cohort, verify usage metering at scale, and confirm commercial reporting against contracted volume. Handover to operational support with runbooks and monitoring dashboards.
Operate and iterate
Continuous usage telemetry, monthly reconciliation, ongoing patch releases via the workstation bridge, and quarterly review of integration health with both the customer and the reporting partner.
What you'll need in place before rollout.
RadIVWL is designed to sit inside existing radiology infrastructure with minimal disruption. Public prerequisites below cover the environmental essentials — detailed technical specifications, security documentation, and network diagrams are shared under NDA as part of the deployment kit.
Worklist and imaging
- InteleViewer Worklist installation, current supported version
- Workstation OS: Windows 10/11 (64-bit)
- Local admin rights during initial install of the bridge
- Reporting partner: platform integration in place (RadPair or contracted equivalent)
Cloud and identity
- Azure tenant (customer's or Radgentix-managed)
- Ability to accept a signed workstation bridge installer
- Named administrative contacts for provisioning
- Optional: SSO integration via OIDC / SAML for the web host
Network
- Outbound HTTPS from radiologist workstations to Radgentix cloud endpoints
- Optional: proxy allowlist entries for controlled network environments
- No inbound firewall rules or DMZ configuration required
- TLS 1.2 or higher on all internal path segments
Governance
- Signed licence and data processing agreement
- Named privacy and security contacts on the customer side
- Change management approval for workstation deployment
- Agreement on incident response and support-tier expectations
Full technical specification available on request
The complete deployment kit includes detailed architecture diagrams, security whitepaper, network path documentation, workstation MSI signing details, licensing SKU matrix, and the operational runbook. It's shared under NDA with prospective customers and integration partners.
Request the deployment kit →Bring your AI reporting platform to IV-anchored practices.
If you build an AI reporting platform and want to reach US practices anchored to InteleViewer, RadIVWL is the fastest path to that market. Rather than negotiating your own integration story with each customer, you license the RadIVWL platform wholesale — and get the integration, licensing, metering, and telemetry as a service.
Our launch partner is RadPair, whose AI-native reporting capability is available to InteleViewer Worklist customers through the RadIVWL platform today. The architecture is designed to support additional reporting partners over time, under similar wholesale terms.
What partners get:
- Integration surface — a stable, versioned integration contract, so your reporting platform can be embedded into IV workflows without per-customer engineering.
- Wholesale licensing — tiered volume-based pricing that scales as your customer volume scales, with transparent monthly reconciliation.
- Metered telemetry — audited per-report usage data that both parties can rely on for commercial reporting.
- Customer trust framework — a shared audit and governance model that reassures customer security and compliance teams.
- Deployment support — Radgentix carries the customer-side integration effort, so your team stays focused on your reporting product.
Interested partners should get in touch below — we're selective about who we onboard, and we look for reporting platforms with clear clinical value, mature product engineering, and a serious go-to-market posture.
Ready to see the full picture?
Whether you're a practice evaluating your reporting future, a hospital system planning an AI-native reporting rollout, or a reporting platform looking to reach IV-anchored customers — we'd like to hear from you.