• English

    Google Translate Disclaimer

    The Maryland Department of Information Technology (“DoIT”) offers translations of the content through Google Translate. Because Google Translate is an external website, DoIT does not control the quality or accuracy of translated content. All DoIT content is filtered through Google Translate which may result in unexpected and unpredictable degradation of portions of text, images and the general appearance on translated pages. Google Translate may maintain unique privacy and use policies. These policies are not controlled by DoIT and are not associated with DoIT’s privacy and use policies. After selecting a translation option, users will be notified that they are leaving DoIT’s website. Users should consult the original English content on DoIT’s website if there are any questions about the translated content.

    DoIT uses Google Translate to provide language translations of its content. Google Translate is a free, automated service that relies on data and technology to provide its translations. The Google Translate feature is provided for informational purposes only. Translations cannot be guaranteed as exact or without the inclusion of incorrect or inappropriate language. Google Translate is a third-party service and site users will be leaving DoIT to utilize translated content. As such, DoIT does not guarantee and does not accept responsibility for, the accuracy, reliability, or performance of this service nor the limitations provided by this service, such as the inability to translate specific files like PDFs and graphics (e.g. .jpgs, .gifs, etc.).

    DoIT provides Google Translate as an online tool for its users, but DoIT does not directly endorse the website or imply that it is the only solution available to users. All site visitors may choose to use alternate tools for their translation needs. Any individuals or parties that use DoIT content in translated form, whether by Google Translate or by any other translation services, do so at their own risk. DoIT is not liable for any loss or damages arising out of, or issues related to, the use of or reliance on translated content. DoIT assumes no liability for any site visitor’s activities in connection with use of the Google Translate functionality or content.

    The Google Translate service is a means by which DoIT offers translations of content and is meant solely for the convenience of non-English speaking users of the website. The translated content is provided directly and dynamically by Google; DoIT has no direct control over the translated content as it appears using this tool. Therefore, in all contexts, the English content, as directly provided by DoIT is to be held authoritative.

    Community Pathways Waiver Amendment #1

    The Department of Health and Mental Hygiene (DHMH) will be making changes to the Community Pathways Waiver to create a more flexible, person-centered, family oriented system of supports. The changes contained herein are based on feedback from individuals receiving services and their families, recommendations from the independent consultants, and are aimed at furthering compliance with new federal rules and requirements from the Center for Medicare and Medicaid Services (CMS) and the Department of Labor (DOL).

    Requests to make changes to the wavier program are made by submitting a Waiver Amendment to CMS. DHMH plans to make several changes to the waiver program in the coming months that require sequencing, therefore amendments will occur in stages and will address new federal rules; will reflect the development of new services, improved business rules, processes, and service rates; and will provide ample opportunity for meaningful public engagement on the prospective changes.

    Community Pathways Waiver Amendment #1 – Effective July 1, 2016

    Amendment #1 - Proposal

    Process/Next Steps

    • Public comment period December 18, 2015 through January 31, 2016
    • State review of comments and consideration for revisions to amendment – February 2016
    • Waiver Amendment Submission to CMS – March 2016
    • Respond to CMS Questions – March through May 2016
    • Projected CMS Approval – June 2016
    • Projected effective Date – July 1, 2016