Description
Map the concatenated order to field, component, repetition, escape, subcomponent, and optional truncation roles.
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.
Map the concatenated order to field, component, repetition, escape, subcomponent, and optional truncation roles.
When to use this tool
Use HL7 Delimiter Role Label when you need one bounded spelling, delimiter, or identifier component.
How to use the tool and how it works
- Enter character, fieldSeparator, encodingCharacters. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read role, recognized. Inspect recognized before interpreting the associated values.
Require one-unit character, printable ASCII fieldSeparator, four or five encodingCharacters, and distinct configured delimiters. Map the concatenated order to field, component, repetition, escape, subcomponent, and optional truncation roles.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| character | Character | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 1. |
| fieldSeparator | Field Separator | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 1. |
| encodingCharacters | Encoding Characters | Required. Text; minimum UTF-16 length 4; maximum UTF-16 length 5. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| role | Role | Required. Text; maximum UTF-16 length 8192. |
| recognized | Whether the token matches the supplied vocabulary or supported mapping. | Required. Boolean. |
{
"input": {
"character": "^",
"fieldSeparator": "|",
"encodingCharacters": "^~\\&"
},
"output": {
"role": "component",
"recognized": true
}
}Limitations and assumptions
- The configured mapping is inspected literally; an unmapped character is not an error and no complete HL7 message or version-specific profile is validated.
- 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
Similar or alternative tools
- HL7 Repeat Escape Unescape One Token
Decode F, S, R, T, or E as field, component, repetition, subcomponent, or escape delimiter.
- HL7 Segment Field Number Offset
Return fieldNumber for ordinary split arrays; for MSH return fieldNumber-1 except separator MSH-1, represented by splitIndex -1 and separatorField true.