Integration Requirements Clause Samples

Integration Requirements. During both business practice/process and IT Department discussions, we examine the systems that are currently integrated to the system and look for opportunities to improve the efficiency of the environment by including them in the specifications for the replacement system. • System Support Requirements – Assess the function and operations performed to support the current system based on interviews with the IT staff and end-user support staff, including: o The ability of the application to support technical services, such as workflow changes o Third party vendor interaction within the overall support structure o User involvement, control and segregation of duties between IT and user departments for configuration changes. Phase 1.2 PHASE 1.2 – NEEDS ASSESSMENT AND PLAN OF ACTION With the findings discovered in Phase 1.1, Sciens will then develop a Plan of Action.

Integration Requirements. By the Launch Date, Concentric and ▇▇▇▇▇▇▇▇.▇▇▇ shall have completed the integration of the ▇▇▇▇▇▇▇▇.▇▇▇ Web Properties and Domain Registration process with the Concentric Web Hosting and E-commerce services such that all obligations of this Section 2 can be fulfilled. This integration shall include, but shall not be limited to, (a) methods to transfer domains from ▇▇▇▇▇▇▇▇.▇▇▇'s DNS to Concentric's DNS in a timely and mechanized manner should Concentric decide, in its sole discretion, to require such a transfer and (b) methods to ensure the timely transfer of customer information as required by Section 2.4.

Integration Requirements. Full integration and synchronization of patient data/information between different systems will be required. Such integration shall include full synchronization of system data through use of HL7 health standard (both offered and existing systems), and it shall allow two-way communication between the systems (sending query requests from Family Medicine system to laboratory information system and radiology information system and Internal medicine stations system and ECG devices (cardio diagnostic support system). It is also expected that Family Medicine system will receive and demonstrate completed results from these systems (EHR – display of test results, diagnostics imaging and physician’s reports, including portions of patient electronic health record). Implemented data classes and their attributes shall comply with basic set of Important data set (Attachment 3, Rulebook on Definition of Primary Health Care Health Informatics System Architecture, Federation of BiH Official Gazette, #82/13) Horizontal integration - data exchange between health institution at the same level (reports of consultations and diagnostics examination) or exchange of data generated by different software solutions used by organizational units of a single institution (for example, where a different software is used for hospital pharmacy, laboratory, or certain specialist departments). Vertical integration - data exchange between institutions at different levels, e.g. canton and/or the Federation of BIH, (referrals and specialist examination reports) in accordance with statutory law- based reporting requirements. Integration with health institutions at the Federation of BiH level - automatic download of codes and automatic sending of statutory law-based electronic reports. Beyond this, LDAP integration at the level of health care provider must be ensured; Each staff member whose job description demands access to the information system shall be assigned with a single authorization code to access the system. Integrate EHRS with cantonal institute of healthcare insurance databases and ensure online communication and data exchange. EHRS will be installed on servers that are/will be physically located in cantonal institute of healthcare insurance, one datacenter rack per at the actual location. On these physical servers virtualization software and proposed server oprating system(s), application server(s) and database server(s) will be installed. Introduce, implement and integrate new Elect...

Integration Requirements. Avaya Aura Communication Manager 3.0 and higher o Start / Stop Recording o Conversation Save invoked during the call records the call from the beginning o Do not record key (Optional key to prevent recording during the call) Avaya CM - Port Spanning with TSAPI

Integration Requirements. The LRV Supplier shall provide Stage 2 LRVs that are compatible with the TRPS as defined in Section 6-1.3 [Train Control System (TCS)] of this Schedule and will be installing all onboard equipment required by the TRPS wayside infrastructure on the Stage 2 LRVs.

Integration Requirements. 26.18.1. The Government of Sudan shall ensure the integration of the armed struggle movements’ forces into the Sudanese military establishment and security services, according to the agreed timetables, criteria, and principles; 26.18.2. Forces of the armed struggle movements shall be integrated in the military establishment and other security institutions in accordance with numbers to be agreed upon later; 26.18.3. Combatants of the armed struggle movements’ forces who are integrated into the military and security institutions may not go into retirement in the first 6 years of their integration, except as the result of discipline violations and violations of the law;

Integration Requirements. Each of Project Co and Operator and LRV Supplier shall perform its respective obligations pursuant to (as applicable) the Project Co Infrastructure Integration Requirements, the Operator Infrastructure Integration Requirements and the LRV Supplier Infrastructure Integration Requirements.

Integration Requirements. 1. Provide support to all Application Programming Interfaces (APIs) including REST API that Service Provider develops/provides.

Integration Requirements. ‌ BEACONING Analytics is part of a larger whole. This section describes the requirements that must be fulfilled to achieve tight integration into the BEACONING Platform, and that are responsibility of other BEACONING partners, as they involve educational, games or minigame issues that are beyond the scope of the Analytics System itself. To achieve full integration, BEACONING Analytics requires full specifications for the following: • Meta-▇▇▇: detailing how analytics for a single game or minigame should be aggregated for GLPs built of multiple games and minigames. • User’s management system: the identity of students is critical to correct analysis of their actions. To avoid duplicating user management, BEACONING Analytics requires access to a robust and well-documented BEACONING User management system which can store user sessions across applications. • Data analytics workflow: while BEACONING Analytics can be queried programmatically to provide in-game adaptation (see Section 5, “Incorporating analytics to a game”), specifics of when and how adaptation information will be used is necessary to provide full support. The following subsections describe each requirement in greater detail. Note that, as soon as each requirement is fulfilled, e-UCM will begin working on making any changes to BEACONING Analytics that may be needed.