Dear,
Because this is my first action on the official SAP healthcare industry Community Network homepage, let me introduce myself.
I'm a SAP Solution Architect with a strong focus on SAP XI/PI/PO, Solution Manager and B2B Integration. You can find more on Dimitri Sannen
Currently, I'm working in a hospital within the integration team.
Off course, HL7 is omnipresent and I'm using the IAH adapter a lot.
In that area, I have a question.
We have a scenario where we process OML 021 messages and the receiver of that message sends back an ORL O22 message.
Everything has been set up on our SAP PI 7.11 system, using HL7 v2.4 and the IAH adapter.
Before we actually want to perform E2E tests, we did some separate tests, using 7Edit Professional, to mimic HL7 messages.
Processing OML O21 is going fine, but when we want to process ORL O21, we face strange behavior.
E.g this message is picked up by a sender IAH communication channel:
MSH|^~\&|xxxxx||yyyyy||20140114090000||ORL^O22|201430011025140001|P|2.4||
MSA|AA|
This message is NOT processed:
MSH|^~\&|xxxxx||yyyyy||20140114090000||ORL^O22|201430011025140001|P|2.4||
MSA|AA|123456
So, we think the problem resides within the MSA segment, field Message Control ID.
This field is defined as being required and our Conversion Agent processes the 2 messages above, with and without that field being filled in.
So, we believe the problem is within the IAH adapter or the configuration of the sender communication channel
Some questions:
- can we test ORL messages separately, using 7Edit, or should there be some how a link with an OML?
- is there any check performed on SAP PI when an ORL message is coming in?
Thanks a lot.
Kind regards,
Dimitri