0
0
Question Patty Aguirre-Romero · Nov 14, 2024

Having problems passing-through an X12 message. What am I missing?

#InterSystems IRIS for Health

What settings do I need to just passthrough an X12 messages from a BS to BO and out the BO without modifying the message?

Currently, we are receiving the X12 messages but, it seems Iris is modifying it by "hiding" some segments like the ISA segment. The message goes out the BO modified and it doesn't reach its destination. Since I just want to pass it through, there is no BP, DTL, or Rule processing the message. Message is received by the BS and sent directly to the BO. 

My current settings:

  1. The BS is set as
    • TCP with Class Name: EnsLib.EDI.X12.Service.TCPService
    • Adapter Class Name: EnsLib.EDI.X12.Adapter.TCPInboundAdapter
    • Doc Schema Category: HIPAA_5010
    • Batch Handling: Individual
    • Framing: None
Product version: IRIS 2023.1
$ZV: IRIS 2023.1.3
Discussion (0)0
Log in or sign up to continue

Comments

Marc Mundt · Nov 15, 2024

Try changing Batch Handling to "Whole Batch".

0
Patty Aguirre-Romero  Nov 19, 2024 to Marc Mundt

Hi Marc,

I tried "Whole Batch" and got the opposite from before. With this setting, the message is showing ISA header and 2 more segments (GroupDocsRef and IEA). It is "hiding" the rest. It is still not passing through the message.  

Message is changed to (1st picture). Clicking on Group documents "110" a second Group batch opens (2nd picture)

After clicking on TransactionSet documents "111", another section opens with the rest of the message. 

Is it possible to just pass through the message without hiding those sections? What settings do I need to do that?

Would Framing matter? It was set up as "Flexible" when Batch Handling was set up as "Whole Batch". 

Thank you!

0
Jeffrey Drumm  Nov 19, 2024 to Patty Aguirre-Romero

I used Single-Session batch and used a business process/router to send only the Interchange DocType to the operation. The Group and Transaction sets within are referenced from the Interchange and are automatically re-assembled by the operation.

0
Patty Aguirre-Romero  Nov 21, 2024 to Jeffrey Drumm

@Jeffrey Drumm  and @Marc Mundt 
Thank you for your suggestions!

This setting allowed the X12 message to go to Epic... Batch Handling was set to "Whole Batch" and Framing on the BO to "Epic02/03" (Framing in BS was already set to "Flexible). 

Another issue that came up is the message is appearing in Epic with newlines after each segment. The Raw Contents in Iris Message Viewer (in the BS and BO) show the message without extra line in between segments. Does this mean Iris is sending the message without extra lines? Is there a setting in Iris that is adding the extra lines? BS setting Tolerate Newlines is true. 

Thanks again!
 

0
Jeffrey Drumm  Nov 21, 2024 to Patty Aguirre-Romero

Sounds like a separators issue. I set that as empty on both the service and operation, which assumes the messages will be formatted with whatever separators are indicated in the ISA segment.

0
Patty Aguirre-Romero  Nov 25, 2024 to Jeffrey Drumm

Thanks Jeffrey! I removed "\n" from Separators and resolved the issue. 

0
Marc Mundt  Nov 20, 2024 to Patty Aguirre-Romero

This is just how the message viewer displays it. But is the message complete when the business operation writes it to the file?

0