TXA-22 manipulation

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf TXA-22 manipulation

  • Creator
    Topic
  • #49706
    Duy Nguyen
    Participant

    I am working on an existing integration from HCA HIM to GE Centricity’s EMR.  My EMR folks tell me the messages keep erroring out unless I hardcopy the first component in the TXA-22 field and copy the last component (DATE STAMP) in the TXA-22 field.

    I modified existing xlate in place and I used a PATHCOPY to null TXA-22 out.  Then I proceeded to do a single COPY with “hcaprov” hardcoded in and I used a COPY statement to copy MSH-7 (TIME STAMP) to the last component in TXA-22.   (FYI- BULKCOPY IS USED by whoever implemented this in the past)

    This works out pretty well for every message EXCEPT when there are 2 physicians noted in the TXA 22 i.e. physician PLUS resident

    Below is an example from a message that errored out.  I basically need to removed the “~” and anything after it.  Should I use TCL fragment or write a TCL proc and to extract the field component, manipulate it, and rebuild it the back?  I am looking for a simple solution.

    hcaprov^^^^^^^^^^^^^^200712141502~r.WILKE^Williams^Kenneth^D^^^MD~^^^^^^^^^^^^^^200712141422

    Thanks.

Viewing 8 reply threads
  • Author
    Replies
    • #63191
      Jim Kosloskey
      Participant

      Duy,

      I think you need to do a field iteration over the field nulling out each repetition (you can probably use PATHCOPY) and then set upt the first occurence.

      Of course if you did not use BULKCOPY or PATHCOPY to populate to begin with…  🙂

      Jim Kosloskey

      email: jim.kosloskey@jim-kosloskey.com

    • #63192
      Duy Nguyen
      Participant

      Jim Kosloskey wrote:

      Duy,

      I think you need to do a field iteration over the field nulling out each repetition (you can probably use PATHCOPY) and then set upt the first occurence.

      Of course if you did not use BULKCOPY or PATHCOPY to populate to begin with…

    • #63193
      John Hamilton
      Participant

      I don’t think you need to iterate on this.

      Just change you patcopy to null out the whole filed.

      change 0(0).TXA.00934(0) to (0).TXA.00934.

      That shoudl fix you up.

    • #63194
      Duy Nguyen
      Participant

      John Hamilton wrote:

      I don’t think you need to iterate on this.

      Just change you patcopy to null out the whole filed.

      change 0(0).TXA.00934(0) to (0).TXA.00934.

      That shoudl fix you up.

      John,

      Can you tell me the difference between 0(0) VS (0) ?  I got the 0(0).TXA.00934(0) from double clicking on the TXA-22 on the destination side on the OUTPUT MESSAGE FORMAT column.

      Thanks.

    • #63195
      John Hamilton
      Participant

      Sorry the change should be after the item number.

      That was a typo in the first part so it should be(If I can type correctly this morning)  0(0).TXA.00934(0)  to  0(0).TXA.00934.  The “(0)” after the item number tells it which of the subfields you are working with. leave it off and it will null out all of the subfields.

    • #63196
      Tom Rioux
      Participant

      John Hamilton wrote:

      I don’t think you need to iterate on this.

      Just change you patcopy to null out the whole filed.

      change 0(0).TXA.00934(0) to (0).TXA.00934.

      That shoudl fix you up.

      I think John meant 0(0).TXA.00934 and not (0).TXA.00934.  Is this correct John.

      Basically, here is the set up:

      0(0).PID.00105(0) = The (0) after the 105 means that the field repeats

      0(0).PID.00111  = The absence of the (0) after the 111 means the field does not repat

      4(0).GT1(0).00407(0) = The (0) after the GT1 means that the segment repeats.  The (0) after the 407 means that the field repeats

      4(0).GT1(0).00413 = This means that the segment repeats but the field does not repeat.

      5(0).0(0).IN1.00368 = The 0(0) means that the group (IN1, IN2, IN3) repeats.  If the segment were to repeat you would see IN1(0).  If the field were to repeats you would see 00368(0)

      Clear as mud?  This may vary a bit depending upon how you have your variant set up. If you are ever unsure of how things repeats and the numbering scheme, simply take an HL7 message and run it through your variant within the HL7 tester.  Turn the detail up to about 2 or 3 and it will show you the tag details.

      Hope this helps…

      Tom Rioux

    • #63197
      Duy Nguyen
      Participant

      Alright, I think I have it working now.

    • #63198
      John Hamilton
      Participant

      The 00934 item can repeat some number of times.

      When you have the (0) on the end your are telling it to work only only on the first field.  If you remove that you are telling it to work on all the fields within that element.   The “~” is the seperator between the different iteration of that field.

    • #63199
      Duy Nguyen
      Participant

      John Hamilton wrote:

      The 00934 item can repeat some number of times.

      When you have the (0) on the end your are telling it to work only only on the first field.

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

Forum Statistics

Registered Users
5,041
Forums
28
Topics
9,199
Replies
34,021
Topic Tags
266