Information Management Practices Sample Clauses

The Information Management Practices clause defines how parties handle, store, and protect information exchanged or generated during their relationship. It typically outlines requirements for data security, access controls, retention periods, and procedures for responding to data breaches or information requests. By establishing clear standards and responsibilities, this clause helps ensure compliance with legal obligations and reduces the risk of data misuse or unauthorized disclosure.
Information Management Practices a. The Clinic will establish and maintain procedures for entering data on the Attachment (and, if the Clinic so chooses for new patients, the enrolment) of patients (see Appendix 3) and for Primary Care Indicators (used for evaluation of this initiative– see Appendix 2) into the Clinic’s electronic medical record (EMR) to ensure consistent and accurate reporting and to assist with training users. b. The Clinic will facilitate the Interprofessional Team Member’s use of the EMR, including providing access to a computer and licensed software. c. The Clinic will establish and maintain a plan to monitor data entry quality to ensure Primary Care Indicator data is captured in a consistent and reportable manner on an ongoing basis. d. The Clinic will collaborate with the Vendor and the PCIS Office, as may be required, in implementing specifications for EMR programming to support the Primary Care Indicators. The Clinic will implement a new version of the EMR if required in order to support evaluation.
Information Management Practices a. The RHA will establish and maintain procedures for entering data on the Attachment (and, if the RHA so chooses for new patients, the enrolment) of patients (see Appendix “2”) and for Primary Care Indicators (used for evaluation of this initiative– see Appendix “1”) into the RHA’s electronic medical record (EMR) to ensure consistent and accurate reporting and to assist with training users. b. The RHA will facilitate the Interprofessional Team Member’s use of the EMR, including providing access to a computer and licensed software. c. The RHA will establish and maintain a plan to monitor data entry quality to ensure Primary Care Indicator data is captured in a consistent and reportable manner on an ongoing basis. d. The RHA will collaborate with the Vendor and the PCIS Office, as may be required, in implementing specifications for EMR programming to support the Primary Care Indicators. The RHA will implement a new version of the EMR if required in order to support evaluation.

Related to Information Management Practices

  • Information Management Information and Records

  • Enterprise Information Management Standards Performing Agency shall conform to HHS standards for data management as described by the policies of the HHS Chief Data and Analytics Officer. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Management; Community Policies Owner may retain employees and management agents from time to time to manage the Property, and Owner’s agent may retain other employees or contractors. Resident, on behalf of himself or herself and his or her Guests, agrees to comply fully with all directions from Owner and its employees and agents, and the rules and regulations (including all amendments and additions thereto, except those that substantially modify the Resident’s bargain and to which Resident timely objects) as contained in this Agreement and the Community Policies of the Property. The Community Policies are available at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/policies.pdf or on request from the management office and are considered part of this Agreement.

  • Safeguards Monitoring and Reporting The Borrower shall do the following or cause the Project Executing Agency to do the following:

  • 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.