hcix12splitinterchange – anybody get argument to work

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf hcix12splitinterchange – anybody get argument to work

  • Creator
  • #50613
    Jim Kosloskey

    Cloverleaf(R) 5.6.

    The splitX12 package indicates that one can specify GS or ST as an argument in order to control whether the GS set of the envelope is in the metadata or the message.

    By default it uses GS.

    The X12 variant for the 997 message (and for that matter the 278) does not have the GS/GE segment set defined and so the usage should be ST for splitX12.

    The only supplied proc I see for deploying the slpitX12 package is hciX12split interchange. That proc invokes splitX12 with two arguments. The message handle and the mode.

    I do not see where the is an opportunity for recognition of an argument for splitX12 inside hcix12splitinterchange.

    Has anyone got this to work?

    Is this a flawed version of hciX12splitinterchange or are we expected to modify it to our needs?

    What am I missing here?


    email: jim.kosloskey@jim-kosloskey.com

Viewing 4 reply threads
  • Author
    • #66795
      Jim Kosloskey

      Okay nobody responded and I need to move forward.

      The proc hcix12splitinterchange functions but when the GS and GE segments need to be removed from the message and the GS fields placed in the metadata USERDATA field (as in the case of the 278 and 997 messages in the 51010 variant), there is no way to tell the X12lib package event split X12 to treat the GS and GE segments as envelope segments (the ST argument as specified in the Cloverleaf(R) User documentation).

      This causes segment errors to appear in the log. The messages still process through an Xlate because the segments are stripped. BUT it means the GS fields are not available to the Xlate AND there are errors in the log. We do not tolerate unnecesary errors in the Process log so that is an issue to us as well.

      So I copied the distributed proc and created a new proc to allow for a user provided argument specifying ST or GS which is passed to the X12lib::splitX12 event – and all is well.

      Rob Abbott if you see this message, I think this is a bug in the supplied proc but that is for HealthVision to decide.

      Suffice to say I could not see how to get the provided proc to behave as advertised or desired without modification.

      I hope this is  of some help. I will also post this on the UHC thread of discussion since it is germain to that discussion as well.

      email: jim.kosloskey@jim-kosloskey.com

    • #66796
      Bob Richardson


      We have an X12 interface that splits up the transactions based on the ST segment.  Here is the code snippet:

              # X12lib returns one msg handle per transaction (ST/SE)

              # we should only get one ST/SE per inbound msg, but

              # this can handle many, just in case

              # The ISA, IEA, GS, GE segments are saved in USERDATA.


                 foreach STmh [X12lib::splitX12 $mh ST] {

                     lappend dispList “CONTINUE $STmh”

                 } ;# end of foreach STmh

      I don’t know if this is what you are looking for in your problem but thought I would offer it up for consideration.


    • #66797
      Jim Kosloskey



      The command you have ‘[X12lib::splitX12 $mh ST] ‘ in the Cloverleaf(R) provided hciX12splitinterchange is ‘[X12lib::splitX12 $mh $mode] ‘ where $mode is the mode argument from the proc invocation that contains ‘start’, ‘run’, ‘time’ , etc.

      Obviously the X12lib::splitX12 event will treat any of those like they are GS and not strip the GS and GE segments off and place the GS fields in the metadata.

      That is what I think is the bug in the provided proc.

      Obviously you have had to make some accomodation as well (or maybe you never even tried the hciX12splitinterchange proc).

      Thanks again I appreciate the input – it is a sanity check.

      email: jim.kosloskey@jim-kosloskey.com

    • #66798
      Charlie Bursell


      I will be back from Thailand next week.  If you can send me an example message and more detail on the problem.  If I can verify it, I will submit a bug report and make the necessary changes to the proc.

    • #66799
      Jim Kosloskey

      Thanks Charlie.

      I hope you got in some golf in Thailand. I hear they have some very nice (but expensive) courses there.

      I am leaving on vacation 2/13/2009 for 2 weeks. Being next week is my last week and only 4 work days, I may not get the info to you next week.

      Have a safe trip back.

      email: jim.kosloskey@jim-kosloskey.com

Viewing 4 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
Topic Tags