City name

  • Creator
    Topic
  • #48291
    Mark Perschbacher
    Participant

      I have an inbound HL7 thread coming from a foreign system, which is xlating ver. 2.3 ORM into 2.2 ADT.  For the  patient address in the PID and insurance address in IN1, when a city comes across with a multiple part name;Lake Stevens, Salt Lake City, the second word in the name moves to the next subfield.  When this hits our lab system, it is recongnized as the state, and errors off.  I have tried Concating the subfields, but what seems to be happening is the field is adding positions with these multipart names.  I was wondering how other sites deal with this.

    Viewing 4 reply threads
    • Author
      Replies
      • #58259
        Ryan Spires
        Participant

          Help me understand,

          The data going out in the address field (city component) has

          “Lake Stevens, Salt Lake City” in the component, but the recieving system is interpreting “Salt Lake City” as the state?  

          This data is being mapped to component 2 (where 0 is street1, 1 is street2, and 2 is city, 3 is state, 4 zip, etc.)

          Is this happening for all messages or just the multipart?

          You may want to try to eliminate the “,” manually and see if the recieving system fails.  

          It shouldn’t be dumping the data into the state field if the state field (comp 3 – 0 based) is valued with something else.

          Have I confused you yet?  I am trying really hard 🙂

          Ryan

        • #58260
          Mark Perschbacher
          Participant

            O.k., let me back up.  Here is a normal insurance address.  

            POBOX^6720^FARGO^ND^58108-6720^^^

            Here is one with a multiple name.  Our lab system will recongnize LAKE as the state.

            POBOX^30271^SALT^LAKE^CITY^^^^U

          • #58261
            Ryan Spires
            Participant

              Ok,

              If you inbound data is presented as you have described, it appears that the field may be getting used inappropriately.

              How would 123 Main ST, Apt 207, Fargo ND 58108 be presented.

              Generally this would be

              123 Main St^Apt 207^Fargo^ND^58108

              If your inbound data is actually being sent as described, then there is no uniformity within your data.  This could be next to impossible to code for.  At least based on the example you have given.

              I would recommend verifying your inbound data, and have the vendor or application responsible give you consistantly placed data.

              Ryan

            • #58262
              Daniel Lee
              Participant

                Are you sure you don’t have an xlate in Cloverleaf that is looking for spaces and assigning them to subfields?  I just can’t imagine a sending system sending an address out like that.

              • #58263
                Mark Perschbacher
                Participant

                  Actually, I went back and looked at the log.  We have a TPS proc we are running the ORM’s through, and it is taking the city string and substituting the spaces between the name with subfield markers.

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