Information on why an error would not report in the error db

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Information on why an error would not report in the error db

  • Creator
    Topic
  • #54646
    Lawrence Nelson
    Participant

      I had a report of ORU messages not being delivered to a client EMR. It turned out I had an xlate that had a hidden problem where a TCL frag caused the translation to break. This could be seen easily in the testing tool on the xlate and also when I ran Routes on it.

      I would have found the problem much earlier, but nothing was reporting  to the error db like I’ve seen in the past.

      My question : What should I be looking at in the route process/route set up to see how these did not report to the error db? The message passed thought the UPOC trxid process but was cracking on the xlate.

      Thanks.

      Lawrence Nelson
      System Architect - MaineHealth IT

    • The forum ‘Cloverleaf’ is closed to new topics and replies.