"The doctor's duty is not fulfilled by…
routinely demanding a signature on a consent form."
Montgomery v Lanarkshire Health Board [2015] UKSC 11
Get Patient Consent turns informed consent into a documented conversation between clinician and patient — with a tamper-proof audit trail that holds up in court.
A signature on a form proves nothing about what the patient understood. A digital consent platform should do better.
Patients can ask questions at any point during the consent process. Clinicians respond. The entire thread becomes part of the documented consent record. Consent as a genuine dialogue.
Every action is logged with cryptographic hash chaining: what was shown, when it was viewed, how long was spent reading, and what was signed. Immutable and independently verifiable.
Track time spent on each section, comprehension checkpoints, and leaflet read-confirmations. Prove the patient was informed, not just that they signed.
Attach versioned PDFs to any consent request. Patients confirm they have read each one. The exact version they saw is locked into the consent record.
Patients receive a secure link by email and complete consent on any device. In clinic, a QR code gets them started instantly. Mobile-first, accessible, no app to download.
On the day, patients scan a QR code to confirm their consent is still valid — or raise new questions. A second layer of evidence for the clinical record.
Sending a consent request takes under two minutes. Completing one takes about ten.
Choose a consent template, attach leaflets, add patient-specific notes or risks.
The patient receives a secure link by email, or scans a QR code in clinic.
The patient reads each section at their own pace, asks questions, confirms understanding.
Digital signature, PDF generated, full audit trail locked in. Consent documented.
Most consent platforms digitise the paper form: present information, capture a signature. That misses the point. The Supreme Court was clear — informed consent requires dialogue.
Montgomery v Lanarkshire Health Board [2015] UKSC 11, para. 90
Security and compliance are not features. They are the foundation.
AES-256 encryption for all stored data. TLS 1.2+ for all connections. Application-level encryption of patient identifiers with AWS KMS.
All data processed and stored in AWS eu-west-2 (London). Nothing leaves the UK.
Cryptographic hash chain on every event. Append-only storage. Independently verifiable years later.
Data minimisation, retention policies, DPIA completed. Designed for special category health data from the ground up.
Every signed consent includes a complete snapshot of exactly what the patient saw. Template updates never alter historical records.
WCAG 2.1 AA compliant. Mobile-first design. Works on any device, any browser, any network. No app required.
We're launching with a small group of private practice clinicians. Get early access and help shape the platform.
Request Early Access