Using Anypoint Studio to Configure X12 EDI Connector 2.7 - Mule 4

Form and validation

X12 form and validation (standard X12, HIPAA SNIP Type 1, or HIPAA SNIP Type 2)

Schema definitions

Manually create or edit the list of schema definitions for the message structures to use. They all need to use the same form (either X12 or HIPAA).

Character encoding

X12 character encoding, used for both send and receive messages

Character set

X12 character set allowed in string data (BASIC, EXTENDED, or UNRESTRICTED)

Substitution character

String substitution character, used to replace invalid characters in string data

Version identifier suffix

Version identifier code suffix, specifying a value appended to the base schema version in the GS08 Version / Release / Industry Identifier Code field

Enforce length limits

Enforce minimum and maximum lengths for receive values

Enforce character set

Enforce allowed character set

Enforce value repeats

Enforce repetition count limits for receive values

Allow unknown segments

Allow unknown segments in a transaction set

Enforce segment order

Enforce segment order in a transaction set

Allow unused segments

Allow segments marked as Unused in a transaction set

Enforce segment repeats

Enforce segment repetition count limits in a transaction set

Require unique interchanges

Require unique ISA Interchange Control Numbers (ISA13)

Require unique groups

Enforce globally unique Group Control Numbers (GS06) for received functional groups

Require unique transactions

Enforce globally unique Transaction Set Control Numbers (ST02) for received transaction sets

Store time-to-live

Set the minimum number of days to store interchange, group, and transaction set numbers for checking uniqueness

Acknowledge every transaction

Include a separate AK2/AK5 (997) or AK2/IK5 (999) acknowledgment for every received transaction set. Instead of using implicit acknowledgments for transaction sets without errors

Generate 999 acknowledgments

Generate 999 Implementation Acknowledgments, rather than the 997 Functional Acknowledgments default. The support for 999 Implementation Acknowledgments does not include CTX segment generation.

Report segment details

Report segment error details to sender in the generated 997 or 999 acknowledgments

Include Acknowledgement schema

Automatically include a standard 997 or 999 schema that matches the generated acknowledgment in the configuration for received messages

Acknowledgment schema path

Set the path to a Functional Acknowledgment schema to be used for generated acknowledgments such as /hipaa/005010X231A1/999.esl, that uses the standard HIPAA 005010X231A1 acknowledgment. The schema type included in the path must match the Generate 999 Functional Acknowledgments setting (false for 997, true for 999). If you do not set the path, the parser uses a hardcoded X12 997 or 999 schema, as appropriate.

Enforce conditional rules

Enforce conditional rules for receive values

Data element separator

Specify characters when writing messages

Component element separator

Specify characters when writing messages

Repetition separator

Specify characters when writing messages

Segment terminator

Specify characters when writing messages

Segment line ending

Line ending written between segments, used to make the output more readable

Unique group numbers

Whether to generate unique GS group control numbers across interchanges

Unique transaction numbers

Whether to generate unique ST transaction set control numbers across groups and interchanges

Implementation reference

An implementation convention reference (ST03) value

Initial interchange number

The starting interchange control number. Only used when no current value is found in the object store

Initial group number

The starting group control number. Only used when no current value is found in the object store

Initial transaction number

The starting transaction set control number. Only used when no current value is found in the object store

Request acknowledgments

Whether to request interchange acknowledgments (ISA14)

Default usage indicator

The default interchange usage indicator (ISA15). Used when no value is present in the message data

Use supplied values

Whether to use supplied values for control segment information (control numbers, in particular). The default behavior is always generate control numbers when writing. This allows you to use chosen values

Output mime type

Whether to use the default output MIME type application/plain, or the X12-specific alternative application/edi-x12.

Enforce length limits

Whether to enforce length limits on input data

Enforce conditional rules

Whether to enforce conditional rules on input data. The default is to ignore conditional rules

Interchange number key

The key-value pair of the interchange control key and interchange control number

Group number key

The key-value pair of group control key and group control number

Transaction number key

The key-value pair of the transaction control key and transaction control number