Skip to content

Main content

Clinical Order Unit Convention

Preserve an explicit order unit convention without interpreting or converting a medication order.

Loading tool…

Description

Preserve an explicit order unit convention.

Clinical pharmacy records preserve medication wording, source dates, supply quantities and reconciliation states. Calendar shifts count weekends unless another rule is explicitly implemented. A supplied discrepancy or dose text describes a record rather than a verified medication history or a recommended regimen.

Preserve an explicit order unit convention.

When to use this tool

Use Clinical Order Unit Convention when you already have orderId, quantityUnit, conventionSource and need to preserve an explicit order unit convention.

How to use the tool and how it works

  1. Enter orderId, quantityUnit, conventionSource. 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 orderId, quantityUnit, conventionSource 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
orderIdOrder IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
quantityUnitQuantity UnitRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
conventionSourceConvention SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "orderId": "O17",
    "quantityUnit": "mg",
    "conventionSource": "Order system A"
  },
  "output": {
    "token": "[\"O17\",\"mg\",\"Order system A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without interpreting or converting a medication order. 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 the original medication, prescription and clinical records through the appropriate professional process. Check actual preparation, supply and patient context; local label formatting and arithmetic do not establish dose safety, therapeutic equivalence or permission to dispense.

References

  1. Calculation and input contract: clinical-pharmacy/clinical-order-unit-convention — tool.io

Similar or alternative tools