<extensionManifest><groupId>org.apache.nifi</groupId><artifactId>nifi-hl7-nar</artifactId><version>1.28.0.250-eep-1001</version><systemApiVersion>1.28.0.250-eep-1001</systemApiVersion><buildInfo><tag>nifi-1.28.0-RC1</tag><branch>UNKNOWN</branch><revision>bdae0d7</revision></buildInfo><extensions><extension><name>org.apache.nifi.processors.hl7.ExtractHL7Attributes</name><type>PROCESSOR</type><description>Extracts information from an HL7 (Health Level 7) formatted FlowFile and adds the information as FlowFile Attributes. The attributes are named as &lt;Segment Name&gt; &lt;dot&gt; &lt;Field Index&gt;. If the segment is repeating, the naming will be &lt;Segment Name&gt; &lt;underscore&gt; &lt;Segment Index&gt; &lt;dot&gt; &lt;Field Index&gt;. For example, we may have an attribute named "MHS.12" with a value of "2.1" and an attribute named "OBX_11.3" with a value of "93000^CPT4".</description><tags><tag>HL7</tag><tag>health level 7</tag><tag>healthcare</tag><tag>extract</tag><tag>attributes</tag></tags><properties><property><name>Character Encoding</name><displayName>Character Encoding</displayName><description>The Character Encoding that is used to encode the HL7 data</description><defaultValue>UTF-8</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>use-segment-names</name><displayName>Use Segment Names</displayName><description>Whether or not to use HL7 segment names in attributes</description><defaultValue>false</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>parse-segment-fields</name><displayName>Parse Segment Fields</displayName><description>Whether or not to parse HL7 segment fields into attributes</description><defaultValue>false</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>skip-validation</name><displayName>Skip Validation</displayName><description>Whether or not to validate HL7 message values</description><defaultValue>true</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>hl7-input-version</name><displayName>HL7 Input Version</displayName><description>The HL7 version to use for parsing and validation</description><defaultValue>autodetect</defaultValue><allowableValues><allowableValue><displayName>autodetect</displayName><value>autodetect</value><description></description></allowableValue><allowableValue><displayName>2.2</displayName><value>2.2</value><description></description></allowableValue><allowableValue><displayName>2.3</displayName><value>2.3</value><description></description></allowableValue><allowableValue><displayName>2.3.1</displayName><value>2.3.1</value><description></description></allowableValue><allowableValue><displayName>2.4</displayName><value>2.4</value><description></description></allowableValue><allowableValue><displayName>2.5</displayName><value>2.5</value><description></description></allowableValue><allowableValue><displayName>2.5.1</displayName><value>2.5.1</value><description></description></allowableValue><allowableValue><displayName>2.6</displayName><value>2.6</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><relationships><relationship><name>success</name><description>A FlowFile is routed to this relationship if it is properly parsed as HL7 and its attributes extracted</description><autoTerminated>false</autoTerminated></relationship><relationship><name>failure</name><description>A FlowFile is routed to this relationship if it cannot be mapped to FlowFile Attributes. This would happen if the FlowFile does not contain valid HL7 data</description><autoTerminated>false</autoTerminated></relationship></relationships><writesAttributes></writesAttributes><supportsBatching>true</supportsBatching><sideEffectFree>true</sideEffectFree><inputRequirement>INPUT_REQUIRED</inputRequirement></extension><extension><name>org.apache.nifi.processors.hl7.RouteHL7</name><type>PROCESSOR</type><description>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.</description><tags><tag>HL7</tag><tag>healthcare</tag><tag>route</tag><tag>Health Level 7</tag></tags><properties><property><name>Character Encoding</name><displayName>Character Encoding</displayName><description>The Character Encoding that is used to encode the HL7 data</description><defaultValue>UTF-8</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><dynamicProperties><dynamicProperty><name>Name of a Relationship</name><value>An HL7 Query Language query</value><description>If a FlowFile matches the query, it will be routed to a relationship with the name of the property</description><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope></dynamicProperty></dynamicProperties><relationships><relationship><name>failure</name><description>Any FlowFile that cannot be parsed as HL7 will be routed to this relationship</description><autoTerminated>false</autoTerminated></relationship><relationship><name>original</name><description>The original FlowFile that comes into this processor will be routed to this relationship, unless it is routed to 'failure'</description><autoTerminated>false</autoTerminated></relationship></relationships><writesAttributes><writesAttribute><name>RouteHL7.Route</name><description>The name of the relationship to which the FlowFile was routed</description></writesAttribute></writesAttributes><supportsBatching>true</supportsBatching><eventDriven>true</eventDriven><sideEffectFree>true</sideEffectFree><inputRequirement>INPUT_REQUIRED</inputRequirement></extension></extensions></extensionManifest>