Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.
Physical Requirements A. The gradation when tested by means of laboratory sieves conform to the following requirements for particle size without any variation: Sieve Size % Passing by Weight 5/8” 100.0% 7/16” 95.0% - 100.0% No. 4 60.0% No. 8 35.0%
Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8
Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.
GENERAL OPERATIONAL REQUIREMENTS 12.1 Interference or damage to Distributor's Equipment by Customers: The Trader must, subject to clause 29.1, include in each of its Customer Agreements a requirement that, during the term of the Customer Agreement and until the end of the period ending on the earlier of 6 months after the termination of the Customer Agreement or the date on which a new Customer Agreement is entered into in respect of the relevant ICP, the Customer must not interfere with or damage, and must ensure that its agents and invitees do not interfere with or damage, the Distributor's Equipment without the prior written consent of the Distributor (except to the extent that emergency action has to be taken to protect the health or safety of persons or to prevent damage to property).
General Requirement Any notice, election, demand, request, consent, approval, or other communication required or permitted to be given under this Contract shall be in writing signed by an officer or duly authorized representative of the party making same and shall be delivered personally or shall be sent by certified or statutory mail, postage prepaid, return receipt requested, shall be effective as of the date on which it is received or would have been received but for the refusal of the addressee to accept delivery, and shall be addressed as shown in the Contract. The persons and addresses to which notices should be given may be changed by notice given in accordance with this Article.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Federal Requirement The Work to be performed under this Agreement may be paid for in part by federal funds and therefore is subject to federal statutes, rules, regulations, laws, orders and directives applicable to work paid for by federal funds. In the event an applicable federal requirement conflicts with any provision of the Contract Documents, the federal requirement shall prevail and take precedence over and against such conflicting provisions. Federal requirements may include, but is not limited to:
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
