CDCgov
[SPIKE] Identify solution to combine MSH fields and batch headers into 1 setting
User Story
As a receiver, I want the batch header to accurately reflect the information received in the MSH segment.
Description/Use Case
Move 4.1.2, 4.1.3, 5.1.2, 5.1.3 fields over to the BHS and FHS segments
MSH fields are set in receiver transforms, whereas Batch Headers are set in receiver settings.
Risks/Impacts/Considerations
Right now, these two areas/fields can be out of sync if onboarding engineers are not careful and do not change the values in both areas. But if they were to combine into 1 setting, it would eliminate this risk of being out of sync.
Adding these blankly will affect all users in production, so we may want to create a setting or something around this to only add them for specific receivers.
Dev Notes
This is done in HL7MessageHelpers line approx 53-59
Acceptance Criteria
- [ ] It is identified IF MSH fields and batch headers can be consolidated into 1 setting
- [ ] If they can, a solution is aligned with tech lead that accomplishes this
- [ ] If tech lead approves solution, follow-on implementation ticket(s) are created
Engagement has implemented a workaround for this with AL. We will put this ticket in the backlog for consideration later in FY25.
This will need a SPIKE to Determine if batch files can contain messages from multiple senders.
@victor-chaparro will update as more information is learned.