Healthcare

Data minimisation at collection, role-scoped access with an audit log, retention decided at design time, encryption in transit and at rest, and hosting in the region you choose inside your own cloud account. We are a processor acting on your instructions. We are not a compliance certifier and we do not give legal advice — we build to what your regulator, counsel and data protection officer require, and we say clearly where our responsibility ends.

Usually yes, and that is normally the right shape: keep the clinical record where it is and build the operational layer around it. Where a modern API or HL7/FHIR interface exists we use it. Where the vendor offers only a file export or a database view, we work with that and are explicit about the limits — a nightly sync is a nightly sync, and we will not describe it as real time.

They help, and we would rather set the expectation properly than quote a figure we have not measured for you. What matters more than the reminder itself is that it goes out on the channel the patient actually reads, in their language, with a working one-tap way to confirm or reschedule. A reminder that cannot be acted on without phoning reception is a notification, not a reduction in no-shows. We instrument it so you can see your own rate before and after.

Yes, and as equal versions rather than a translated afterthought — the Arabic booking flow is laid out right-to-left with its own typography, not the English layout mirrored. Reminders and confirmations go out in the language the patient chose, and staff-facing screens can run in a different language from the patient-facing ones, which is usually what a mixed team actually needs.