I believe that the HL7 2.3.1 standard requires MSH-9-2 to exist. However, we have a not-to-be-named vendor who sends us messages with one MSH segment and one Z-segment but doesn't populate MSH-9-2 (they do populate MSH-9-1 with "ZPM".
I defined the message in studio in a Custom.HL7 file thusly:
<MessageType name='ZPM' structure='ZPM'/>
<MessageStructure name='ZPM' definition='base:MSH~ZPM'/>
<SegmentStructure name='ZPM' description='floor stock'>
<SegmentSubStructure piece='1' description='Transaction Type' length='0' required='1' ifrepeating='0'/>
<SegmentSubStructure piece='2' description='MedStation System' length='0' required='1' ifrepeating='0'/>
... 21 other segment sub structure definitions ...
<SegmentSubStructure piece='24' description='Transaction Time' length='0' required='1' ifrepeating='0'/>
</SegmentStructure>
The DTL script runs fine when testing the transformation from within Studio. However, when running in our development namespace we get the following error in the HL7 message router event log:
" 0 F <Ens>ErrGeneraló Error from Validation : ERROR <Ens>ErrGeneral: Not forwarding message 5203048 with message body Id=6683363, Doc Identifier=EPL_05022008050643, SessionId=5203048 because of validation failure: ERROR <Ens>ErrGeneral: Message has no DocType set : zOnError+7^EnsLib.HL7.MsgRouter.RoutingEngine.2:ENSHHDEV"
The message routing rule editor rule for this message does have a Doc Type defined - it is "ZPM".
Question: is the above error coming from the fact that there is no trigger event or do I need to look elsewhere? Is it is coming from the lack of an event tripper, is there anyway, short of the vendor populating MSH-9-2, to allow the router to parse the message and run the routing script?
Thanks,
Jim Dolson
Holland Hosital
Holland, MI (where the tulips are in full bloom)