Added encoder for HL7 messages (pipehat format) #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cts to byte slices. The Encoder is constructed with a slice of hl7.Segment structs, one of which must be a valid message header (MSH) segment. The delimiter characters are parsed from the MSH segment and used to encode all of the segments into a []byte.
|
Could you change the API to be like: So it more closely matches how the stdlib does it and how hl7 decoding works. |
|
No problem! Let me know if you see any other issues with this PR. |
kdar
added a commit
that referenced
this pull request
Mar 14, 2015
Added encoder for HL7 messages (pipehat format)
|
Thanks for this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added hl7.Encoder type and hl7.Marshal() function to convert HL7 objects to byte slices. The Encoder is constructed with a slice of hl7.Segment structs, one of which must be a valid message header (MSH)
segment. The delimiter characters are parsed from the MSH segment and used to encode all of the
segments into a []byte.