25.01.2015 Views

Ensemble HL7 Version 2 Development Guide - InterSystems ...

Ensemble HL7 Version 2 Development Guide - InterSystems ...

Ensemble HL7 Version 2 Development Guide - InterSystems ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Elements of a Routing Production<br />

Note:<br />

To navigate to the configuration diagram from the [<strong>Ensemble</strong>] > [Productions] > [Production<br />

Model] page, where the previous topic ended, click Configure Production, then continue.<br />

You may configure an <strong>HL7</strong> business service by entering values in the following fields. When you are<br />

done editing, click Apply to save your changes, or Cancel to ignore them.<br />

• General Settings — This column of settings appears at left. These are settings that configure the<br />

<strong>HL7</strong> business service as a production item. The most important of these for <strong>HL7</strong> are as follows.<br />

For descriptions of the other General Settings, see the section “Business Service Settings” in<br />

“The Configuration Page” chapter of Managing <strong>Ensemble</strong> Productions.<br />

- PoolSize — The default PoolSize value of 1 ensure FIFO (First In, First Out) processing. In<br />

many cases, multiple patient demographic updates must be received in order. For example,<br />

many applications require receipt of an ADT Registration message before they can process<br />

an Order message, an Order message must be received before a Result message, and so on.<br />

- Category — This text label permits configuration items to be sorted in the configuration diagram.<br />

For example, you can assign the same Category name to all items in the same interface.<br />

You may enter multiple category names separated by commas. Space characters count (do<br />

not use them around the commas).<br />

• Specific Settings — This column of settings appears at right. The column is organized into settings<br />

that configure the <strong>HL7</strong> business service (at top) and settings that configure its associated adapter<br />

(at bottom). The specific settings will be different depending on which <strong>HL7</strong> business service you<br />

are configuring, and which adapter that business service is using. The following list describes<br />

how to configure the most important of these settings. For details about which class provides<br />

which settings, see the “<strong>HL7</strong> Business Service Classes” section in the chapter “Settings for a<br />

Routing Production.”<br />

The Specific Settings for an <strong>HL7</strong> business service are as follows:<br />

AckMode<br />

Helps to establish the format and conventions for issuing <strong>HL7</strong> acknowledgement messages<br />

in response to <strong>HL7</strong> messages received. For a list of codes to enter in this field, see the “<strong>HL7</strong><br />

Acknowledgement (ACK) Mode” section in the chapter “Settings for a Routing Production.”<br />

Ack Target Config Names<br />

(File and FTP only) Unlike TCP business services, File and FTP business services have no<br />

persistent connection on which to send <strong>HL7</strong> acknowledgement messages (ACK or NACK).<br />

For this reason, the default AckMode for File and FTP business services is Never, which is<br />

usually appropriate. However, when you do want to send ACKs from a File or FTP business<br />

service, use the Ack Target Config Names setting to identify an <strong>Ensemble</strong> routing process or<br />

business operation that will receive the ACK messages. For AckMode details, see the “<strong>HL7</strong><br />

Acknowledgement (ACK) Mode” section in the chapter “Settings for a Routing Production.”<br />

26 <strong>Ensemble</strong> <strong>HL7</strong> <strong>Version</strong> 2 <strong>Development</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!