arnejduranovic
commented
2 weeks ago Marking as blocked: Waiting on ETOR-TI team to provide exact requirements for the HL7v2 message for this use case.
Open arnejduranovic opened 2 weeks ago
arnejduranovic
commented
2 weeks ago Marking as blocked: Waiting on ETOR-TI team to provide exact requirements for the HL7v2 message for this use case.
User Story
As a sender of Lab Orders using the EPIC system, I require ReportStream's submission API to return an HL7v2 formatted response instead of the normal JSON, so that the EPIC system can properly acknowledge the submission was successful.
Description/Use Case
Certain senders may require RS response objects to be in a certain format, which may potentially limit the information RS can provide. This ticket is specifically asking for a HL7v2 formatted message to support epic systems sending lab orders. It is likely this HL7v2 message will be the following: https://hl7-definition.caristix.com/v2/HL7v2.5.1/Segments/MSA
Risks/Impacts/Considerations
Dev Notes
The submission API in RS returns a JSON object with a lot of properties, and we may not need to port all of them to the new message type. This is pending requirements.
Epic has indicated they are willing to populate “x-application” with a value of “hl7-v2+er7” to indicate to RS it should return an HL7v2 message in the body of the response. Another option is we can create a new sender setting that indicates what format senders want their responses it.
Acceptance Criteria