ข้ามสารบัญไปยังเนื้อหา
อัปเดต 2026-09-07
E-signature sign-off & record immutability
freeze-on-signature · write-lock
Defines sign-off requirements per study, captures electronic signatures with a password re-authentication step, and — the moment the first required signer signs — freezes the study content read-only and hard-locks every write endpoint (409 on further edits), so a signed record can never be silently altered underneath its own approval.
เมื่อไรจึงใช้
- A completed hazard study needs a formal, auditable approval before it governs a design.
- You need to guarantee a signed study genuinely cannot change afterward — not just discourage it.
ค่าที่ต้องกรอก
| ค่า | คำอธิบาย |
|---|---|
| Required signers & roles | Who must sign before the study is considered issued. |
| Content hash | A SHA-256 hash stamped at sign-off; downstream reviewers can verify the exact content that was signed. |
คำนวณอย่างไร
The first qualifying signature flips the study read-only study-wide; every content-write API call thereafter returns a hard 409, enforced server-side so it can't be bypassed from the UI. The signed PDF/Word export carries a Signatures appendix (signer, role, timestamp, hash-prefix) that travels with the document.
ข้อควรระวัง
noteThe write-lock is enforced at the API, not just hidden in the UI — there is no client-side path around it once a study is issued.
ที่เกี่ยวข้อง