Batch Data Exchange Sample Clauses

The Batch Data Exchange clause governs the process by which data is transferred between parties in grouped or scheduled batches rather than individually or in real time. Typically, this clause outlines the frequency, format, and protocols for exchanging data sets, such as daily transaction records or periodic inventory updates, ensuring both parties are aligned on timing and technical requirements. Its core function is to streamline and standardize data transfers, reducing administrative burden and minimizing the risk of errors or miscommunication during the exchange process.
POPULAR SAMPLE Copied 1 times
Batch Data Exchange. Unless another mutually agreed to alternative exists between PACIFIC and CLEC, CLEC will use two types of orders, the Infrastructure Provisioning order and Customer Specific Provisioning order, to establish local service capabilities based on a UNE architecture. The Infrastructure Footprint Form and associated ASR forms (Local Switching, Interoffice Transport, Signaling and Database, Operator Services and DA, and Operations Systems). CLEC will provide these Infrastructure Provisioning and ASR forms via the ASR process, including passing the information over a file transfer network, (e.g. Network Data Mover Network) using the CONNECT: Direct file transfer product. Customer Specific provisioning will be based on OBF LSR forms and applicable SOSC interpretations of transactions in accordance with OBF forms. PACIFIC and CLEC agree to adapt interfaces based on evolving ATIS/OBF and SOSC standards.
View SourceView Similar (2)
Batch Data Exchange. Unless another mutually agreed to alternative exists between NEVADA and CLEC, CLEC will use the same types of orders as it uses with Pacific B▇▇▇ for Batch Data Exchange.
View Source

Related to Batch Data Exchange

  • Data Exchange Except where prohibited by law or regulation, MCP and MHP must share the minimum necessary data and information to facilitate referrals and coordinate care under this MOU. The Parties must have policies and procedures for supporting the timely and frequent exchange of Member information and data, including behavioral health and physical health data; for ensuring the confidentiality of exchanged information and data; and, if necessary, for obtaining Member consent, when required. The minimum necessary information and data elements to be shared as agreed upon by the Parties, are set forth in Exhibit C of this MOU. To the extent permitted under applicable law, the Parties must share, at a minimum, Member demographic information, behavioral and physical health information, diagnoses, assessments, medications prescribed, laboratory results, referrals/discharges to/from inpatient or crisis services and known changes in condition that may adversely impact the Member’s health and/or welfare. The Parties must annually review and, if appropriate, update Exhibit C of this MOU to facilitate sharing of information and data. MHP and MCP must 4 CalAIM Data Sharing Authorization Guidance VERSION 2.0 June 2023 available at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇.▇▇▇/Documents/MCQMD/CalAIM-Data-Sharing-Authorization- Guidance-Version-2- Draft-Public-Comment.pdf. establish policies and procedures to implement the following with regard to information sharing: i. A process for timely exchanging information about Members eligible for ECM, regardless of whether the Specialty Mental Health provider is serving as an ECM provider; ii. A process for MHP to send regular, frequent batches of referrals to ECM and Community Supports to MCP in as close to real time as possible; iii. A process for MHP to send admission, discharge, and transfer data to MCP when Members are admitted to, discharged from, or transferred from facilities contracted by MHP (e.g., psychiatric inpatient hospitals, psychiatric health facilities, residential mental health facilities), and for MCP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3); iv. A process to implement mechanisms to alert the other Party of behavioral health crises (e.g., MHP alerts MCP of Members’ uses of mobile health, psych inpatient, and crisis stabilization and MCP alerts MHP of Members’ visits to emergency departments and hospitals); and v. A process for MCP to send admission, discharge, and transfer data to MHP when Members are admitted to, discharged from, or transferred from facilities contracted by MCP (e.g., emergency department, inpatient hospitals, nursing facilities), and for MHP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3).

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.