The platform

Teleradiology software that treats a read as a record.

Raydiac is the radiology workflow software the network runs on: an edge gateway at the scanner, pseudonymised intake, an assignment engine that routes under a service-level clock, a web DICOM viewer, structured radiology reporting software, digital signing, and an audit trail that cannot be edited. Built and operated in India, for CT and MRI.

Request access Security and compliance

1
Scanner or PACS
DICOM C-STORE on your LAN
2
Edge gateway
HTTPS 443, client certificate, buffers 30 days
3
Raydiac
Pseudonymise, order, route under SLA
4
Radiologist
Full study in the browser viewer
5
Signed report
Re-identified, PDF, audit trail

No software on the scanner
No VPN, no inbound ports
No diagnostic AI
No scanned signatures
No patient data outside India

01 · Getting the study in

A gateway on your LAN, and a vault between the patient and the reader.

The two hardest things in teleradiology are getting the study off the scanner without a project, and making sure the person reading it does not need to know who the patient is. Raydiac solves both before a radiologist is ever involved.

PACS, RIS and DICOM explained

Edge gateway

A mini-PC running Orthanc, placed on the hospital network and added to the CT or MRI console, or the PACS, as a DICOM destination. Studies arrive by C-STORE on the LAN. The gateway forwards them to Raydiac over HTTPS on port 443 with a client certificate unique to the site, so there is no VPN, no open inbound port and nothing installed on the scanner. If the internet drops it buffers up to 30 days and catches up when the link returns. Sites without a gateway yet use a manual resumable browser upload that survives a dropped connection.

Intake and pseudonymisation

On arrival, patient name, hospital ID, date of birth and phone number are moved into an identity vault encrypted with AES-256-GCM and replaced with a pseudonym such as RDX-26-000418. The order the radiologist sees carries the pseudonym, age, sex, a mandatory clinical history of at least 50 characters, the clinical question, and any priors from the same site, attached automatically by matching inside the vault. Priority rules run at intake: the site sets routine, urgent or STAT, and the priority can be raised later but never lowered.

WorklistTonight · 5 open

SLA clock

Order	Study	Site	Priority	Due in	Status
RDX-26-000418	CT Brain, plain	District hospital	STAT	00:41	Reading
RDX-26-000417	CT KUB	Diagnostic centre	Urgent	02:58	Assigned
RDX-26-000416	MRI Lumbar spine	Diagnostic centre	Routine	14:20	Queued
RDX-26-000415	CT Chest, contrast	District hospital	Routine	11:05	Draft
RDX-26-000414	MRI Brain, contrast	Nursing home	Urgent	Signed	Delivered

The coordinator’s view. The radiologist sees only orders offered or assigned to them, with the same clock.

02 · Routing

An engine decides who reads. A clock decides how fast.

Assignment engine

Every order is offered only to radiologists who hold an active credential for that organisation and that modality. Among them, the engine weighs subspecialty where the panel has it (optional, since most Indian radiologists are generalists), the roster, each reader’s current load and the service-level clock. STAT orders go to the top of every eligible list. Offers are time-boxed: if the first radiologist does not accept in time, the order moves to a backup route. Sites can name invited or preferred radiologists who are tried first.

Worklist

One worklist per role. The site coordinator sees every open study from their site with its priority, status and the time left on its service-level target. The radiologist sees the orders offered or assigned to them, ordered by the same clock. Statuses run from queued through offered, assigned, reading, draft, signed and delivered, and each change is an audit event. Nobody picks cases from an open pool and nobody changes an urgency after the fact.

03 · Reading

The whole study in a browser. A report that is data, not prose.

Viewer

Raydiac embeds OHIF, the open-source web DICOM viewer, so the radiologist reads the full study in the browser with multiplanar reconstruction, window presets, measurements and priors side by side. Nothing is installed. Each study is opened with a per-study viewer token that expires, and every open, series view and export is written to the audit trail. Raydiac asks panel radiologists to read on a diagnostic display that meets the ACR-AAPM-SIIM standard, and records the display declared at onboarding.

Reporting

