for Eiclient Portal Users Clause Samples

for Eiclient Portal Users. As a course of doing business together, our two organizations may, from time to time, exchange PHI. Under the Health Insurance Portability and Accountability Act (“HIPAA”) regulations, Eiclient users are considered a Covered Entity and RMD Enterprises, LLC is considered a Business Associate. As a result, our two organizations are required to enter into a Business Associate Agreement that provides assurances that both organizations will protect the confidentiality of any PHI received, used, created, or disclosed to either of our organizations. Please find the attached copy of the Business Associate Agreement. After reviewing and signing the agreement, please make a copy for your records and return a copy to RMD Enterprises, LLC. You may mail the signed agreement to RMD Enterprises, LLC, ▇▇▇ ▇▇▇▇ ▇▇▇▇▇▇ Pl., Charleston, WV 25312, or scan and e-mail to ▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇. If you have any questions regarding the agreement, please feel free to text or call me at (▇▇▇) ▇▇▇-▇▇▇▇ or E-mail me at ▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇. Thank you in advance for your prompt attention to this matter. Sincerely, ▇▇▇▇▇▇▇ ▇. ▇▇▇▇▇▇▇, Owner Eiclient This Agreement ("Agreement") is entered into by and between RMD Enterprises, LLC ("Business Associate") and ("Cover Entity").
View Source

Related to for Eiclient Portal Users

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment. 5.2 If a Reconex Customer is served by resold Verizon Telecommunications Service or a Verizon Local Switching UNE, subject to any call blocking feature used by Reconex, to the extent reasonably feasible, Verizon will route Voice Information Services Traffic originating from such Service or UNE to the Voice Information Service platform. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.3 Reconex shall have the option to route Voice Information Services Traffic that originates on its own network to the appropriate Voice Information Services platform(s) connected to Verizon’s network. In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow Reconex to route Voice Information Services Traffic originated on its network to Verizon. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.4 Reconex shall pay Verizon such charges in full regardless of whether or not it collects charges for such calls from its own Customers. 5.5 For variable rated Voice Information Services Traffic (e.g., NXX 550, 540, 976, 970, 940, as applicable) from Reconex Customers served by resold Verizon Telecommunications Services or a Verizon Local Switching Network Element, Reconex shall either (a) pay to Verizon without discount the Voice Information Services provider charges, or (b) enter into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers. 5.6 Either Party may request the other Party provide the requesting Party with non discriminatory access to the other party’s information services platform, where such platform exists. If either Party makes such a request, the Parties shall enter into a mutually acceptable written agreement for such access. 5.7 In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Information Service serving switch. This trunk group will be utilized to allow Reconex to route information services traffic originated on its network to Verizon.