SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS
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.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
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
Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.
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.
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.
