Encounter Data Elements Sample Clauses

Encounter Data Elements. Encounter data elements are based on the Medicaid-Medicare Common Data Initiative (McData Set) which is a minimum core data set for states and MCOs developed by HCFA and HSD for use in managed care. HSD may increase or reduce or make mandatory or optional, data elements as it deems necessary.
Sample 1
AutoNDA by SimpleDocs
Encounter Data Elements. Encounter data elements are a combination of those elements required by HIPAA-compliant transaction formats, which comprise a minimum core data set for states and managed care organizations, and those 148 required by CMS or the State for use in managed care. The State may increase or reduce or make mandatory or optional, data elements, as it deems necessary. The CONTRACTOR will be held harmless in conversion to HIPAA coded encounter data when delays are the result of HIPAA implementation issues. The transition to HIPAA codes and requirements does not relieve the CONTRACTOR of timely submission of encounter data. The State will approve necessary default values for paper claim encounters that must pass the State’s required HIPAA format edits. The CONTRACTOR shall submit encounter data to the State using the 837 and NCPDP formats. The State will work with the CONTRACTOR and HSD/MAD’s claims processing contractor to provide the CONTRACTOR with an electronic disposition of each submitted encounter. Financial Reporting
Sample 1
Encounter Data Elements. Encounter data elements are a combination of those elements required by HIPAA-compliant transaction formats, which comprise a minimum core data set for states and managed care organizations, and those required by CMS or HSD/MAD for use in managed care. . Subject to the provisions of Section 4.2 of this Agreement, HSD/MAD may increase or reduce or make mandatory or optional, data elements, as it deems necessary. The CONTRACTOR will be held harmless in conversion to HIPAA coded encounter data when delays are the result of HIPAA implementation issues at HSD/MAD. The transition to HIPAA codes and requirements does not relieve the CONTRACTOR of timely submission of encounter data. HSD/MAD will approve necessary default values for paper claim encounters that must pass HSD/MAD required HIPAA format edits.
Sample 1
Encounter Data Elements. Encounter data elements are based on the Medicaid-Medicare Common Data Initiative (McData Set), which is a minimum core data set for states and MCOs developed by CMS and HSD for use in managed care. Subject to the provisions of Section 4.2 of this Agreement, HSD may increase or reduce or make mandatory or optional, data elements as it deems necessary. The CONTRACTOR will be held harmless in conversion to HIPAA coded encounter data when delays are the result of HIPAA implementation issues at HSD. The transition to HIPAA codes and requirements does not relieve the CONTRACTOR of timely submission of encounter data.
Sample 1

