Information Management and Use Sample Clauses

Information Management and Use a. DFCS shall have a Mississippi Automated Child Welfare Information System (MACWIS) appropriate to its size and complexity that permits (1) timely access to information about persons served by any part of the organization, or by other practitioners within the organization, to support child safety and continuity of care across settings and services; (2) capturing, tracking, and reporting of financial, compliance, and child welfare information, including federally required AFCARS elements; (3) longitudinal reporting and comparison of performance over time; (4) the use of clear and consistent formats and methods for reporting and disseminating data, including system-wide reports; (5) the collection of data necessary to monitor compliance with the Plan; (6) DFCS county staff access to a computerized database of the placement resources currently available for placement statewide; (7) notification to caseworkers when a xxxxxx care provider for a child assigned to the worker is under investigation, or that provider’s xxxxxx care license has expired or been revoked; (8) notification to caseworkers investigating a report of abuse of subsequent reports of abuse concerning the same child or alleged perpetrator; (9) caseworkers to access information on available services statewide; and (10) review of prior (i.e. historical) case documents including Individual Service Plans. By the end of implementation Period 1:
Sample 1Sample 2
AutoNDA by SimpleDocs
Information Management and Use. Defendants shall, in conjunction with COA, develop and begin implementing a written plan to meet the needs identified in the required Administration and Management MACWIS Assessment. Defendants will develop and begin implementing a plan that will ensure MACWIS maintains statewide placement resource information such as current availability, capacity limitations, census, suitability by age, sex and special needs, and any related licensing and maltreatment investigations information accessible to DFCS county staff.
Sample 1Sample 2

Related to Information Management and Use

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

  • Project Management and Coordination The Engineer shall coordinate all subconsultant activity to include quality of and consistency of work and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Construction Management Services a. A-E may be required to review and recommend approval of submittals, shop drawings, Request for Information (RFI) and/or calculations for temporary structures such as trench shoring, false work and other temporary structural forms.

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

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with 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.

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

  • Patient Information Each Party agrees to abide by all laws, rules, regulations, and orders of all applicable supranational, national, federal, state, provincial, and local governmental entities concerning the confidentiality or protection of patient identifiable information and/or patients’ protected health information, as defined by any other applicable legislation in the course of their performance under this Agreement.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

Time is Money Join Law Insider Premium to draft better contracts faster.