HL7 v2 NTE-3 Field Guide: Comment Values and Common Mistakes
NTE-3 is the whole point of the segment - the actual note text - and it is also the field most likely to break a parser that was only ever tested against short, tidy sample values.
NTE-3 holds the free-text content of the note. Unlike most HL7 v2 fields, it is meant to carry unstructured prose rather than a coded or formatted value, it can repeat within a single NTE segment to represent multiple lines of the same note, and in practice it can run far longer than the short examples most sample messages use.
What this field contains
Example
A synthetic NTE segment carrying a longer free-text comment following PID, with a fabricated patient and reminder preference.
Where this trips people up
Test messages built by hand almost always use short, grammatically tidy comments, so parsers that truncate long text, mishandle embedded punctuation, or choke on a comment that happens to contain a pipe or caret character never get caught until a real note trips over them. Multi-line notes split across repeating NTE segments are another common gap - if your test data never generates a comment long enough to need a second or third NTE segment for the same note, the logic that reassembles them into one block of text is running blind in production.