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
{{ message }}
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently LFH returns a message body that does not comply with some industry standards such as HL7 message protocol. This issue can be broken down to address different protocol in a case-by-case basis.
As an example, HL7v2 requires that messages that are successful (or failed) be returned in HL7 message format such as ACK response. This would allow for better compatibility with existing systems that leverage those responses in order to perform audit or retry logic etc.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Implement protocol responses for each route as appropriate.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
None. Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently LFH returns a message body that does not comply with some industry standards such as HL7 message protocol. This issue can be broken down to address different protocol in a case-by-case basis.
As an example, HL7v2 requires that messages that are successful (or failed) be returned in HL7 message format such as ACK response. This would allow for better compatibility with existing systems that leverage those responses in order to perform audit or retry logic etc.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Implement protocol responses for each route as appropriate.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
None.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: