Once an incoming interface has been created, the routing can be set up so that messages or documents are automatically passed on to the outbound interfaces as they arrive at the inbound interface.

Create a New Route

  1. Click on Administration in the HL7Connect navigation tool bar
  2. Choose the Interfaces tab
  3. Select the incoming interface that you want to add a route(s) to an outgoing interface, and click on the Routing button
  4. Click the Add a new route tab and select the "To Interface" (outbound interface) from the drop down box
  5. Fill out additional fields as required, refer below for more information
  6. Specify an audit history comment and click Add
  7. Repeat steps 3 to 7 for each route from the interface
  8. Routes will be listed under the Current Routes for xxxx tab (where xxxx is the interface name)

NOTE: You can also click on the routing icon for an incoming interface on the status page to take you directly to the interface's routing page.
 If the routing icon is red, this indicates that there are no routes defined for this interface.
 If the routing icon is blue, this indicates that there are routes defined for this interface.

Additional Fields

Field    Description
Types    The type of document or message. For Messages, type is the event type of the HL7Message message. A list of defined types can be found in HL7 Table 0003 - Event type (in version 2.4), though HL7Connect will also recognized undefined event types. Use comma's to separate the list items. Use [X]* to include all events of a particular type, such as A* for all ADT messages. For documents, use the extension from the ClinicalDocument.code.
Conditions    Conditions are an open field, where multiple conditions can be specified.

Standard logical evaluators like =, <>, !=, <, >, <=, >=, AND, NOT, OR, can be used.

You can use several functions to extract content from the message or document:

  • f("[SEG[]-N[].O.P]") (Messages) Extract the contents of a cell. SEG: 3 letter code of segment. N: Data Element index (starts at 1). O: Component Element index (starts at 1) [optional]. P: Subcomponent index [optional]. For example, f("MSH-5") retrieves the Receiving Application from the message
  • a("name") (Messages and Documents) Get a message annotation by name. For example: a("Conversation Id").
  • x("xpath") (Documents) An xpath extractions. For example: x("//v3:recordTarget/v3:patientRole/v3:providerOrganization/v3:id/@root") extracts the oid of the provider organization from the document.
  • s("xpath", "code") (Documents) A snomed subsumption test. For example: x("//v3:observation/v3:code", "257495001") extracts any snomed codes found in any observation codes, and returns true if any of them represent some kind of organism.
Rules    Stops processing further rules after the the rule matches.
Audit History Comment    Compulsory field.
NOTE: Try to make this field as self-explanatory as possible to help future users and administrators.

© Kestral Computing P/L 2000-2015. HL7Connect v2.00-063 generated on 30-Nov 2015
Keywords: Routing, Messages / Delivering, Messages / Routing, Routing / Configuring