Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.
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.
Certification Requirements The applicant will provide Vista Laboratories, Inc. with all product information for the evaluation of the product to be certified and warrant that the information provided is accurate and complete so that Vista Labs may perform the services requested. If the product was tested at an external laboratory, the applicant must provide the complete test report to Vista Labs. If the external testing facility is not ISO 17025 accredited, or does not have the proper scope, Vista Labs must determine if the test report can be used for certification activities. The applicant’s information is used to perform a product review and evaluation to determine the product’s compliance to the specific certification requested. Throughout the process, the client agrees to make claims regarding certification consistent with the scope of certification. The applicant agrees to supply the required number of product samples, to be determined by Vista Labs, to the laboratory for testing, measurement, and evaluation purposes. The client understands that certain tests may damage or destroy the sample and acknowledge that Vista Labs is not responsible for such damages. Samples will be returned only upon request by the applicant and at the applicant’s expense, after the completion of certification. Samples will be disposed of after six months if not requested for return by applicant. The product is ineligible for certification if it has been modified by the client after testing or certification. Changes to the product must be approved by Vista Laboratories. Vista Labs reserves the right to re- evaluate the product as a result of information that raises questions concerning the conformance of the product. Certified products maintain fulfilment of product requirements if the certification applies to ongoing production. If the client provides copies of the certification documents to other parties, the documents are reproduced in their entirety, or as specified in the certification scheme. In making reference to its product certification in media, such as brochures or advertisement, the client complies with the requirements of the Vista Labs or as specified by the certification scheme. The client complies with any requirements that may be prescribed in the certification scheme relating to the use of marks of conformity, and on all product correspondences and product related information. Vista Labs reserves the right to revise or withdraw the requirements as required in order to maintain conformance with FCC rules and regulations governing the product. The product may continue with certification and receive certification upon demonstration of compliance with the revised requirements, to the satisfaction of Vista Laboratories.
GRADUATION REQUIREMENTS I understand that in order to graduate from the program and to receive a certificate of completion, diploma or degree I must successfully complete the required number of scheduled clock hours as specified in the catalog and on the Enrollment Agreement, pass all written and practical examinations with a minimum score of 80%, and complete all required clinical hours and satisfy all financial obligations to the College. Initial
Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.
Food Service Waste Reduction Requirements Contractor shall comply with the Food Service Waste Reduction Ordinance, as set forth in San Francisco Environment Code Chapter 16, including but not limited to the remedies for noncompliance provided therein.
Notification Requirement Through and up to the conclusion of the Non-Competition Period, Executive shall give notice to the Company of each new business activity he plans to undertake, at least seven (7) days prior to beginning any such activity. Such notice shall state the name and address of the Person for whom such activity is undertaken and the nature of Executive’s business relationship(s) and position(s) with such Person.
Admission and Graduation Requirements A. The receiving institution’s admission and program admission requirements apply to both direct entry students and to students who transfer under this agreement.
Personnel Action Requirements The evaluation procedure contained in this agreement shall not be used in any decision concerning the assignment, reassignment, contract status, non-renewal, termination, reduction or recall of any counselor prior to May 1, 2018.
Action Required To Complete This Project: Complete
