-
Notifications
You must be signed in to change notification settings - Fork 127
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
W-16778879 HL7 Connector 4.3.0 Release #2698
base: latest
Are you sure you want to change the base?
Conversation
|valueLengthErrorFail="true" |Fail when a value length is outside an allowed range | ||
|wrongSegmentsRepeatsFail="true" |Fail when there are too many repeats of a segment | ||
|wrongValuesRepeatsFail="true" |Fail when there are too many repetitions of a value | ||
|enforceERRSegmentRepeatability="true"|Enforces the ERR Segment repeatability (count) in the Acknowledgment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|enforceERRSegmentRepeatability="true"|Enforces the ERR Segment repeatability (count) in the Acknowledgment. | |
|enforceERRSegmentRepeatability="true"|Enforces the ERR Segment repeatability (count) in the acknowledgment. |
|
||
** CR | ||
** LF | Value for the segment terminator. | CR | | ||
| Enforce Acknowledgment ERR Segment repeatability a| Boolean a| Whether to enforce the ERR Segment repeatability (count) in the Acknowledgment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Enforce Acknowledgment ERR Segment repeatability a| Boolean a| Whether to enforce the ERR Segment repeatability (count) in the Acknowledgment: | |
| Enforce Acknowledgment ERR Segment repeatability a| Boolean a| Whether to enforce the ERR Segment repeatability (count) in the acknowledgment: |
** LF | Value for the segment terminator. | CR | | ||
| Enforce Acknowledgment ERR Segment repeatability a| Boolean a| Whether to enforce the ERR Segment repeatability (count) in the Acknowledgment: | ||
|
||
* If `true` and the ERR segment count is not 1, errors will be added to the ERR-01 (ELD) in a single ERR segment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* If `true` and the ERR segment count is not 1, errors will be added to the ERR-01 (ELD) in a single ERR segment. | |
* If `true` and the ERR segment count is not 1, errors are added to the ERR-01 (ELD) in a single ERR segment. |
| Enforce Acknowledgment ERR Segment repeatability a| Boolean a| Whether to enforce the ERR Segment repeatability (count) in the Acknowledgment: | ||
|
||
* If `true` and the ERR segment count is not 1, errors will be added to the ERR-01 (ELD) in a single ERR segment. | ||
* If `false`, every error will be added to the ERR list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* If `false`, every error will be added to the ERR list. | |
* If `false`, every error is added to the ERR list. |
|
||
The generated ACK messages have MSH data set up for sending back to the sender of the original message, so you don't need to change anything in the data to perform the send. | ||
|
||
If you include an ACK message schema in your configuration, that schema is used to both receive and generate ACK messages, you also need to specify include the `eventMessageMap` to use the ACK structure in the parser. If you don't specify an ACK schema, the standard `hl7/v2_5_1/ACK.esl` schema default is used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you include an ACK message schema in your configuration, that schema is used to both receive and generate ACK messages, you also need to specify include the `eventMessageMap` to use the ACK structure in the parser. If you don't specify an ACK schema, the standard `hl7/v2_5_1/ACK.esl` schema default is used. | |
If you include an ACK message schema in your configuration and that schema is used to receive and generate ACK messages, you must specify the `eventMessageMap` value to enable the ACK structure in the parser. If you don't specify an ACK schema, the configuration uses the standard `hl7/v2_5_1/ACK.esl` schema by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see comments
Writer's Quality Checklist
Before merging your PR, did you: