Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.
Project Design Applicants must design a project that provides access to health services to enable eligible women and men experiencing health needs to secure and maintain safe and accessible quality screening and diagnostic services, comprehensive family planning, and/ or other women’s health services.
A. Applicants are encouraged to emphasize the following components in the design of their projects. Projects must:
1. Use a collaborative approach to maximize existing community resources and avoid duplication of effort;
2. Enhance systems and local processes to make it easier for people to transition to, from, and between services;
3. Address barriers to ensure services are accessible to people regardless of setting or location; and
4. Promote improvement and positively impact health and well-being through coordinated service delivery.
B. To be effective, services and activities provided or made available as part of the Proposed Project should have policies and procedures in place and include with the application as an attachment that:
1. Delineate the timely provision of services;
2. Deem Client eligibility and service provision as soon as possible and no later than 30 calendar days from initial request;
3. Require staff to assess and prioritize Client needs;
4. Implement with model fidelity to an evidence-based program or based upon best available research;
5. Plan in partnership with the person and are inclusive;
6. Provide in an environment that is most appropriate and based on a person’s preference including reasonable clinic/reception wait times that are not a barrier to care;
7. Provide referral sources for Clients that cannot be served or receive a specific service;
8. Are culturally and linguistically sensitive;
9. Tailor services to a person’s unique strengths and needs;
10. Manage funds to ensure established Clients continuity of care throughout budget year;
11. Continue to provide services to established Clients after allocated funds are expended;
12. Have processes to identify and eliminate possible barriers to care;
13. Do not deny services due to inability to pay;
14. Have appropriate key personnel and required staff to meet the medical and health needs of Clients;
15. Bill services appropriately and timely through TMHP;
16. Effectively communicate and document information related to health care needs with next steps available to Client;
17. Establish outreach and education plan for the community; and
18. Outline successful delivery of direct clinical services to Clients By submitting an Application under this RFA, the Applicant certifies that Applicant has or will have at time of grant award services, policies, or procedures that conform with the requirements in this section as applicable. HHSC, in its sole discretion, may request to review relevant documentation during the project period as necessary to ensure program fidelity.
Study Design This includes a discussion of the evaluation design employed including research questions and hypotheses; type of study design; impacted populations and stakeholders; data sources; and data collection; analysis techniques, including controls or adjustments for differences in comparison groups, controls for other interventions in the State and any sensitivity analyses, and limitations of the study.
Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
Schematic Design Phase 1.2.1 Based on the mutually agreed upon Program of Requirements, Amount Available for the Construction Contract and the Project Schedule, the Architect/Engineer shall prepare sufficient alternative approaches utilizing BIM for design and construction of the Project to satisfy Owner’s project requirements and shall, at completion of this phase, submit Schematic Design Documents derived from the model in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review alternative approaches to design and construction for the Project as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by the Owner within the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Schematic Design. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner.
1.2.2 Architect/Engineer shall provide all services necessary to perform the services of this phase (preparation of model(s), relevant data, decision support model views and Schematic Design Documents) including, without limitation, unless otherwise approved by Owner, the preparation and prompt delivery of all items specified in the BIM Execution Plan and “Facility Design Guidelines”.
1.2.3 Architect/Engineer shall work closely with Owner in preparation of schematic drawings and shall specifically conform to Owner’s requirements regarding aesthetic design issues.
1.2.4 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments.
1.2.5 Before proceeding into the Design Development Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Schematic Design documents and approval of the Architect/Engineer’s preliminary Estimated Construction Cost and schedule.
1.2.6 The Architect/Engineer shall participate in a final review of the Schematic Design Documents and model(s) with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Schematic Design Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments, any of which may be appealed for good cause.
Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.
Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.
