The planning council works with the Ryan White Part A Office to identify service needs by conducting a needs assessment. This involves first finding out how many persons living with HIV are in the area through an epidemiologic profile. Usually, an epidemiologist from the local or state health department provides this information. Next, the council determines the needs of populations living with HIV and the capacity of the service system to meet those needs. This assessment of needs is done through surveys, interviews, key informant sessions, focus groups, or other methods.
The planning council uses needs assessment data and data from a number of other sources to set priorities and allocate resources. This means the members decide which services are most important to people living with HIV (priority setting) and then agree on which service categories to fund and how much funding to provide (resource allocations). In setting priorities, the planning council considers what service categories are needed to provide a comprehensive system of care for people living with HIV, without regard to who funds those services.
The planning council works with the Ryan White Part A Office in developing a written plan that defines short- and long-term goals and objectives for delivering HIV services and strengthening the system of care in Broward County. This is called a comprehensive plan in the legislation but is now called the CDC and HRSA Integrated HIV Prevention and Care Plan, including the Statewide Coordinated Statement of Need (SCSN).
The planning council is responsible for evaluating how rapidly RWHAP Part A funds are allocated and made available for care. This involves ensuring that funds are being contracted quickly and through an open process, and that providers are being paid in a timely manner. It also means reviewing whether the funds are used to pay only for services that were identified as priorities by the planning council and whether the amounts contracted for each service category are the same as the planning council’s allocations. The results of this assessment of the efficiency of the administrative mechanism are shared with the Ryan White Part A Office, who develops a response including corrective actions if needed.
The planning council is responsible for ensuring that RWHAP Part A resource allocation decisions account for and are coordinated with other funds and services. The planning tasks described earlier (needs assessment, priority setting, resource allocation, and integrated/comprehensive planning) require getting lots of input, including finding out what other sources of funding exist. This information helps avoid duplication in spending and reduce gaps in care.
Service standards guide providers in implementing funded services. They typically address the elements and expectations for service delivery, such as service components, intake and eligibility, personnel qualifications, and client rights and responsibilities. The service standards set the minimum requirements of a Ryan White Part A service and serve. Developing service standards is usually a joint activity; the Clinical Quality Management team works with the Ryan White Part A Office, planning council, providers, consumers, and experts on service categories.
The planning council may choose to evaluate how well services funded by RWHAP Part A are meeting identified community needs, or it can pay someone else to do such an evaluation. The CQM program provides information on clinical outcomes that informs the planning council about the impact of services. Planning Council members participate through the Quality Management and System of Care Committees. In addition, the planning council regularly reviews performance along the HIV care continuum. The planning council uses evaluation findings in considering ways to improve the system of care, including changing service priorities and allocations, and developing directives.
HIV Health Service Planning Council
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to