Closed arnejduranovic closed 11 months ago
Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jalbinson @JessicaWNava @jimmyfagan @thetaurean
Please add your planning poker estimate with Zenhub @JFU-NAVA-PBC
The msg_1_hci.hl7 message gets the following error when I submit it as is: Required field missing: A datatype for OBX-5 must be specified in OBX-2. FHS, BHS, BTS, and BTS all added to the message as well.
Differences documented here: https://docs.google.com/document/d/1i4dMY3NCZ5FSR9M4XUVjYOk5_OdqT1LhnnX6TP4VvC0/edit?usp=sharing
Once I grabbed form master, all of the differences not in OBR were taken care of or made sense. (Kalish is goignt o take care of OBR in his PR)
User Story
As a sender to ReportStream, I want to ensure all my messages are transmitted to the appropriate sender losslessly.
Description/Use Case
We have received a set of sample messages from the sender. This folder includes:
moreSampleResults_20231115.txt
- the original file sent from the sender. This contains multiple HL7v2 messages pasted in a single file. The messages come in pairs, labelled "Original" and "Transformed". Original means the messages was sent by ProPhase to HCI, and Transformed means the message HCI received was updated to follow the HL7v2 NIST ELR spec and is what ReportStream will receive. The HL7v2 messages have been broken out of this file into their own separate files, labeled "prophase" and "hci" respectively.msg_<n>_<hci/prophase>.hl7
- a standalone HL7 message. RS should only have to process the messages from hci, the prophase ones are there for reference only.We should run all the HCI messages through the pipeline and compare that the output message from RS is not missing any important data that exists in the input message. We should also document any differences between the input and output and fix them if it makes sense. All differences should be documented in a spreadsheet or file in the folder containing the sample messages
Risks/Impacts/Considerations
Dev Notes
Acceptance Criteria