A08 Issue

  • Creator
    Topic
  • #47610
    Jared Miller
    Participant

      Suddenly, anytime I receive an A08 in our test site it gets translated into a message like the following:

      MSH|^~&|SPC|W|IM|MISYS|20050405101800.0000-0500|41|ADT^A08|36698273|D|2.3|36698273||AL

      EVN|A08|20050405101800.0000-0500

      PID

      PV1

      Doesn’t matter which ADT interface it is.  I’ve tried rebuilding the Xlate, the message route and the thread as a whole.  Still no success in resolving the problem.  I think this stems from a reboot we had to do a couple weeks ago in which the testsite processes weren’t brought down prior to rebooting.  I’m trying to avoid reuilding the entire process, but I’m thinking that is going to be the only way to fix things.

      Does anybody have any other ideas??  Thanks.

    Viewing 6 reply threads
    • Author
      Replies
      • #56250
        Stephan Head
        Participant

          Check your field definition for these fields on the variant you are using.  The standard definition for these fields are usually TS – timestamp, which puts all of the information you see.

        • #56251
          Terry Kellum
          Participant

            Is the problem the date?  Datecopyopt with precision turned off.

          • #56252
            Jared Miller
            Participant

              The problem is that no data is getting passed through in any segments besides MSH and EVN.  PID, PV1 and any other segment received gets blanked out.  Bulkcopy and mappings are defined in the xlate file.

            • #56253
              Kevin Scantlan
              Participant

                What do your process logs and error logs for the process the thread belongs to say?  That’s always a good place to look for clues.

              • #56254
                Jared Miller
                Participant

                  Here’s the message I get when an A08 goes through:

                  04/05/2005 15:19:42

                  [msg :RecP:WARN/0:   work_xlate] [0.0.1495075] The # 2 segment encountered ‘PV1’

                  is out of order for message type ‘ADT_A08’.  Segment ignored.

                  Looked at the messages coming in and they appear to be in the correct order.

                • #56255
                  Kevin Scantlan
                  Participant

                    Look at your HL7 variant that you are using for the translation.  The engine thinks it’s in a different order than the message you are receiving.

                  • #56256
                    Jared Miller
                    Participant

                      Well, after looking at the messages again it appears that any A08 that is sent from out Star test system does not have a PID segment.  Since thats a required segment its knocking everything out of whack.

                      Thanks for your assistance.

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