# mulesoft HL7 EDI Connector - Full Documentation --- product: HL7 EDI Connector version: 4.2 --- # HL7 EDI - Customizing Schemas and Mapping Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use these options to: - Customize your schema definitions - Define a mapping from the HL7 event and message types to message structures - Customize global elements ## Copy and Edit Schema Definitions HL7 schema definitions are located in the `hl7-schemas-4.0.0.jar` file, embedded inside the HL7 EDI Connector update site, and within the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). You can copy a message structure schema from the `hl7-schemas-4.0.0.jar` file and edit it to match your specific needs. To make changes at the segment level, copy the message structure schema. To change segment definitions, copy the `basedefs.esl` schema of the same version, as that file contains the segment, composite, and element definitions. The [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference) provides an overview of the ESL schema structure used by all the EDI connectors, including HL7 EDI Connector. The following is an example HL7 message structure schema for the standard v2.5.1 ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", position: "01", usage: M } - { idRef: "SFT", position: "02", usage: O, count: ">1" } - { idRef: "EVN", position: "03", usage: M } - { idRef: "PID", position: "04", usage: M } - { idRef: "PD1", position: "05", usage: O } - { idRef: "ROL", position: "06", usage: O, count: ">1" } - { idRef: "NK1", position: "07", usage: O, count: ">1" } - { idRef: "PV1", position: "08", usage: M } - { idRef: "PV2", position: "09", usage: O } - { idRef: "ROL", position: "10", usage: O, count: ">1" } - { idRef: "DB1", position: "11", usage: O, count: ">1" } - { idRef: "OBX", position: "12", usage: O, count: ">1" } - { idRef: "AL1", position: "13", usage: O, count: ">1" } - { idRef: "DG1", position: "14", usage: O, count: ">1" } - { idRef: "DRG", position: "15", usage: O } - groupId: "PROCEDURE" count: ">1" usage: O items: - { idRef: "PR1", position: "17", usage: M } - { idRef: "ROL", position: "18", usage: O, count: ">1" } - { idRef: "GT1", position: "20", usage: O, count: ">1" } - groupId: "INSURANCE" count: ">1" usage: O items: - { idRef: "IN1", position: "22", usage: M } - { idRef: "IN2", position: "23", usage: O } - { idRef: "IN3", position: "24", usage: O, count: ">1" } - { idRef: "ROL", position: "25", usage: O, count: ">1" } - { idRef: "ACC", position: "27", usage: O } - { idRef: "UB1", position: "28", usage: O } - { idRef: "UB2", position: "29", usage: O } ``` This shows the list of segments that compose the `ADT_A05` message structure, including the segment groups PROCEDURE and INSURANCE. Because this example illustrates the standard definition (not the lax version), it includes both mandatory segments (indicated with `usage: M`) and optional segments (indicated with `usage: O`). The full set of usage codes used for HL7 includes: - `C` for Conditional Equivalent to Optional - `M` for Mandatory - `O` for Optional - `U` for Unused Accepted without warning when reading, but not present in the data passed on from the read operation and ignored when writing The possible number of occurrences of a segment or group is defined by the count value. This defaults to a value of `1`. To delete segments from the message structure or change segment requirements from mandatory to optional (or vice versa), make the change in your copy of the schema and use the modified version in your application. You can add segments that are not present in the original message structure definition. Remove the position values from all existing segment and group definition lines in the schema; otherwise, you must renumber everything following an added segment. If you remove the explicit position numbers, segments and groups are assigned position numbers sequentially, and for most purposes these numbers are not seen by HL7 EDI Connector applications. If you want to add a standard HL7 segment to a message structure, reference it with an `idRef` line at the appropriate place, and HL7 obtains the definition from the `basedefs.esl` file referenced as an import. The following partial example shows `CON` segments added to an ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", usage: M } - { idRef: "SFT", usage: O, count: ">1" } - { idRef: "EVN", usage: M } - { idRef: "PID", usage: M } - { idRef: "PD1", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "NTE", usage: O } - { idRef: "ROL", usage: O, count: ">1" } - { idRef: "NK1", usage: O, count: ">1" } - { idRef: "PV1", usage: M } - { idRef: "PV2", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "ROL", usage: O, count: ">1" } ... ``` If you want to define a nonstandard segment for your message structure, add the segment definition to the schema. This is more complex than just modifying the segment structure, because you need to list all components in the segment. The easiest starting point is to find a similar standard HL7 segment and copy the definition used for that standard segment from the `basedefs.esl` file. You can then add the segment’s key, following your message structure definition, followed by one or more segment definitions. ### Set Your Schema Locations You can configure schema locations in the Anypoint Studio XML view. 1. Select the XML view by clicking **Configuration XML**. 2. Modify your HL7 EDI configuration to include a list of all the schemas to include by adding an `` element for each document type: ```xml hl7/v2_6/ADT_A01.esl ``` 3. After you create a global element for your HL7 EDI, configure the event and message structure. ## Event and Message-to-Message Structure Map If you configure the connector with multiple message structure schemas (whether in separate schema definitions files, as with the provided schemas, or in a single file), you must define a mapping from the HL7 event and message types to message structures. HL7 defines the message type in the component values of `MSH-09`, a composite structure of type MSG. HL7 EDI Connector uses these component values to find the structure schema to use for processing a receive message, according to the following rules: - If the MSG-01 Message Code value is `ACK`, always use the predefined ACK schema. - If the MSG-03 Message Structure value is present (a value such as `ADT_A01`), use the schema structure with that ID. - If neither of these, then use a configured Event and Message-to-Message Structure Map to determine the message structure from the specified Trigger Event (`MSG-02`) and Message Code (`MSG-01`) values. The Event and Message-to-Message Structure Map is an optional configuration parameter. It must be a YAML file consisting of a map from each Event Type to a map for each supported Message Code to the actual Message Structure. Here’s an example: ```yaml A01: { XYZ: ADT_A01, ACK: ACK } A02: { XYZ: ADT_A02, ACK: ACK } A03: { XYZ: ADT_A03, ACK: ACK } A04: { XYZ: ADT_A01, ACK: ACK } A05: { XYZ: ADT_A05, ACK: ACK } A06: { XYZ: ADT_A06, ACK: ACK } A07: { XYZ: ADT_A06, ACK: ACK } A08: { XYZ: ADT_A01, ACK: ACK } ``` Each version of HL7 defines a different set of mappings from the event type and message code to the message structure. The default mappings are provided in the same JAR file as the standard HL7 schema definitions, in files named `event-message.yaml`. You use the same type of paths for these mapping definitions as for the actual message structure schemas. ### Uses for the General Tab Use the **General** tab to configure settings for reading and writing HL7 messages: - HL7 character encoding Always used for writing messages and used when reading messages unless a different encoding is specified by the MSH-18 (Character Set). - Disable numeric prefixes for data keys This option is true by default, which turns off numeric prefixes for segment data. The only reason to set this option as false is to achieve compatibility with mappings defined for HL7 EDI Connector 3.0.0. - Manually create or edit the list of schemas ### Set Your HL7 Identification in the Visual Editor You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI Connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages, then leave these blank and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. In Studio, these values are set in the following Global Element Properties: - Self identification parameters identify your side of the trading partner relationship. These are some self identification settings: ```text Mule Application Namespace ID (MSH-03/HD-01 when sending, MSH-05/HD-01 when receiving) Mule Application Universal ID (MSH-03/HD-02 when sending, MSH-05/HD-02 when receiving) Mule Application Universal ID Type (MSH-03/HD-03 when sending, MSH-05/HD-03 when receiving) ``` - Partner identification parameters identify your trading partner. These are some partner identification settings: ```text Partner Application Namespace ID (MSH-03/HD-01 when receiving, MSH-05/HD-01 when sending) Partner Application Universal ID (MSH-03/HD-02 when receiving, MSH-05/HD-02 when sending) Partner Application Universal ID Type (MSH-03/HD-03 when receiving, MSH-05/HD-03 when sending) ``` ### Parser Tab You can set the following options if needed:
XML ValueStudio Option

eventMessageMap="/hl7/v2_5_1/event-message.yaml"

Event and message-to-message structure map path (required if using multiple message structures, unless the MSH-09 and MSG-03 message structure values are always present in the received messages)

genericExtensionPattern="Z.."

Java regular pattern for generic extension segment names (to allow handling of extension segments as maps of field values)

invalidCharacterInValueFail="true"

Fail when an invalid character is in a value

missingRequiredValueFail="true"

Fail when a required value is missing

processingId="PRODUCTION"

Required processing ID (to specify a particular processing ID required on receive messages, such as P for Production)

segmentOutOfOrderFail="true"

Fail when a segment is out of order in a message

unknownSegmentFail="true"

Fail when an unknown segment is in a message

unusedSegmentPresentFail="true"

Fail when an unused segment is included in a message

validateHL7Version="true"

Validate the HL7 message version

valueLengthErrorFail="true"

Fail when a value length is outside an allowed range

wrongSegmentsRepeatsFail="true"

Fail when there are too many repeats of a segment

wrongValuesRepeatsFail="true"

Fail when there are too many repetitions of a value

## Next Step After you complete connector configuration, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # HL7 EDI - Customizing Schemas and Mapping Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use these options to: - Customize your schema definitions - Define a mapping from the HL7 event and message types to message structures - Customize global elements ## Copy and Edit Schema Definitions HL7 schema definitions are located in the `hl7-schemas-4.0.0.jar` file, embedded inside the HL7 EDI Connector update site, and within the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). You can copy a message structure schema from the `hl7-schemas-4.0.0.jar` file and edit it to match your specific needs. To make changes at the segment level, copy the message structure schema. To change segment definitions, copy the `basedefs.esl` schema of the same version, as that file contains the segment, composite, and element definitions. The [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference) provides an overview of the ESL schema structure used by all the EDI connectors, including HL7 EDI Connector. The following is an example HL7 message structure schema for the standard v2.5.1 ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", position: "01", usage: M } - { idRef: "SFT", position: "02", usage: O, count: ">1" } - { idRef: "EVN", position: "03", usage: M } - { idRef: "PID", position: "04", usage: M } - { idRef: "PD1", position: "05", usage: O } - { idRef: "ROL", position: "06", usage: O, count: ">1" } - { idRef: "NK1", position: "07", usage: O, count: ">1" } - { idRef: "PV1", position: "08", usage: M } - { idRef: "PV2", position: "09", usage: O } - { idRef: "ROL", position: "10", usage: O, count: ">1" } - { idRef: "DB1", position: "11", usage: O, count: ">1" } - { idRef: "OBX", position: "12", usage: O, count: ">1" } - { idRef: "AL1", position: "13", usage: O, count: ">1" } - { idRef: "DG1", position: "14", usage: O, count: ">1" } - { idRef: "DRG", position: "15", usage: O } - groupId: "PROCEDURE" count: ">1" usage: O items: - { idRef: "PR1", position: "17", usage: M } - { idRef: "ROL", position: "18", usage: O, count: ">1" } - { idRef: "GT1", position: "20", usage: O, count: ">1" } - groupId: "INSURANCE" count: ">1" usage: O items: - { idRef: "IN1", position: "22", usage: M } - { idRef: "IN2", position: "23", usage: O } - { idRef: "IN3", position: "24", usage: O, count: ">1" } - { idRef: "ROL", position: "25", usage: O, count: ">1" } - { idRef: "ACC", position: "27", usage: O } - { idRef: "UB1", position: "28", usage: O } - { idRef: "UB2", position: "29", usage: O } ``` This shows the list of segments that compose the `ADT_A05` message structure, including the segment groups PROCEDURE and INSURANCE. Because this example illustrates the standard definition (not the lax version), it includes both mandatory segments (indicated with `usage: M`) and optional segments (indicated with `usage: O`). The full set of usage codes used for HL7 includes: - `C` for Conditional Equivalent to Optional - `M` for Mandatory - `O` for Optional - `U` for Unused Accepted without warning when reading, but not present in the data passed on from the read operation and ignored when writing The possible number of occurrences of a segment or group is defined by the count value. This defaults to a value of `1`. To delete segments from the message structure or change segment requirements from mandatory to optional (or vice versa), make the change in your copy of the schema and use the modified version in your application. You can add segments that are not present in the original message structure definition. Remove the position values from all existing segment and group definition lines in the schema; otherwise, you must renumber everything following an added segment. If you remove the explicit position numbers, segments and groups are assigned position numbers sequentially, and for most purposes these numbers are not seen by HL7 EDI Connector applications. If you want to add a standard HL7 segment to a message structure, reference it with an `idRef` line at the appropriate place, and HL7 obtains the definition from the `basedefs.esl` file referenced as an import. The following partial example shows `CON` segments added to an ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", usage: M } - { idRef: "SFT", usage: O, count: ">1" } - { idRef: "EVN", usage: M } - { idRef: "PID", usage: M } - { idRef: "PD1", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "NTE", usage: O } - { idRef: "ROL", usage: O, count: ">1" } - { idRef: "NK1", usage: O, count: ">1" } - { idRef: "PV1", usage: M } - { idRef: "PV2", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "ROL", usage: O, count: ">1" } ... ``` If you want to define a nonstandard segment for your message structure, add the segment definition to the schema. This is more complex than just modifying the segment structure, because you need to list all components in the segment. The easiest starting point is to find a similar standard HL7 segment and copy the definition used for that standard segment from the `basedefs.esl` file. You can then add the segment’s key, following your message structure definition, followed by one or more segment definitions. ### Set Your Schema Locations You can configure schema locations in the Anypoint Studio XML view. 1. Select the XML view by clicking **Configuration XML**. 2. Modify your HL7 EDI configuration to include a list of all the schemas to include by adding an `` element for each document type: ```xml hl7/v2_6/ADT_A01.esl ``` 3. After you create a global element for your HL7 EDI, configure the event and message structure. ## Event and Message-to-Message Structure Map If you configure the connector with multiple message structure schemas (whether in separate schema definitions files, as with the provided schemas, or in a single file), you must define a mapping from the HL7 event and message types to message structures. HL7 defines the message type in the component values of `MSH-09`, a composite structure of type MSG. HL7 EDI Connector uses these component values to find the structure schema to use for processing a receive message, according to the following rules: - If the MSG-01 Message Code value is `ACK`, always use the predefined ACK schema. - If the MSG-03 Message Structure value is present (a value such as `ADT_A01`), use the schema structure with that ID. - If neither of these, then use a configured Event and Message-to-Message Structure Map to determine the message structure from the specified Trigger Event (`MSG-02`) and Message Code (`MSG-01`) values. The Event and Message-to-Message Structure Map is an optional configuration parameter. It must be a YAML file consisting of a map from each Event Type to a map for each supported Message Code to the actual Message Structure. Here’s an example: ```yaml A01: { XYZ: ADT_A01, ACK: ACK } A02: { XYZ: ADT_A02, ACK: ACK } A03: { XYZ: ADT_A03, ACK: ACK } A04: { XYZ: ADT_A01, ACK: ACK } A05: { XYZ: ADT_A05, ACK: ACK } A06: { XYZ: ADT_A06, ACK: ACK } A07: { XYZ: ADT_A06, ACK: ACK } A08: { XYZ: ADT_A01, ACK: ACK } ``` Each version of HL7 defines a different set of mappings from the event type and message code to the message structure. The default mappings are provided in the same JAR file as the standard HL7 schema definitions, in files named `event-message.yaml`. You use the same type of paths for these mapping definitions as for the actual message structure schemas. ### Uses for the General Tab Use the **General** tab to configure settings for reading and writing HL7 messages: - HL7 character encoding Always used for writing messages and used when reading messages unless a different encoding is specified by the MSH-18 (Character Set). - Disable numeric prefixes for data keys This option is true by default, which turns off numeric prefixes for segment data. The only reason to set this option as false is to achieve compatibility with mappings defined for HL7 EDI Connector 3.0.0. - Manually create or edit the list of schemas ### Set Your HL7 Identification in the Visual Editor You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI Connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages, then leave these blank and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. In Studio, these values are set in the following Global Element Properties: - Self identification parameters identify your side of the trading partner relationship. These are some self identification settings: ```text Mule Application Namespace ID (MSH-03/HD-01 when sending, MSH-05/HD-01 when receiving) Mule Application Universal ID (MSH-03/HD-02 when sending, MSH-05/HD-02 when receiving) Mule Application Universal ID Type (MSH-03/HD-03 when sending, MSH-05/HD-03 when receiving) ``` - Partner identification parameters identify your trading partner. These are some partner identification settings: ```text Partner Application Namespace ID (MSH-03/HD-01 when receiving, MSH-05/HD-01 when sending) Partner Application Universal ID (MSH-03/HD-02 when receiving, MSH-05/HD-02 when sending) Partner Application Universal ID Type (MSH-03/HD-03 when receiving, MSH-05/HD-03 when sending) ``` ### Parser Tab You can set the following options if needed:
XML ValueStudio Option

