> For the complete documentation index, see [llms.txt](https://www.opioidsettlementguides.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opioidsettlementguides.com/delaware/delawares-opioid-settlements.md). # Delaware’s Opioid Settlements *This Community Guide will describe how Delaware is spending its opioid settlements and whether Delaware is working to ensure community access to opioid settlement funds. Last revised September 1, 2024.*

Total Funds

$197.36 million[1]

[1] Total is rounded. See The Official Opioid Settlement Tracker Tally. Accessed September 1, 2024.

Allocation

100% to the Prescription Opioid Settlement Fund


Mechanism

State-Local Agreement (Remediating Opioids Across Delaware through State-Municipal Abatement Partnership (‘ROADS MAP’) Agreement); Legislation (Del. Code Ann. tit. 16, Secs. 4808B, 5195, 5196, 5196A, 5196B); Commission Resolutions (Resolution Nos. 2022-1 and 2023-1)

100% Prescription Opioid Settlement Fund

Ultimate DecisionmakerDelaware Behavioral Health Consortium
Decision-making ProcessThe Delaware Behavioral Health Consortium distributes settlement funds based on recommendations from the Prescription Opioid Settlement Distribution Commission (POSDC).
SupplantationProhibited
Grant FundingYes. See the POSDC’s Open Public Opportunities page.
Public InputYes (public input and public hearings required)
Advisory Body

Yes (required). See the Prescription Opioid Settlement Distribution Commission (POSDC).

The POSDC is not required to include member(s) with lived and/or living experience.

ExpendituresPublic reporting required. See the Prescription Opioid Settlement Tracker and view grant awards on the PSODC’s website.
UpdatesFor updates on the Prescription Opioid Settlement Fund, visit the POSDC’s website and subscribe to receive emails. To view and subscribe to the POSDC’s calendared public events, including the meetings of its various committees, click “Subscriptions” here.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.opioidsettlementguides.com/delaware/delawares-opioid-settlements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.