Extracts information from an HL7 (Health Level 7) formatted FlowFile and adds the information as FlowFile Attributes. The attributes are named as <Segment Name> <dot> <Field Index>. If the segment is repeating, the naming will be <Segment Name> <underscore> <Segment Index> <dot> <Field Index>. 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".
HL7, health level 7, healthcare, extract, attributes
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 Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Character Encoding | Character Encoding | UTF-8 | The Character Encoding that is used to encode the HL7 data Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | |
| Use Segment Names | use-segment-names | false |
| Whether or not to use HL7 segment names in attributes |
| Parse Segment Fields | parse-segment-fields | false |
| Whether or not to parse HL7 segment fields into attributes |
| Skip Validation | skip-validation | true |
| Whether or not to validate HL7 message values |
| HL7 Input Version | hl7-input-version | autodetect |
| The HL7 version to use for parsing and validation |
| Name | Description |
|---|---|
| success | A FlowFile is routed to this relationship if it is properly parsed as HL7 and its attributes extracted |
| failure | 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 |