AuraPACS generates a secure link for each study once the report is signed. Front desk sends it on WhatsApp to the referring doctor and the patient. They tap it and see the images and the PDF in a browser. Nobody creates an account, and every view is audited.
When a report is finalised, AuraPACS creates a secure link for that study. The front desk sends the link on WhatsApp to the referring doctor, the patient or both. Opening it shows the images in the browser viewer and the signed PDF, with no app to install and no account to create. Each view is recorded in the audit log.
This replaces the way most Indian centres already share results, which is a phone photo of a printed report or a JPEG of the screen. The link carries the actual study and the actual PDF, comes from the centre's system rather than someone's personal phone, and can be found again later from the patient's history.
The channel is not the problem. The problem is what gets sent down it and from whose phone.
A staff member photographs the printed page and sends it from a personal number. It is blurry, uncropped and unrecoverable a month later.
One slice of a CT, captured from the monitor, stands in for the whole study.
Nobody can say which doctor got which patient's report, or when.
A referrer portal with a username and password is set up and never used. Doctors do not remember passwords for every centre they refer to.
The report goes on WhatsApp; the images still travel by courier or patient.
When the staff member leaves, hundreds of reports leave in the chat history.
The radiologist finalises the PDF on the study.
AuraPACS creates a secure link for that study.
Front desk sends it to the referrer, the patient, or both.
The recipient sees the images and the report, nothing to install.
The access is logged against the study.
The link and the study remain in the patient's history at the centre.
Workflow: Minutes after sign-off, the link arrives on WhatsApp; the surgeon scrolls the series on a phone between patients.
Result: The patient's next consultation happens with the images already seen.
Workflow: The patient forwards the link to the consultant there.
Result: No CD, no film, no repeat scan.
Workflow: She has a referrer role and sees her own patients' studies in a browser, plus links for each one.
Result: One place for all her referrals from your centre.
Workflow: The owner checks who opened a particular study and when.
Result: The answer is in the audit log, not in someone's chat history.
Send to the number the patient or referrer gave at registration, and verify before the first send.
Note at registration that the patient agrees to receive results by WhatsApp and to sharing with the named referrer.
The link is served from your system and every view is audited; a forwarded JPEG is not.
Send from the centre's WhatsApp account, not a staff member's personal phone.
Health-record and data-protection rules differ by country and change over time. Confirm your obligations with your advisers.
No. The link opens in the phone's browser and shows the images and the report PDF. There is no app, no account and no password at the recipient's end.
The link is generated per study by AuraPACS and served from the system, and every view of it is audited. Generating links is controlled by role-based access, so only permitted staff can send one.
Yes. Views are recorded against the study in the audit log, which is part of the role-based access built into AuraPACS.
The link can open both. Many centres send the report to the patient and the report plus images to the referring doctor; the choice is yours per study.
Rules on health records and personal data differ by country and are updated over time. Record the patient's consent at registration, send to verified numbers from the centre's own account, and confirm your obligations with your advisers. AuraPACS gives you the audited link; the policy is yours.
Yes, for the link to be opened by someone outside. Studies are received and reported on the on-premise node without internet, and links go out once the connection is available. See hybrid PACS.
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