A patient portal without a patient database in the cloud

What the portal covers

The portal handles the patient traffic that otherwise leaks into email, phone tag and paper left at reception:

• Secure messages that land in the chart, not a shared inbox
• Document delivery — reports, letters and invoices
• PROM forms patients complete at home before a review
• Self-booking against the availability you publish

Invitation, not registration

Patients do not sign up to SideClick; the practice invites them. That single design choice keeps the boundary where clinicians want it — you decide who can message you and who can book online, patient by patient, and you can withdraw access as easily as you granted it.

Each patient sees only the surface of their own record: their messages, their documents, their forms, their bookings. The clinical record itself never leaves your custody.

How it works in practice

A review is coming up, so the practice sends the PROM form through the portal; the patient completes it on their phone at home, and the scores are on the chart before the session starts. Afterwards the visit summary and the invoice go back out the same way, and the follow-up question the patient thinks of that evening arrives as a message on their record rather than an email to your personal address at 9 pm.

The privacy posture behind it

Portal traffic rides the same relay as multi-device sync, and inherits its defining property: the server stores and forwards ciphertext it cannot read. The full mechanics — keys, device trust, what the operator can and cannot see — are documented on that page rather than repeated here.

The kiosk is not the portal

Two things are easy to conflate. The in-office kiosk — patients completing forms on a practice device in the waiting room — ships in every edition including Solo. The remote portal, reaching patients at home, is what the Portal edition adds. If your intake forms happen in the waiting room, Solo already covers you; see the pricing page for the ladder.