Data Standards Clause Samples
The Data Standards clause establishes the specific requirements and protocols for how data must be managed, formatted, and exchanged between parties under the agreement. It typically outlines the technical specifications, such as file formats, data security measures, and compliance with relevant industry or legal standards. By setting clear expectations for data handling, this clause ensures consistency, interoperability, and reduces the risk of misunderstandings or data-related errors between the parties.
Data Standards. 10.1. The CONTRACTOR shall develop, document, operate and maintain standards and procedures for ensuring the quality and integrity of all key data. These standards and procedures must be agreed with the CUSTOMER.
Data Standards. To facilitate processing of Outage(IMS) data for the Availability performance monitoring system, and to enable consistent and equitable interpretation of PTO Maintenance records by the ISO, these standards address the need for data recording and reporting. The ISO and PTO’s have committed to developing standardized formats for transmitting Outage(IMS) data to the ISO for the Availability performance monitoring system. These standard formats are to be finalized within the first 60 days of 1998. Additionally, the ISO and PTO’s have agreed to develop and implement a standard Maintenance reporting system by the end of the third year of operation of the ISO. This system will provide for consistent gathering of information that can be used as the basis for optimizing and forecasting maintenance of Transmission Facilities. The development of such a Maintenance reporting system is consistent with fostering the spirit of cooperation among the ISO and the PTO’s as it may eventually aid in the resolution of performance problems, and provide the basis for research on an ISO grid-wide basis to identify opportunities to enhance Transmission Facility Maintenance.
Data Standards. The Operator shall (and shall procure that Material Sub-Contractors shall) comply with the following data standards:
3.1 Data standards should follow the UK Government Data Standards Catalogue within the eGIF Interoperability framework (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇.▇▇/). In particular:
3.1.1 Property data: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇.▇▇/gdsc/html/frames/default.htm
3.1.2 For property data that has not yet been defined and published, the Authority is a member of PISCES (see ▇▇▇.▇▇▇▇▇▇.▇▇.▇▇) which is in the process of developing the eCommerce standard for real estate. In order to enable the electronic transfer of information directly from one system to another, the Authority will be working towards defining and publishing data standards that the Operator will be expected to use.
3.1.3 Any business conducted through the internet should follow the ebXML standard.
Data Standards. The MHBE will provide Carrier with details and requirements for submitting and receiving data required in the Carrier Reference Manual.
Data Standards. 1. Grantee shall ensure compliance with the Homeless Management Information System (HMIS) Participation Agreement and Continuous Data Quality Improvement (CDQI) Process2 , including but not limited to:
a. Entering all client data within three working days (unless specifically requested to do so sooner);
b. Ensuring accurate dates for client enrollment, client exit, and client move in (if appropriate); and
c. Running monthly data quality reports and correcting errors.
2. Records entered into the Online Navigation and Entry (ONE) System shall meet or exceed the ONE System CDQI Process standards1.
3. Grantee shall enter data into the ONE System, but may be required to report certain measures or conduct interim reporting in CARBON, via secure email, or through uploads to a File Transfer Protocol (FTP) site. When required by HSH, Grantee shall submit the monthly, quarterly and/or annual metrics into either the CARBON database, via secure email, or through uploads to an FTP site. HSH 2 HMIS Participation Agreement and Continuous Data Quality Improvement Process, available here: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/get-information/one-system/ will provide clear instructions to all Grantees regarding the correct mechanism for sharing data. Changes to data collection or reporting requirements shall be communicated to Grantees via written notice at least one month prior to expected implementation.
4. Any information shared between Grantee, HSH, and other providers about the served population shall be communicated in a secure manner, with appropriate release of consent forms and in compliance with 24 C.F.R. Part 578, Continuum of Care; 45 C.F.R. Parts 160 and 164, the Health Insurance Portability and Accountability Act (HIPAA) and federal and state data privacy and security guidelines.
5. Failure to comply with data security, storage and access requirements may result in loss of access to the HMIS and other data systems.
Data Standards. 1. Grantee shall ensure compliance with the Homeless Management Information System (HMIS) Participation Agreement and Continuous Data Quality Improvement (CDQI) Process1, including but not limited to:
a. Entering all tenant data within three working days (unless specifically requested to do so sooner);
b. Ensuring accurate dates for tenant enrollment, tenant exit, and tenant move in (if appropriate); and
c. Running monthly data quality reports and correcting any errors.
2. Records entered into the ONE system shall meet or exceed the ONE System Continuous Data Quality Improvement Process standard.1
3. Grantee shall maintain updated unit vacancy information on a weekly basis in the data system designated by HSH (Offline Vacancy Tracker and/or ONE System) as required. Changes to vacancy reporting shall be communicated to Grantees in writing from HSH.
4. Grantee shall enter data into the ONE System, but may be required to report certain measures or conduct interim reporting in CARBON, via secure email, or 1 HMIS Participation Agreement and Continuous Data Quality Improvement Process, available here: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/get-information/one-system/ through uploads to a File Transfer Protocol (FTP) site. When required by HSH, Grantee shall submit the monthly, quarterly and/or annual metrics into the CARBON database Changes to data collection or reporting requirements shall be communicated to Grantees via written notice at least one month prior to expected implementation.
5. Any information shared between Grantee, HSH, and other providers about the served population shall be communicated in a secure manner, with appropriate release of consent forms and in compliance with 24 C.F.R. Part 578, Continuum of Care; 45 C.F.R. Parts 160 and 164, the Health Insurance Portability and Accountability Act (HIPAA) and federal and state data privacy and security guidelines.
6. Failure to comply with data security, storage and access requirements may result in loss of access to the HMIS and other data systems.
Data Standards. 1. Grantee shall ensure compliance with the Homeless Management Information System (HMIS) Participation Agreement and Continuous Data Quality Improvement (CDQI) Process1, including but not limited to:
a. Entering all household data within three working days (unless specifically requested to do so sooner);
b. Ensuring accurate dates for household enrollment, household exit, and household move in (if appropriate); and
c. Running monthly data quality reports and correcting any errors.
2. Records entered into the Online Navigation and Entry (ONE) system shall meet or exceed the ONE System CDQI Process standard.1
3. Grantee shall enter data into the ONE System but may be required to report certain measures or conduct interim reporting in CARBON, via secure email, or through uploads to a File Transfer Protocol (FTP) site. When required by HSH, Grantee shall submit the monthly, quarterly and/or annual metrics into the CARBON database. Changes to data collection or reporting requirements shall be 1 HMIS Participation Agreement and Continuous Data Quality Improvement Process, available here: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/get-information/one-system/ communicated to Grantees via written notice at least one month prior to expected implementation.
4. Any information shared between Grantee, HSH, and other providers about the served population shall be communicated in a secure manner, with appropriate release of consent forms and in compliance with 24 C.F.R. Part 578, Continuum of Care; 45 C.F.R. Parts 160 and 164, the Health Insurance Portability and Accountability Act (HIPAA) and federal and state data privacy and security guidelines.
5. Failure to comply with data security, storage and access requirements may result in loss of access to the HMIS and other data systems.
Data Standards. BS7666 is the standard for describing locations such as addresses, rights of way and streets. Most information in the public sector has a location element to it so it is appropriate to use the BS7666 standard in order to convert disparate data sets from different systems and agencies.
Data Standards. 8.1 The Contractor shall develop, document, operate and maintain standards and procedures for ensuring the quality and integrity of all key data. These standards and procedures must be agreed with the Framework Authority.
8.2 Key data shall include: • Financial data, including credit and debit card details; • Candidate data; and • Management Information. Policies • Information Risk Policy; • Information Security Policy; • Information Management Policy; • Records Management Policy; • Information Assurance Policy; and • Information Charter.
Data Standards. The SERVICE PROVIDER shall develop, document, operate and maintain standards and procedures for ensuring the quality and integrity of all key data. These standards and procedures must be agreed with the CUSTOMER. The SERVICE PROVIDER shall develop procedures which ensure that only the correct release or version of a Deliverable can be delivered to the CUSTOMER. The SERVICE PROVIDER shall provide a copy of the draft procedures to the CUSTOMER for its approval. On receipt of such approval, the SERVICE PROVIDER shall then operate those procedures.