Transaction Specifications definition

Transaction Specifications means with respect to a party that party's Transaction specifications, data format and certification requirements and instructions, and payer data format and technical requirements. Each party shall provide its respective Services in connection with one or more of the following "Transactions": Commercial electronic claims processing, non-commercial electronic claims processing, electronic remittance advice transmission, paper claims processing, and patient statements. Each party acknowledges with respect to Transactions submitted by it to the other party that: (i) the other party's Services will reject any Transaction that fails to meet applicable Transaction Specifications (a "Non-Conforming Transaction") and (ii) each recipient of the Transactions through the other party's Services has the right to reject any Non-Conforming Transaction. Each party reserves the right from time to time in its sole and exclusive judgment without liability to the other party or the other party's applicable customers, Partners or End-Users to suspend, revise, modify or update any part of the Services upon reasonable advance written notice to the other party. However, the parties agree to work together in good faith to accommodate regulatory or payer changes that necessitate modifications to the Services, any Transaction, or any applicable Transaction Specifications. Moreover, the parties agree to conform to changes in the Transaction Specifications for the applicable Services within fourteen (14) days after notice from the other party or within such shorter period of time as mandated by a payer.
View Source
Transaction Specifications means those certain documents and other related materials, as updated from time to time, developed and maintained by Quest Diagnostics, which describe in detail all of the required formats, data fields, code sets, protocols and other transaction specifications required to send successfully and receive Transactions to and from Quest Diagnostics, via the Database and the Licensed Software.
View Source

Examples of Transaction Specifications in a sentence

  • Vendor shall conform to changes in the Transaction Specifications resulting from any non-optional change, feature, enhancement or module of the NEIC Services furnished without charge by NEIC in or to the NEIC Services within the number of days (not less than 90) which NEIC shall designate in the notice regarding such change.

  • Providing access to reports listing, for the reporting period, the Transactions processed by DAS, the Transactions rejected by DAS due to non-compliance with the Transaction Specifications, and status messages received from the payers for specific Transactions.

  • Furthermore, MedPlus warrants that for the Term of this Agreement, the Software will perform in accordance with the Documentation, Performance Standards, Transaction Specifications and any other functional specifications (collectively, the "Specifications").

  • Each party shall use the other party's system, Services, and Transaction Specifications only in accordance with this Agreement and shall provide the other party with adequate information and cooperation and the necessary data in the proper format (as reasonably determined by the party) to enable the first party to properly furnish its Services.

  • However, the parties agree to work together in good faith to accommodate regulatory or payer changes that necessitate modifications to the Services, any Transaction, or any applicable Transaction Specifications.

  • Each party shall make no statement, representation or warranty to any of its customers, End-Users or any other third party regarding the other party's system, Services, or Transaction Specifications that derogates from the representation, disclaimers or liability limitations made by the other party in, or otherwise is inconsistent with, this Agreement.

  • Moreover, the parties agree to conform to changes in the Transaction Specifications for the applicable Services within fourteen (14) days after notice from the other party or within such shorter period of time as mandated by a payer.

  • The Merchant shall ensure that its website and any computer software used for processing transactions includes unique internet transaction identifiers and uses Secure Electronic Transaction Specifications in accordance with the requirements of its internet service provider, gateway provider or international best practice.

  • TXEN shall use, and the TXEN NEIC Product shall enable each Customer to use, all parts of NEIC's Claim Status Exception Report Services, i.e. unprocessed claim messages, request for additional information, and claims settlement and zero payment messages (at least Level 2 status) all as defined in the Transaction Specifications.

  • As used in this Agreement, the term "Services" shall either mean the ProxyMed Services or the Claimsnet Services, or both, depending on the context; and "Transaction Specifications" shall mean with respect to a party that party's Transaction specifications, data format and certification requirements and instructions, and payer data format and technical requirements.