Skip to content

Main content

GMP Electronic Signature Meaning Code

Qualify an explicit electronic-signature meaning code by source without authenticating a signature.

Loading tool…

Description

Record the meaning assigned to a manufacturing electronic signature.

Manufacturing quality records connect batch and material IDs, controlled versions, signatures, counts and calendar references. A status label or residual can expose a record convention while actual release, personnel qualification and compliance require verified evidence and authorized procedures. A recorded release label does not itself release anything.

Record the meaning assigned to a manufacturing electronic signature.

When to use this tool

Use GMP Electronic Signature Meaning Code when checking the stated manufacturing record, count or calendar-margin convention.

How to use the tool and how it works

  1. Enter recordId, signatureMeaningCode, codeSource. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Require nonempty record ID, signature-meaning code and code source. Encode them in that order as JSON text.1

Input fieldMeaning and unitsAccepted input
recordIdNonempty caller-supplied record label; not independently resolved.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
signatureMeaningCodeRecorded code only; no signature generation, identity verification or actual approval.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
codeSourceCode SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordId": "R17",
    "signatureMeaningCode": "reviewed",
    "codeSource": "System key A"
  },
  "output": {
    "token": "[\"R17\",\"reviewed\",\"System key A\"]"
  }
}

Limitations and assumptions

  • No signature is created or verified; a meaning code alone does not establish signer identity, approval or electronic-record compliance.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review original controlled records, applicable quality requirements and qualified authorized personnel for actual material, equipment or batch decisions.

References

  1. Calculation and input contract: gmp/gmp-electronic-signature-meaning-code — tool.io

Similar or alternative tools