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.
Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:
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.
Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.
Alternate Work Schedule An alternate work schedule is any work schedule where an employee is regularly scheduled to work five (5) days per week, but the employee’s regularly scheduled two (2) days off are NOT Saturday and Sunday.
Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.
ORDERING PROCEDURE Orders placed against this contract may be in the form of an agency issued purchase order on an as-required basis. Or an agency may also use the Arkansas State Purchasing Card (P- Card) to purchase furniture.
Program Design The County Human Resources Department will operate a Catastrophic Leave Bank which is designed to assist any County employee who has exhausted all paid accruals due to a serious or catastrophic illness, injury, or condition of the employee or family member. The program establishes and maintains a Countywide bank wherein any employee who wishes to contribute may authorize that a portion of his/her accrued vacation, compensatory time, holiday compensatory time or floating holiday be deducted from those account(s) and credited to the Catastrophic Leave Bank. Employees may donate hours either to a specific eligible employee or to the bank. Upon approval, credits from the Catastrophic Leave Bank may be transferred to a requesting employee's sick leave account so that employee may remain in paid status for a longer period of time, thus partially ameliorating the financial impact of the illness, injury, or condition. Catastrophic illness or injury is defined as a critical medical condition, a long-term major physical impairment or disability which manifests itself during employment.
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.
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
