Creating a new HL7 subcomponent

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Creating a new HL7 subcomponent

  • Creator
    Topic
  • #48963
    Randy Colella
    Participant

      In the PID 10 seq (Race) we are sending two values (i.e. “W^A”).  The Quovadx HL7 templates are set up for only one component.  I’ve tried various tcl procs to overcome the problem, but once it hits the xlate it kills the second subcomponent.  If I put the proc after the xlate, it creates the second subcomponent, but the value in it is lost.  HELP!!!!!!!!!!!!!

    Viewing 1 reply thread
    • Author
      Replies
      • #60257
        Jim Kosloskey
        Participant

          Randy,

          Check the length of the Race field in your outbound variant and assure it is long enough to contain all of the data.

          If it is not (it may have a length of one), change it and test again.

          If the length is the problem, you should not need any Tcl just COPY each component from inbound to outbound.

          Jim Kosloskey

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

        • #60258
          Alex Puzikov
          Participant

            Randy.

            The issue can be a field type.

            As default pid-10 defined as a “Code Value (IS)” if you will define it as “Coded Element (CE)” and allow appropriate lenght everything will get fixed

            I hope that this will help.

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