eventMessageMap="/hl7/v2_5_1/event-message.yaml"

Event and message-to-message structure map path (required if using multiple message structures, unless the MSH-09 and MSG-03 message structure values are always present in the received messages)

genericExtensionPattern="Z.."

Java regular pattern for generic extension segment names (to allow handling of extension segments as maps of field values)

invalidCharacterInValueFail="true"

Fail when an invalid character is in a value

missingRequiredValueFail="true"

Fail when a required value is missing

processingId="PRODUCTION"

Required processing ID (to specify a particular processing ID required on receive messages, such as P for Production)

segmentOutOfOrderFail="true"

Fail when a segment is out of order in a message

unknownSegmentFail="true"

Fail when an unknown segment is in a message

unusedSegmentPresentFail="true"

Fail when an unused segment is included in a message

validateHL7Version="true"

Validate the HL7 message version

valueLengthErrorFail="true"

Fail when a value length is outside an allowed range

wrongSegmentsRepeatsFail="true"

Fail when there are too many repeats of a segment

wrongValuesRepeatsFail="true"

Fail when there are too many repetitions of a value

## Next Step After you complete connector configuration, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 EDI - Customizing Schemas and Mapping Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use these options to: - Customize your schema definitions - Define a mapping from the HL7 event and message types to message structures - Customize global elements ## Copy and Edit Schema Definitions HL7 schema definitions are located in the `hl7-schemas-4.0.0.jar` file, embedded inside the HL7 EDI Connector update site, and within the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). You can copy a message structure schema from the `hl7-schemas-4.0.0.jar` file and edit it to match your specific needs. To make changes at the segment level, copy the message structure schema. To change segment definitions, copy the `basedefs.esl` schema of the same version, as that file contains the segment, composite, and element definitions. The [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference) provides an overview of the ESL schema structure used by all the EDI connectors, including HL7 EDI Connector. The following is an example HL7 message structure schema for the standard v2.5.1 ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", position: "01", usage: M } - { idRef: "SFT", position: "02", usage: O, count: ">1" } - { idRef: "EVN", position: "03", usage: M } - { idRef: "PID", position: "04", usage: M } - { idRef: "PD1", position: "05", usage: O } - { idRef: "ROL", position: "06", usage: O, count: ">1" } - { idRef: "NK1", position: "07", usage: O, count: ">1" } - { idRef: "PV1", position: "08", usage: M } - { idRef: "PV2", position: "09", usage: O } - { idRef: "ROL", position: "10", usage: O, count: ">1" } - { idRef: "DB1", position: "11", usage: O, count: ">1" } - { idRef: "OBX", position: "12", usage: O, count: ">1" } - { idRef: "AL1", position: "13", usage: O, count: ">1" } - { idRef: "DG1", position: "14", usage: O, count: ">1" } - { idRef: "DRG", position: "15", usage: O } - groupId: "PROCEDURE" count: ">1" usage: O items: - { idRef: "PR1", position: "17", usage: M } - { idRef: "ROL", position: "18", usage: O, count: ">1" } - { idRef: "GT1", position: "20", usage: O, count: ">1" } - groupId: "INSURANCE" count: ">1" usage: O items: - { idRef: "IN1", position: "22", usage: M } - { idRef: "IN2", position: "23", usage: O } - { idRef: "IN3", position: "24", usage: O, count: ">1" } - { idRef: "ROL", position: "25", usage: O, count: ">1" } - { idRef: "ACC", position: "27", usage: O } - { idRef: "UB1", position: "28", usage: O } - { idRef: "UB2", position: "29", usage: O } ``` This shows the list of segments that compose the `ADT_A05` message structure, including the segment groups PROCEDURE and INSURANCE. Because this example illustrates the standard definition (not the lax version), it includes both mandatory segments (indicated with `usage: M`) and optional segments (indicated with `usage: O`). The full set of usage codes used for HL7 includes: - `C` for Conditional Equivalent to Optional - `M` for Mandatory - `O` for Optional - `U` for Unused Accepted without warning when reading, but not present in the data passed on from the read operation and ignored when writing The possible number of occurrences of a segment or group is defined by the count value. This defaults to a value of `1`. To delete segments from the message structure or change segment requirements from mandatory to optional (or vice versa), make the change in your copy of the schema and use the modified version in your application. You can add segments that are not present in the original message structure definition. Remove the position values from all existing segment and group definition lines in the schema; otherwise, you must renumber everything following an added segment. If you remove the explicit position numbers, segments and groups are assigned position numbers sequentially, and for most purposes these numbers are not seen by HL7 EDI Connector applications. If you want to add a standard HL7 segment to a message structure, reference it with an `idRef` line at the appropriate place, and HL7 obtains the definition from the `basedefs.esl` file referenced as an import. The following partial example shows `CON` segments added to an ADT\_A05 message structure: ```yaml form: HL7 version: "2.5.1" imports: ["/hl7/v2_5_1/basedefs.esl"] id: "ADT_A05" name: "ADT_A05" data: - { idRef: "MSH", usage: M } - { idRef: "SFT", usage: O, count: ">1" } - { idRef: "EVN", usage: M } - { idRef: "PID", usage: M } - { idRef: "PD1", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "NTE", usage: O } - { idRef: "ROL", usage: O, count: ">1" } - { idRef: "NK1", usage: O, count: ">1" } - { idRef: "PV1", usage: M } - { idRef: "PV2", usage: O } - { idRef: "CON", usage: O, count: ">1" } - { idRef: "ROL", usage: O, count: ">1" } ... ``` If you want to define a nonstandard segment for your message structure, add the segment definition to the schema. This is more complex than just modifying the segment structure, because you need to list all components in the segment. The easiest starting point is to find a similar standard HL7 segment and copy the definition used for that standard segment from the `basedefs.esl` file. You can then add the segment’s key, following your message structure definition, followed by one or more segment definitions. ### Set Your Schema Locations You can configure schema locations in the Anypoint Studio XML view. 1. Select the XML view by clicking **Configuration XML**. 2. Modify your HL7 EDI configuration to include a list of all the schemas to include by adding an `` element for each document type: ```xml hl7/v2_6/ADT_A01.esl ``` 3. After you create a global element for your HL7 EDI, configure the event and message structure. ## Event and Message-to-Message Structure Map If you configure the connector with multiple message structure schemas (whether in separate schema definitions files, as with the provided schemas, or in a single file), you must define a mapping from the HL7 event and message types to message structures. HL7 defines the message type in the component values of `MSH-09`, a composite structure of type MSG. HL7 EDI Connector uses these component values to find the structure schema to use for processing a receive message, according to the following rules: - If the MSG-01 Message Code value is `ACK`, always use the predefined ACK schema. - If the MSG-03 Message Structure value is present (a value such as `ADT_A01`), use the schema structure with that ID. - If neither of these, then use a configured Event and Message-to-Message Structure Map to determine the message structure from the specified Trigger Event (`MSG-02`) and Message Code (`MSG-01`) values. The Event and Message-to-Message Structure Map is an optional configuration parameter. It must be a YAML file consisting of a map from each Event Type to a map for each supported Message Code to the actual Message Structure. Here’s an example: ```yaml A01: { XYZ: ADT_A01, ACK: ACK } A02: { XYZ: ADT_A02, ACK: ACK } A03: { XYZ: ADT_A03, ACK: ACK } A04: { XYZ: ADT_A01, ACK: ACK } A05: { XYZ: ADT_A05, ACK: ACK } A06: { XYZ: ADT_A06, ACK: ACK } A07: { XYZ: ADT_A06, ACK: ACK } A08: { XYZ: ADT_A01, ACK: ACK } ``` Each version of HL7 defines a different set of mappings from the event type and message code to the message structure. The default mappings are provided in the same JAR file as the standard HL7 schema definitions, in files named `event-message.yaml`. You use the same type of paths for these mapping definitions as for the actual message structure schemas. ### Uses for the General Tab Use the **General** tab to configure settings for reading and writing HL7 messages: - HL7 character encoding Always used for writing messages and used when reading messages unless a different encoding is specified by the MSH-18 (Character Set). - Disable numeric prefixes for data keys This option is true by default, which turns off numeric prefixes for segment data. The only reason to set this option as false is to achieve compatibility with mappings defined for HL7 EDI Connector 3.0.0. - Manually create or edit the list of schemas ### Set Your HL7 Identification in the Visual Editor You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI Connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages, then leave these blank and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. In Studio, these values are set in the following Global Element Properties: - Self identification parameters identify your side of the trading partner relationship. These are some self identification settings: ```text Mule Application Namespace ID (MSH-03/HD-01 when sending, MSH-05/HD-01 when receiving) Mule Application Universal ID (MSH-03/HD-02 when sending, MSH-05/HD-02 when receiving) Mule Application Universal ID Type (MSH-03/HD-03 when sending, MSH-05/HD-03 when receiving) ``` - Partner identification parameters identify your trading partner. These are some partner identification settings: ```text Partner Application Namespace ID (MSH-03/HD-01 when receiving, MSH-05/HD-01 when sending) Partner Application Universal ID (MSH-03/HD-02 when receiving, MSH-05/HD-02 when sending) Partner Application Universal ID Type (MSH-03/HD-03 when receiving, MSH-05/HD-03 when sending) ``` ### Parser Tab You can set the following options if needed:
XML ValueStudio Option

eventMessageMap="/hl7/v2_5_1/event-message.yaml"

Event and message-to-message structure map path (required if using multiple message structures, unless the MSH-09 and MSG-03 message structure values are always present in the received messages)

genericExtensionPattern="Z.."

Java regular pattern for generic extension segment names (to allow handling of extension segments as maps of field values)

invalidCharacterInValueFail="true"

Fail when an invalid character is in a value

missingRequiredValueFail="true"

Fail when a required value is missing

processingId="PRODUCTION"

Required processing ID (to specify a particular processing ID required on receive messages, such as P for Production)

segmentOutOfOrderFail="true"

Fail when a segment is out of order in a message

unknownSegmentFail="true"

Fail when an unknown segment is in a message

unusedSegmentPresentFail="true"

Fail when an unused segment is included in a message

validateHL7Version="true"

Validate the HL7 message version

valueLengthErrorFail="true"

Fail when a value length is outside an allowed range

wrongSegmentsRepeatsFail="true"

Fail when there are too many repeats of a segment

wrongValuesRepeatsFail="true"

Fail when there are too many repetitions of a value

enforceERRSegmentRepeatability="true"

Enforces the ERR Segment repeatability (count) in the acknowledgment.

## Next Step After you complete connector configuration, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.2 --- # HL7 EDI - Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the following examples to see how to customize a schema, configure the Message Header (MSH) application and facility identification for you and your trading partner, and view a test flow with an HTTP Listener that initiates a flow. ## Simplify a Schema Using Example Messages The HL7 standard definitions are very complex, with segments often having twenty or more components. Many of these components are broken down into subcomponents. This component nesting can make mapping HL7 difficult, since the DataSense view of the message has to contain all these subcomponents. In practice, most users of HL7 populate only a small fraction of the total HL7 standard definitions. To take advantage of this, HL7 EDI Connector provides a console-based Java tool you can use to simplify your schema definitions by eliminating components that are not normally used in your messages. The schema simplification tool is in the `hl7-simplify-4.0.0.jar` file, which is found in the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). The tool accepts a message structure schema and one or more example messages (as separate files) as input, and generates an output schema reduced to only those segments and components present in one or more of the sample messages. To use this tool, download the `JAR` and open a command line console, then type: ```console java -jar hl7-simplify-4.0.0.jar {input-schema} {output-schema} {sample1} {sample2} ... ``` The placeholders in this syntax represent the following values: - `input-schema` Message structure schema used to read the messages, which can be a file or a classpath reference to a supplied schema such as the `/hl7/v2_5_1/ADT_A05.esl` path. - `output-schema` File path for the simplified schema output. - `sample1…​n` File paths to the sample messages. Ensure that each sample message file is saved with a carriage return (CR) line ending, which is the required HL7 segment delimiter. Text editors generally use the default line ending for your operating system, and this might not be correct. Here’s a partial example of a simplified schema generated using this tool: ```yaml form: HL7 version: "2.5.1" structures: - id: "SIU_S12" name: "SIU_S12" data: - { idRef: "MSH", position: "01", usage: O } - { idRef: "SCH", position: "02", usage: O } - groupId: "PATIENT" count: ">1" usage: O items: - { idRef: "PID", position: "06", usage: O } - { idRef: "PV1", position: "08", usage: O } - groupId: "RESOURCES" count: ">1" usage: O items: - { idRef: "RGS", position: "14", usage: O } - groupId: "SERVICE" count: ">1" usage: O items: - { idRef: "AIS", position: "16", usage: O } - groupId: "GENERAL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIG", position: "20", usage: O } - groupId: "LOCATION_RESOURCE" count: ">1" usage: O items: - { idRef: "AIL", position: "24", usage: O } - groupId: "PERSONNEL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIP", position: "28", usage: O } segments: - id: "AIG" name: "Appointment Information - General Resource" varTag: "AIG" values: - { idRef: "SI", name: "Set ID - AIG", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "CE_2", name: "Resource ID", usage: O } - { idRef: "varies", name: "Resource Type", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity Units", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIL" name: "Appointment Information - Location Resource" varTag: "AIL" values: - { idRef: "SI", name: "Set ID - AIL", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "PL", name: "Location Resource ID", usage: O, count: ">1" } - { idRef: "CE", name: "Location Type-AIL", usage: O } - { idRef: "varies", name: "Location Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIP" name: "Appointment Information - Personnel Resource" varTag: "AIP" values: - { idRef: "SI", name: "Set ID - AIP", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "XCN_2", name: "Personnel Resource ID", usage: O, count: ">1" } - { idRef: "CE_1", name: "Resource Type", usage: O } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } ... composites: - id: "CE" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - id: "CE_1" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - id: "CE_2" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - { idRef: "ID", name: "Name of Coding System", usage: O } ... ``` Because unused components of a segment cannot be dropped from the segment definition unless they’re at the end of the segment, the simplification tool substitutes a `varies` data type for the component and marks it with `Usage: U` for Unused. The repetition count for `varies` remains the same as for the original component, but it does not display in the DataSense view of the data you see in DataWeave. When the schema simplification tool checks for data present in the messages, it handles each occurrence of a composite in context. Different uses of the same composite might have different values present in your samples. When this happens, the composite is defined more than once, using different identifiers. The simplified schema retains the segment positions from the original schema. You can delete these position values from the simplified schema, because they’re not used by HL7 EDI Connector unless you use position prefixes on segment keys (one of the connector configuration options). ### Example: HL7 Studio The following flow can be loaded from the XML. ```xml ``` ## Set Your HL7 Identification in XML You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages you can leave these blank, and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. - Self-identification parameters identify your side of the trading partner relationship. Self-identification parameters: ```text appNamespaceIdSelf="" appUniversalIdSelf="" appUniversalIdTypeSelf="" ``` - Partner-identification parameters identify your trading partner. Partner-identification parameters: ```text appNamespaceIdPartner="" appUniversalIdPartner="" appUniversalIdTypePartner="" ``` ## Reading and Validating HL7 ER7 Messages To read an HL7 message: 1. Search the palette for **HL7 EDI** and drag it into a flow. 2. From the properties view, select the previously created connector configuration and then the `Read` operation. This operation reads any byte stream into the structure as described by your HL7 schemas. HL7 EDI validates the message structure when read: - Checking the syntax and content of the MSH and all component segments of the message. - The generated ACK message logs, accumulates, and reports errors provided in the generated data structure. - All messages, whether error-free or with non-fatal errors, are passed on for processing as part of the output message map. - Reading input data errors can throw exceptions. Error data entered in the receive data map uses the HL7Error class, a read-only JavaBean with the following properties:
PropertyDescription

