Setting Up a Custom EDI Repository

In this document, we are going to walk through the steps on configuring a custom repository in your EDI flows for accommodating any customizations in the standard EDI validation rules.

Creating a custom repository

  1. From the toolbar, go to File > New > EDI Custom Repository

  2. Now, select the relevant EDI dialect and version to modify the EDI schema rules

  1. The EDI repository divides the EDI standard schema into 4 hierarchies: Transaction Sets, Segments, Composite Elements and Elements. Each of these can be modified and saved to create a new ‘custom’ version. As an example, we will look at two use cases,

    1. In Loop 2100A, change the character limit on NM105 (middle name) from 25 to 50 characters.

    2. In Loop 2100 A, remove the pair dependency where if either NM108 or NM109 are null, it requires all other fields to be present

  1. Identify the relevant message, 834_HIPAA and navigate to the segment where the change is required: LOOP_2000 > LOOP_2100A > NM1

  2. Move to the Segments tab and find NM1. Click on the top green node of NM1

  3. Here, we see the pair dependent rule is defined. Select the rule and delete it.

  4. Click on save. This adds a new segment NM1 custom to the list

  5. Go back to the Transaction Sets tab and select the new NM1 custom segment from the dropdown menu.

  6. Click save, this adds a new custom 834_HIPAA transaction which can be used to apply to the new changes

  1. Save the custom EDI repository and add this to your trade partner profile used in the parser

  1. Next, specify this partner profile in the parser. In the messages drop down you will see the custom transaction set we had created.

  1. Select it for the modified rules to be applicable.

This concludes the documentation for using a custom EDI repository in Astera.

PreviousAstera Best PracticesNextInstallation

Last updated

Was this helpful?