Skip to content

Main content

Nursing Device Patient Assignment Tag

Record an explicitly asserted device-to-patient assignment without identity resolution or device suitability checks.

Loading tool…

Description

Record an explicitly asserted device-to-patient assignment.

Nursing records connect observations, chart-entry times, handoff identifiers, device assignments and task status. A timestamp delay differs from verified retrospective documentation, and a matching identifier differs from an authenticated specimen or handoff. Time windows and due times must retain their stated boundary rules.

Record an explicitly asserted device-to-patient assignment.

When to use this tool

Use Nursing Device Patient Assignment Tag when you already have deviceId, patientRecordId, assignmentRecordId and need to record an explicitly asserted device-to-patient assignment.

How to use the tool and how it works

  1. Enter deviceId, patientRecordId, assignmentRecordId. 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 deviceId, patientRecordId, assignmentRecordId 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
deviceIdDevice IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
patientRecordIdPatient Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
assignmentRecordIdAssignment Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "deviceId": "D17",
    "patientRecordId": "P3",
    "assignmentRecordId": "ASSIGN2"
  },
  "output": {
    "token": "[\"D17\",\"P3\",\"ASSIGN2\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without identity resolution or device suitability checks. 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

Reconcile original chart, specimen and handoff records when identity or completion matters. Use the documented workflow and actual care context for task timing; a literal match or supplied time margin is only one local record check.

References

  1. Calculation and input contract: nursing/nursing-device-patient-assignment-tag — tool.io

Similar or alternative tools