segment

Zero-based index within the input of the segment causing the error

fatal

Flag for a fatal error, meaning the associated message was rejected as a result of the error

errorType

Enumeration for the different types of errors defined by the HL7 standards (ERR-3 values)

errorCode

Error code, as defined by the HL7 standard for the indicated type of error

errorText

Text description of the error

The `Read` operation returns error data as an optional list with the `Errors` key. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # HL7 EDI - Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the following examples to see how to customize a schema, configure the Message Header (MSH) application and facility identification for you and your trading partner, and view a test flow with an HTTP Listener that initiates a flow. ## Simplify a Schema Using Example Messages The HL7 standard definitions are very complex, with segments often having twenty or more components. Many of these components are broken down into subcomponents. This component nesting can make mapping HL7 difficult, since the DataSense view of the message has to contain all these subcomponents. In practice, most users of HL7 populate only a small fraction of the total HL7 standard definitions. To take advantage of this, HL7 EDI Connector provides a console-based Java tool you can use to simplify your schema definitions by eliminating components that are not normally used in your messages. The schema simplification tool is in the `hl7-simplify-4.0.0.jar` file, which is found in the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). The tool accepts a message structure schema and one or more example messages (as separate files) as input, and generates an output schema reduced to only those segments and components present in one or more of the sample messages. To use this tool, download the `JAR` and open a command line console, then type: ```console java -jar hl7-simplify-4.0.0.jar {input-schema} {output-schema} {sample1} {sample2} ... ``` The placeholders in this syntax represent the following values: - `input-schema` Message structure schema used to read the messages, which can be a file or a classpath reference to a supplied schema such as the `/hl7/v2_5_1/ADT_A05.esl` path. - `output-schema` File path for the simplified schema output. - `sample1…​n` File paths to the sample messages. Ensure that each sample message file is saved with a carriage return (CR) line ending, which is the required HL7 segment delimiter. Text editors generally use the default line ending for your operating system, and this might not be correct. Here’s a partial example of a simplified schema generated using this tool: ```yaml form: HL7 version: "2.5.1" structures: - id: "SIU_S12" name: "SIU_S12" data: - { idRef: "MSH", position: "01", usage: O } - { idRef: "SCH", position: "02", usage: O } - groupId: "PATIENT" count: ">1" usage: O items: - { idRef: "PID", position: "06", usage: O } - { idRef: "PV1", position: "08", usage: O } - groupId: "RESOURCES" count: ">1" usage: O items: - { idRef: "RGS", position: "14", usage: O } - groupId: "SERVICE" count: ">1" usage: O items: - { idRef: "AIS", position: "16", usage: O } - groupId: "GENERAL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIG", position: "20", usage: O } - groupId: "LOCATION_RESOURCE" count: ">1" usage: O items: - { idRef: "AIL", position: "24", usage: O } - groupId: "PERSONNEL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIP", position: "28", usage: O } segments: - id: "AIG" name: "Appointment Information - General Resource" varTag: "AIG" values: - { idRef: "SI", name: "Set ID - AIG", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "CE_2", name: "Resource ID", usage: O } - { idRef: "varies", name: "Resource Type", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity Units", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIL" name: "Appointment Information - Location Resource" varTag: "AIL" values: - { idRef: "SI", name: "Set ID - AIL", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "PL", name: "Location Resource ID", usage: O, count: ">1" } - { idRef: "CE", name: "Location Type-AIL", usage: O } - { idRef: "varies", name: "Location Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIP" name: "Appointment Information - Personnel Resource" varTag: "AIP" values: - { idRef: "SI", name: "Set ID - AIP", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "XCN_2", name: "Personnel Resource ID", usage: O, count: ">1" } - { idRef: "CE_1", name: "Resource Type", usage: O } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } ... composites: - id: "CE" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - id: "CE_1" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - id: "CE_2" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - { idRef: "ID", name: "Name of Coding System", usage: O } ... ``` Because unused components of a segment cannot be dropped from the segment definition unless they’re at the end of the segment, the simplification tool substitutes a `varies` data type for the component and marks it with `Usage: U` for Unused. The repetition count for `varies` remains the same as for the original component, but it does not display in the DataSense view of the data you see in DataWeave. When the schema simplification tool checks for data present in the messages, it handles each occurrence of a composite in context. Different uses of the same composite might have different values present in your samples. When this happens, the composite is defined more than once, using different identifiers. The simplified schema retains the segment positions from the original schema. You can delete these position values from the simplified schema, because they’re not used by HL7 EDI Connector unless you use position prefixes on segment keys (one of the connector configuration options). ### Example: HL7 Studio The following flow can be loaded from the XML. ```xml ``` ## Set Your HL7 Identification in XML You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages you can leave these blank, and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. - Self-identification parameters identify your side of the trading partner relationship. Self-identification parameters: ```text appNamespaceIdSelf="" appUniversalIdSelf="" appUniversalIdTypeSelf="" ``` - Partner-identification parameters identify your trading partner. Partner-identification parameters: ```text appNamespaceIdPartner="" appUniversalIdPartner="" appUniversalIdTypePartner="" ``` ## Reading and Validating HL7 ER7 Messages To read an HL7 message: 1. Search the palette for **HL7 EDI** and drag it into a flow. 2. From the properties view, select the previously created connector configuration and then the `Read` operation. This operation reads any byte stream into the structure as described by your HL7 schemas. HL7 EDI validates the message structure when read: - Checking the syntax and content of the MSH and all component segments of the message. - The generated ACK message logs, accumulates, and reports errors provided in the generated data structure. - All messages, whether error-free or with non-fatal errors, are passed on for processing as part of the output message map. - Reading input data errors can throw exceptions. Error data entered in the receive data map uses the HL7Error class, a read-only JavaBean with the following properties:
PropertyDescription

segment

Zero-based index within the input of the segment causing the error

fatal

Flag for a fatal error, meaning the associated message was rejected as a result of the error

errorType

Enumeration for the different types of errors defined by the HL7 standards (ERR-3 values)

errorCode

Error code, as defined by the HL7 standard for the indicated type of error

errorText

Text description of the error

The `Read` operation returns error data as an optional list with the `Errors` key. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 EDI - Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the following examples to see how to customize a schema, configure the Message Header (MSH) application and facility identification for you and your trading partner, and view a test flow with an HTTP Listener that initiates a flow. ## Simplify a Schema Using Example Messages The HL7 standard definitions are very complex, with segments often having twenty or more components. Many of these components are broken down into subcomponents. This component nesting can make mapping HL7 difficult, since the DataSense view of the message has to contain all these subcomponents. In practice, most users of HL7 populate only a small fraction of the total HL7 standard definitions. To take advantage of this, HL7 EDI Connector provides a console-based Java tool you can use to simplify your schema definitions by eliminating components that are not normally used in your messages. The schema simplification tool is in the `hl7-simplify-4.0.0.jar` file, which is found in the standard MuleSoft enterprise Maven repositories (under group ID `com.mulesoft.connectors`). The tool accepts a message structure schema and one or more example messages (as separate files) as input, and generates an output schema reduced to only those segments and components present in one or more of the sample messages. To use this tool, download the `JAR` and open a command line console, then type: ```console java -jar hl7-simplify-4.0.0.jar {input-schema} {output-schema} {sample1} {sample2} ... ``` The placeholders in this syntax represent the following values: - `input-schema` Message structure schema used to read the messages, which can be a file or a classpath reference to a supplied schema such as the `/hl7/v2_5_1/ADT_A05.esl` path. - `output-schema` File path for the simplified schema output. - `sample1…​n` File paths to the sample messages. Ensure that each sample message file is saved with a carriage return (CR) line ending, which is the required HL7 segment delimiter. Text editors generally use the default line ending for your operating system, and this might not be correct. Here’s a partial example of a simplified schema generated using this tool: ```yaml form: HL7 version: "2.5.1" structures: - id: "SIU_S12" name: "SIU_S12" data: - { idRef: "MSH", position: "01", usage: O } - { idRef: "SCH", position: "02", usage: O } - groupId: "PATIENT" count: ">1" usage: O items: - { idRef: "PID", position: "06", usage: O } - { idRef: "PV1", position: "08", usage: O } - groupId: "RESOURCES" count: ">1" usage: O items: - { idRef: "RGS", position: "14", usage: O } - groupId: "SERVICE" count: ">1" usage: O items: - { idRef: "AIS", position: "16", usage: O } - groupId: "GENERAL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIG", position: "20", usage: O } - groupId: "LOCATION_RESOURCE" count: ">1" usage: O items: - { idRef: "AIL", position: "24", usage: O } - groupId: "PERSONNEL_RESOURCE" count: ">1" usage: O items: - { idRef: "AIP", position: "28", usage: O } segments: - id: "AIG" name: "Appointment Information - General Resource" varTag: "AIG" values: - { idRef: "SI", name: "Set ID - AIG", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "CE_2", name: "Resource ID", usage: O } - { idRef: "varies", name: "Resource Type", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity", usage: U, count: ">1" } - { idRef: "varies", name: "Resource Quantity Units", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIL" name: "Appointment Information - Location Resource" varTag: "AIL" values: - { idRef: "SI", name: "Set ID - AIL", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "PL", name: "Location Resource ID", usage: O, count: ">1" } - { idRef: "CE", name: "Location Type-AIL", usage: O } - { idRef: "varies", name: "Location Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } - id: "AIP" name: "Appointment Information - Personnel Resource" varTag: "AIP" values: - { idRef: "SI", name: "Set ID - AIP", usage: O } - { idRef: "varies", name: "Segment Action Code", usage: U, count: ">1" } - { idRef: "XCN_2", name: "Personnel Resource ID", usage: O, count: ">1" } - { idRef: "CE_1", name: "Resource Type", usage: O } - { idRef: "varies", name: "Resource Group", usage: U, count: ">1" } - { idRef: "TS", name: "Start Date/Time", usage: O } ... composites: - id: "CE" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - id: "CE_1" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - id: "CE_2" name: "Coded Element" values: - { idRef: "ST", name: "Identifier", usage: O } - { idRef: "ST", name: "Text", usage: O } - { idRef: "ID", name: "Name of Coding System", usage: O } ... ``` Because unused components of a segment cannot be dropped from the segment definition unless they’re at the end of the segment, the simplification tool substitutes a `varies` data type for the component and marks it with `Usage: U` for Unused. The repetition count for `varies` remains the same as for the original component, but it does not display in the DataSense view of the data you see in DataWeave. When the schema simplification tool checks for data present in the messages, it handles each occurrence of a composite in context. Different uses of the same composite might have different values present in your samples. When this happens, the composite is defined more than once, using different identifiers. The simplified schema retains the segment positions from the original schema. You can delete these position values from the simplified schema, because they’re not used by HL7 EDI Connector unless you use position prefixes on segment keys (one of the connector configuration options). ### Example: HL7 Studio The following flow can be loaded from the XML. ```xml ``` ## Set Your HL7 Identification in XML You can configure the Message Header (MSH) application and facility identification for you and your trading partner in the HL7 EDI connector configuration. The values you set are used when writing HL7 messages to supply the namespace ID, universal ID, and universal ID type, and are verified in receive messages. If you don’t want to restrict incoming messages you can leave these blank, and set the values for outgoing messages on the write operation or the actual outgoing message. Values set on the write operation override the connector configuration, and values set directly on the message override both the connector configuration and any values set on the write operation. - Self-identification parameters identify your side of the trading partner relationship. Self-identification parameters: ```text appNamespaceIdSelf="" appUniversalIdSelf="" appUniversalIdTypeSelf="" ``` - Partner-identification parameters identify your trading partner. Partner-identification parameters: ```text appNamespaceIdPartner="" appUniversalIdPartner="" appUniversalIdTypePartner="" ``` ## Reading and Validating HL7 ER7 Messages To read an HL7 message: 1. Search the palette for **HL7 EDI** and drag it into a flow. 2. From the properties view, select the previously created connector configuration and then the `Read` operation. This operation reads any byte stream into the structure as described by your HL7 schemas. HL7 EDI validates the message structure when read: - Checking the syntax and content of the MSH and all component segments of the message. - The generated ACK message logs, accumulates, and reports errors provided in the generated data structure. - All messages, whether error-free or with non-fatal errors, are passed on for processing as part of the output message map. - Reading input data errors can throw exceptions. Error data entered in the receive data map uses the HL7Error class, a read-only JavaBean with the following properties:
PropertyDescription

segment

Zero-based index within the input of the segment causing the error

fatal

Flag for a fatal error, meaning the associated message was rejected as a result of the error

errorType

Enumeration for the different types of errors defined by the HL7 standards (ERR-3 values)

