13.07.2015 Views

Clearinghouse Trading Partner Agreement - DHHR - State of West ...

Clearinghouse Trading Partner Agreement - DHHR - State of West ...

Clearinghouse Trading Partner Agreement - DHHR - State of West ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

II.INTRODUCTION.This <strong>Agreement</strong> authorizes the Parties to electronically exchange Data, including PHI, through a public or privatetelecommunications network using language and code sets authorized at 45 CFR § 160 et seq., in an efficient and costeffectivemanner without limiting the obligations <strong>of</strong> each party as set forth in this <strong>Agreement</strong> or imposed by applicablelaw, solely for the purposes set forth herein, in accordance with the terms "Standard” and “Transactions" as defined at45 CFR § 160.103 (hereinafter aggregated and referred to as “Standard Transactions”), the privacy standards describedand referenced below, and requirements for non-standard transactions (if applicable). Any Data, Proprietary Data or PHIexchanged under this <strong>Agreement</strong> is to be used and exchanged solely as authorized by HIPAA, and is further subject tothe terms and conditions set forth in this <strong>Agreement</strong>. Company acknowledges that coverage for any servicesfurnished by a Provider and electronically exchanged through this <strong>Agreement</strong> is subject to the terms and conditions <strong>of</strong>the individual’s benefit program, any participation agreement between Provider and Unisys, and Unisys’ policies andprocedures.III.TERM, TERMINATION and SUSPENSION.The term <strong>of</strong> this <strong>Agreement</strong> shall commence upon its execution. Company agrees that its ability to transmit, receive orotherwise electronically access Data will cease if Company or Unisys terminates this <strong>Agreement</strong>.Either party may terminate this <strong>Agreement</strong> without cause upon sixty- (60) days prior written notice or immediately byeither party for cause.This <strong>Agreement</strong> may immediately be terminated in the event <strong>of</strong> a material breach. A material breach shall include, butnot be limited to, breach <strong>of</strong> any substantive term(s) <strong>of</strong> this <strong>Agreement</strong>, fraud, abuse, and/or failure to protect PHI. Theterminating party may rescind notice <strong>of</strong> termination if the other party successfully cures the breach complained <strong>of</strong> tothe terminating party's satisfaction. Each party may also temporarily suspend electronic communications under this<strong>Agreement</strong> to protect computer or data systems in cases <strong>of</strong> emergencies, or to perform maintenance. Each partyagrees to minimize the frequency and duration <strong>of</strong> these temporary suspensions. This <strong>Agreement</strong> shall automaticallyterminate in the event there is no electronic transaction activity for six (6) consecutive months.Any ambiguity in any term or condition <strong>of</strong> this <strong>Agreement</strong> shall be resolved in favor <strong>of</strong> a meaning that permits theparties to comply with HIPAA.IV.UNISYS OBLIGATIONS.A. ID(s) and Password(s) - Upon execution <strong>of</strong> this <strong>Agreement</strong>, Unisys will assign logon ID(s) and password(s) toCompany to allow Company to authenticate its identity and transmit data electronically for Providers and EmployerGroups identified in EDI Transaction Application.Unisys shall retain title to all logon ID(s) and password(s), and reserves the right to change any logon ID or password atany time, for any reason, or if required to do so by law, regulation, or court order.B. Data - The Data the Parties may exchange pursuant to this <strong>Agreement</strong> may change as a result <strong>of</strong> changes in law orregulation, or actions taken by an employer group in accordance with the terms and conditions <strong>of</strong> certain health carebenefits contracts, or changes made to those contracts. Unisys’ response to inquiries does not guarantee coverage.Acceptance by Unisys <strong>of</strong> the Data Company sends electronically, on any Provider or Employer Group’s behalf, does notconstitute guarantee <strong>of</strong> reimbursement.V. COMPANY OBLIGATIONS and AUTHORIZATIONS.A. Provision <strong>of</strong> Data - Company may provide Unisys Data electronically, including the minimum necessary PHI (see45 CFR § 164.502(b)) in accordance with the terms <strong>of</strong> the <strong>Agreement</strong> and the Guide. Company is solely responsible toensure that the Data it providesUnisys is correct.B. Logon ID and Password - Company agrees to protect Unisys' logon ID(s) and password(s) from compromise,release or discovery by any unauthorized person, and shall not disclose logon ID(s) and password(s) to any third partyin any manner. A breach <strong>of</strong> this provision shall be considered material. In the event a breach occurs, Company mustnotify Unisys immediately as set forth in the Guide. Company acknowledges and agrees that only Company personnelit designates shall be permitted to use the logon ID(s) and password and only within the scope <strong>of</strong> the approvedapplication. Company's use <strong>of</strong> logon ID(s) and password(s) constitutes an Electronic Signature that confirmsCompany’s willingness to remain bound by these terms and conditions and ratify any transaction conductedelectronically by Unisys. In the event logon ID(s) and/or password(s) are compromised, <strong>Clearinghouse</strong> shall beresponsible for such ramifications resulting from <strong>Clearinghouse</strong>’s failure to protect Unisys logon ID(s) and password(s).Unisys <strong>Clearinghouse</strong> <strong>Trading</strong> <strong>Partner</strong> <strong>Agreement</strong> rev. 3.8.2004 Page 2 <strong>of</strong> 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!