Related to Encounter Data Elements

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Contract Database Metadata Elements Title: Spencerport Central School District and Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO (2015) Employer Name: Spencerport Central School District Union: Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO Local: Effective Date: 07/01/2015 Expiration Date: 06/30/2018 PERB ID Number: 6253 Unit Size: Number of Pages: 27 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT between the SUPERINTENDENT OF SCHOOLS SPENCERPORT CENTRAL SCHOOL DISTRICT Town of Ogden, Gates, Greece and Parma and SPENCERPORT PARAPROFESSIONAL ASSOCIATION July 1, 2015 - June 30, 2018 TABLE OF CONTENTS ARTICLE PAGE PREAMBLE 1 RECOGNITION 1 ELIGIBLITY FOR BENEFITS 1 ARTICLE 1 DUES DEDUCTION 2 ARTICLE 2 SICK LEAVE 2 ARTICLE 3 PERSONAL LEAVE 3 ARTICLE 4 ILLNESS IN FAMILY 4 ARTICLE 5 FAMILY MEDICAL LEAVE ACT 4 ARTICLE 6 HEALTH INSURANCE 5 ARTICLE 7 WORKER'S COMPENSATION 8 ARTICLE 8 BEREAVEMENT 9 ARTICLE 9 SNOW DAYS AND EMERGENCY CLOSING 9 ARTICLE 10 JURY DUTY 9 ARTICLE 1 WORK YEAR 9 ARTICLE 12 EXTRA HOURS WORKED 10 ARTICLE 13 1:1 AIDES 10 ARTICLE 14 LUNCH & BREAKS 10 ARTICLE 15 LONGEVITY 10 ARTICLE 16 PAID HOLIDAYS 1 ARTICLE 17 SALARY 12 ARTICLE 18 UNUSED SICK DAYS AT RETIREMENT 14 ARTICLE 19 GRIEVANCE PROCEDURE 15 ARTICLE 20 UNPAID LEAVE OF ABSENCE 17 ARTICLE 21 SENIORITY, ASSIGNMENT, AND LAYOFF 18 ARTICLE 22 VACANCY NOTIFICATIONS 20 ARTICLE 23 CREDIT FOR IN-SERVICE COURSES 20 ARTICLE 24 PROBATIONARY PERIOD 21 ARTICLE 25 FLEXIBLE SPENDING ACCOUNT 21 ARTICLE 26 ATTENDANCE INCENTIVE 21 ARTICLE 27 PERSONNEL FILES 22 ARTICLE 28 EVALUATIONS 22 ARTICLE 29 EARLY DISMISSAL - i - 22 ARTICLE 30 DIRECT DEPOSIT 23 ARTICLE 31 PAYROLL DEDUCTION 23 ARTICLE 32 PAYROLL DISTRIUBTION 23 ARTICLE 33 CONFORMITY OF LAW 23 ARTICLE 34 CHAPERONING AND PROCTORING 23 ARTICLE 35 BUS ATTENDANTS 24 ARTICLE 36 DURATION OF AGREEMENT 24 P R E A M B L E The Spencerport Central School District and the Spencerport Paraprofessional Association desire to enter into the agreement in order to effectuate the provisions of the Public Employees' Fair Employment Act and to encourage and increase the effective and harmonious work relationship between the district and the paraprofessionals who comprise the unit members within the bargaining unit represented by the association. The association hereby reaffirms that it will not engage in any strike, or cause, instigate, encourage, assist or condone any strike. The district recognizes the right of these unit members to organize and to bargain collectively through the association on such matters as salaries, hours and other terms and conditions of employment. The agreement is made and entered into on the 23rd day of June, 2015, by and between the Superintendent of Schools, SPENCERPORT CENTRAL SCHOOL DISTRICT, Spencerport, New York, hereinafter referred to as the "district," and the unit members of this unit of aforementioned school district, represented by the SPENCERPORT PARAPROFESSIONAL ASSOCIATION, hereinafter referred to as the "association." RECOGNITION Pursuant to the New York State Public Employees Fair Employment Act, the Board of Education of Spencerport Central School District has recognized the Spencerport Paraprofessional Association, hereinafter referred to as "association," as the exclusive negotiating representative for all Accompanists, Bus Attendants, Licensed Practical Nurses, Microcomputer Maintenance Technicians, School Aides and Teacher Aides employed by said district. ELIGIBILITY FOR BENEFITS All unit members employed by the District on June 30, 2000, while serving in a 27.5 (or more) hours per week position, will be considered as “full time” and will receive all of the benefits of unit members working 30 or more hours per week as detailed in Articles 2, 3, 4, 6, and 12 of this agreement. All unit members hired after June 30, 2000 are eligible for all of the benefits as detailed in Articles 2, 3, 4, 6, and 12 of this agreement and considered “full time” when serving in a 30 (or more) hours per week position. Any unit member hired after July 1, 2000 in a 30 (or more) hours per week capacity who is involuntarily reduced to at least 27.5 hours per week will receive the benefits associated with “full time” employment (Articles 2, 3, 4, 6, and 12). Spencerport Paraprofessional Association - 1 - July 1, 2012 - June 30, 2015

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Contractor Changes The Contractor shall notify DAS in writing no later than ten (10) Days from the effective date of any change in:

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Customer Data 4.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Claims Review Population A description of the Population subject to the Claims Review.

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