Any Wildcard ADT Routing Tips?

This topic has 4 replies, 4 voices, and was last updated 10 years, 8 months ago by James Cobane.

Creator

Topic
November 14, 2013 at 4:20 pm #53915
John Stafford
Participant
Since taking over our Cloverleaf Environment, I’ve been overwhelmed by how granular our ADT routing is: Every trigger is defined for every route we have. This produces well over 150 xlates that have to be updated and maintained in the event of a change.

I saw another thread on here from another user with a similar situation, but I was really looking for some tips about wildcard routing. I have two questions in particular, but I am open to any information that you feel is valuable to consider when using wildcard routes.

Note: We are upgrading from CL 5.5 to CL 6.0, so any information on newer functionality such as chained xlates is welcome.

First, is there an easy way to identify which xlates can be put under the wildcard umbrella? For example, I know that merge messages utilize a very different message structure from most other ADT formats and so must have their own route.

Next, If I have a route that requires special configuration, how would I have that done? Perform the wildcard ‘parent’ xlate and chain it into a ‘child’ for that specific trigger?
Creator

Topic

Viewing 3 reply threads

Author

Replies
- November 14, 2013 at 7:25 pm #79513
  Vince Angulo
  Participant
  If the translates are configured with the same inbound variant and message type, they are excellent candidates for using a wildcard route with a single translate.
  
  I often start with one translate based on ADT_A01 with a wildcard route of ADT_A(0[1-8]|1[1-3]|29|31) or something similar depending on what the sending system supports. Remember to check the “Wildcard Route” box!
  
  Another way to do that is to route everything to the ADT_A01 translate with the ADT_A* route, and in the translate put in logic to suppress things like merges or swaps that use different structures, but this is MUCH less efficient in the engine.
  
  If there’s a LOT of custom processing for a discharge or update, you could do a separate route/translate, but most of the time all that logic can be built into same translate with the rest…
  
  Then two other translates are required, one routed to ADT_A17, and one to ADT_A35 to cover the swaps the merges. I’m not sure what you mean by chaining — maybe someone else can chime in on that.
  
  Hope this helps…
- November 18, 2013 at 3:12 pm #79514
  Jim Kosloskey
  Participant
  John,
  
  I don’t know if this will help but I did a short treatise on chaning and branching for our group.
  
  If you would like a copy email me.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- April 10, 2014 at 5:28 pm #79515
  John Stafford
  Participant
  I have created Xlates for all of our receiving systems and ran each message type through the testing tool, checking against the existing xlates for consistency. I am now looking to configure wildcard routing and begin testing the changes, but I would like to test one system at a time.
  
  My question is if I can add receiving systems to the wildcard route as I go and leave the existing routes, or will the Wildcard Route supercede the other routes?
  
  For example, if and A01 comes through and I have ADT^A[0-3][0-8].* as well as ADT^A01 defined, will Cloverleaf use both routes, or will it use the first one only?
- April 10, 2014 at 5:37 pm #79516
  James Cobane
  Participant
  John,
  
  Cloverleaf will process the message down both routes.
  
  Jim Cobane
  
  Henry Ford Health
Author

Replies

Viewing 3 reply threads

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