#81 PipeParser generates wrong segment name

[Anonymous]

We use the PipeParser to create an HL7 message from the following text:

MSH|...
SPM|1|...
SPM|2|...

We modify the HL7 message and convert it back to a string using the same PipeParser:

MSH|...
SPM|1|...
SPM2|2|...

The second SPM segment name is transformed into SPM2!
What is the cause for such behaviour?

[Nobody/Anonymous]

Logged In: NO

We have encountered the same issue with our QRI segment where the name of the segment seems to have a counter on appended onto it.
MSH|...
PID|1|...
QRI|...
PID|2|...
QRI2|...
etc.