> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/areas-and-zones-portfolio/boundary-line/boundary-line-product-information/case-studies.md). # Case studies ## **Creating the right environment for data management: The Welsh Environmental Data Interface (WENDI)** Agriculture, forestry and woodland account for 90% of Wales’s land use, generating a wealth of insightful statistical information. The Senedd Cymru / Welsh Parliament uses this data to inform policy, assist decision-making and help deliver a wide range of services to rural communities. ## **Sharing data across the NHS to improve patient services** NHS North West was established under government policy to strengthen primary care trusts (PCTs) and give GPs greater ability to commission or purchase health services directly for their patients. The organisation replaced the three former strategic health authorities in Cumbria and Lancashire, Cheshire and Merseyside, and Greater Manchester. The Association of Greater Manchester PCTs is taking forward a data analysis and reporting tool called the TIS Analyser, which was developed by Greater Manchester health organisations as part of the Tactical Information Service (TIS). --- # 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://docs.os.uk/os-downloads/products/areas-and-zones-portfolio/boundary-line/boundary-line-product-information/case-studies.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.