|
All vendors, billing agents, clearinghouses, and providers who have created their own electronic transactions submission software are required to
engage in the ACS EDI Gateway testing process before they will be entered into production mode. ACS EDI Gateway provides companion guides for developers to use in coding their software. The
companion guides provide payer-specific requirements and are to be used in conjunction with the ANSI X12N Implementation Guides. Submitters who have created their own software will be required to test with
EDIFECS to validate their transactions for HIPAA compliance before submitting test files to ACS EDI Gateway. After completing the ACS EDI Gateway enrollment process, the submitter must obtain the EDIFECS website
address, logon ID, and password from an ACS business analyst. Test files submitted to EDIFECS will be analyzed for HIPAA compliance based on the seven levels of testing as defined by WEDI SNIP. The submitter
must address any errors discovered by EDIFECS during the analysis before moving on to test with ACS EDI Gateway. When the submitter has certification from EDIFECS that an error-free transaction has
passed, the ACS business analyst and the submitter will schedule a communication test with ACS EDI Gateway. Upon successful completion of testing with ACS EDI Gateway, the submitter will be moved into production
for the specified X12N format. |
