Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow option to specify the end-of-segment character in the LLP listener #53

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 3 comments
Milestone

Comments

@rbeckman-nextgen
Copy link
Collaborator

The HL7 spec expects CR (ascii 13) characters to deliminate segments of an HL7 message, however certain vendors only deliminate thier lines with \n (ascii 10). Mirth should stay compatabile with these vendors by allowing the option to specify the end of segment encoding character.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-29
Reporter: chrisl
Created: 2006-09-12T14:05:54.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the 1.2.0 milestone May 11, 2020
@rbeckman-nextgen
Copy link
Collaborator Author

Priority updated due to client need.

Imported Comment. Original Details:
Author: chrisl
Created: 2006-09-14T02:20:00.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

The property "segmentEnd" has been added to the TCP connector. The LLP listener and sender panels now need a field to set this property on the connector. The format should be the same as the other protocol encoding properties.

Imported Comment. Original Details:
Author: geraldb
Created: 2006-09-21T07:58:32.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

Added the requested feature.

Imported Comment. Original Details:
Author: brendanh
Created: 2006-09-21T17:12:07.000-0700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant