Skip to content

Main content

HL7 Person Name Family Given Component Token Tool

Split explicit HL7 name components without decoding delimiter escapes or choosing a culturally universal display order.

Loading tool…

Description

Return the first as family, second as given, and all remaining as additional.

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 the first as family, second as given, and all remaining as additional.

When to use this tool

Use HL7 Person Name Family Given Component Token when you need one bounded spelling, delimiter, or identifier component.

How to use the tool and how it works

  1. Enter encoded, separator. 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 family, given, additional. Use the output convention below.

Require a one-UTF-16-unit separator and at least two split components. Return the first as family, second as given, and all remaining as additional.1

Input fieldMeaning and unitsAccepted input
encodedEncodedRequired. Text; maximum UTF-16 length 8192.
separatorSeparatorRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
familyFamilyRequired. Text; maximum UTF-16 length 8192.
givenGivenRequired. Text; maximum UTF-16 length 8192.
additionalAdditionalRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
json
{
  "input": {
    "encoded": "Smith^Alex^J",
    "separator": "^"
  },
  "output": {
    "family": "Smith",
    "given": "Alex",
    "additional": [
      "J"
    ]
  }
}

Limitations and assumptions

  • Empty components are retained and HL7 escaping and nested name structure are not decoded; no identity, cultural name order, or complete person-name validity is inferred.
  • 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/hl7-person-name-family-given-component-token — tool.io

Similar or alternative tools