HL7 Variant message types

This topic has 1 reply, 2 voices, and was last updated 15 years, 5 months ago by Sergey Sevastyanov.

Creator

Topic
June 22, 2009 at 2:02 pm #50995
Roy Trombly
Participant
Can anyone explain this?

We have an HL7 2.3 variant with a RAS message type defined and also RAS_O01 type defined. The message types have different structures. We have built a translator configured to use the RAS message type and all looks well in the configurator and the translator compiles. However, when a message of type RAS^O01 goes through it applies the RAS_O01 structure. Is this intended behavior?

It makes sense to me that the RAS_O01 is a subtype of RAS, however, it seems peculiar that the “compiled” translator would use a variant other than the one it was configured to use.
Creator

Topic

Viewing 0 reply threads

Author

Replies
- July 2, 2009 at 5:22 pm #68328
  Sergey Sevastyanov
  Participant
  Roy,
  
  If I remember correctly it will use whatever you have in MSH-9. As you have there RAS^O01 it will use RAS_O01 variant.
  
  I use trxId proc that returns for some of my messages types like ORU_R01_LM, ORU_R01_MB, etc
  
  But I still have to use HL7 variant for ORU_R01. So in route details I can route messages based on returned trxId but not in translation
  
  Check this thread that I started a while ago – I was the same confused as you are:
  
  ~~<a href="~~https://usspvlclovertch2.infor.com/viewtopic.php?p=13292&highlight=#13292″ class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?p=13292&highlight=#13292
  
  Hope that helps
  
  Thanks
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.