Common use of Testing Protocol Clause in Contracts

Testing Protocol. Contractor shall execute a contract with all SoonerCare providers, or their authorized designee, for submitting and receiving MMIS data. Said contract must stipulate that SoonerCare providers, or their authorized designee, must utilize software tested and approved by Contractor as being in the proper format and compatible with the MMIS system. Contractor agrees to submit test transactions to ES prior to the submission of initial transactions of each individual transaction type to the MMIS production system, to determine that the transactions and responses comply with all requirements and specifications approved by the State of Oklahoma. The parties agree that ES and OHCA will make the sole determination that test data is acceptable. This capability to submit test transactions will be maintained by Contractor throughout the term of this Agreement. Furthermore, Contractor agrees to submit only those individual transaction types that ES has previously approved. Contractor agrees that prior to the submission of any additional transaction types to the MMIS production system, or as a result of making changes to an existing transaction type or system, to submit test transactions to ES. Additionally, Contractor shall release MMIS transmitted data only to authorized parties who have signed contracts with the Contractor. Successful testing means the ability to pass all HIPAA compliance standards, and to process electronic healthcare information transmitted by Contractor to ES.

Appears in 3 contracts

Samples: Electronic Data Exchange Agreement, Electronic Data Exchange Agreement, Electronic Data Exchange Agreement

AutoNDA by SimpleDocs

Testing Protocol. Contractor shall execute a contract with all SoonerCare providers, or their authorized designee, for submitting and receiving MMIS data. Said contract must stipulate that SoonerCare providers, or their authorized designee, must utilize software tested and approved by Contractor as being in the proper format and compatible with the MMIS system. Contractor agrees to submit test transactions to ES HPES prior to the submission of initial any transactions of each individual transaction type to the MMIS production system, to determine that the transactions and responses comply with all requirements and specifications approved by the State of Oklahoma. The parties agree that ES HPES and OHCA will make the sole determination that test data is acceptable. This capability to submit test transactions will be maintained by Contractor throughout the term of this Agreement. Furthermore, Contractor agrees to submit only those individual transaction types that ES HPES has previously approved. Contractor agrees that prior to the submission of any additional transaction types to the MMIS production system, or as a result of making changes to an existing transaction type or system, to submit test transactions to ESHPES. Additionally, Contractor shall release MMIS transmitted data only to authorized parties who have signed contracts with the Contractor. Successful testing means the ability to pass all HIPAA compliance standards, and to process electronic healthcare information transmitted by Contractor to ESHPES.

Appears in 1 contract

Samples: Electronic Data Exchange Agreement

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.