Structured templates for each CT and MRI study type, curated by the clinical co-founder, with named sections for findings, impression, recommendations and measurements. Measurements are stored as data so that a follow-up can compare them. The radiologist can dictate, fill a template, and ask for an impression drafted from the findings they wrote. Before signing, a proofreading pass checks for laterality slips, negation errors and missing measurements. The language model behind these runs on Raydiac servers in India, sees only the radiologist’s text, and never sees the images. Reports move through preliminary, final and addendum states.

RDX-26-000414 · MRI Brain with contrast

Final report · v1

Signed

Clinical question

Recurrent headache, 6 weeks. Rule out space-occupying lesion.

Findings

Impression

No intracranial mass lesion. No abnormal enhancement.

MDReporting radiologist · MD Radiology · Reg. no. on report

eSign · SHA-256 · 21:14 IST

04 · Signing and after

Signed, delivered, and closed out.

A report is only finished when the referrer has it and any critical finding has been acknowledged by a named person. Raydiac treats delivery and communication as part of the record, not as something that happens outside it.

How radiology quality is measured

Signing and delivery

The radiologist signs with Aadhaar eSign, producing a PAdES digital signature under the IT Act; Raydiac adds a platform counter-signature and a QR code that opens a verification page. Identity is re-identified server-side at the moment of signing, so the PDF carries the patient’s details and the radiologist’s name, qualification, council and registration number. The signed PDF goes to the site portal and is delivered by email and WhatsApp to the people the site names. Once signed, a report is immutable at the database level and can only be superseded by an addendum. Return into a PACS or HIS is on the roadmap.

Critical results

Marking a finding critical opens a closed-loop communication task: who was called, at what time, on which channel, and who acknowledged the result. Open tasks escalate to the site coordinator and then to Raydiac. The whole loop sits in the audit trail beside the report.

Second reads and peer review

A second read is a second assignment on the same order, producing a separate report that sits beside the first. Random-sample peer review runs across the panel, and discrepancy rates and service-level compliance are the measures Raydiac reports to sites. There are no star ratings.

05 · Running the network

Billing, audit and tenancy are part of the product.

A managed network needs to prove what happened and who was paid for it. These parts are as much of the platform as the viewer.

Billing

Every signed report produces a rate card line: modality, study type, contrast, priority and shift, with the radiologist fee and the platform fee as separate amounts. Sites receive one monthly invoice, with GST at 18 percent on the platform fee only. Radiologists receive a monthly payout statement with TDS under section 194-O deducted at 0.1 percent and a Form 16A. Settlement runs through an authorised payment aggregator’s split settlement; Raydiac never holds the hospital’s money.

How pricing works

Audit trail

Every event, from a study arriving to a report being exported, is appended to a per-tenant log that cannot be updated or deleted. Each entry is hash-chained to the one before with SHA-256 and a keyed HMAC, and the chain head is written daily to write-once storage, so a gap or a rewrite is detectable. Logs are retained for a minimum of one year, matching Rule 6 of the DPDP Rules 2025. Sites can request the full trail for any order.

Security and compliance

Multi-tenant, white-label, self-hostable

Designed for, later phase

The platform is multi-tenant from the first commit: every organisation’s data, templates, credentials and audit chain are separated by tenant. It is designed so that a hospital group could run it under its own name or on infrastructure it controls. Those deployments are a later phase and are not available at launch; Raydiac operates a single managed network today.

Where Raydiac is today

Built on open standards

Nothing proprietary between your scanner and the report.

Raydiac uses the same standards a hospital PACS or RIS already speaks. Where a standard is not yet implemented, the table says so.

