Healthcare & Clinical Systems

Nexus Reporting — from billing desk to patient portal

Radiology and lab reporting for a diagnostic centre. Paid procedures flow into a worklist on their own, radiologists report on structured templates, finished reports are locked and signed, and patients get their reports on their phones, each with a QR code anyone can check for authenticity.

Laravel 12 MariaDB Blade Dompdf Built · Pre-launch

The 45-second tour

Recorded on a development copy with fictional patients and staff; no real patient data. The video has no sound.

Reports written in Word, chased on the phone

In many diagnostic centres a report starts as a Word file, is retyped or copied between people, printed, and collected in person. Nobody can easily tell which studies are still waiting, a finalised report can be quietly edited, critical findings rely on someone remembering to call, and a patient’s report can’t be checked for authenticity once it leaves the building.

One workflow, from payment to the patient’s phone

Paid procedures arrive in the reporting worklist automatically from the centre’s billing system. A radiologist claims a study, so only one person works on it, and writes the report on a structured template for that modality and protocol, saving it as preliminary and finalising when ready. Final reports are locked: corrections go through addenda or versioned amendments with the full history kept. Each report becomes a signed PDF carrying the radiologist’s registration number and a QR code that anyone can scan to confirm it is genuine. Patients are notified by WhatsApp or SMS and sign in to their own portal to download their reports. A statistics page shows turnaround times and critical-finding communication, and an append-only audit log records who did what.

Built so a report can be trusted later

A worklist that fills itself
A scheduled job pulls billed procedures from the billing system through a signed service API every two minutes, and claims left idle are released automatically.
Final means final
Finalised reports can’t be edited. Changes are added as addenda or versioned amendments, so the original is always recoverable.
Verifiable anywhere
Every PDF carries a QR code that opens a public verification page, confirming which centre issued the report and when.
Consent-gated partner access
An outside partner can receive reports through an API only where the patient has consented, documented with its own integration guide.
Backups that are actually tested
Encrypted nightly backups with long-term retention, and a regular drill that restores them to a scratch database to prove they work.
Tested end to end
Automated tests cover the whole workflow, from queue and claim through finalising, notifying and the portal, plus lockouts, critical findings, amendments and verification. It is built for more than one centre from the start.

Under the hood

ApplicationLaravel 12 with server-rendered Blade pages, no JavaScript build step
DatabaseMariaDB, with every table scoped to a centre
DocumentsDompdf for signed report PDFs with QR verification codes
IntegrationSigned service API with Nexus Finance (billing); WhatsApp and SMS drivers for notifications
HostingDesigned for shared hosting on Hostinger: cron-driven queue, no background daemons

Where it stands

Built and tested, and waiting on the centre’s real report templates, letterhead and signatures, messaging-provider credentials and a partner data-sharing agreement before it goes live alongside Nexus Finance.

← PreviousNexus Finance Next case studyEarmark / Gosha →

Running a centre on Word files and phone calls?

The reporting workflow can be made traceable, verifiable and easy for patients, without changing how your radiologists like to work.