Converting ORU_R01 to a UDM message via Xlate

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Converting ORU_R01 to a UDM message via Xlate

  • Creator
    Topic
  • #48530
    Bill Rambo
    Participant

      I am in the process of upgrading from 3.7.1P to 5.3. I have an Xlate for Misys Lab result to McKesson STAR that converts the ORU_R01 to an UDM message. the translation uses a TCL fragment to construct the DSP segments via a command xlateStoreData. In the 5.3 version, I am getting the error message that the command xlateStoreData is not valid.

      Has this command been removed?

      If so, does anyone have a suggestion as to how to convert the OBX with NTE segments to a DSP segment?

      Thanks,

      Bill Rambo

      Self Regional Healthcare

      Greenwood, SC

    Viewing 0 reply threads
    • Author
      Replies
      • #58887
        James Cobane
        Participant

          Bill,

          I don’t believe the xlateStoreData is a Quovadx supplied proc/command; it may be one that was developed in-house that uses the ‘xpm’ functions (i.e. ‘xpmstore’), which are what is used when attempting to do some translation-type functions.

          I would look through the tclprocs directory at the root level (of 3.7.1P) to see if you can find this proc.  If it was at the ‘site’ level it would have gotten carried over, assuming you are using the Quovadx site promotion scripts, and moving from 3.7.1P —> 3.8.1P —-> 5.3.  If you are just manually moving your configurations between versions, then it’s possible that this proc exists at the site level and didn’t get moved.

          Hope this helps.

          Jim Cobane

          Henry Ford Health

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