While EDI provides a standard syntax and data format for data transfer, it presents significant challenges for QA organizations responsible for testing the software that manages the massive volumes of payments and transactions taking place thousands of times per minute.
GenRocket addresses these test data challenges with the EDI Test Data Management Platform. With this platform, you can generate X12 EDI test data for a standardized transaction sets / documents such as EDI 837, 834, 835, and 850.
The GenRocket EDI Test Data Management Platform can be used to customize the industry standard transaction set (e.g. 837-I) to meet with a healthcare organizations specific implementation of the EDI standard. Then when testers want to generate test data for different testing scenarios GenRocket's Test Data Cases, Test Data Rules and Test Data Queries modules can be used to speed the process of creating many different test data sets to match the data requirements of each test case.
How Does It Work?
EDI Test Data Management Example
Select the EDI Management Option
Create a Project in the EDI Store
Creating a project through the EDI Store ensures that the appropriate Domains, Attributes, and Values are generated for the selected standardized EDI document.
For this example, a project will be created for an 834 document. Please note that it will take a few minutes to create the project.
- Click on EDI Store in the upper right corner.
- Locate the appropriate document in the EDI Document pane.
- Select the Version (if multiple exist).
- Click on the EDI Document Name to select it.
- Click on Create Project for the right document.
Note: To learn more about the EDI Management Dashboard, please see: EDI Management Dashboard Overview.
When you are ready to start using GenRocket test data for your many different test cases you will want to use Test Data Cases and Test Data Rules. You can build a group of test data cases and then apply specific test data rules against those cases when you want to. Test Data Cases and Test Data Rules were designed to be used together.
Note: To learn more about how to use Test Data Cases, please see: Test Data Cases.
Note: To learn more about how to use Test Data Rules, please see: Test Data Rules.
Some of the data values in your EDI transaction set will likely need to be actual production data values such as a Member ID.
You can use the Test Data Queries module to quickly replace the Generators on specified Attributes with Query Generators so that production data is queried from a database or CSV file when the document is generated.
Note: To learn more about how to use Test Data Queries please see: Test Data Queries.
These three modules can be accessed from the EDI Management Dashboard by clicking on one of the button below:
- Click on the Download Scenarios option within the EDI Management Dashboard.
- Please note that it may take a few minutes for the Scenarios to be available for downloading after viewing the EDI Project.
- Open a CMD or Terminal Window to run the Scenario Chain.
- Change the directory to your output directory.
- Enter the following command to run the Scenario Chain:
genrocket -r <ScenarioChainName.grs>
EDI Example Output
The following shows the EDI output for an EDI 834 Document.