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

W-16778879 HL7 Connector 4.3.0 Release #2698

Open
wants to merge 4 commits into
base: latest
Choose a base branch
from
Open

Conversation

sms-dchen
Copy link
Contributor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

@tasmoore tasmoore changed the title HL7 Connector 4.3.0 Release W-16778879 HL7 Connector 4.3.0 Release Sep 18, 2024
|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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor

@tasmoore tasmoore left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see comments

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

Successfully merging this pull request may close these issues.

2 participants