Skip to content

Main content

Tooth Surface Notation Token

Format explicit tooth and uppercase surface-code fields under a local tooth:surfaces notation without interpreting a dental numbering system.

Loading tool…

Description

Join unique supplied uppercase surface codes after a tooth identifier.

Dental records depend on surface notation, assessed and excluded denominators, missing versus observed zero, reporting quanta and recorded equipment dates. Calendar-day counts can be elapsed or inclusive, and nominal expiry comparisons do not establish sterility. Local surface fractions and source labels are not automatically validated clinical indices.

Join unique supplied uppercase surface codes after a tooth identifier.

When to use this tool

Use Tooth Surface Notation Token when you already have toothCode, surfaceCodes and need to join unique supplied uppercase surface codes after a tooth identifier.

How to use the tool and how it works

  1. Enter toothCode, surfaceCodes. 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 toothCode nonempty, a nonempty unique list of single uppercase ASCII letters, and preserve their order after toothCode:.1

Input fieldMeaning and unitsAccepted input
toothCodeTooth CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
surfaceCodesNonempty unique single uppercase ASCII letters in supplied order; no dental vocabulary lookup.Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "toothCode": "16",
    "surfaceCodes": [
      "M",
      "O"
    ]
  },
  "output": {
    "token": "16:MO"
  }
}

Limitations and assumptions

  • Any uppercase letter passes; no dental surface vocabulary, notation system, tooth identity or chart validity is verified.
  • 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 original chart, observation and reprocessing records with the complete scoring or controlled workflow. Keep denominator, missingness and date conventions explicit; local arithmetic does not determine oral-health status, appropriate recall intervals or readiness for care.

References

  1. Calculation and input contract: dental-hygiene/tooth-surface-notation-token — tool.io

Similar or alternative tools