Non-Standard Z-Segment Detected
A segment whose ID starts with Z was found. Z-segments are reserved by HL7 for local, site-specific use and cannot be validated against the standard spec because there is no published definition.
HL7v2 · Info
The error
Non-standard Z-segment detectedWhy it happens
A trading partner added custom data (ZPD, ZIN, and similar). This is legitimate and expected, which is why the validator reports it as information rather than an error.
How to fix it
No fix is required if the Z-segment is intentional. To validate its contents, supply a custom segment definition or deviation rule so the platform knows the expected fields. Otherwise it is correctly left unvalidated.
Example
The snippet below triggers the error:
ZPD|1|CUSTOM-VALUE|EXTRA-LOCAL-DATAThe corrected version:
ZPD|1|CUSTOM-VALUE|EXTRA-LOCAL-DATAFrequently asked questions
Are Z-segments allowed in HL7v2?
Yes. The HL7 standard explicitly reserves the Z prefix for local extensions. They are valid to send; the validator simply cannot check their structure without a custom definition.