Managing Ensemble Productions - InterSystems Documentation

Message Filter
Type
VDoc Segment
Field
Conditions
You may use the Conditions panel as follows:
1. Ensure that the left-hand Conditions field is empty.
2. Click ... and when prompted, click OK.
3. Choose a schema category and segment name from a list of supported schema
categories and segment names. The contents of this list depend on your Class Name
choice of virtual document type. Click OK to save your selections.
4. A list of fields in the chosen segment displays. Choose a field and click OK.
5. The resulting entry in the left-hand Conditions field looks something like this. This is
an HL7 example. Different specific syntax is offered for X12, but the idea is the same:
2.3.1:[PID:PatientAddress().city]
Instead of selecting options to fill the left-hand Conditions field, you can type a string into
the field, as long as you are careful to use the correct syntax. For HL7, you can type a
numeric references if you prefer them to names, for example [5], [18.1], or 2.3.1:[3().1].
You may edit out the category reference and colon prefix, but keep the square brackets
and their contents intact.
Square brackets differ from curly brackets in that square brackets enclose a segment:field
combination that does not require you to identify its containing message structure. In the
example above, Ensemble matches any message structure in the 2.3.1 schema category
that contains a PID segment with a PatientAddress().city field .
VDoc Property
Path
You may use the Conditions panel as follows:
1. Ensure that the left-hand Conditions field is empty.
2. Click ... and when prompted, click OK.
3. Choose a schema category and message structure from a list of supported schema
categories and message structures. The contents of this list depend on your Class
Name choice of virtual document type. Click OK to save your selections.
4. A list of segments and fields in the chosen message structure displays. Choose a
segment:field combination and click OK.
5. The resulting entry in the left-hand Conditions field looks something like this. This is
an HL7 example. Different specific syntax is offered for X12, but the idea is the same:
2.3:ADT_A06:{MSH:SendingFacility.namespaceID}
Instead of selecting options to fill the left-hand Conditions field, you can type a virtual
property path into the field, as long as you are careful to use the correct syntax. Curly
bracket syntax requires a specific message structure, such as ADT_A06, to be identified.
The comparison operator between the two values in a Conditions statement can be any one of the following.
Table 8–4: Comparison Operators for Message Filter Conditions
Operator
=
!=
The condition is true when the value at left is...
Equal to the value on the right.
Not equal to the value on the right.
Managing Ensemble Productions 83