Vedashwa QMS · Compliance
Part 11 and Annex 11, built in
Inspectors check every signature and every audit trail. Vedashwa QMS builds the controls in, so your validation team starts from evidence.
- hash binds every signature to its record
- SHA-256hash binds every signature to its record
- audit-trail review rules
- 16audit-trail review rules
- failed sign-ins lock an account
- 5failed sign-ins lock an account
Your part of compliance
Procedural controls stay with your organisation:
- Signature accountability policies
- Identity checks before issuing accounts
- Certifying e-signature use to the FDA
- Validating for your intended use
Six controls, built in
Electronic signatures
Meaning, re-entered credentials, and a hash that flags any change after signing.
§11.50 · §11.70 · §11.200 · Annex 11 §14
Audit trail
Append-only and time-stamped, with reasons for change and a built-in review.
§11.10(e) · Annex 11 §9
Access control
Role-based permissions, optional MFA, lockout and idle sign-out.
§11.10(d), (g) · Annex 11 §12
Records and copies
Any record as one inspection-ready PDF; exports permission-gated and audited.
§11.10(b) · Annex 11 §8
Operational checks
Workflows enforce the right order, from OOS retests to batch release.
§11.10(f)
Validation and change
A GAMP 5 approach, IQ/OQ evidence and signed configuration changes.
§11.10(a) · Annex 11 §4, §10