An EDI document can be further customized using the Self Service Platform. It can be customized using the following three Self Service components:
Test Data Cases (G-Cases)
With G-Cases, users can customize the EDI Document/Transaction Set based on a specific test case or business scenario (e.g., Institutional Health Insurance Claim, Ambulance Claim, Adding Subscriber Coverage).
Each G-Case represents one test case or business scenario. Within a G-Case, users can customize the following:
- Segments/Loops included within the generated EDI Document/Transaction Set
- Number of generated Documents/Transaction Sets
- Number of generated Segments/Loops (e.g., number of claims, number of service lines) within a Document/Transaction Set
- Customize the values generated for each Element/Attribute
GenRocket provides accelerated G-Cases based on standard business scenarios for each EDI Document/Transaction Set.
These G-Cases are automatically provided within the EDI Project and accessed using the G-Cases button within the EDI Management Dashboard. The image below shows the accelerated G-Cases for an 837I EDI Document.
Additional G-Cases Information
|G-Cases Documentation||Learn more by viewing the standard G-Cases documentation.|
|EDI Test Data Cases (G-Cases) Overview||Learn more about using G-Cases to customize EDI Documents or Transaction Sets.|
|EDI: How to Copy a G-Case Suite or G-Case||Learn more about copying EDI G-Case Suites and G-Cases.|
|EDI: How to Enable/Disable Segments and Loops in G-Cases||Learn more about enabling and disabling EDI Segments and Loops in G-Cases.|
|EDI: How to Add Domains for Segments/Loops to a G-Case||Learn more about adding Domains to EDI Segments and Loops in G-Cases.|
|EDI: How to set the Loop Count for Segments/Loops in G-Cases||Learn more about setting the Loop Count for EDI Segments and Loops in G-Cases.|
|EDI: How to Customize Generators in a G-Case Element/Attribute||Learn more about customizing Generators for an EDI G-Case Element.|
|EDI G-Cases: Using grEnable to Dynamically Turn Segments On and Off||Learn more about using the grEnable Attribute to dynamically turn segments on and off.|
Test Data Rules (G-Rules)
G-Rules may be created within a suite and added to a G-Case to apply specific business logic during EDI test data generation. A G-Rule Suite may be added to one or more G-Cases and is applied automatically when the G-Case is used to generate the EDI Documents/Transaction Sets.
Additional G-Rules Information
|G-Rules Documentation||Learn more by viewing the standard G-Rules documentation.|
|EDI: Test Data Rules (G-Rules) Overview||Learn more about using G-Rules for EDI Documents and Transaction Sets.|
|EDI: G-Rules Example||See a step-by-step example of using G-Rules with EDI.|
Test Data Queries (G-Queries)
G-Queries may be used to query real data within a database, CSV file, or Excel file and map it to a specific Domain Attribute (i.e., Element) within the EDI Project. The generated EDI Document/Transaction Set will contain the real value that was queried from the Database or CSV File.
An increased number of G-Queries will increase the time it takes to generate EDI test data.
Additional G-Queries Information
|G-Queries Documentation||Learn more by viewing the standard G-Queries documentation.|
|EDI: Test Data Queries (G-Queries) Overview||Learn more about using G-Queries for EDI Documents and Transaction Sets.|
|EDI: G-Queries CSV File Example||See a step-by-step example of using G-Queries with EDI using CSV files.|