Skip to content

Main content

Terminology Code System Token Tool

Build an unambiguous exact terminology identity key without resolving or interpreting a code system.

Loading tool…

Description

Return a JSON-array key with version or null when unknown.

Clinical exchange formats use exact delimiters, character grammars, and scoped identifiers. A local token check addresses one syntax condition and can succeed without validating a complete message or its clinical meaning.

Return a JSON-array key with version or null when unknown.

When to use this tool

Use Terminology Code System Token when you need one bounded spelling, delimiter, or identifier component.

How to use the tool and how it works

  1. Enter system, code, version, versionKnown. 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 key. Use the output convention below.

Require nonempty system and code and a nonempty version only when versionKnown. Return a JSON-array key with version or null when unknown.1

Input fieldMeaning and unitsAccepted input
systemSystemRequired. Text; maximum UTF-16 length 8192.
codeCodeRequired. Text; maximum UTF-16 length 8192.
versionVersionRequired. Text; maximum UTF-16 length 8192.
versionKnownVersion KnownRequired. Boolean.
Output fieldInterpretationReturned shape
keyKeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "system": "sys",
    "code": "A1",
    "version": "v2",
    "versionKnown": true
  },
  "output": {
    "key": "[\"sys\",\"A1\",\"v2\"]"
  }
}

Limitations and assumptions

  • Unknown version differs from a known version string; system authority, terminology membership, code validity, and clinical meaning are not 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 the relevant full standard, implementation profile, and validated parser when interoperable or clinical record validity matters.

References

  1. Calculation and input contract: health-informatics/terminology-code-system-token — tool.io

Similar or alternative tools