We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Data Standards Sample Clauses

Data Standards. 11.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. 11.2. Key data shall include: [*** insert list of data ***] 11.3. [*** insert any further applicable Standards and Regulations ***] ***]
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. 1. Grantee shall ensure compliance with the Homeless Management Information System (HMIS) Participation Agreement and Continuous Data Quality Improvement (CDQI) Process3 , 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. When applicable, records entered into the ONE System shall meet or exceed the ONE System Continuous Data Quality Improvement Process standards1. 3. When applicable, Grantee shall meet City’s Coordinated Homeless Assessment of Needs and Guidance through Effective Services (CHANGES) data standards and requirements. 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 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 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. 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 StandardsThe 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 (xxxx://xxx.xxxxxxx.xxx.xx/). In particular: 3.1.1 Property data: xxxx://xxx.xxxxxxx.xxx.xx/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 xxx.xxxxxx.xx.xx) 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. Contractor shall ensure compliance with the HMIS Participation Agreement and Continuous Data Quality Improvement (CDQI) Process10, 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 date quality reports and correcting errors. 10 HMIS Participation Agreement and Continuous Data Quality Improvement Process, available here: xxxxx://xxx.xxxxx.xxx/get-information/one-system/ Appendix A to P-600 FSP #: 1000030849 Page 6 of 12 January 1, 2024 2. Records entered into the ONE system shall meet or exceed the ONE System Continuous Data Quality Improvement Process standards: xxxxx://xxxxx.xxxxxxxxx.xxxx/hc/en-us/articles/360001145547-ONE-System- Continuous-Data-Quality-Improvement-Process. 3. Contractor shall enter data into the ONE System and shall 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, Contractor 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 shall provide clear instructions to all Contractors regarding the correct mechanism for sharing data. Changes to data collection or reporting requirements shall be communicated to Contractors via written notice at least one month prior to expected implementation. 4. Any information shared between Contractor, 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 maintain the current and active guest list, as well as maintaining the records of former clients who are not longer active, in the designated HSH database. 2. When applicable, records entered into the ONE system shall meet or exceed the ONE System Continuous Data Quality Improvement Process standards: xxxxx://xxxxx.xxxxxxxxx.xxxx/hc/en-us/articles/360001145547-ONE-System- Continuous-Data-Quality-Improvement-Process. 2 HSH Shelter Grievance Policy: xxxx://xxx.xxxxx.xxx/wp-content/uploads/2018/08/Shelter-Grievance-Policy-Final- 8-25-16-4.pdf. 3. When applicable, Grantee shall meet City’s Coordinated Homeless Assessment of Needs and Guidance through Effective Services (CHANGES) data standards and requirements. 4. When applicable, 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 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. 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 Health Insurance Portability and Accountability Act (HIPAA) and privacy guidelines, as required.
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. 1. Records entered into the (ONE) System shall meet or exceed the ONE System Continuous Data Quality Improvement Process standards: xxxxx://xxxxx.xxxxxxxxx.xxxx/hc/en-us/articles/360001145547-ONE-System- Continuous-Data-Quality-Improvement-Process. 2. 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 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. 3. All grantees, subgrantees, and their employees and agents shall comply with the confidentiality and data security requirements of all federal, state and local privacy and data management laws and regulations, including, but not limited to, 24 C.F.R. Part 578 (Continuum of Care); 45 C.F.R. Parts 160 and 164 (Health Insurance Portability and Accountability Act “HIPAA”); 28 CFR §90.4 (Violence Against Women Act); 28 CFR §94.115 (Victim of Crimes Act); California Civil Code §§ 1798 - 1798.78 (Information Practices Act of 1977); §§1798.85 - 1798.89 (Confidentiality of Social Security Numbers); §§1798.79.8 - 1798.79.95 (Domestic Violence, Sexual Assault, and Stalking: Personal Information); California Welfare & Institutions Code §10850; disclosure of confidential information regarding the criminal justice system and child protective services records; and related and successor provisions.
Data Standards. Data shall be provided to the City in a format acceptable to the City, such as the Mobility Data Specification (MDS) Provider API. Company is directly responsible for providing the API key to the City or the City’s designated third party and shall not refer the City or the proxy to another subsidiary or parent company representative for API access.