All projects
05 Live 2026
DocumentsHub — Document Completion & Signing
Multi-tenant SaaS for consent forms signed on the clinic’s tablet — request to archive, no paper.
Documentse-SignatureMulti-tenant SaaS
Context
Paper consent forms get lost, get signed incomplete, and cannot be found on the day someone actually asks for them. Clinics needed a digital flow that reception staff could use without training, and a resulting document that would survive later scrutiny.
What I built
- The full request → tablet → signature → archive flow, with a re-deliverable tablet session: an accidental refresh no longer loses the document in progress.
- A .NET 10 modular monolith with fail-closed per-tenant isolation — a missing tenant context means zero data, and a write without a tenant throws; the rules are enforced by architecture tests rather than by discipline.
- An integration surface for other products: app tokens, requests started from a template or a pre-generated PDF, cursor-paginated reconciliation, and HMAC-signed webhooks with retry, dead-lettering and SSRF protection.
Technical highlights
An archive that cannot be rewritten
finalised documents go to storage with WORM versioning and a 7-year retention policy — not even an administrator can overwrite a signed document.
Immutability enforced in code
a finalised document and a published template version are never modified again; corrections go through new versions. Guaranteed by an interceptor plus an architecture test.
Encrypted national ID, still searchable
search by national ID without partial digits ever leaving the browser — an audited endpoint, so the identifier never reaches access logs.
Versioned templates
a draft → publish model: edit freely, but a version is only born on publish, and already-sent requests stay pinned to theirs.