errorCode

Error code, as defined by the HL7 standard for the indicated type of error

errorText

Text description of the error

The `Read` operation returns error data as an optional list with the `Errors` key. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.2 --- # HL7 EDI - XML and Maven Support > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio: - If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML editor or from a text editor, you can access the connector from your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file. - If you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file. ## Add a Namespace for the Connector Paste the following code inside the `mule` tag of the header of your configuration XML: ```xml http://www.mulesoft.org/schema/mule/hl7 http://www.mulesoft.org/schema/mule/hl7/current/mule-hl7.xsd ``` This example shows how the namespace statements are placed in the XML: ```xml ``` ## Add a POM File Dependency The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector: ```xml com.mulesoft.connectors mule-hl7-extension x.x.x mule-plugin ``` Replace `` with the version that corresponds to the connector you are using. To obtain the most up-to-date `pom.xml` file information: 1. Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/). 2. In Exchange, click **Login** and supply your Anypoint Platform username and password. 3. In Exchange, search for `HL7 EDI`. 4. Select the connector. 5. Click **Dependency Snippets** near the upper right of the screen. ## Next Step After completing your namespace and `pom.xml` file, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # HL7 EDI - XML and Maven Support > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio: - If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML editor or from a text editor, you can access the connector from your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file. - If you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file. ## Add a Namespace for the Connector Paste the following code inside the `mule` tag of the header of your configuration XML: ```xml http://www.mulesoft.org/schema/mule/hl7 http://www.mulesoft.org/schema/mule/hl7/current/mule-hl7.xsd ``` This example shows how the namespace statements are placed in the XML: ```xml ``` ## Add a POM File Dependency The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector: ```xml com.mulesoft.connectors mule-hl7-extension x.x.x mule-plugin ``` Replace `` with the version that corresponds to the connector you are using. To obtain the most up-to-date `pom.xml` file information: 1. Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/). 2. In Exchange, click **Login** and supply your Anypoint Platform username and password. 3. In Exchange, search for `HL7 EDI`. 4. Select the connector. 5. Click **Dependency Snippets** near the upper right of the screen. ## Next Step After completing your namespace and `pom.xml` file, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 EDI - XML and Maven Support > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio: - If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML editor or from a text editor, you can access the connector from your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file. - If you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file. ## Add a Namespace for the Connector Paste the following code inside the `mule` tag of the header of your configuration XML: ```xml http://www.mulesoft.org/schema/mule/hl7 http://www.mulesoft.org/schema/mule/hl7/current/mule-hl7.xsd ``` This example shows how the namespace statements are placed in the XML: ```xml ``` ## Add a POM File Dependency The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector: ```xml com.mulesoft.connectors mule-hl7-extension x.x.x mule-plugin ``` Replace `` with the version that corresponds to the connector you are using. To obtain the most up-to-date `pom.xml` file information: 1. Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/). 2. In Exchange, click **Login** and supply your Anypoint Platform username and password. 3. In Exchange, search for `HL7 EDI`. 4. Select the connector. 5. Click **Dependency Snippets** near the upper right of the screen. ## Next Step After completing your namespace and `pom.xml` file, you can try the [Examples](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-examples). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.2 --- # HL7 EDI Connector 4.2 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Connector for HL7 EDI (HL7 EDI Connector) is a collection of features that facilitate integration with healthcare systems by providing the tools needed to easily create, read, and transform HL7 version v2.x messages within Mule. Health Level Seven International (HL7) is a standards development organization that defines a set of standards for the transport and communication of healthcare information. For compatibility information and fixed issues, see the HL7 EDI Connector Release Notes. Standard schema definitions are included in HL7 EDI Connector for HL7 versions 2.1, 2.2, 2.3.1, 2.3, 2.4, 2.5, 2.5.1, 2.6, 2.7, 2.7.1, 2.8, 2.8.1. The schemas are provided in two forms: - Standard HL7 Uses required or optional status data types, field lengths, and repetition counts (as listed) for each HL7 version. - Lax HL7 All segments and value items are optional. These low-level data types are treated as simple strings. Field lengths and repetition counts are not enforced. Both forms of schemas are available in the connector’s `classpath`. Standard HL7 schemas use the path `/hl7/v2_5_1/ADT_A01.esl`. Lax schemas use the path `/hl7lax/v2_5_1/ADT_A01.esl`. The schema definitions you need for [HL7 supplied schemas](https://docs.mulesoft.com/hl7-connector/4.2/hl7-schemas) are included. For complete information about schemas, see [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ## Before You Begin To use this connector, you must be familiar with: - Anypoint Connectors - Mule runtime engine (Mule) - Elements and global elements in a Mule flow - Creating a Mule app using Anypoint Studio or Anypoint Code Builder - HL7 EDI Connector To use HL7 EDI Connector, you must have: - Purchased a MuleSoft license for HL7. Contact your Account Representative about purchasing a license. - Anypoint Studio or Anypoint Code Builder. ### Understanding the EDI Schema Language HL7 EDI Connector uses a YAML format called EDI Schema Language (ESL) to represent EDI schemas. Basic ESLs define the structure of Electronic Data Interchange (EDI) messages in terms of: - structures (_message structures_, in HL7 terminology) - groups - segments, composites, and elements You can customize the HL7 schema definitions to suit your data by copying and editing the schema definitions directly or by using a console tool to generate a simplified schema based on one or more sample documents. Alternatively, you can use an overlay schema for HL7, as with other EDI formats, but this option is not recommended due to the complexity of HL7 definitions. You can define your own schemas from scratch, or you can copy and edit a base HL7 schema definition to suit your data as shown in the [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ### Finding the HL7 Schema Location To use the connector, you must know the locations of the schemas in your project. If you’re using the out-of-the-box HL7 schemas and not customizing anything, the standard schema location follows the `/hl7/{version}/{message structure}.esl` pattern and the lax schema location follows the `/hl7lax/{version}/{message structure}.esl` pattern. For example, if you’re using the 2.5.1 schema version and the ADT\_A01 message structure, your schema location is `/hl7/v2_5_1/ADT_A01.esl` for the standard version or `/hl7lax/v2_5_1/ADT_A01.esl` for the lax version. If you’re using one or more custom schemas, put these in a directory in `src/main/mule` and refer to the location using `${app.home}`. For example, if you put your ADT\_A01 schema under ``src/main/mule/mypartner/ADT_A01.esl, your schema location is `${app.home}/mypartner/ADT_A01.esl``. The Mule runtime engine automatically checks `src/main/mule` for any locations that contain the `${app.home}` value. ## The Hierarchy of X12 EDI Connector Message Structure Use this connector to read or write HL7 documents into (or from) the canonical ER7 message structure. This structure is a hierarchy of Java Maps and Lists. You use either DataWeave or code to manipulate them. Each transaction structure is defined in the schemas. The message itself contains the following keys, some of which apply only to either the read operation or the write operation, as indicated:
Key NameDescription

ACK (read only)

Message generated by the module during the read operation. The MSA-01 acknowledgment code value is based on the parser configuration settings.

Data (read or write)

Wrapper for message data, with a key matching the message structure ID value that links to the actual data. Allows different messages to be included in the metadata and handled in DataWeave mappings.

Delimiters (read or write)

The delimiters used for the message. The characters in the string of delimiters are interpreted based on their position in string, in the following order: component separator, repetition separator, escape character, and subcomponent separator, with a value of U indicating no value in that position.

Errors (read only)

A list of errors associated with the input message.

Id

Message structure ID.

MSH (read only)

Link that receives MSH segment data.

Name (read only)

Message structure name.

Individual messages have their own maps, with keys matching the segments of the message. For example, an ACK message uses the message structure ID ACK, and the data for the sent or received ACK message is an ACK value in the data map. The ACK message is itself a map, and the segments and groups of the message are represented as maps (in the case of singleton instances) or lists of maps (for repeating instances) with positional keys. In two special cases, use generic handling for data that is not included in a schema definition. The first case is HL7 values of the `varies` type. Because these values consist of any structure of components and subcomponents that can be repeated, the parser uses a list of map representations for each `varies` of type. The keys in each map are generated as the value is parsed, matching standard HL7 value names with two digits used for each nesting level. For example, a simple text value for an `OBX-05 Observation Value` field would use the key `OBX-05` in a map. If there are two components present, they use keys `OBX-05-01` and `OBX-05-02`. The second case is when extension segments have tags that match a pattern configured under parser options. These are similar in structure to the `varies` values, with the exception of only being within a single map for the entire segment. The maps containing extension segment data are added to the basic message map in lists with the key `ExtensionSegs`. In addition to the actual extension segment data, the map for the extension segment contains two other keys:
KeyDescription

Ident

The extension segment identifier (tag).

Position

The position of the segment within the message structure, as a two-digit string. This is the same as the position of the immediately preceding defined segment, as defined in the schema. If a ZVN extension segment is used following the EVN segment in an ADT_A01 message structure, the ZVN is at position 03).

If extension segments are used in nested groups, the list containing those segments are included in the map representing that group. Extension segments are ordered by position in the lists created by the parser, and must also be ordered by position when writing. ### About Sending Acknowledgments An ACK (acknowledgment) message is an HL7 message that enables you to acknowledge to a message sender that your application has received a message. ACK messages are the same as any other HL7 message write operations, except that you set the ACK message to what was generated during the read operation as the output message under a `Data` key. Here is an example: ```xml \ ... ... ``` The generated ACK messages have MSH data set up for sending back to the sender of the original message, so you don’t need to change anything in the data to perform the send. If you include an ACK message schema in your configuration, that schema is used to both receive and generate ACK messages. If you don’t specify an ACK schema, the standard `hl7/v2_5_1/ACK.esl` schema default is used. ## Exchange Templates and Examples [Anypoint Exchange](https://www.mulesoft.com/exchange/) provides both templates and examples that you can use as starting points for your apps and examples that illustrate a complete solution. ## Next Step After you complete the prerequisites, you are ready to create your own app and configure the connector using [Anypoint Studio](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-studio). ## See Also [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange) [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.2 --- # HL7 EDI Connector 4.2 Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Configurations --- ### Config #### Parameters
NameTypeDescriptionDefault ValueRequired

Name

String

Name for this configuration. Connectors reference the configuration with this name.

x

Connection

Connection

Connection type for this configuration.

x

Expiration Policy

ExpirationPolicy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the instance expires at the exact moment that it becomes eligible. Mule purges the instances when appropriate.

Mule application namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless the send configuration or message parameters override it.

Mule Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Mule Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Partner Application Namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Schema definitions

Array of String

List of schema paths for the connector to use. The paths can be filesystem paths or classpaths.

x

Event and message to message structure map path

String

Path to a YAML file that defines the mapping of the event code and message code to the message structure ID:

  • If working with multiple message structures, this mapping definition supports using MSH-9-1 and MSH-9-2 to determine the message structure when MSH-9-3 is not present in a message.

  • If only a single message structure is present in the schemas for which this message structure is used, the connector uses the message structure to parse all messages.

  • If MSH-9-3 is present in a message, the connector ignores the MSH-9-1 and MSH-9-2 values.

HL7 Message character encoding

Enumeration, one of:

  • ASCII

  • BIG_5

  • EUC_KR

  • EUC_TW

  • GB_18030

  • ISO_8859_1

  • ISO_8859_15

  • ISO_8859_2

  • ISO_8859_3

  • ISO_8859_4

  • ISO_8859_5

  • ISO_8859_6

  • ISO_8859_7

  • ISO_8859_8

  • ISO_8859_9

  • JIS0208

  • JIS_X0201

  • JIS_X0212

  • UTF_16

  • UTF_32

  • UTF_8

Character encoding for HL7 messages. This is the default for receive messages when MSH-18 is not present and for send messages when MSH-18 is not present in the send message data.

ASCII

Disable numeric prefixes for data keys

Boolean

Uses segment and group IDs directly as keys in the data, rather than prefixing the segment and group IDs with position values.

true

Required processing ID

Enumeration, one of:

  • DEBUGGING

  • PRODUCTION

  • TRAINING

Value to match the MSH-11-1 processing ID. If set, only messages with the specified processing ID are accepted for processing. Messages with other processing ID values or with no processing ID specified are rejected with an exception.

Pattern for generic extension segment names

String

Java regular pattern for segment names to treat as generic extension segments. If specified, segment names matching this pattern are allowed anywhere in the message and are converted to maps of string values for elements and composites.

Fail when required value missing

Boolean

Whether to reject a message if a required value is missing:

  • If true, a message with this error is rejected.

  • If false, the value is ignored and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when value length outside allowed range

Boolean

Whether to reject a message if the receive value length is outside of allowed the range:

  • If true, a message with this error is rejected.

  • If false, the value is used and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when invalid character in value

Boolean

Whether to reject a message if the receive value contains an invalid character:

  • If true, a message with this error is rejected.

  • If false, the character is either passed through or substituted, and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of value

Boolean

Whether to reject a message if the receive value is repeated too many times:

  • If true, a message with this error is rejected.

  • If false, the value is accepted and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unknown segment in message

Boolean

Whether to reject a message if it contains an unknown segment:

  • If true, a message with this error is rejected.

  • If false, the segment is ignored and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when segment out of order in message set

Boolean

Whether to reject a message when a segment in a message set is out of order:

  • If true, a message with this error is rejected.

  • If false and the segment can be reordered, the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unused segment included in message set

Boolean

Whether to reject a message when a segment marked as unused is included in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted and the unused segment is ignored.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of segment

Boolean

Whether to reject a message when a segment occurs too many times in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted.

In either case, the error is reported in an ERR segment.

false

HL7 Message segment terminator

Enumeration, one of:

  • CR

  • LF

Value for the segment terminator.

CR

## Connection Type ### Parameters
NameTypeDescriptionDefault ValueRequired

Reconnection

Configures a reconnection strategy to use when a connector operation fails to connect to an external server.

## Operations - [Read](#read) - [Write](#write) ### Read `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Read Content

Binary

Input payload.

#[payload]

Target Variable

String

Name of the variable that stores the operation’s output.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Object

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ### Write `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Write Content

Object

Output payload.

#[payload]

Streaming Strategy

Configures how Mule processes streams. Repeatable streams are the default behavior.

Target Variable

String

The name of a variable that stores the output of the operation.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Binary

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ## Types ### Expiration Policy Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.
FieldTypeDescriptionDefault ValueRequired

Max Idle Time

Number

Maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.

Time Unit

Enumeration, one of:

  • NANOSECONDS

  • MICROSECONDS

  • MILLISECONDS

  • SECONDS

  • MINUTES

  • HOURS

  • DAYS

A time unit that qualifies the Max Idle Time field.

### Forever Configures a forever reconnection strategy by which the connector operation attempts to reconnect at a specified frequency for as long as the Mule app runs.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

### Non-Repeatable Stream Disables the repeatable stream functionality and uses non-repeatable streams to have lower performance overhead, memory use, and cost. ### Reconnection Configures reconnection options.
FieldTypeDescriptionDefault ValueRequired

Fails deployment when test connection fails

Boolean

