hl7 message test fine in DTL, but the message is not transformed correctly in end to end test

Question

Question

Has anybody encountered this before?

I did a very usual hl7 adt transformation DTL, but it is with a customized schema, like ADT_ALL, it is a structure that tries to cover all the ADT schema scenario so we can use 1 type for all ADT messages.

the DTL tests fine in DTL test, with all the segment transformed correctly, but once I put it to test, to send message through source and the message after transformation can only go to MSH, EVN, but won't transform other segment like PID etc.

Originally I was suggested that in my DTL I didn't loop through all the (), so I changed everything to loop through very thoroughly. but the result is still same. I do not quite understand why it works in DTL test but it won't work once I put it through a rule and DTL.

we are using healthshare cloud

Any suggestions?

Thank you

Product version: HealthShare 2024.1

Discussion (5)2

Log in or sign up to continue

score 0 · Answer 1 · 2024-11-21T15:42:25-05:00

Check the settings on your inbound HL7 service and make sure that Message Schema Category is set to your custom schema (ADT_ALL).

score 0 · Answer 2 · 2024-11-21T15:59:25-05:00

I didn't state it correct. so the schema is 2ADT, in this schema, we have ADT_A01, etc, and we added one as ADT_ALL, so in my dtl, I used this ADT_ALL in schema 2ADT, and the incoming service is setup to use 2ADT schema, so when the message coming in with actual A04, A05, etc. it should be treated as ADT_ALL in dtl. but however , the test in DTL gets correct transformation but it won't in the whole process when I test with the service, rule and dtl and operation.

score 0 · Answer 3 · 2024-11-21T16:45:03-05:00

Marc Mundt · Nov 21

In the message trace for the whole process, what is the value of DocType in the Body tab?

0 0

score 0 · Answer 4 · 2024-11-21T17:46:23-05:00

in the whole trace, the message itself is ADT_A03, doctype is 2ADT: ADT_A01 before the DTL, after it is showing as 2ADT:ADT_ALL, so how does the whole process decide which doctype it should be?

score 0 · Answer 5 · 2024-11-22T11:47:07-05:00

I think I found the reason, we made this super message structure ADT_ALL to cover the A01, A17, A18 etc. pretty cover all type, but the incoming message strucutre is A01 which is different than this super structure ADT_ALL, so the process cannot recognize it, I changed the A01 to use ADT_ALL structure in schema and it worked.