Description
Qualify an explicit oral-surgery tooth/site code by its notation source.
Oral-surgery records link sites, containers, tray counts, guide versions and printed dates. Matching item counts does not establish correct or sterile items, while a printed-date margin is only one record check. Supplied labels and dates do not establish surgical readiness, specimen identity, healing or an appropriate clinical procedure.
Qualify an explicit oral-surgery tooth/site code by its notation source.
When to use this tool
Use Oral Surgery Tooth Site Code when you already have procedureId, toothSiteCode, notationSource and need to qualify an explicit oral-surgery tooth/site code by its notation source.
How to use the tool and how it works
- Enter procedureId, toothSiteCode, notationSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter procedureId, toothSiteCode, notationSource 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 field | Meaning and units | Accepted input |
|---|---|---|
| procedureId | Procedure Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| toothSiteCode | Tooth Site Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| notationSource | Notation Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"procedureId": "OS17",
"toothSiteCode": "SITE3",
"notationSource": "Notation A"
},
"output": {
"token": "[\"OS17\",\"SITE3\",\"Notation A\"]"
}
}Limitations and assumptions
- The result records supplied values without anatomical lookup. 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 actual tray, packaging, specimen labels and versioned procedure records when checking readiness or traceability. Review storage and handling evidence as well as printed dates; matching counts and date margins alone do not establish safe use.
References
Similar or alternative tools
- Oral Surgery Guide Version Label
Record an explicit oral-surgery guide identifier and version.
- Oral Biopsy Specimen Bottle Code
Associate explicit oral-biopsy specimen, bottle, and site identifiers.