Clovertech

Wildcard Routing for Meaningful Use Messages

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Wildcard Routing for Meaningful Use Messages

  • Creator
    Topic
  • May 21, 2014 at 3:12 pm #54224
    Bob Richardson
    Participant

      Greetings,

      We are running CIS 5.8.7.0 on AIX 6.1 TL 7.

      We have one of those “Meaningful Use” interfaces to build for an application called BioSense.  Our Xlates can work with the HL7 message types with the extra 3rd component however my specification for the wild routing fails – no errors, just fails.  Cloverleaf online doco is not very helpful.

      Here is a sample of the MSH segment:

      ADT^A04^ADT_A01

      Apparently Wildcard does not support all regexp expresssions.

      Tried the following without success so far:

      ADT_A04_.*

      Will continue to scour this Forum for those of you who have solved this problem.  

      Thanks.

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • May 22, 2014 at 2:39 pm #80636
        Chad Flodman
        Participant

          Bob – this will do your static routing ADT_A04_ADT_A01 for a 2.5.1 message or wildcard ADT.A04.ADT.* – or variations thereof.

          Basically, in wildcard routing;

          The . is regexp for “any single character” in the used encoding set typically ANSI or UTF-8.

          The .* is regexp for “any character from here i.e. multiple characters”

          Hope that helps you out…

        • May 22, 2014 at 3:04 pm #80637
          Bob Richardson
          Participant

            Chad,

            Thanks for your reply and explanations.  As it turned out my wildcard

            routing was not the problem but a filter buried in the depths of the flow stream (TPS stack).

            I am hoping that once we get to Integrator 6.0.2 (latest as of this post)

            then we can play around with its message tracing feature.

            Enjoy.

          • June 6, 2014 at 7:20 pm #80638
            Tom Griffiths
            Participant

              Thanks for your input Bill.    I had already seen that post, but that requires that I modify the interface routing for each interface that switches to hl7 2.5.1.     I would expect Cloverleaf to recognize that the message is hl7 2.5.1 and use routing logic that does not require that the routing configuration be changed.

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