Standard	Where Raydiac uses it	Status
DICOM C-STORE	How the scanner or PACS sends studies to the edge gateway on the LAN. Any modality console or PACS that can add a DICOM destination can send to Raydiac.	Live
DICOMweb STOW-RS	How the gateway forwards studies to Raydiac over HTTPS, and how the manual resumable upload delivers a study when no gateway is present.	Live
OHIF viewer	Open-source (MIT) web DICOM viewer used for every primary read. No proprietary viewer, no plug-in, nothing installed on the radiologist’s machine.	Live
Aadhaar eSign, PAdES	Electronic signature under the IT Act, sections 3A and 5, via a CCA-empanelled service provider. PAdES signature embedded in the PDF with a verification page.	Live
IHE-style audit events	Append-only audit trail modelled on the IHE ATNA event vocabulary: who did what, to which study, from where, when. Hash-chained per tenant.	Live
HL7 v2 ORU, FHIR R4	Return of signed reports into a hospital PACS, RIS or HIS, and the ABDM DiagnosticReportImaging profile for milestone M2.	Roadmap
IHE MRRT, ACR-RSNA CDE	Report templates in the MRRT format and measurements coded to the ACR-RSNA Common Data Elements so that structured content can be exchanged, not just printed.	Roadmap

Roadmap

What is not live yet.

Raydiac would rather list these here than have a hospital discover them after signing. None of them is part of a launch agreement.

Roadmap
PACS and HIS return
DICOM SR, HL7 ORU and FHIR R4 delivery of signed reports back into the site’s own systems.
Roadmap
ABDM milestone M2
Pushing signed reports as FHIR DiagnosticReport bundles to the patient’s ABHA-linked record, for sites that opt in.
Roadmap
ISO 27001
Certification of the information security management system. Controls are being built to the standard now; the certificate does not exist yet.
Roadmap
White-label and self-hosting
Running the platform under a hospital group’s own name, or on infrastructure it controls. The platform is multi-tenant from the first commit; these deployments are a later phase.
Roadmap
MRRT templates and coded measurements
Exporting the structured content of a report in an interoperable format rather than only as a PDF.

FAQ

Questions about the platform

Is Raydiac a cloud PACS?

Not in the sense a hospital usually means. A PACS is the long-term image archive for a department. Raydiac is a teleradiology platform: it receives studies from the scanner or PACS through an edge gateway, holds images for 90 days hot for reporting and priors, and keeps signed reports for eight years. Sites that have no PACS often use the Raydiac portal as their day-to-day viewer, but Raydiac does not replace the archive a hospital is obliged to keep.

Which DICOM viewer does Raydiac use?

OHIF, the open-source web DICOM viewer, embedded in the Raydiac reporting workspace. The radiologist opens the full study in the browser with multiplanar views, window presets, measurements and priors side by side. Each study is opened with a per-study viewer token that expires, and every open, series view and export is written to the audit trail. Raydiac does not ship a phone viewer for primary reads.

Does the platform include AI reporting?

Raydiac ships no diagnostic AI. No pre-read, no triage, no detection. The language model in the reporting workspace runs on Raydiac servers in India, sees only the radiologist’s own text, and is used for dictation transcription, template fill, drafting an impression from the findings the radiologist wrote, and pre-sign proofreading for laterality, negation and missing measurements. It never sees an image and never proposes a finding.

How does the edge gateway connect to our scanner?

The Raydiac gateway is a small computer running Orthanc on the hospital network. The CT or MRI console, or the PACS, is given the gateway as a DICOM destination and sends by C-STORE, exactly as it would to any other node. The gateway forwards each study to Raydiac over HTTPS on port 443 using a client certificate unique to the site, with no VPN and no inbound ports, and buffers up to 30 days if the internet drops.

How are reports signed?

The radiologist signs with Aadhaar eSign, which produces a PAdES digital signature under the IT Act, and Raydiac adds a platform counter-signature. Each PDF carries a QR code that opens a verification page showing the signer, the qualification and registration number, and whether the document has been altered. Raydiac never places a scanned signature image on a report. Signed reports are immutable; corrections are issued as addenda.

Can we get reports back into our PACS or HIS?

Not at launch. Today Raydiac delivers the signed PDF through the site portal, by email and by WhatsApp to the people the site names. Return of reports into a PACS or HIS by DICOM SR, HL7 ORU or FHIR R4 DiagnosticReport is on the Raydiac roadmap, as is ABDM milestone M2. Raydiac does not promise either as part of a launch agreement.

See the platform on your own studies.

Tell us about your scanners and the hours you need covered. We will come back within two working days with a rate card, the data processing agreement and a plan for the gateway.

Request access For hospitals

Hospitals and centres: AERB licence for CT. Radiologists: State Medical Council or NMC registration.