Platform overview
Radiology Software Holdco delivers an enterprise imaging workflow platform shaped around Australian hospitals and imaging groups: predictable behaviour across acquisition, reading, reporting, distribution, and governance—not a loose bundle of point tools that only align on a slide deck.
What “platform” means in a live imaging service
In practice, a platform is the set of guarantees your department can rely on when volumes spike, staff rotate, and integrations misbehave. That includes consistent identity and authorisation, coherent worklist behaviour, traceable template and macro changes, and support processes that understand severity in clinical terms—not only ticket categories.
We architect around the reality that imaging is both a clinical service and an operational system of record. Radiologists need high-fidelity presentation and dependable hanging protocols; referrers need timely, trustworthy results; operations teams need queue visibility and configuration control; security and privacy teams need evidence of least-privilege and defensible logging. A platform approach refuses to treat those needs as optional add-ons.
Acquisition-to-distribution, without losing accountability
Studies move through multiple systems and teams. The failure mode we see most often is not “missing features” but ambiguous ownership: who is responsible when priors are late, when an order maps to the wrong encounter, or when a reporting template silently diverges between two sites? Our product direction emphasises explicit workflows, versioned configuration, and operational telemetry so those questions have answers—not improvised email threads.
Australian networks also carry interoperability obligations that sound technical but are deeply clinical: HL7 v2, DICOM, emerging FHIR usage, and local integration practices that vary between states and vendors. The platform is designed to make reconciliation and failure handling observable, because “it usually works” is not a control posture.
Deployment models that respect sovereignty and continuity
Whether you operate on-premise, in a private cloud, or adopt hybrid patterns, the discussion should begin with data residency, exit strategy, and degraded-mode behaviour—not headline savings. We bias toward designs that keep imaging services functional when dependencies wobble, and that allow your teams to rehearse incidents with runbooks that match real staffing, not vendor defaults.
If you are comparing platforms, ask for evidence across six months of production behaviour: integration failure cohorts, template drift audits, after-hours incident timelines, and upgrade windows that did not require heroics. Those artefacts separate enterprise delivery from marketing claims.