What to do if, when an app is deployed, a connectivity test does not pass after exhausting the associated reconnection strategy:

  • true

    Allow the deployment to fail.

  • false

    Ignore the results of the connectivity test.

Reconnection Strategy

Reconnection strategy to use.

### Repeatable File Store Stream Configures the repeatable file store streaming strategy by which Mule keeps a portion of the stream content in memory. If the stream content is larger than the configured buffer size, Mule backs up the buffer’s content to disk and then clears the memory.
FieldTypeDescriptionDefault ValueRequired

Max In Memory Size

Number

Maximum amount of memory that the stream can use for data. If the amount of memory exceeds this value, Mule buffers the content to disk. To optimize performance:

  • Configure a larger buffer size to avoid the number of times Mule needs to write the buffer on disk. This increases performance, but it also limits the number of concurrent requests your application can process, because it requires additional memory.

  • Configure a smaller buffer size to decrease memory load at the expense of response time.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Max In Memory Size field.

### Repeatable In Memory Stream Configures the in-memory streaming strategy by which the request fails if the data exceeds the maximum buffer size. Always run performance tests to find the optimal buffer size for your specific use case.
FieldTypeDescriptionDefault ValueRequired

Initial Buffer Size

Number

Initial amount of memory to allocate to the data stream. If the streamed data exceeds this value, the buffer expands by the Buffer Size Increment, with an upper limit of the Max Buffer Size value.

Buffer Size Increment

Number

Amount by which the buffer size expands if it exceeds its initial size. Setting a value of 0 or lower specifies that the buffer can’t expand.

Max Buffer Size

Number

Maximum size of the buffer. If the buffer size exceeds this value, Mule raises a STREAM_MAXIMUM_SIZE_EXCEEDED error. A value of less than or equal to 0 means no limit.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Initial Buffer Size, Buffer Size Increment, and Max Buffer Size fields.

### Standard Configures a standard reconnection strategy, which specifies how often to reconnect and how many reconnection attempts the connector operation can make.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

Reconnection Attempts

Number

How many reconnection attempts the Mule app can make.

## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # HL7 EDI Connector 4.3 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Connector for HL7 EDI (HL7 EDI Connector) is a collection of features that facilitate integration with healthcare systems by providing the tools needed to easily create, read, and transform HL7 version v2.x messages within Mule. Health Level Seven International (HL7) is a standards development organization that defines a set of standards for the transport and communication of healthcare information. For compatibility information and fixed issues, see the HL7 EDI Connector Release Notes. Standard schema definitions are included in HL7 EDI Connector for HL7 versions 2.1, 2.2, 2.3.1, 2.3, 2.4, 2.5, 2.5.1, 2.6, 2.7, 2.7.1, 2.8, 2.8.1. The schemas are provided in two forms: - Standard HL7 Uses required or optional status data types, field lengths, and repetition counts (as listed) for each HL7 version. - Lax HL7 All segments and value items are optional. These low-level data types are treated as simple strings. Field lengths and repetition counts are not enforced. Both forms of schemas are available in the connector’s `classpath`. Standard HL7 schemas use the path `/hl7/v2_5_1/ADT_A01.esl`. Lax schemas use the path `/hl7lax/v2_5_1/ADT_A01.esl`. The schema definitions you need for [HL7 supplied schemas](https://docs.mulesoft.com/hl7-connector/4.3/hl7-schemas) are included. For complete information about schemas, see [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ## Before You Begin To use this connector, you must be familiar with: - Anypoint Connectors - Mule runtime engine (Mule) - Elements and global elements in a Mule flow - Creating a Mule app using Anypoint Studio or Anypoint Code Builder - HL7 EDI Connector To use HL7 EDI Connector, you must have: - Purchased a MuleSoft license for HL7. Contact your Account Representative about purchasing a license. - Anypoint Studio or Anypoint Code Builder. ### Understanding the EDI Schema Language HL7 EDI Connector uses a YAML format called EDI Schema Language (ESL) to represent EDI schemas. Basic ESLs define the structure of Electronic Data Interchange (EDI) messages in terms of: - structures (_message structures_, in HL7 terminology) - groups - segments, composites, and elements You can customize the HL7 schema definitions to suit your data by copying and editing the schema definitions directly or by using a console tool to generate a simplified schema based on one or more sample documents. Alternatively, you can use an overlay schema for HL7, as with other EDI formats, but this option is not recommended due to the complexity of HL7 definitions. You can define your own schemas from scratch, or you can copy and edit a base HL7 schema definition to suit your data as shown in the [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ### Finding the HL7 Schema Location To use the connector, you must know the locations of the schemas in your project. If you’re using the out-of-the-box HL7 schemas and not customizing anything, the standard schema location follows the `/hl7/{version}/{message structure}.esl` pattern and the lax schema location follows the `/hl7lax/{version}/{message structure}.esl` pattern. For example, if you’re using the 2.5.1 schema version and the ADT\_A01 message structure, your schema location is `/hl7/v2_5_1/ADT_A01.esl` for the standard version or `/hl7lax/v2_5_1/ADT_A01.esl` for the lax version. If you’re using one or more custom schemas, put these in a directory in `src/main/mule` and refer to the location using `${app.home}`. For example, if you put your ADT\_A01 schema under ``src/main/mule/mypartner/ADT_A01.esl, your schema location is `${app.home}/mypartner/ADT_A01.esl``. The Mule runtime engine automatically checks `src/main/mule` for any locations that contain the `${app.home}` value. ## The Hierarchy of X12 EDI Connector Message Structure Use this connector to read or write HL7 documents into (or from) the canonical ER7 message structure. This structure is a hierarchy of Java Maps and Lists. You use either DataWeave or code to manipulate them. Each transaction structure is defined in the schemas. The message itself contains the following keys, some of which apply only to either the read operation or the write operation, as indicated:
Key NameDescription

ACK (read only)

Message generated by the module during the read operation. The MSA-01 acknowledgment code value is based on the parser configuration settings.

Data (read or write)

Wrapper for message data, with a key matching the message structure ID value that links to the actual data. Allows different messages to be included in the metadata and handled in DataWeave mappings.

Delimiters (read or write)

The delimiters used for the message. The characters in the string of delimiters are interpreted based on their position in string, in the following order: component separator, repetition separator, escape character, and subcomponent separator, with a value of U indicating no value in that position.

Errors (read only)

A list of errors associated with the input message.

Id

Message structure ID.

MSH (read only)

Link that receives MSH segment data.

Name (read only)

Message structure name.

Individual messages have their own maps, with keys matching the segments of the message. For example, an ACK message uses the message structure ID ACK, and the data for the sent or received ACK message is an ACK value in the data map. The ACK message is itself a map, and the segments and groups of the message are represented as maps (in the case of singleton instances) or lists of maps (for repeating instances) with positional keys. In two special cases, use generic handling for data that is not included in a schema definition. The first case is HL7 values of the `varies` type. Because these values consist of any structure of components and subcomponents that can be repeated, the parser uses a list of map representations for each `varies` of type. The keys in each map are generated as the value is parsed, matching standard HL7 value names with two digits used for each nesting level. For example, a simple text value for an `OBX-05 Observation Value` field would use the key `OBX-05` in a map. If there are two components present, they use keys `OBX-05-01` and `OBX-05-02`. The second case is when extension segments have tags that match a pattern configured under parser options. These are similar in structure to the `varies` values, with the exception of only being within a single map for the entire segment. The maps containing extension segment data are added to the basic message map in lists with the key `ExtensionSegs`. In addition to the actual extension segment data, the map for the extension segment contains two other keys:
KeyDescription

Ident

The extension segment identifier (tag).

Position

The position of the segment within the message structure, as a two-digit string. This is the same as the position of the immediately preceding defined segment, as defined in the schema. If a ZVN extension segment is used following the EVN segment in an ADT_A01 message structure, the ZVN is at position 03).

If extension segments are used in nested groups, the list containing those segments are included in the map representing that group. Extension segments are ordered by position in the lists created by the parser, and must also be ordered by position when writing. ### About Sending Acknowledgments An ACK (acknowledgment) message is an HL7 message that enables you to acknowledge to a message sender that your application has received a message. ACK messages are the same as any other HL7 message write operations, except that you set the ACK message to what was generated during the read operation as the output message under a `Data` key. Here is an example: ```xml \ ... ... ``` The generated ACK messages have MSH data set up for sending back to the sender of the original message, so you don’t need to change anything in the data to perform the send. If you include an ACK message schema in your configuration, that schema is used to both receive and generate ACK messages. If you don’t specify an ACK schema, the standard `hl7/v2_5_1/ACK.esl` schema default is used. ## Exchange Templates and Examples [Anypoint Exchange](https://www.mulesoft.com/exchange/) provides both templates and examples that you can use as starting points for your apps and examples that illustrate a complete solution. ## Next Step After you complete the prerequisites, you are ready to create your own app and configure the connector using [Anypoint Studio](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-studio). ## See Also [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange) [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # HL7 EDI Connector 4.3 Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Configurations --- ### Config #### Parameters
NameTypeDescriptionDefault ValueRequired

Name

String

Name for this configuration. Connectors reference the configuration with this name.

x

Connection

Connection

Connection type for this configuration.

x

Expiration Policy

ExpirationPolicy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the instance expires at the exact moment that it becomes eligible. Mule purges the instances when appropriate.

Mule application namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless the send configuration or message parameters override it.

Mule Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Mule Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Partner Application Namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Schema definitions

Array of String

List of schema paths for the connector to use. The paths can be filesystem paths or classpaths.

x

Event and message to message structure map path

String

Path to a YAML file that defines the mapping of the event code and message code to the message structure ID:

  • If working with multiple message structures, this mapping definition supports using MSH-9-1 and MSH-9-2 to determine the message structure when MSH-9-3 is not present in a message.

  • If only a single message structure is present in the schemas for which this message structure is used, the connector uses the message structure to parse all messages.

  • If MSH-9-3 is present in a message, the connector ignores the MSH-9-1 and MSH-9-2 values.

HL7 Message character encoding

Enumeration, one of:

  • ASCII

  • BIG_5

  • EUC_KR

  • EUC_TW

  • GB_18030

  • ISO_8859_1

  • ISO_8859_15

  • ISO_8859_2

  • ISO_8859_3

  • ISO_8859_4

  • ISO_8859_5

  • ISO_8859_6

  • ISO_8859_7

  • ISO_8859_8

  • ISO_8859_9

  • JIS0208

  • JIS_X0201

  • JIS_X0212

  • UTF_16

  • UTF_32

  • UTF_8

Character encoding for HL7 messages. This is the default for receive messages when MSH-18 is not present and for send messages when MSH-18 is not present in the send message data.

ASCII

Disable numeric prefixes for data keys

Boolean

Uses segment and group IDs directly as keys in the data, rather than prefixing the segment and group IDs with position values.

true

Required processing ID

Enumeration, one of:

  • DEBUGGING

  • PRODUCTION

  • TRAINING

Value to match the MSH-11-1 processing ID. If set, only messages with the specified processing ID are accepted for processing. Messages with other processing ID values or with no processing ID specified are rejected with an exception.

Pattern for generic extension segment names

String

Java regular pattern for segment names to treat as generic extension segments. If specified, segment names matching this pattern are allowed anywhere in the message and are converted to maps of string values for elements and composites.

Fail when required value missing

Boolean

Whether to reject a message if a required value is missing:

  • If true, a message with this error is rejected.

  • If false, the value is ignored and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when value length outside allowed range

Boolean

Whether to reject a message if the receive value length is outside of allowed the range:

  • If true, a message with this error is rejected.

  • If false, the value is used and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when invalid character in value

Boolean

Whether to reject a message if the receive value contains an invalid character:

  • If true, a message with this error is rejected.

  • If false, the character is either passed through or substituted, and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of value

Boolean

Whether to reject a message if the receive value is repeated too many times:

  • If true, a message with this error is rejected.

  • If false, the value is accepted and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unknown segment in message

Boolean

Whether to reject a message if it contains an unknown segment:

  • If true, a message with this error is rejected.

  • If false, the segment is ignored and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when segment out of order in message set

Boolean

Whether to reject a message when a segment in a message set is out of order:

  • If true, a message with this error is rejected.

  • If false and the segment can be reordered, the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unused segment included in message set

Boolean

Whether to reject a message when a segment marked as unused is included in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted and the unused segment is ignored.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of segment

Boolean

Whether to reject a message when a segment occurs too many times in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted.

In either case, the error is reported in an ERR segment.

false

HL7 Message segment terminator

Enumeration, one of:

  • CR

  • LF

Value for the segment terminator.

CR

Handle empty arrays for fields in message

Boolean

When the incoming payload contains empty arrays and the parameter is set to true, the connector includes the field separation character for optional repeatable fields.

false

## Connection Type ### Parameters
NameTypeDescriptionDefault ValueRequired

Reconnection

Configures a reconnection strategy to use when a connector operation fails to connect to an external server.

## Operations - [Read](#read) - [Write](#write) ### Read `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Read Content

Binary

Input payload.

#[payload]

Target Variable

String

Name of the variable that stores the operation’s output.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Object

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ### Write `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Write Content

Object

Output payload.

#[payload]

Streaming Strategy

Configures how Mule processes streams. Repeatable streams are the default behavior.

Target Variable

String

The name of a variable that stores the output of the operation.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Binary

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ## Types ### Expiration Policy Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.
FieldTypeDescriptionDefault ValueRequired

Max Idle Time

Number

Maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.

Time Unit

Enumeration, one of:

  • NANOSECONDS

  • MICROSECONDS

  • MILLISECONDS

  • SECONDS

  • MINUTES

  • HOURS

  • DAYS

A time unit that qualifies the Max Idle Time field.

### Forever Configures a forever reconnection strategy by which the connector operation attempts to reconnect at a specified frequency for as long as the Mule app runs.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

### Non-Repeatable Stream Disables the repeatable stream functionality and uses non-repeatable streams to have lower performance overhead, memory use, and cost. ### Reconnection Configures reconnection options.
FieldTypeDescriptionDefault ValueRequired

Fails deployment when test connection fails

Boolean

What to do if, when an app is deployed, a connectivity test does not pass after exhausting the associated reconnection strategy:

  • true

    Allow the deployment to fail.

  • false

    Ignore the results of the connectivity test.

Reconnection Strategy

Reconnection strategy to use.

### Repeatable File Store Stream Configures the repeatable file store streaming strategy by which Mule keeps a portion of the stream content in memory. If the stream content is larger than the configured buffer size, Mule backs up the buffer’s content to disk and then clears the memory.
FieldTypeDescriptionDefault ValueRequired

Max In Memory Size

Number

Maximum amount of memory that the stream can use for data. If the amount of memory exceeds this value, Mule buffers the content to disk. To optimize performance:

  • Configure a larger buffer size to avoid the number of times Mule needs to write the buffer on disk. This increases performance, but it also limits the number of concurrent requests your application can process, because it requires additional memory.

  • Configure a smaller buffer size to decrease memory load at the expense of response time.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Max In Memory Size field.

### Repeatable In Memory Stream Configures the in-memory streaming strategy by which the request fails if the data exceeds the maximum buffer size. Always run performance tests to find the optimal buffer size for your specific use case.
FieldTypeDescriptionDefault ValueRequired

