2023.1:EDI Integration (Functionality)
|
This article is about an older version of Grooper. Information may be out of date and UI elements may have changed. | |
| 2025 | 2023.1 |
EDI Integration refers to Grooper's ability to process EDI files.
|
|
You may download the ZIP(s) below and upload it into your own Grooper environment (version 2023.1). The first contains one or more Batches of sample documents. The second contains one or more Projects with resources used in examples throughout this article. |
About
This article instructs users about features designed to process EDI files. Grooper can do the the following things with EDI files:
- Create a Data Model from an X12 EDI schema using Grooper's Schema Importer.
- Collect data from an EDI file using the "EDI File - Load Data" command.
|
FYI |
Grooper's EDI integration was born from a necessity for Grooper to efficiently collect data from medical EDI files. At the time of writing this article Grooper supports the following EDI schemas:
|
How To
Build a Data Model from an EDI schema
Here, we will show you how to use Grooper's EDI integration features to build a Data Model from an EDI schema and collect information from an EDI file.
Follow the instructions in the screenshots below.
- With the "EDI Integration - Batch" selected...
- ...on the "Viewer" tab...
- ...we can see the contents of this EDI file. This is a standardized format used by businesses to send data in a way that might typically be seen in the form of a document like an "Invoice" or "EOB Form". Understanding the structure of this document, especially to the untrained eye, is daunting at best. Grooper will do the hard work for us.
Selecting an EDI Schema
There is a massive library of EDI standards, and Grooper has built into a small selection of X12 schemas to choose from. These act as templates that will populate a Data Model with all the appropriate "Data Elements" necessary to house all data from a given format.
- Right-click on the "EDI Integration" Data Model and choose Import Schema.
- Check the Remove Existing property if you want to remove existing "Data Elements" from the model.
- In the "Import Schema" dialog click the drop-down for the Source property and choose EDI Schema Importer.
- Once set, expand the sub-properties of Source.
- Choose X12 837 Professional in the drop-down for the X12 Schema property.
- This action has created a massive assortment of requisite "Data Elements" for the chosen standard, including validation.
Execute Activity to Collect EDI Data
Configure the 
Batch Process Step
Extraction using EDI Schemas does not leverage the standard Extract activity. Instead, the Execute activity will be used.
- Select the "Execute"
Batch Process Step in the "EDI Process" Batch Process. - Click the ellipsis button for the Commands property which will open the "Commands" dialog box.
- In the "Commands" dialog box, click the "Add" button to add a Command and set it to EDI File - Load Data. You will see a command added to the command list.
- Click the ellipsis button for the Mappings property which will open the "Mappings" dialog box.
- In the "Mappings" dialog box, click the "Add" button to add a Mapping and set the Schema Name property to X12 837 Professional". You will see a mapping added to the mapping list.
- Click the drop-down for the "Content Type" property and set it to the 837 Prof
Document Type. Click "OK" to confirm changes and close all dialog boxes.
Test the Batch Process Step
- With the "Execute" Batch Process Step selected, go to the "Activity Testing" tab.
- Select the document from the "EDI Integration - Batch" in the "Batch Viewer".
- Click the "Test" button to test the activity and get extraction results.
Data View to see Results
- To view results, go to the "Data Review" Batch Process Step.
- Go to the "Activity Tester" tab.
- Select the "EDI Integration - Batch" in the "Batch Viewer".
- Click the Test button to test the activity.
- In the Data Viewer you will see that the appropriate data was collected.
