Skip to content

Main content

Biosecurity Training Record Version

Qualify an explicit administrative training record by version without deciding competence or authorization.

Loading tool…

Description

Qualify an explicit administrative training record by version.

Biosecurity metadata can record custody references, inventory counts, access assertions and review dates. A balanced inventory does not authenticate materials or explain discrepancies, and a recorded permission flag does not grant access. These tools organize supplied records rather than inspect facilities, assess threats or provide operational procedures.

Qualify an explicit administrative training record by version.

When to use this tool

Use Biosecurity Training Record Version when you already have personRecordId, trainingRecordId, version and need to qualify an explicit administrative training record by version.

How to use the tool and how it works

  1. Enter personRecordId, trainingRecordId, version. 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.

Enter personRecordId, trainingRecordId, version using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
personRecordIdPerson Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
trainingRecordIdTraining Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
versionVersionRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "personRecordId": "P17",
    "trainingRecordId": "TR2",
    "version": "v2"
  },
  "output": {
    "token": "[\"P17\",\"TR2\",\"v2\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without deciding competence or authorization. Sources and asserted relationships are not independently authenticated.
  • 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

Use controlled inventory, custody, authorization and oversight records for real decisions. Verify the underlying evidence and applicable requirements through the established professional process; local labels and balances do not establish security or compliance.

References

  1. Calculation and input contract: biosecurity/biosecurity-training-record-version — tool.io

Similar or alternative tools