Check Requirements Any image of a check that I transmit to you must accurately and legibly provide all the information on the front and back of the check at the time presented to me by the drawer. Prior to capturing the original check, I will indorse the back of the original check. My endorsement will include "For Directions E- Deposit Only" in addition to my signature. The image of the check transmitted to you must accurately and legibly provide, among other things, the following information: (1) the information identifying the drawer and the paying bank that is preprinted on the check, including complete and accurate MICR information and the signature(s); and (2) other information placed on the check prior to the time an image of the check is captured, such as any required identification written on the front of the check and any endorsements applied to the back of the check. The image quality for the check will meet the standards for image quality established by the American National Standards Institute ("ANSI"), the Board of Governors of the Federal Reserve, and any other regulatory agency, clearing house or association. Rejection of Deposit. You are not liable for any service or late charges levied against me due to your rejection of any item. In all cases, I am responsible for any loss or overdraft plus any applicable fees to my Account due to an item being returned. Items Returned Unpaid. A written notice will be sent to me of transactions you are unable to process because of returned items. With respect to any item that I transmit to you for remote deposit that you credit to my Account, in the event such item is dishonored, I authorize you to debit the amount of such item from the Account. Email Address. I agree to notify you immediately if I change my email address, as this is the email address where you will send me notification of receipt of remote deposit items.
DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Network Requirements (A) The Contractor shall maintain and monitor a network of appropriate Network Providers that is supported by written agreements and is sufficient to provide adequate access to all Covered Services for all Enrollees, including those with limited English proficiency or physical or mental disabilities. In establishing and maintaining the network of Network Providers the Contractor shall consider:
TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.
Health Requirements This is an active trip that requires you to make a realistic assessment of your health. To enjoy the trips as intended, a minimum level of fitness is required. All Participants are expected to be in active good health, to be comfortable traveling as part of a group, and to be ready to experience cultural differences with grace. Air Journey will require prior notice if any participant has any physical or other condition or disability that would prevent them from participating in active elements of any trip and/or could create a hazard to him or herself or to other members of the group. Air Journey may require guests to produce a doctor’s certificate certifying that they are fit to participate. Any physical condition requiring special attention, diet, or treatment should be reported in writing when the reservation is made. We will make reasonable efforts to accommodate Participants with special needs; however, we cannot accommodate wheelchairs. . Walking and climbing stairs are required in many hotels and airports, and are part of many excursions. If you require a slower pace, extra assistance, or the use of a cane or walking stick, arrangements will be made for private touring at each destination, if necessary, at the discretion of our Journey staff. Any extra cost for such arrangements will be the responsibility of the Participant. If you would like to forego some of the scheduled sightseeing to rejuvenate and relax, please feel free to do so at any time. Acting reasonably, if Air Journey is unable to properly accommodate the need of the person(s) concerned or believes that health and safety may be compromised, Air Journey reserves the right to refuse participation. Air Journey also reserves the right to remove from the trip, at the participant’s own expense, anyone whose physical condition or conduct negatively impacts the enjoyment of the other guests or disrupts the tour. Malaria and other diseases may be present in some of the countries featured in this itinerary; proof of yellow fever inoculation may be required. For the latest recommendations on specific health precautions for the areas you will visit, consult your physician and the Centers for Disease Control. The participant represents that neither he nor she nor anyone traveling with him or her has any physical or other condition or disability that could create a hazard to himself or herself or other members of the tour. Itinerary Changes The itinerary and Journey leaders are subject to modification and change by Air Journey. Every reasonable effort will be made to operate the Journey as planned; however, should unforeseen world events and conditions require our itinerary to be altered, Air Journey reserves the right to do so for the safety and best interest of the group without prior notification or consultation. The operation of these flights is subject to the foreign governments involved granting landing rights for the flight. If the air carrier cannot obtain these rights for any particular flight leg of the Journey, that flight leg will be canceled and alternative arrangements may be made, at the discretion of Air Journey. Every effort will be made to operate tours as planned but alterations may occur after the final itinerary has been issued.
Management Requirements Procedures for managing equipment (including replacement equipment), whether acquired in whole or in part under a Federal award, until disposition takes place will, as a minimum, meet the following requirements:
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.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Procurement Requirements The below listed provisions of State Procurement requirements shall be complied with throughout the contract period:
