AuraPACS gives the radiologist you already work with a browser viewer and reporting from anywhere you allow. Studies sync from the on-premise node through the cloud layer; the reader opens them, reports and signs. It is your radiologist, your archive and your report, not a pay-per-scan service.
Remote reading in AuraPACS means an authorised radiologist opens the centre's studies in a browser from wherever they are, scrolls the slices, adjusts window/level, writes the report on a template and signs it, exactly as they would in the reading room. Studies are received on the on-premise node and made available outside through the cloud layer.
This is teleradiology in the sense of reading at a distance, but it is not a teleradiology service. AuraPACS does not supply radiologists or charge per study read. It gives the radiologist you already work with a way to report between visits, and gives you role-based control and an audit trail over who saw what.
Most small centres have a radiologist who could read from home. What they lack is a safe way to get the study to them.
A few slices are photographed and sent; the radiologist reports on a fraction of the study.
A workstation client and a VPN that someone has to maintain, and that breaks when the radiologist changes laptop.
A shared login means nobody knows who opened which patient's study.
The document is emailed to the centre, printed and filed, disconnected from the images.
Outsourcing to a service solves the reading but bills every study forever and takes the relationship with your radiologist away.
Uploading a whole MR to a remote workstation over a weak line takes longer than the read.
The modality sends to the on-premise node as usual.
An encrypted copy reaches the cloud layer when the connection is up.
The radiologist logs in from home and sees unread studies for their role.
Slice scrolling and window/level on any laptop, priors from the history.
Template report finalised to PDF on the study, same as on site.
Front desk sends the secure WhatsApp link to the referrer.
Workflow: On the other days he opens the pending list from home and reports; on visit days he reviews in person.
Result: Reports go out daily instead of twice a week.
Workflow: She reads the centre's CT and MR from her own practice in a browser, with her own login.
Result: The centre keeps its radiologist and its archive; nothing is outsourced.
Workflow: Both nodes sync to the cloud layer; the radiologist sees one pending list across both.
Result: The second branch does not need its own radiologist on site.
Workflow: The on-call radiologist opens the study on a laptop at home and reports.
Result: The emergency physician gets the report without waiting for morning.
A partner or visiting radiologist who reads between visits.
Read for one or more centres from one browser.
On-call reporting at night without a workstation at home.
One reader, two scanners, one archive.
Remote reading without renting the archive.
No. It does not supply radiologists or charge per study read. It gives your own radiologist a browser viewer and reporting from anywhere you allow. If you use a third-party reporting service as well, that is a separate arrangement.
A laptop with a standard browser and an internet connection. The viewer opens CT, MR, X-ray and ultrasound with nothing installed. Display quality for reading is the radiologist's choice.
Each radiologist has their own login with the radiologist role. Every view is audited, so the owner can see who opened which study and when. See radiology workflow.
Studies sync from the on-premise node to the cloud layer in the background after they are received. The remote reader opens the synced study in the browser; on-site reading is never held up by the sync.
Yes. Each branch runs its own node and both sync to the cloud layer, so the reader sees a single pending list across sites.
It is written on the study itself, so it is already at the centre the moment it is signed. Front desk sends the secure link on WhatsApp. See reporting software.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it