Scripter handles consultations, prescriptions and patient records, so protection is a design property rather than a bolt-on: encrypted storage, enforced roles and an audit trail that writes itself.
The same six properties the platform is built around, wherever your data flows.
Designed to support UK GDPR-compliant management of patient data, with data kept in-region.
Documents and records stored encrypted, with S3 and KMS-backed storage.
Prescriber and non-prescriber roles enforced; privileges follow the membership across every site.
Every consultation tied to the protocol version it was run under.
Document history kept, shared safely with patients and colleagues.
PGD sign-offs and training records tracked per practitioner, expiring when protocols change.
Patient records, consultation notes, prescriptions and documents are stored encrypted at rest using S3 with KMS-backed keys. Access is authenticated and role-based: what a team member can see and do follows their membership and role, enforced by the platform across every location of your organisation, never by convention.
Documents are versioned rather than overwritten, so the record of what was shared, when, and in what form is retained, and sharing with patients and colleagues happens through the platform rather than as email attachments.
PGD templates carry the governing PDF and their full version history. Practitioner sign-offs are tracked per version; when a protocol is updated, old sign-offs expire, everyone affected is notified, and subscriptions, consultations and service affiliations cascade to the new version. Every consultation records the exact protocol version it ran under, which is what makes audits a lookup rather than a project.
Security and data-protection questionnaires are part of pharmacy life. Send yours through the contact page and it goes straight to the team.
See the audit views, the version history and the access model live in a demo.