Managed Care Data Requirements Sample Clauses

Managed Care Data Requirements. All managed care organizations shall maintain an information system that collects, analyzes, integrates and reports data as set forth at 42 CFR 438.242. This system shall include encounter data that can be reported in a standardized format. Encounter data requirements shall include the following:
AutoNDA by SimpleDocs
Managed Care Data Requirements. The DVHA must maintain an information system that collects, analyzes, integrates, and reports data. The system must provide information that would be required from managed care entities as set forth in Federal regulations at 42 CFR section 438, on program elements including, but not limited to, service utilization, grievances, appeals, and disenrollments for reasons other than loss of Medicaid eligibility. The management information system must collect data on member and provider characteristics, as specified by the AHS, and on services as set forth under the intergovernmental agreement. DVHA must collect, retain and report encounter data in accordance with the Demonstration terms and conditions. All collected data must be available to AHS, and to CMS, upon request. The State must have contractual provisions in place to impose sanctions on the DVHA if accurate data are not submitted in a timely fashion.
Managed Care Data Requirements. All managed care organizations, prepaid inpatient health plans (PIHPs) and prepaid ambulatory health plans (PAHPs) shall maintain an information system that collects, analyzes, integrates and reports data as set forth at 42 CFR 438.
Managed Care Data Requirements. The Office of Vermont Health Access (OVHA) shall maintain an information system that collects, analyzes, integrates, and reports data. The system must provide information as set forth in Federal regulations at 42 CFR 438, on program elements including, but not limited to, service utilization, grievances, appeals, and disenrollments for reasons other than loss of Medicaid eligibility. The management information system must collect data on member and provider characteristics, as specified by the Agency of Human Services (AHS), and on services as set forth under section 2.12.1 of the intergovernmental agreement. OVHA must collect, retain and report encounter data in accordance with the demonstration terms and conditions. All collected data must be available to AHS, and to CMS, upon request. The State shall have contractual provisions in place to impose sanctions on the OVHA if accurate data are not submitted in a timely fashion.

Related to Managed Care Data 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.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Specific Requirements 7.4.1 Workers’ compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

  • 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.

  • 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)

Time is Money Join Law Insider Premium to draft better contracts faster.