Initial Buffer Size

Number

Initial amount of memory to allocate to the data stream. If the streamed data exceeds this value, the buffer expands by the Buffer Size Increment, with an upper limit of the Max Buffer Size value.

Buffer Size Increment

Number

Amount by which the buffer size expands if it exceeds its initial size. Setting a value of 0 or lower specifies that the buffer can’t expand.

Max Buffer Size

Number

Maximum size of the buffer. If the buffer size exceeds this value, Mule raises a STREAM_MAXIMUM_SIZE_EXCEEDED error. A value of less than or equal to 0 means no limit.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Initial Buffer Size, Buffer Size Increment, and Max Buffer Size fields.

### Standard Configures a standard reconnection strategy, which specifies how often to reconnect and how many reconnection attempts the connector operation can make.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

Reconnection Attempts

Number

How many reconnection attempts the Mule app can make.

## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 EDI Connector 5.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Connector for HL7 EDI (HL7 EDI Connector) is a collection of features that facilitate integration with healthcare systems by providing the tools needed to easily create, read, and transform HL7 version v2.x messages within Mule. Health Level Seven International (HL7) is a standards development organization that defines a set of standards for the transport and communication of healthcare information. For compatibility information and fixed issues, see the HL7 EDI Connector Release Notes. Standard schema definitions are included in HL7 EDI Connector for HL7 versions 2.1, 2.2, 2.3.1, 2.3, 2.4, 2.5, 2.5.1, 2.6, 2.7, 2.7.1, 2.8, 2.8.1. The schemas are provided in two forms: - Standard HL7 Uses required or optional status data types, field lengths, and repetition counts (as listed) for each HL7 version. - Lax HL7 All segments and value items are optional. These low-level data types are treated as simple strings. Field lengths and repetition counts are not enforced. Both forms of schemas are available in the connector’s `classpath`. Standard HL7 schemas use the path `/hl7/v2_5_1/ADT_A01.esl`. Lax schemas use the path `/hl7lax/v2_5_1/ADT_A01.esl`. The schema definitions you need for [HL7 supplied schemas](https://docs.mulesoft.com/hl7-connector/latest/hl7-schemas) are included. For complete information about schemas, see [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ## Before You Begin To use this connector, you must be familiar with: - Anypoint Connectors - Mule runtime engine (Mule) - Elements and global elements in a Mule flow - Creating a Mule app using Anypoint Studio or Anypoint Code Builder - HL7 EDI Connector To use HL7 EDI Connector, you must have: - Purchased a MuleSoft license for HL7. Contact your Account Representative about purchasing a license. - Anypoint Studio or Anypoint Code Builder. ### Understanding the EDI Schema Language HL7 EDI Connector uses a YAML format called EDI Schema Language (ESL) to represent EDI schemas. Basic ESLs define the structure of Electronic Data Interchange (EDI) messages in terms of: - structures (_message structures_, in HL7 terminology) - groups - segments, composites, and elements You can customize the HL7 schema definitions to suit your data by copying and editing the schema definitions directly or by using a console tool to generate a simplified schema based on one or more sample documents. Alternatively, you can use an overlay schema for HL7, as with other EDI formats, but this option is not recommended due to the complexity of HL7 definitions. You can define your own schemas from scratch, or you can copy and edit a base HL7 schema definition to suit your data as shown in the [EDI Schema Language Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference). ### Finding the HL7 Schema Location To use the connector, you must know the locations of the schemas in your project. If you’re using the out-of-the-box HL7 schemas and not customizing anything, the standard schema location follows the `/hl7/{version}/{message structure}.esl` pattern and the lax schema location follows the `/hl7lax/{version}/{message structure}.esl` pattern. For example, if you’re using the 2.5.1 schema version and the ADT\_A01 message structure, your schema location is `/hl7/v2_5_1/ADT_A01.esl` for the standard version or `/hl7lax/v2_5_1/ADT_A01.esl` for the lax version. If you’re using one or more custom schemas, put these in a directory in `src/main/mule` and refer to the location using `${app.home}`. For example, if you put your ADT\_A01 schema under `src/main/mule/mypartner/ADT_A01.esl`, your schema location is `${app.home}/mypartner/ADT_A01.esl`. The Mule runtime engine automatically checks `src/main/mule` for any locations that contain the `${app.home}` value. ## The Hierarchy of HL7 EDI Connector Message Structure Use this connector to read or write HL7 documents into (or from) the canonical ER7 message structure. This structure is a hierarchy of Java Maps and Lists. You use either DataWeave or code to manipulate them. Each transaction structure is defined in the schemas. The message itself contains the following keys, some of which apply only to either the read operation or the write operation, as indicated:
Key NameDescription

ACK (read only)

Message generated by the module during the read operation. The MSA-01 acknowledgment code value is based on the parser configuration settings.

Data (read or write)

Wrapper for message data, with a key matching the message structure ID value that links to the actual data. Allows different messages to be included in the metadata and handled in DataWeave mappings.

Delimiters (read or write)

The delimiters used for the message. The characters in the string of delimiters are interpreted based on their position in string, in the following order: component separator, repetition separator, escape character, and subcomponent separator, with a value of U indicating no value in that position.

Errors (read only)

A list of errors associated with the input message.

Id

Message structure ID.

MSH (read only)

Link that receives MSH segment data.

Name (read only)

Message structure name.

Individual messages have their own maps, with keys matching the segments of the message. For example, an ACK message uses the message structure ID ACK, and the data for the sent or received ACK message is an ACK value in the data map. The ACK message is itself a map, and the segments and groups of the message are represented as maps (in the case of singleton instances) or lists of maps (for repeating instances) with positional keys. In two special cases, use generic handling for data that is not included in a schema definition. The first case is HL7 values of the `varies` type. Because these values consist of any structure of components and subcomponents that can be repeated, the parser uses a list of map representations for each `varies` of type. The keys in each map are generated as the value is parsed, matching standard HL7 value names with two digits used for each nesting level. For example, a simple text value for an `OBX-05 Observation Value` field would use the key `OBX-05` in a map. If there are two components present, they use keys `OBX-05-01` and `OBX-05-02`. The second case is when extension segments have tags that match a pattern configured under parser options. These are similar in structure to the `varies` values, with the exception of only being within a single map for the entire segment. The maps containing extension segment data are added to the basic message map in lists with the key `ExtensionSegs`. In addition to the actual extension segment data, the map for the extension segment contains two other keys:
KeyDescription

Ident

The extension segment identifier (tag).

Position

The position of the segment within the message structure, as a two-digit string. This is the same as the position of the immediately preceding defined segment, as defined in the schema. If a ZVN extension segment is used following the EVN segment in an ADT_A01 message structure, the ZVN is at position 03).

If extension segments are used in nested groups, the list containing those segments are included in the map representing that group. Extension segments are ordered by position in the lists created by the parser, and must also be ordered by position when writing. ### About Sending Acknowledgments An ACK (acknowledgment) message is an HL7 message that enables you to acknowledge to a message sender that your application has received a message. ACK messages are the same as any other HL7 message write operations, except that you set the ACK message to what was generated during the read operation as the output message under a `Data` key. Here is an example: ```xml \ ... ... ``` The generated ACK messages have MSH data set up for sending back to the sender of the original message, so you don’t need to change anything in the data to perform the send. If you include an ACK message schema in your configuration, that schema is used to both receive and generate ACK messages. If you don’t specify an ACK schema, the standard `hl7/v2_5_1/ACK.esl` schema default is used. ## Exchange Templates and Examples [Anypoint Exchange](https://www.mulesoft.com/exchange/) provides both templates and examples that you can use as starting points for your apps and examples that illustrate a complete solution. ## Next Step After you complete the prerequisites, you are ready to create your own app and configure the connector using [Anypoint Studio](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-studio). ## See Also [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange) [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 EDI Connector 5.0 Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Configurations --- ### Config #### Parameters
NameTypeDescriptionDefault ValueRequired

Name

String

Name for this configuration. Connectors reference the configuration with this name.

x

Connection

Connection

Connection type for this configuration.

x

Expiration Policy

ExpirationPolicy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the instance expires at the exact moment that it becomes eligible. Mule purges the instances when appropriate.

Mule application namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless the send configuration or message parameters override it.

Mule Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Mule Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for Mule in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH receiving application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Partner Application Namespace ID (MSH-3-1/MSH-5-1)

String

Application namespace ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application namespace ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application namespace ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID (MSH-3-2/MSH-5-2)

String

Application universal ID for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID unless it is overridden in the send configuration or message parameters.

Partner Application universal ID Type (MSH-3-3/MSH-5-3)

String

Application universal ID type for the partner in the message header (MSH segment). If set, this value affects both receive and send message handling:

  • On the receive side, the MSH sending application universal ID type must match this value.

  • On the send side, the connector uses this value as the MSH sending application universal ID type unless it is overridden in the send configuration or message parameters.

Schema definitions

Array of String

List of schema paths for the connector to use. The paths can be filesystem paths or classpaths.

x

Event and message to message structure map path

String

Path to a YAML file that defines the mapping of the event code and message code to the message structure ID:

  • If working with multiple message structures, this mapping definition supports using MSH-9-1 and MSH-9-2 to determine the message structure when MSH-9-3 is not present in a message.

  • If only a single message structure is present in the schemas for which this message structure is used, the connector uses the message structure to parse all messages.

  • If MSH-9-3 is present in a message, the connector ignores the MSH-9-1 and MSH-9-2 values.

HL7 Message character encoding

Enumeration, one of:

  • ASCII

  • BIG_5

  • EUC_KR

  • EUC_TW

  • GB_18030

  • ISO_8859_1

  • ISO_8859_15

  • ISO_8859_2

  • ISO_8859_3

  • ISO_8859_4

  • ISO_8859_5

  • ISO_8859_6

  • ISO_8859_7

  • ISO_8859_8

  • ISO_8859_9

  • JIS0208

  • JIS_X0201

  • JIS_X0212

  • UTF_16

  • UTF_32

  • UTF_8

Character encoding for HL7 messages. This is the default for receive messages when MSH-18 is not present and for send messages when MSH-18 is not present in the send message data.

ASCII

Disable numeric prefixes for data keys

Boolean

Uses segment and group IDs directly as keys in the data, rather than prefixing the segment and group IDs with position values.

true

Required processing ID

Enumeration, one of:

  • DEBUGGING

  • PRODUCTION

  • TRAINING

Value to match the MSH-11-1 processing ID. If set, only messages with the specified processing ID are accepted for processing. Messages with other processing ID values or with no processing ID specified are rejected with an exception.

Pattern for generic extension segment names

String

Java regular pattern for segment names to treat as generic extension segments. If specified, segment names matching this pattern are allowed anywhere in the message and are converted to maps of string values for elements and composites.

Fail when required value missing

Boolean

Whether to reject a message if a required value is missing:

  • If true, a message with this error is rejected.

  • If false, the value is ignored and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when value length outside allowed range

Boolean

Whether to reject a message if the receive value length is outside of allowed the range:

  • If true, a message with this error is rejected.

  • If false, the value is used and the message is accepted.

In either case, the error is logged and reported in an ERR segment.

false

Fail when invalid character in value

Boolean

Whether to reject a message if the receive value contains an invalid character:

  • If true, a message with this error is rejected.

  • If false, the character is either passed through or substituted, and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of value

Boolean

Whether to reject a message if the receive value is repeated too many times:

  • If true, a message with this error is rejected.

  • If false, the value is accepted and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unknown segment in message

Boolean

Whether to reject a message if it contains an unknown segment:

  • If true, a message with this error is rejected.

  • If false, the segment is ignored and the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when segment out of order in message set

Boolean

Whether to reject a message when a segment in a message set is out of order:

  • If true, a message with this error is rejected.

  • If false and the segment can be reordered, the message is accepted.

In either case the error is reported in an ERR segment.

false

Fail when unused segment included in message set

Boolean

Whether to reject a message when a segment marked as unused is included in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted and the unused segment is ignored.

In either case the error is reported in an ERR segment.

false

Fail when too many repeats of segment

Boolean

Whether to reject a message when a segment occurs too many times in a message set:

  • If true, a message with this error is rejected.

  • If false, the message is accepted.

In either case, the error is reported in an ERR segment.

false

HL7 Message segment terminator

Enumeration, one of:

  • CR

  • LF

Value for the segment terminator.

CR

Handle empty arrays for fields in message

Boolean

When the incoming payload contains empty arrays and the parameter is set to true, the connector includes the field separation character for optional repeatable fields.

false

Enforce Acknowledgment ERR Segment repeatability

Boolean

Whether to enforce the repeatability of the ERR segment (count) in the acknowledgment of HL7 messages. This configuration can be used for handling of ERR segments in HL7 messages prior to v2.5.

  • If true, the connector collapses all errors into one ERR segment, with multiple errors packed as repeated ERR‑1 (ELD) field occurrences joined by the repetition terminator.

  • If false, the connector does not enforce the repeatability of the ERR segment.

In either case, the error is reported in an ERR segment.

false

## Connection Type ### Parameters
NameTypeDescriptionDefault ValueRequired

Reconnection

Configures a reconnection strategy to use when a connector operation fails to connect to an external server.

## Operations - [Read](#read) - [Write](#write) ### Read `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Read Content

Binary

Input payload.

#[payload]

Target Variable

String

Name of the variable that stores the operation’s output.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Object

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ### Write `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Write Content

Object

Output payload.

#[payload]

Streaming Strategy

Configures how Mule processes streams. Repeatable streams are the default behavior.

Target Variable

String

The name of a variable that stores the output of the operation.

Target Value

String

Expression that evaluates the operation’s output. The outcome of the expression is stored in the Target Variable field.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Binary

#### For Configurations - config #### Throws - HL7:RETRY\_EXHAUSTED - HL7:UNKNOWN - HL7:PARSE - HL7:SCHEMA - HL7:CONNECTIVITY - HL7:WRITE ## Types ### Expiration Policy Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.
FieldTypeDescriptionDefault ValueRequired

Max Idle Time

Number

Maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.

Time Unit

Enumeration, one of:

  • NANOSECONDS

  • MICROSECONDS

  • MILLISECONDS

  • SECONDS

  • MINUTES

  • HOURS

  • DAYS

A time unit that qualifies the Max Idle Time field.

### Forever Configures a forever reconnection strategy by which the connector operation attempts to reconnect at a specified frequency for as long as the Mule app runs.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

### Non-Repeatable Stream Disables the repeatable stream functionality and uses non-repeatable streams to have lower performance overhead, memory use, and cost. ### Reconnection Configures reconnection options.
FieldTypeDescriptionDefault ValueRequired

Fails deployment when test connection fails

Boolean

What to do if, when an app is deployed, a connectivity test does not pass after exhausting the associated reconnection strategy:

  • true

    Allow the deployment to fail.

  • false

    Ignore the results of the connectivity test.

Reconnection Strategy

Reconnection strategy to use.

