News Releases Certain sections of Lithium Hosting, llc news releases may contain forward-looking statements projecting future events, such as new software installations, updates, promotions, hosting introductions, etc. It is possible that these statements may deviate from the actual circumstances, since they are treated as intentions and express expectations and approximate plans of action regarding the relevant forthcoming events. Forward Looking Statements can be recognized by the availability of indicative words such as "believes","anticipates", "plans", "may", "hopes", "can", "will", "expects", "is designed to", "with the intent", "potential", etc. However, their availability is not a prerequisite for a forward-looking statement to be treated as such.
Media Releases A. Grantee shall not use System Agency’s name, logo, or other likeness in any press release, marketing material or other announcement without System Agency’s prior written approval. System Agency does not endorse any vendor, commodity, or service. Grantee is not authorized to make or participate in any media releases or public announcements pertaining to this Grant Agreement or the Services to which they relate without System Agency’s prior written consent, and then only in accordance with explicit written instruction from System Agency.
Photographic/Recording Release I hereby grant and convey unto the Released Parties all right, title and interest in any and all photographs and video/audio/electronic recordings of me, including as to my name, image and voice, made by or on behalf of any of the Released Parties during my Activities with the Released Parties, including, but not limited to, the right to use such materials for any purpose and to any royalties, proceeds or other benefits derived from them. I understand that I will not have any ownership interest in or to such photographs, images and/or recordings, I have not been provided or promised any compensation to me, and I hereby waive any rights, privileges or claims based on any right of publicity, privacy, ownership or any other rights arising, relating to or resulting from the photographs, images and/or recordings. I understand and agree that this paragraph also applies to my minor child(ren) who are volunteering.
The Settling Entity’s Release of Xxxxxxx The Settling Entity, on behalf of itself, its past and current agents, representatives, attorneys, successors, and assignees, hereby waives any and all claims against Xxxxxxx and his attorneys and other representatives, for any and all actions taken or statements made (or those that could have been taken or made) by Xxxxxxx and his attorneys and other representatives, whether in the course of investigating claims or otherwise seeking to enforce Proposition 65 in connection with the notice or Products.
TIMELINESS OF BILLING SUBMISSION The parties agree that timeliness of billing is of the essence to this Contract and recognize that the City is on a fiscal year. All xxxxxxxx for dates of service prior to July 1 must be submitted to the City no later that the first Friday in August of the same year.
Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.
Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)
Data Rights User retains all rights over any data and other information that User may provide, upload, transfer or make available in relation to, or which is collected from User’s devices or equipment by, the Software, including, without limitation, information pertaining to how the Software obtains, uses, and respond to inputs, location, ambient conditions, and other information related to use and operation of the Software with Honeywell or third-party products, software or websites (“Usage Data”). Honeywell has the right to retain, transfer, disclose, duplicate, analyze, modify, and otherwise use Usage Data to protect, improve, or develop its products, services, and related offerings. All information, analysis, insights, inventions, and algorithms derived from Usage Data by Honeywell (but excluding the Usage Data itself) and any intellectual property rights obtained related thereto, are owned exclusively and solely by Xxxxxxxxx.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
