Management Information System The M&E Plan will describe the information system that will be used to collect data, store, process and deliver information to relevant stakeholders in such a way that the Program information collected and verified pursuant to the M&E Plan is at all times accessible and useful to those who wish to use it. The system development will take into consideration the requirement and data needs of the components of the Program, and will be aligned with existing MCC systems, other service providers, and ministries.
Management Information Systems A. The CONTRACTOR shall maintain a process that collects, analyzes, integrates, and reports data. (42 C.F.R. § 438.242(a); Cal. Code Regs., tit. 9, § 1810.376.) This process shall provide information on areas including, but not limited to, utilization, claims, grievances, and appeals. (42 C.F.R. § 438.242(a).)
Information Systems The Official Agency in conjunction with the Authority will meet the relevant requirements of Articles 131 to 136 of Regulation (EU) 2017/625 and Implementing Regulation (EU) 2019/1715 as appropriate to the Official Agency. The Official Agency shall record appropriate data in the Official Agency Premises Inspection database (OAPI), which will be further developed over the life of the contract. Data should be entered into the database on an ongoing basis but shall be entered within one month of the activity taking place, unless otherwise agreed with the Authority.
Access Management The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.
Monitoring and Management Information C10.1 The Contractor shall comply with the monitoring arrangements set out in the Monitoring Schedule including, but not limited to, providing such data and information as the Contractor may be required to produce under the Contract.
Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. 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.
Health Information System i. As required by 42 CFR 438.242(a), the MCP shall maintain a health information system that collects, analyzes, integrates, and reports data. The system shall provide information on areas including, but not limited to, utilization, grievances and appeals, and MCP membership terminations for other than loss of Medicaid eligibility.
DEFECTIVE MANAGEMENT INFORMATION 5.1 The Supplier acknowledges that it is essential that the Authority receives timely and accurate Management Information pursuant to this Framework Agreement because Management Information is used by the Authority to inform strategic decision making and allows it to calculate the Management Charge.
Management Information To be Supplied to CCS no later than the 7th of each month without fail. Report are to be submitted via MISO CCS Review 100% Failure to submit will fall in line with FA KPI CONTRACT CHARGES FROM THE FOLLOWING, PLEASE SELECT AND OUTLINE YOUR CHARGING MECHANISM FOR THIS SOW. WHERE A CHARGING MECHANISM IS NOT REQUIRED, PLEASE REMOVE TEXT AND REPLACE WITH “UNUSED”.
Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.