You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been testing and using your package and it's excellent! We really appreciate your effort on it. We would like to know if it supports Z segments, and if not, how do we customize hl7 messages including Z segments? As far as I've tested it, it doesn't handle Z segments but it doesn't invalidate it either, so after decoding, there's no trace of it in the response.
Thanks in advance!
PS: Also would love to know if you are planning to implement this feature in the near future.
The text was updated successfully, but these errors were encountered:
Of note, the hl7 decoder/encoder is separate from the segment definition. Is the Z segment a decoder/encoder request or a segment package definition change request?
Okay, I did a quick search. It appears Z-Segments refer to user defined segments that can appear anywhere. In this case, I would encurage you to copy one of the segment definition packages in the repository, edit as required, and use.
Were you thinking of something else that would not require this? Please sketch roughly what you are thinking.
Hi there!
We have been testing and using your package and it's excellent! We really appreciate your effort on it. We would like to know if it supports Z segments, and if not, how do we customize hl7 messages including Z segments? As far as I've tested it, it doesn't handle Z segments but it doesn't invalidate it either, so after decoding, there's no trace of it in the response.
Thanks in advance!
PS: Also would love to know if you are planning to implement this feature in the near future.
The text was updated successfully, but these errors were encountered: