Routes incoming HL7 data according to user-defined queries. To add a query, add a new property to the processor. The name of the property will become a new relationship for the processor, and the value is an HL7 Query Language query. If a FlowFile matches the query, a copy of the FlowFile will be routed to the associated relationship.


HL7, healthcare, route, Health Level 7


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Character EncodingCharacter EncodingUTF-8The Character Encoding that is used to encode the HL7 data
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)

Dynamic Properties:

Supports Sensitive Dynamic Properties: No

Dynamic Properties allow the user to specify both the name and value of a property.

Name of a RelationshipAn HL7 Query Language queryIf a FlowFile matches the query, it will be routed to a relationship with the name of the property
Supports Expression Language: false


failureAny FlowFile that cannot be parsed as HL7 will be routed to this relationship
originalThe original FlowFile that comes into this processor will be routed to this relationship, unless it is routed to 'failure'

Reads Attributes:

None specified.

Writes Attributes:

RouteHL7.RouteThe name of the relationship to which the FlowFile was routed

State management:

This component does not store state.


This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

None specified.