Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.
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.
Employee Verification In accordance with Neb. Rev.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
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.
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)
Therapist Availability Therapist’s office is equipped with a confidential voice mail system that allows Patient to leave a message at any time. Therapist will make every effort to return calls within 24 hours (or by the next business day), but cannot guarantee the calls will be returned immediately. Therapist is unable to provide 24-hour crisis service. In the event that Patient is feeling unsafe or requires immediate medical or psychiatric assistance, he/she should call 911, or go to the nearest emergency room.
Earned Value Management System An earned value management system (EVMS) means a project management tool that effectively integrates the project scope of work with cost, schedule and performance elements for optimum project planning and control. The qualities and operating characteristics of EVMS are described in American National Standards Institute /Electronics Industries Alliance (ANSI/EIA) Standard-748. An EVMS is not mandatory; however, Contractors are encouraged to have an EVMS ANSI/EIA Standard-748 during the entire term of OASIS. The Contractor shall notify the OASIS CO, in writing, if there are any changes in the status of their EVMS and provide the reasons for the change and copies of audits by the Defense Contract Management Agency (DCMA) or other cognizant Government administration office, as applicable. If only part of a Contractor’s organization is EVMS ANSI/EIA Standard-748 certified, the Contractor shall make the distinction between which business units or sites and geographic locations have been certified.
Medicaid-Funded Hours Worked Effective July 1, 2021, the Employer shall contribute the Retirement Rate or eighty cents ($0.80), whichever is higher, to the Retirement Trust for each Medicaid-Funded Hour worked by all home care workers covered by this Agreement with seven-hundred and one (701) or more cumulative career hours and fifty cents ($0.50) for each hour worked by all home care workers covered by this Agreement with less than seven-hundred one (701) cumulative career hours. Medicaid- Funded Hour(s) worked shall be defined as all hours worked by all employees covered by this Agreement in the Employer's in-home care program that are paid by Medicaid, excluding vacation hours, paid-time off hours, and training hours.
Bulk Migration 2.1.9.1 If Telepak Networks requests to migrate twenty-five (25) or more UNE- Port/Loop Combination (UNE-P) customers to UNE-Loop (UNE-L) in the same Central Office on the same due date, Telepak Networks must use the Bulk Migration process, which is described in the BellSouth CLEC Information Package, “UNE-Port/Loop Combination (UNE-P) to UNE-Loop (UNE-L) Bulk Migration.” This CLEC Information package, incorporated herein by reference as it may be amended from time to time, is located at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/xxxxxx/xxxx/xxxx.xxxx. The rates for the Bulk Migration process shall be the nonrecurring rates associated with the Loop type being requested on the Bulk Migration, as set forth in Exhibit A of this Attachment. Additionally, OSS charges will also apply per LSR generated per customer account as provided for in the Bulk Migration Request. The migration of loops from Integrated Digital Loop Carrier (IDLC) will be done pursuant to Section 2.6 of this Attachment.
