Testing — EDI Transactions
(1)When a trading partner or authorized EDI submitter registers an EDI transaction with the Department, the Department may require testing before authorizing the transaction. Testing may include third party and business-to-business testing. An EDI submitter must be able to demonstrate its capacity to send and receive each transaction type for which it has registered. The Department will reject any EDI transaction if an EDI submitter either refuses or fails to comply with the Department testing requirements.
(2)The Department may require EDI submitters to complete compliance testing at an EDI submitter’s expense for each transaction type if either the Department or an EDI submitter has experienced a change to hardware or software applications by entering into business-to-business testing.
(3)When third party or business-to-business testing is completed to the Department’s satisfaction, the Department will notify an EDI submitter that it will register and accept the transactions in the production environment. This notification authorizes an EDI submitter to submit the registered EDI transactions to the Department for processing and response, as applicable. If there are any changes in the trading partner or EDI submitter authorization, profile data or EDI registration information on file with the Department, updated information must be submitted to the Department as required in OAR 407-120-0190 (Material Changes).
(4)Testing will be conducted using secure electronic media communications methods.
(5)An EDI submitter may be required to re-test with the Department if the Department format changes or if the EDI submitter format changes.
Rule 407-120-0150 — Testing — EDI Transactions,