Audit Method and Data Requirement 5 Sample Clauses

Open Split View

Download

Share

Cite

Audit Method and Data Requirement 5. Auditové metody a požadavky na informace

Sample 1

Save

Copy

Related to Audit Method and Data Requirement 5

• Power Factor Requirement Consistent with Section 4.7 of Appendix 2 to this ISA, the power factor requirement is as follows: The Generation Interconnection Customer shall design its non-synchronous Customer Facility with the ability to maintain a power factor of at least 0.95 leading to 0.95 lagging measured at the high-side of the facility substation transformers.

• Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

• Reasonable Suspicion Testing The Employer may, but does not have a legal duty to, request or require an employee to undergo drug and alcohol testing if the Employer or any supervisor of the employee has a reasonable suspicion (a belief based on specific facts and rational inferences drawn from those facts) related to the performance of the job that the employee:

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

• Service Order Process Requirements 53.5.1 CenturyLink will accept orders for As-Is Transfer of services from CenturyLink to CLEC where CenturyLink is the End User’s current local exchange carrier.

• Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

• Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

• Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

• Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

• Minimum Standard of Treatment 1. Each Party shall accord to a covered investment treatment in accordance with the customary international law minimum standard of treatment of aliens, including fair and equitable treatment and full protection and security.