Data Timeliness Sample Clauses

Data Timeliness. Using Node Transfer, data submitted through CDX by facilities are converted to XML and pushed from CDX to the State node automatically on a facility-by-facility basis. Based on pilot testing of the TRI Data Exchange, it is expected that the data will be submitted to the State node within several minutes of its receipt through the CDX. For enforcement purposes, EPA and State agree that the date-stamp attached to a submission when it is successfully received by CDX will act as the date-received for the State. These data are also available to the State through Download at the State’s convenience.
AutoNDA by SimpleDocs
Data Timeliness. In most cases, the regulated community will enter RCRA handler data online. DEP will store the data in its database, and make it available for checking by the regulated community within minutes after it is entered. In these cases, the data is available for transmission over the Exchange Network within minutes after it is entered. In other cases, DEP staff must intervene in the data entry process for quality control of data. In these cases, DEP has a goal of making the data available to the Exchange Network within two weeks.
Data Timeliness. Data entered in HMIS in a timely manner is necessary to ensure that clients receive the services they need in a quick and efficient manner. Additionally, timely data entry ensures that regular, accurate reporting can be done through HMIS. Users who enter data into HMIS earlier are less likely to make data entry errors and are more likely to focus on overall data quality. HUD recommends that projects data is entered into HMIS, at most, within 48 hours of collecting the information from the client. The HMIS Lead will give Agency Administrators the reports to run to review Data Timeliness as part of the quarterly data review. It is recommended this occur monthly to avoid having many data corrections completed in the required two-week timeframe. Those providers who fall below the baseline requirement for Data Timeliness for their project type will be asked to work with the HMIS Lead to make sure that they can meet the Data Timeliness standard moving forward. For consistent issues with Data Timeliness, providers may be directed to create a Data Quality Improvement Plan (DQIP). HMIS users of any Participating Agency must record individual client and household data, from initial intake, exit, service provision, or any other client interaction which necessitates any form of data entry into HMIS within three business days. The Program Entry Date must be the date of the initial intake and not the HMIS data entry date. The only exception is data entry for large mass emergency shelters extended to five business days for only basic HUD universal data elements and disability information. Data timeliness benchmarks: • Coordinated Entry, Homeless Prevention, Rapid Rehousing, Transitional Housing, Services Only and Street Outreach: o Live time or within 3 business days of contact with the client. • Emergency Shelter o Live time or within 5 business days of contact with the client given that at time emergerncy shelters may have an influx of guests each evening.

Related to Data Timeliness

  • Timeliness Time is of the essence in this Agreement.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Feedback You have no obligation to provide us with ideas, suggestions, or proposals (“Feedback”). However, if you submit Feedback to us, then you grant us a non-exclusive, worldwide, royalty-free license that is sub-licensable and trans- ferable, to make, use, sell, have made, offer to sell, import, reproduce, publicly display, distribute, modify, or publicly perform the Feedback in any manner without any obligation, royalty, or restriction based on intellectual property rights or otherwise.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!