25.01.2015 Views

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Message Filter<br />

selection in the Type field. Suppose you added an OR row and a fourth logical statement to the list shown above. The<br />

Detailed Filter Terms panel now looks like this:<br />

Logical Statement 1<br />

Logical Statement 2<br />

Logical Statement 3<br />

OR<br />

Logical Statement 4<br />

And the resulting logic is now:<br />

Logical Statement 1<br />

AND<br />

Logical Statement 2<br />

AND<br />

Logical Statement 3<br />

OR<br />

Logical Statement 4<br />

The operator AND binds more tightly than OR, so the effect of the above sequence is actually:<br />

(1 AND 2 AND 3) OR 4<br />

8.2.2.2 Filter Type<br />

In the Type column, choose a value from the drop-down list. The following table lists the Type choices and how they affect<br />

your subsequent choices in the Class Name and Conditions fields.<br />

Table 8–1: Options for Filter Type<br />

Type<br />

Body Property<br />

Header Field<br />

OR<br />

VDoc SearchTable Field<br />

VDoc Segment Field<br />

VDoc Property Path<br />

Class Name and Conditions refer to...<br />

Properties of a standard <strong>Ensemble</strong> message body object.<br />

Fields in a standard <strong>Ensemble</strong> message header object.<br />

(used to logical OR two filter terms)<br />

Entries in a search table class that you have defined in this <strong>Ensemble</strong> namespace.<br />

A search table class is a specialized tool that you create to work with virtual<br />

documents, a convention for representing Electronic Data Interchange (EDI)<br />

formats like HL7 Version 2 or X12.<br />

Fields in a virtual document message segment. Identify the standard (HL7 Version<br />

2 or X12) and the segment of interest. <strong>Ensemble</strong> then prompts you to choose<br />

from a list of fields in that segment.<br />

Fields in a virtual document message segment. Identify the standard (HL7 Version<br />

2 or X12) and then enter a virtual property path that identifies a message segment<br />

and field that is valid for that standard.<br />

Note:<br />

For background information about the VDoc fields in the Detailed Filter Terms interface, see <strong>Ensemble</strong> Virtual<br />

Documents. You do not need to use these fields unless your production routes HL7 Version 2 or X12 messages.<br />

8.2.2.3 Filter Class<br />

In the Class Name column, click ... (the More command). <strong>Ensemble</strong> displays a list of all the classes appropriate for the Type<br />

of message that you have chosen. For example:<br />

<strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong> 81

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

Saved successfully!

Ooh no, something went wrong!