Skip to content

Main content

Biosafety Cleaning Handoff Code

Preserve explicit cleaning-handoff metadata without specifying or validating cleaning procedures.

Loading tool…

Description

Preserve explicit cleaning-handoff metadata.

Biosafety records distinguish required training, recorded completion, service labels, incidents and document versions. A false outstanding-training flag can mean training was not required, rather than competence being demonstrated. Supplied service-date text or permission assertions do not verify equipment readiness or authorize work.

Preserve explicit cleaning-handoff metadata.

When to use this tool

Use Biosafety Cleaning Handoff Code when you already have equipmentId, handoffRecordId, suppliedStatusCode and need to preserve explicit cleaning-handoff metadata.

How to use the tool and how it works

  1. Enter equipmentId, handoffRecordId, suppliedStatusCode. 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 equipmentId, handoffRecordId, suppliedStatusCode 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
equipmentIdEquipment IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
handoffRecordIdHandoff Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedStatusCodeSupplied Status CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "equipmentId": "EQ17",
    "handoffRecordId": "H2",
    "suppliedStatusCode": "recorded"
  },
  "output": {
    "token": "[\"EQ17\",\"H2\",\"recorded\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without specifying or validating cleaning procedures. 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

Check controlled training, equipment, incident and authorization records through the established safety process. Use appropriate professional assessment for actual work; local status logic and record formatting do not validate containment, competence or operating conditions.

References

  1. Calculation and input contract: biosafety/biosafety-cleaning-handoff-code — tool.io

Similar or alternative tools