HL7 to X12 interface issue

Homepage Clovertech Forums Cloverleaf HL7 to X12 interface issue

  • Creator
    Topic
  • #116125
    Belaid Akharaze
    Participant

    I have an HL7 to X12 interface to Epic I can’t get to work. Using 005010/271 and have added ISA/GS/GE/IEA to the variant. CL shows msgs leave the OB thread but nothing showing in Epic. Created internal conn to test using tcpip and getting this in the log for recv conn.

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  00 00 03 72  49 53 41 2a  |…rISA*|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  30 30 2a 31  39 35 31 30  |00*19510|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  30 20 20 20  20 2a 30 31  |0    *01|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  2a 4d 4b 36  51 55 4e 4b  |*MK6QUNK|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  57 5a 31 2a  5a 5a 2a 35  |WZ1*ZZ*5|

     

    End:

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  34 2a 31 37  37 33 31 33  |4*177313|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  7e 47 45 2a  31 2a 31 37  |~GE*1*17|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  37 33 31 33  7e 49 45 41  |7313~IEA|

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  2a 31 2a 31  37 37 33 31  |*1*17731|

    [tcp :read:WARN/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data received.  Enable tcp/read/info/0 to see detail

    [tcp :read:DBUG/1:I_temp_x12_tcp1:03/26/2020 11:48:42] Raw read with length 32768

    [tcp :read:DBUG/1:I_temp_x12_tcp1:03/26/2020 11:48:42] Wanted 32768; got -1

    [tcp :read:INFO/0:I_temp_x12_tcp1:03/26/2020 11:48:42] Nonmessage data:  33 7e                     |3~|

    [tcp :read:DBUG/1:I_temp_x12_tcp1:03/26/2020 11:48:42] pdTcpip Server Thread Read Done

     

    Any help is appreciated.

    Thanks

Viewing 2 reply threads
  • Author
    Replies
    • #116126
      Jim Kosloskey
      Participant

      You cannot have the envelope segments (ISA, etc.) in the variant.

      Cloverleaf expects that information to  be in the metadata of each message.

      I have done this before and have some procs that can assist (assuming Xlate involved here).

      Too involved to discuss on this forum – email me and I will assist.

      email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

    • #116198
      Belaid Akharaze
      Participant

      Thanks Jim, I removed the headers from the variant and used the proc you provided with the arguments along with hciX12buildinterchange. I started getting a different error “invalid command name X12lib::buildISA isa_array”.

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–]        result  = ”

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–]        errorInfo: ‘

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–] invalid command name “X12lib::buildISA”

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–]     while executing

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–] “X12lib::buildISA isa_array”

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–]     (procedure “tps_x12_put_envelope_userdata” line 405)

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–]     invoked from within

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–] “tps_x12_put_envelope_userdata {MSGID message0} {CONTEXT xlt_post} {ARGS {{DEBUG N}

      [xlt :xlat:ERR /0:recondo_adt_xlate:–/–/—- –:–:–] {SEPCHARS {{FIELD *} {COMPONENT /} {SEGMENT ~}}}

       

      The package X12lib exist but it is not recognizing it somehow. As a work around, I moved the proc X12lib.tcl to tclprocs folder and did mktclindex and that solved my issue.

      I still need to find out why it wouldn’t run under /cloverleaf/cis6.2/integrator/tcl/lib/X12lib

      Thanks again to Jim for helping with the proc and directions.

    • #116201
      Charlie Bursell
      Participant

      Where did you put the package?  Did you run mkpkgindex?

      Tcl will search one level below the TCLPATH for packages.

      For a package specific to a site I usually create a directory under the site tclprocs directory.  Name it anything like lib, pkglib, etc.  Put the package in that directory and run mkpkgindex.  mkpkgindex assumes the file has a .pkg suffix.  If not you can pass the name or even :”*.tcl” to it.

Viewing 2 reply threads
  • You must be logged in to reply to this topic.

Forum Statistics

Registered Users
5,129
Forums
28
Topics
9,301
Replies
34,448
Topic Tags
288
Empty Topic Tags
10