Electronic Records You acknowledge and agree that we may in our discretion store all records electronically; and that we will not retain and have no obligation to retain any original documents for any period of time. This applies to all documentation including but not limited to checks, transaction records, notes, mortgages, deeds of trust and other loan and/or security documentation. We will routinely destroy all original documentation. We may store records electronically via imaging, scanning, filming or other technology used in the financial services industry for the storage of documentation via internal processes or third-party processors that we approve for these services. You agree that such storage shall be secure, and further agree that such records shall for all purposes be recognized and admissible in evidence or otherwise to prove the agreements, rights and obligations of the parties pursuant to any such records.
Electronic Record Search The Reporting Estonian Financial Institution must review electronically searchable data maintained by the Reporting Estonian Financial Institution for any of the following U.S. indicia:
a) Identification of the Account Holder as a U.S. citizen or resident;
b) Unambiguous indication of a U.S. place of birth;
c) Current U.S. mailing or residence address (including a U.S. post office box);
d) Current U.S. telephone number;
e) Standing instructions to transfer funds to an account maintained in the United States;
f) Currently effective power of attorney or signatory authority granted to a person with a U.S. address; or
g) An “in-care-of” or “hold mail” address that is the sole address the Reporting Estonian Financial Institution has on file for the Account Holder. In the case of a Preexisting Individual Account that is a Lower Value Account, an “in-care-of” address outside the United States or “hold mail” address shall not be treated as U.S. indicia.
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.
System Agency Data A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
B. Grantee has no right or license to use, analyze, aggregate, transmit, create derivatives of, copy, disclose, or process the System Agency Data except as required for Grantee to fulfill its obligations under the Grant Agreement or as authorized in advance in writing by System Agency.
C. For the avoidance of doubt, Grantee is expressly prohibited from using, and from permitting any third party to use, System Agency Data for marketing, research, or other non-governmental or commercial purposes, without the prior written consent of System Agency.
D. Grantee shall make System Agency Data available to System Agency, including to System Agency’s designated vendors, as directed in writing by System Agency. The foregoing shall be at no cost to System Agency.
E. Furthermore, the proprietary nature of Xxxxxxx’s systems that process, store, collect, and/or transmit the System Agency Data shall not excuse Xxxxxxx’s performance of its obligations hereunder.
Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts.
Contractor’s Records The Contractor shall keep true and accurate accounts, records, books and data which shall correctly reflect the business transacted by the Contractor in accordance with generally accepted accounting principles. These records shall be stored in Orange County for a period of three (3) years after final payment is received from the County. Storage of records in another county will require written approval from the County of Orange assigned Deputy Purchasing Agent.
Project Records Borrower shall: Make and keep books, records, and accounts, in such reasonable detail, so as to fully, accurately, and fairly reflect the activities of Borrower. Record the Project’s assets, liabilities, revenues, expenses, receipts and disbursements in separate accounts from any other assets, liabilities, revenues, expenses, receipts and disbursements of Borrower so as to permit the production of a Statement of Financial Position, a Statement of Profit and Loss (Statement of Activities), and a Statement of Cash Flows for Borrower in which the activities of Borrower are separately identifiable from the activities of the Operator, unless Borrower is also Operator. Devise and maintain a system of internal accounting controls sufficient to provide reasonable assurances that: Transactions are executed, and access to assets is permitted, only in accordance with Xxxxxxxx’s authorization; Transactions are accurately and timely recorded to permit the preparation of quarterly and annual financial reports in conformity with applicable Program Obligations; Transactions are timely recorded in sufficient detail so as to permit an efficient audit of the Borrower’s books and records in accordance with Generally Accepted Auditing Standards (GAAS), Generally Accepted Government Auditing Standards (GAGAS), and other applicable Program Obligations; and Transactions are timely recorded in sufficient detail so as to maintain accountability of the Borrower’s assets. The recorded accountability for assets shall be compared with the existing assets at reasonable intervals, but not less than annually, and appropriate action shall be taken with respect to any differences. Make the books, records and accounts of Borrower available for inspection by HUD or its authorized representatives, after reasonable prior notice, during normal business hours, at the Project or other mutually agreeable location or, at HUD’s request, shall provide legible copies of such documents to HUD or its authorized representatives within a reasonable time after HUD or its authorized representative makes a request for such documents. Include as a requirement in any operating or management contract that the books, records, and accounts of any agent of Borrower, as they pertain to the operations of the Project, shall be kept in accordance with the requirements of this Section 19 and be available for examination by HUD or its authorized representatives after reasonable prior notice during customary business hours at the Project or other mutually agreeable location or, at HUD’s request, the Management Agent shall provide legible copies of such documents to HUD or its authorized representatives within a reasonable time after HUD or its authorized representative makes the request.
DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A.
b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915.
c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.
Electronic Visit Verification ("EVV A. To ensure:
1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor;
2. only authorized people access the Contractor's EVV account;
3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim;
4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and
5. service delivery documentation is immediately available for review by HHSC when requested.
B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above.
C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook.
D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable.
E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim.
F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied.
G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook.
H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter.
I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
