Dynamic Data Replication Requirements Sample Clauses

Dynamic Data Replication Requirements. This service case deals with replication of data on demand to compute nodes such as HPC or grid compute elements, or to storage close to those nodes, where they will be used for analysis. Following analysis data will be removed from the site. In terms of the requirements which could impact scalability, the size and volumes of collections to replicate for an analysis run are clearly similar to the problems detailed in the Safe Replication Use case above. Depending on the infrastrcture, there could be additional scalability issues which need to be addresed such as whether the analysis jobs download data from the (local) storage element to the compute node (streaming model) or whether the jobs read directly from the storage element using a 'standard' protocol such as 'file' (random access model).  Streaming model has similar problems to the 'Safe Replication' service case described above, but potentially much worse. If many jobs are run concurrently and some subset of the data is required by all these jobs, unless the storage element provides 'automatic hot file replication', this could put significant load and result in very poor performance of the underlying storage system.  The random access model puts a different type of load on the underlying storage system; while throughput is significantly reduced in this model it does require the storage system to maintain very many open connections for an extended period of time. The number of concurrent open connections will be limited by both the underlying storage technology and possibly the federation technology used.
AutoNDA by SimpleDocs

Related to Dynamic Data Replication Requirements

  • Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following: 1. Total premiums reported on IRS Form 8963;

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

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Design Requirements The DG Facility shall be installed in compliance with Wisconsin Administrative Code Chapter PSC 119.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • 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. 2. If the event necessitating the Family Leave becomes known to the employee less than thirty (30) calendar days prior to the employee's need for Family Leave, the employee must provide as much notice as possible. In no case shall the employee provide notice later than five (5) calendar days after he or she learns of the need for Family Leave. 3. For foreseeable leave due to a qualifying exigency, an employee must provide notice of the need for leave as soon as practicable, regardless of how far in advance such leave is foreseeable. 4. When the Family Leave is for the purpose of the scheduled medical treatment or planned medical care of a child, parent, spouse or registered domestic partner, the employee shall, to the extent practicable, schedule treatment and/or care in a way that minimizes disruption to agency/department operations.

  • Construction Requirements (a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required. (b) Electric panel schedules must be brought up to date identifying all new circuits added. (c) All electrical outlets and lighting circuits are to be properly identified. Outlets will be labeled on back side of each cover plate. (d) All electrical and phone closets being used must have panels replaced and doors shut at the end of each day’s work. Any electrical closet that is opened with the panel exposed must have a work person present. (e) All electricians, telephone personnel, etc. will, upon completion of their respective projects, pick up and discard their trash leaving the telephone and electrical rooms clean. If this is not complied with, a clean-up will be conducted by the building janitors and the general contractor will be back-charged for this service. (f) Welding or burning with an open flame will not be done without prior approval of the Building Manager. Fire extinguishers must be on hand at all times. (g) All “anchoring” of walls or supports to the concrete are not to be done during normal working hours (7:30 AM—6:00 PM, Monday through Friday). This work must be scheduled before or after these hours during the week or on the weekend. (h) All core drilling is not to be done during normal working hours (7:30 AM—6:00 PM, Monday through Friday). This work must be scheduled before or after these hours during the week or on the weekend. (i) All HVAC work must be inspected by the Building Engineer. The following procedures will be followed by the general contractor: i) A preliminary inspection of the HVAC work in progress will be scheduled through the Building Office prior to the reinstallation of the ceiling grid. ii) A second inspection of the HVAC operation will also be scheduled through the Building Office and will take place with the attendance of the HVAC contractor’s Air Balance Engineer. This inspection will take place when the suite in question is ready to be air-balanced. [***] = CONFIDENTIAL INFORMATION HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THIS OMITTED INFORMATION. iii) The Building Engineer will inspect the construction on a periodic basis as well. (j) All existing thermostats, ceiling tiles, lighting fixtures and air conditioning grilles shall be saved and turned over to the Building Engineer.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!