### Repeatable File Store Stream Configures the repeatable file store streaming strategy by which Mule keeps a portion of the stream content in memory. If the stream content is larger than the configured buffer size, Mule backs up the buffer’s content to disk and then clears the memory.
FieldTypeDescriptionDefault ValueRequired

Max In Memory Size

Number

Maximum amount of memory that the stream can use for data. If the amount of memory exceeds this value, Mule buffers the content to disk. To optimize performance:

  • Configure a larger buffer size to avoid the number of times Mule needs to write the buffer on disk. This increases performance, but it also limits the number of concurrent requests your application can process, because it requires additional memory.

  • Configure a smaller buffer size to decrease memory load at the expense of response time.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Max In Memory Size field.

### Repeatable In Memory Stream Configures the in-memory streaming strategy by which the request fails if the data exceeds the maximum buffer size. Always run performance tests to find the optimal buffer size for your specific use case.
FieldTypeDescriptionDefault ValueRequired

Initial Buffer Size

Number

Initial amount of memory to allocate to the data stream. If the streamed data exceeds this value, the buffer expands by the Buffer Size Increment, with an upper limit of the Max Buffer Size value.

Buffer Size Increment

Number

Amount by which the buffer size expands if it exceeds its initial size. Setting a value of 0 or lower specifies that the buffer can’t expand.

Max Buffer Size

Number

Maximum size of the buffer. If the buffer size exceeds this value, Mule raises a STREAM_MAXIMUM_SIZE_EXCEEDED error. A value of less than or equal to 0 means no limit.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Initial Buffer Size, Buffer Size Increment, and Max Buffer Size fields.

### Standard Configures a standard reconnection strategy, which specifies how often to reconnect and how many reconnection attempts the connector operation can make.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to attempt to reconnect, in milliseconds.

Reconnection Attempts

Number

How many reconnection attempts the Mule app can make.

## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.2 --- # HL7 Supplied Schemas > For the full documentation index, see: https://docs.mulesoft.com/llms.txt These are the message structures included in the schema definitions for each version of HL7. ## Version 2.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_Q01 DSR\_Q03 MCF\_Q02 ORM\_O01 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_Q01 QRY\_Q02 UDM\_Q05 ## Version 2.2 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_P04 DSR\_Q01 DSR\_Q03 DSR\_R03 MFD\_M01 MFD\_M02 MFD\_M03 MFK\_M01 MFK\_M02 MFK\_M03 MFN\_M01 MFN\_M02 MFN\_M03 MFQ\_M01 MFQ\_M02 MFQ\_M03 MFR\_M01 MFR\_M02 MFR\_M03 NMD\_N01 NMQ\_N02 NMR\_N02 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_P04 QRY\_Q01 QRY\_Q02 QRY\_R02 UDM\_Q05 ## Version 2.3 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CRM\_C02 CRM\_C03 CRM\_C04 CRM\_C05 CRM\_C06 CRM\_C07 CRM\_C08 CSU\_C09 CSU\_C10 CSU\_C11 CSU\_C12 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q02 DSR\_Q03 EDR\_Q01 EQQ\_Q01 ERP\_Q01 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M02 MFK\_M03 MFK\_M04 MFK\_M05 MFK\_M07 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PEX\_P08 PGL\_PC6 PGL\_PC7 PGL\_PC8 PIN\_I07 PPG\_PCG PPG\_PCH PPG\_PCJ PPP\_PCB PPP\_PCC PPP\_PCD PPR\_PC1 PPR\_PC2 PPR\_PC3 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RAS\_O02 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 REF\_I13 REF\_I14 REF\_I15 RER\_RER RGR\_RGR RGV\_O01 ROR\_ROR RPA\_I08 RPA\_I09 RPA\_I10 RPA\_I11 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQA\_I09 RQA\_I10 RQA\_I11 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q01 RRA\_O02 RRD\_O02 RRE\_O01 RRG\_O02 RRI\_I12 RRI\_I13 RRI\_I14 RRI\_I15 RRO\_O02 SIU\_S12 SIU\_S13 SIU\_S14 SIU\_S15 SIU\_S16 SIU\_S17 SIU\_S18 SIU\_S19 SIU\_S20 SIU\_S21 SIU\_S22 SIU\_S23 SIU\_S24 SIU\_S26 SPQ\_Q01 SQM\_S25 SQR\_S25 SRM\_S01 SRM\_S02 SRM\_S03 SRM\_S04 SRM\_S05 SRM\_S06 SRM\_S07 SRM\_S08 SRM\_S09 SRM\_S10 SRM\_S11 SRR\_S01 SRR\_S02 SRR\_S03 SRR\_S04 SRR\_S05 SRR\_S06 SRR\_S07 SRR\_S08 SRR\_S09 SRR\_S10 SRR\_S11 SUR\_P09 TBR\_Q01 UDM\_Q05 VQQ\_Q01 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.3.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CSU\_C09 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q03 EDR\_R07 EQQ\_Q04 ERP\_R09 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M04 MFK\_M05 MFK\_M06 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORS\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PGL\_PC6 PIN\_I07 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 RER\_RER RGR\_RGR RGV\_O01 ROR\_R0R ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q09 RRA\_O02 RRD\_O02 RRE\_O02 RRG\_O02 RRI\_I12 RRO\_O02 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SUR\_P09 TBR\_R08 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.4 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O03 OMG\_O19 OML\_O21 OMN\_O07 OMP\_O09 OMS\_O05 ORD\_O04 ORF\_R04 ORG\_O20 ORL\_O22 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 OSQ\_Q06 OSR\_Q06 OUL\_R21 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K13 RSP\_K15 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K24 RSP\_K25 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Q13 RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.6 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 SUR\_P09 TCU\_U10 UDM\_Q05 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.7 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.7.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORL\_O41 ORL\_O42 ORL\_O43 ORL\_O44 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 --- product: HL7 EDI Connector version: 4.3 --- # HL7 Supplied Schemas > For the full documentation index, see: https://docs.mulesoft.com/llms.txt These are the message structures included in the schema definitions for each version of HL7. ## Version 2.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_Q01 DSR\_Q03 MCF\_Q02 ORM\_O01 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_Q01 QRY\_Q02 UDM\_Q05 ## Version 2.2 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_P04 DSR\_Q01 DSR\_Q03 DSR\_R03 MFD\_M01 MFD\_M02 MFD\_M03 MFK\_M01 MFK\_M02 MFK\_M03 MFN\_M01 MFN\_M02 MFN\_M03 MFQ\_M01 MFQ\_M02 MFQ\_M03 MFR\_M01 MFR\_M02 MFR\_M03 NMD\_N01 NMQ\_N02 NMR\_N02 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_P04 QRY\_Q01 QRY\_Q02 QRY\_R02 UDM\_Q05 ## Version 2.3 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CRM\_C02 CRM\_C03 CRM\_C04 CRM\_C05 CRM\_C06 CRM\_C07 CRM\_C08 CSU\_C09 CSU\_C10 CSU\_C11 CSU\_C12 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q02 DSR\_Q03 EDR\_Q01 EQQ\_Q01 ERP\_Q01 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M02 MFK\_M03 MFK\_M04 MFK\_M05 MFK\_M07 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PEX\_P08 PGL\_PC6 PGL\_PC7 PGL\_PC8 PIN\_I07 PPG\_PCG PPG\_PCH PPG\_PCJ PPP\_PCB PPP\_PCC PPP\_PCD PPR\_PC1 PPR\_PC2 PPR\_PC3 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RAS\_O02 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 REF\_I13 REF\_I14 REF\_I15 RER\_RER RGR\_RGR RGV\_O01 ROR\_ROR RPA\_I08 RPA\_I09 RPA\_I10 RPA\_I11 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQA\_I09 RQA\_I10 RQA\_I11 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q01 RRA\_O02 RRD\_O02 RRE\_O01 RRG\_O02 RRI\_I12 RRI\_I13 RRI\_I14 RRI\_I15 RRO\_O02 SIU\_S12 SIU\_S13 SIU\_S14 SIU\_S15 SIU\_S16 SIU\_S17 SIU\_S18 SIU\_S19 SIU\_S20 SIU\_S21 SIU\_S22 SIU\_S23 SIU\_S24 SIU\_S26 SPQ\_Q01 SQM\_S25 SQR\_S25 SRM\_S01 SRM\_S02 SRM\_S03 SRM\_S04 SRM\_S05 SRM\_S06 SRM\_S07 SRM\_S08 SRM\_S09 SRM\_S10 SRM\_S11 SRR\_S01 SRR\_S02 SRR\_S03 SRR\_S04 SRR\_S05 SRR\_S06 SRR\_S07 SRR\_S08 SRR\_S09 SRR\_S10 SRR\_S11 SUR\_P09 TBR\_Q01 UDM\_Q05 VQQ\_Q01 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.3.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CSU\_C09 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q03 EDR\_R07 EQQ\_Q04 ERP\_R09 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M04 MFK\_M05 MFK\_M06 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORS\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PGL\_PC6 PIN\_I07 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 RER\_RER RGR\_RGR RGV\_O01 ROR\_R0R ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q09 RRA\_O02 RRD\_O02 RRE\_O02 RRG\_O02 RRI\_I12 RRO\_O02 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SUR\_P09 TBR\_R08 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.4 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O03 OMG\_O19 OML\_O21 OMN\_O07 OMP\_O09 OMS\_O05 ORD\_O04 ORF\_R04 ORG\_O20 ORL\_O22 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 OSQ\_Q06 OSR\_Q06 OUL\_R21 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K13 RSP\_K15 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K24 RSP\_K25 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Q13 RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.6 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 SUR\_P09 TCU\_U10 UDM\_Q05 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.7 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.7.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORL\_O41 ORL\_O42 ORL\_O43 ORL\_O44 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # HL7 Supplied Schemas > For the full documentation index, see: https://docs.mulesoft.com/llms.txt These are the message structures included in the schema definitions for each version of HL7. ## Version 2.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_Q01 DSR\_Q03 MCF\_Q02 ORM\_O01 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_Q01 QRY\_Q02 UDM\_Q05 ## Version 2.2 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 BAR\_P01 BAR\_P02 DFT\_P03 DSR\_P04 DSR\_Q01 DSR\_Q03 DSR\_R03 MFD\_M01 MFD\_M02 MFD\_M03 MFK\_M01 MFK\_M02 MFK\_M03 MFN\_M01 MFN\_M02 MFN\_M03 MFQ\_M01 MFQ\_M02 MFQ\_M03 MFR\_M01 MFR\_M02 MFR\_M03 NMD\_N01 NMQ\_N02 NMR\_N02 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 ORU\_R03 QRY\_A19 QRY\_P04 QRY\_Q01 QRY\_Q02 QRY\_R02 UDM\_Q05 ## Version 2.3 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CRM\_C02 CRM\_C03 CRM\_C04 CRM\_C05 CRM\_C06 CRM\_C07 CRM\_C08 CSU\_C09 CSU\_C10 CSU\_C11 CSU\_C12 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q02 DSR\_Q03 EDR\_Q01 EQQ\_Q01 ERP\_Q01 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M02 MFK\_M03 MFK\_M04 MFK\_M05 MFK\_M07 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PEX\_P08 PGL\_PC6 PGL\_PC7 PGL\_PC8 PIN\_I07 PPG\_PCG PPG\_PCH PPG\_PCJ PPP\_PCB PPP\_PCC PPP\_PCD PPR\_PC1 PPR\_PC2 PPR\_PC3 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RAS\_O02 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 REF\_I13 REF\_I14 REF\_I15 RER\_RER RGR\_RGR RGV\_O01 ROR\_ROR RPA\_I08 RPA\_I09 RPA\_I10 RPA\_I11 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQA\_I09 RQA\_I10 RQA\_I11 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q01 RRA\_O02 RRD\_O02 RRE\_O01 RRG\_O02 RRI\_I12 RRI\_I13 RRI\_I14 RRI\_I15 RRO\_O02 SIU\_S12 SIU\_S13 SIU\_S14 SIU\_S15 SIU\_S16 SIU\_S17 SIU\_S18 SIU\_S19 SIU\_S20 SIU\_S21 SIU\_S22 SIU\_S23 SIU\_S24 SIU\_S26 SPQ\_Q01 SQM\_S25 SQR\_S25 SRM\_S01 SRM\_S02 SRM\_S03 SRM\_S04 SRM\_S05 SRM\_S06 SRM\_S07 SRM\_S08 SRM\_S09 SRM\_S10 SRM\_S11 SRR\_S01 SRR\_S02 SRR\_S03 SRR\_S04 SRR\_S05 SRR\_S06 SRR\_S07 SRR\_S08 SRR\_S09 SRR\_S10 SRR\_S11 SUR\_P09 TBR\_Q01 UDM\_Q05 VQQ\_Q01 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.3.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A04 ADT\_A05 ADT\_A06 ADT\_A07 ADT\_A08 ADT\_A09 ADT\_A10 ADT\_A11 ADT\_A12 ADT\_A13 ADT\_A14 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A22 ADT\_A23 ADT\_A24 ADT\_A25 ADT\_A26 ADT\_A27 ADT\_A28 ADT\_A29 ADT\_A30 ADT\_A31 ADT\_A32 ADT\_A33 ADT\_A34 ADT\_A35 ADT\_A36 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A40 ADT\_A41 ADT\_A42 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A46 ADT\_A47 ADT\_A48 ADT\_A49 ADT\_A50 ADT\_A51 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 CRM\_C01 CSU\_C09 DFT\_P03 DOC\_T12 DSR\_Q01 DSR\_Q03 EDR\_R07 EQQ\_Q04 ERP\_R09 MDM\_T01 MDM\_T02 MDM\_T03 MDM\_T04 MDM\_T05 MDM\_T06 MDM\_T07 MDM\_T08 MDM\_T09 MDM\_T10 MDM\_T11 MFK\_M01 MFK\_M04 MFK\_M05 MFK\_M06 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O01 OMN\_O01 OMS\_O01 ORD\_O02 ORF\_R04 ORM\_O01 ORN\_O02 ORR\_O02 ORS\_O02 ORU\_R01 OSQ\_Q06 OSR\_Q06 PEX\_P07 PGL\_PC6 PIN\_I07 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QCK\_Q02 QRY\_A19 QRY\_PC4 QRY\_PC9 QRY\_PCE QRY\_PCK QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 RAR\_RAR RAS\_O01 RCI\_I05 RCL\_I06 RDE\_O01 RDO\_O01 RDR\_RDR RDS\_O01 REF\_I12 RER\_RER RGR\_RGR RGV\_O01 ROR\_R0R ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQC\_I06 RQI\_I01 RQI\_I02 RQI\_I03 RQP\_I04 RQQ\_Q09 RRA\_O02 RRD\_O02 RRE\_O02 RRG\_O02 RRI\_I12 RRO\_O02 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SUR\_P09 TBR\_R08 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.4 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFQ\_M01 MFR\_M01 NMD\_N02 NMQ\_N01 NMR\_N01 OMD\_O03 OMG\_O19 OML\_O21 OMN\_O07 OMP\_O09 OMS\_O05 ORD\_O04 ORF\_R04 ORG\_O20 ORL\_O22 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 OSQ\_Q06 OSR\_Q06 OUL\_R21 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K13 RSP\_K15 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K24 RSP\_K25 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Q13 RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_K13 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.5.1 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EDR\_R07 EQQ\_Q04 ERP\_R09 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RQQ\_Q09 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SIU\_S12 SPQ\_Q08 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 SUR\_P09 TBR\_R08 TCU\_U10 UDM\_Q05 VQQ\_Q07 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.6 ACK ADR\_A19 ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A18 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A30 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 DOC\_T12 DSR\_Q01 DSR\_Q03 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M01 MFN\_M02 MFN\_M03 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn MFQ\_M01 MFR\_M01 MFR\_M04 MFR\_M05 MFR\_M06 MFR\_M07 NMD\_N02 NMQ\_N01 NMR\_N01 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORB\_O28 ORD\_O04 ORF\_R04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORM\_O01 ORN\_O08 ORP\_O10 ORR\_O02 ORS\_O06 ORU\_R01 ORU\_R30 OSQ\_Q06 OSR\_Q06 OUL\_R21 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCK\_Q02 QCN\_J01 QRY\_A19 QRY\_PC4 QRY\_Q01 QRY\_Q02 QRY\_R02 QRY\_T12 QSB\_Q16 QVR\_Q17 RAR\_RAR RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RER\_RER RGR\_RGR RGV\_O15 ROR\_ROR RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_Q11 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SQM\_S25 SQR\_S25 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 SUR\_P09 TCU\_U10 UDM\_Q05 VXQ\_V01 VXR\_V03 VXU\_V04 VXX\_V02 ## Version 2.7 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.7.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DFT\_P03 DFT\_P11 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 OSM\_R26 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 PPT\_PCL PPV\_PCA PRR\_PC5 PTR\_PCF QBP\_E03 QBP\_E22 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QRY\_PC4 QSB\_Q16 QVR\_Q17 RAS\_O17 RCI\_I05 RCL\_I06 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQC\_I05 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_Z82 RSP\_Z86 RSP\_Z88 RSP\_Z90 RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 ## Version 2.8.1 ACK ADT\_A01 ADT\_A02 ADT\_A03 ADT\_A05 ADT\_A06 ADT\_A09 ADT\_A12 ADT\_A15 ADT\_A16 ADT\_A17 ADT\_A20 ADT\_A21 ADT\_A24 ADT\_A37 ADT\_A38 ADT\_A39 ADT\_A43 ADT\_A44 ADT\_A45 ADT\_A50 ADT\_A52 ADT\_A54 ADT\_A60 ADT\_A61 BAR\_P01 BAR\_P02 BAR\_P05 BAR\_P06 BAR\_P10 BAR\_P12 BPS\_O29 BRP\_O30 BRT\_O32 BTS\_O31 CCF\_I22 CCI\_I22 CCM\_I21 CCQ\_I19 CCR\_I16 CCU\_I20 CQU\_I19 CRM\_C01 CSU\_C09 DBC\_O41 DBC\_O42 DEL\_O46 DEO\_O45 DER\_O44 DFT\_P03 DFT\_P11 DPR\_O48 DRC\_O47 DRG\_O43 EAC\_U07 EAN\_U09 EAR\_U08 EHC\_E01 EHC\_E02 EHC\_E04 EHC\_E10 EHC\_E12 EHC\_E13 EHC\_E15 EHC\_E20 EHC\_E21 EHC\_E24 ESR\_U02 ESU\_U01 INR\_U06 INU\_U05 LSU\_U12 MDM\_T01 MDM\_T02 MFK\_M01 MFN\_M02 MFN\_M04 MFN\_M05 MFN\_M06 MFN\_M07 MFN\_M08 MFN\_M09 MFN\_M10 MFN\_M11 MFN\_M12 MFN\_M13 MFN\_M15 MFN\_M16 MFN\_M17 MFN\_Znn NMD\_N02 OMB\_O27 OMD\_O03 OMG\_O19 OMI\_O23 OML\_O21 OML\_O33 OML\_O35 OML\_O39 OMN\_O07 OMP\_O09 OMQ\_O42 OMS\_O05 OPL\_O37 OPR\_O38 OPU\_R25 ORA\_R33 ORA\_R41 ORB\_O28 ORD\_O04 ORG\_O20 ORI\_O24 ORL\_O22 ORL\_O34 ORL\_O36 ORL\_O40 ORL\_O41 ORL\_O42 ORL\_O43 ORL\_O44 ORN\_O08 ORP\_O10 ORS\_O06 ORU\_R01 ORU\_R30 ORX\_O43 OSM\_R26 OSU\_O41 OUL\_R22 OUL\_R23 OUL\_R24 PEX\_P07 PGL\_PC6 PMU\_B01 PMU\_B03 PMU\_B04 PMU\_B07 PMU\_B08 PPG\_PCG PPP\_PCB PPR\_PC1 QBP\_E03 QBP\_E22 QBP\_O33 QBP\_O34 QBP\_Q11 QBP\_Q13 QBP\_Q15 QBP\_Q21 QBP\_Qnn QBP\_Z73 QCN\_J01 QSB\_Q16 QVR\_Q17 RAS\_O17 RDE\_O11 RDR\_RDR RDS\_O13 RDY\_K15 RDY\_Z80 REF\_I12 RGV\_O15 RPA\_I08 RPI\_I01 RPI\_I04 RPL\_I02 RPR\_I03 RQA\_I08 RQI\_I01 RQP\_I04 RRA\_O18 RRD\_O14 RRE\_O12 RRG\_O16 RRI\_I12 RSP\_E03 RSP\_E22 RSP\_K11 RSP\_K21 RSP\_K22 RSP\_K23 RSP\_K25 RSP\_K31 RSP\_K32 RSP\_O33 RSP\_O34 RSP\_Z82 RSP\_Z84 RSP\_Z86 RSP\_Z88 RSP\_Z90 RSP\_Znn RTB\_K13 RTB\_Knn RTB\_Z74 SDR\_S31 SDR\_S32 SIU\_S12 SLR\_S28 SRM\_S01 SRR\_S01 SSR\_U04 SSU\_U03 STC\_S33 TCU\_U10 UDM\_Q05 VXU\_V04 --- product: HL7 EDI Connector version: 4.2 --- # Using Anypoint Studio to Configure HL7 EDI Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files. To add and configure a connector in Studio: 1. [Create a Mule project](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). 6. [Configure the other connector fields](#configure-other-fields). When you run the connector, you can view the app log to check for problems in real time, as described in [View the App Log](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [HL7 EDI Reference](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-reference). ## Create a Mule Project In Studio, create a new Mule project in which to add and configure the connector: 1. In Studio, select **File > New > Mule Project**. 2. Enter a name for your Mule project and click **Finish**. ## Add the Connector to Your Mule Project Add HL7 EDI Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s `pom.xml` file: 1. In the **Mule Palette** view, click **(X) Search in Exchange**. 2. In the **Add Dependencies to Project** window, type `HL7` in the search field. 3. Click HL7 EDI in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace. ## Configure a Source A source initiates a flow when a specified condition is met. You can configure HTTP Listener as the source for the HL7 EDI Connector to initiate a flow each time the listener receives a request on the configured host and port. To configure an HTTP Listener source, follow these steps: 1. In the **Mule Palette** view, select **HTTP > Listener**. 2. Drag **Listener** to the Studio canvas. 3. On the **Listener** configuration screen, optionally change the value of the **Display Name** field. 4. Specify a value for the **Path** field. 5. Click the plus sign (**+**) next to the **Connector configuration** field to configure a global element that can be used by all instances of the HTTP Listener source in the app. 6. On the **General** tab, specify connection information for the connector. 7. On the **TLS** tab, optionally specify the TLS information for the connector. 8. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 9. Click **Test Connection** to confirm that Mule can connect with the specified server. 10. Click **OK**. ## Add a Connector Operation to the Flow When you add a connector operation to your flow, you are specifying an action for that connector to perform. To add an operation for HL7 EDI Connector, follow these steps: 1. In the **Mule Palette** view, select **HL7** and then select the desired operation. 2. Drag the operation onto the Studio canvas to the right of the input source. ## Configure a Global Element for the Connector When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials that the connector requires to access the target HL7 EDI system. To configure the global element for HL7 EDI Connector, follow these steps: 1. Select the operation in the Studio canvas. 2. In the configuration screen for the operation, click the plus sign (**+**) next to the **Connector configuration** field to access the global element configuration fields. You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. 3. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 4. Click **Test Connection** to confirm that Mule can connect with the specified server. 5. Click **OK**. ## Configure Additional Connector Fields After you configure a global element for HL7, configure the other required fields for the connector. The required fields vary depending on which connector operation you use. ## View the App Log To check for problems, you can view the app log as follows: - If you’re running the app from Anypoint Platform, the output is visible in the Anypoint Studio console window. - If you’re running the app using Mule from the command line, the app log is visible in your OS console. Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the app log in the default location `MULE_HOME/logs/.log`. ## Next Step See [Additional Configuration Information](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-config-topics) for more configuration steps. ## See Also - [HL7 EDI Connector Reference](https://docs.mulesoft.com/hl7-connector/4.2/hl7-connector-reference) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 4.3 --- # Using Anypoint Studio to Configure HL7 EDI Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files. To add and configure a connector in Studio: 1. [Create a Mule project](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). 6. [Configure the other connector fields](#configure-other-fields). When you run the connector, you can view the app log to check for problems in real time, as described in [View the App Log](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [HL7 EDI Reference](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-reference). ## Create a Mule Project In Studio, create a new Mule project in which to add and configure the connector: 1. In Studio, select **File > New > Mule Project**. 2. Enter a name for your Mule project and click **Finish**. ## Add the Connector to Your Mule Project Add HL7 EDI Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s `pom.xml` file: 1. In the **Mule Palette** view, click **(X) Search in Exchange**. 2. In the **Add Dependencies to Project** window, type `HL7` in the search field. 3. Click HL7 EDI in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace. ## Configure a Source A source initiates a flow when a specified condition is met. You can configure HTTP Listener as the source for the HL7 EDI Connector to initiate a flow each time the listener receives a request on the configured host and port. To configure an HTTP Listener source, follow these steps: 1. In the **Mule Palette** view, select **HTTP > Listener**. 2. Drag **Listener** to the Studio canvas. 3. On the **Listener** configuration screen, optionally change the value of the **Display Name** field. 4. Specify a value for the **Path** field. 5. Click the plus sign (**+**) next to the **Connector configuration** field to configure a global element that can be used by all instances of the HTTP Listener source in the app. 6. On the **General** tab, specify connection information for the connector. 7. On the **TLS** tab, optionally specify the TLS information for the connector. 8. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 9. Click **Test Connection** to confirm that Mule can connect with the specified server. 10. Click **OK**. ## Add a Connector Operation to the Flow When you add a connector operation to your flow, you are specifying an action for that connector to perform. To add an operation for HL7 EDI Connector, follow these steps: 1. In the **Mule Palette** view, select **HL7** and then select the desired operation. 2. Drag the operation onto the Studio canvas to the right of the input source. ## Configure a Global Element for the Connector When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials that the connector requires to access the target HL7 EDI system. To configure the global element for HL7 EDI Connector, follow these steps: 1. Select the operation in the Studio canvas. 2. In the configuration screen for the operation, click the plus sign (**+**) next to the **Connector configuration** field to access the global element configuration fields. You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. 3. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 4. Click **Test Connection** to confirm that Mule can connect with the specified server. 5. Click **OK**. ## Configure Additional Connector Fields After you configure a global element for HL7, configure the other required fields for the connector. The required fields vary depending on which connector operation you use. ## View the App Log To check for problems, you can view the app log as follows: - If you’re running the app from Anypoint Platform, the output is visible in the Anypoint Studio console window. - If you’re running the app using Mule from the command line, the app log is visible in your OS console. Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the app log in the default location `MULE_HOME/logs/.log`. ## Next Step See [Additional Configuration Information](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-config-topics) for more configuration steps. ## See Also - [HL7 EDI Connector Reference](https://docs.mulesoft.com/hl7-connector/4.3/hl7-connector-reference) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 EDI Connector version: 5.0 is-latest-version: true --- # Using Anypoint Studio to Configure HL7 EDI Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files. To add and configure a connector in Studio: 1. [Create a Mule project](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). 6. [Configure the other connector fields](#configure-other-fields). When you run the connector, you can view the app log to check for problems in real time, as described in [View the App Log](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [HL7 EDI Reference](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-reference). ## Create a Mule Project In Studio, create a new Mule project in which to add and configure the connector: 1. In Studio, select **File > New > Mule Project**. 2. Enter a name for your Mule project and click **Finish**. ## Add the Connector to Your Mule Project Add HL7 EDI Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s `pom.xml` file: 1. In the **Mule Palette** view, click **(X) Search in Exchange**. 2. In the **Add Dependencies to Project** window, type `HL7` in the search field. 3. Click HL7 EDI in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace. ## Configure a Source A source initiates a flow when a specified condition is met. You can configure HTTP Listener as the source for the HL7 EDI Connector to initiate a flow each time the listener receives a request on the configured host and port. To configure an HTTP Listener source, follow these steps: 1. In the **Mule Palette** view, select **HTTP > Listener**. 2. Drag **Listener** to the Studio canvas. 3. On the **Listener** configuration screen, optionally change the value of the **Display Name** field. 4. Specify a value for the **Path** field. 5. Click the plus sign (**+**) next to the **Connector configuration** field to configure a global element that can be used by all instances of the HTTP Listener source in the app. 6. On the **General** tab, specify connection information for the connector. 7. On the **TLS** tab, optionally specify the TLS information for the connector. 8. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 9. Click **Test Connection** to confirm that Mule can connect with the specified server. 10. Click **OK**. ## Add a Connector Operation to the Flow When you add a connector operation to your flow, you are specifying an action for that connector to perform. To add an operation for HL7 EDI Connector, follow these steps: 1. In the **Mule Palette** view, select **HL7** and then select the desired operation. 2. Drag the operation onto the Studio canvas to the right of the input source. ## Configure a Global Element for the Connector When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials that the connector requires to access the target HL7 EDI system. To configure the global element for HL7 EDI Connector, follow these steps: 1. Select the operation in the Studio canvas. 2. In the configuration screen for the operation, click the plus sign (**+**) next to the **Connector configuration** field to access the global element configuration fields. You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. 3. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 4. Click **Test Connection** to confirm that Mule can connect with the specified server. 5. Click **OK**. ## Configure Additional Connector Fields After you configure a global element for HL7, configure the other required fields for the connector. The required fields vary depending on which connector operation you use. ## View the App Log To check for problems, you can view the app log as follows: - If you’re running the app from Anypoint Platform, the output is visible in the Anypoint Studio console window. - If you’re running the app using Mule from the command line, the app log is visible in your OS console. Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the app log in the default location `MULE_HOME/logs/.log`. ## Next Step See [Additional Configuration Information](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-config-topics) for more configuration steps. ## See Also - [HL7 EDI Connector Reference](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-reference) - [Salesforce Help](https://help.salesforce.com)