HL7 TX Text Data
HL7 datatype components TX components from HL7 v2.5.1 Hide components
These are the generated components for the version selected at the top of the page. The article stays practical, and this panel follows the chosen HL7 version.
Components
TX is text data. It is for longer plain text values where formatting is not the main point. Even plain text still needs HL7 escaping when it contains delimiters.
In this guide, TX appears in ED, JCC, PRL, RFR, SPS, TQ and related fields. That used-by list is a good reality check: the datatype is only half the story, and the field that uses it tells you the workflow.
The component panel above is expanded by default because most datatype pages are used as quick lookup pages. Start there for the exact HL7 v2.5.1 shape, then use the notes below for the practical gotchas.
The Value
TX is primitive in this v2.5.1 reference data, so there are no caret-separated components to expand. The whole field value is the datatype value. That makes it quick to read, but it also means validation has to happen at the field level: the datatype will not give you extra components to explain what the value means.
Practical Notes
Text still has to survive HL7 delimiters. If the source value can contain |, ^, ~, &, or a backslash, encode it before putting it into the message. Integration Soup and the HL7 parser helpers include HL7Encode and HL7Decode for that exact kind of cleanup.
In HL7 Soup Web, click a field that uses TX to see the field meaning beside the raw value. For primitive datatypes, that quick field-level check is usually more useful than looking for components that do not exist.
Official and Reference Notes
For formal reference, compare the generated HL7 v2.5.1 panel above with the HL7 v2.5.1 datatype list and the HL7 Terminology data type code system. Local implementation guides can narrow allowed values, tables, and component usage.