> For the complete documentation index, see [llms.txt](https://docs.sygnal.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sygnal.network/build-and-join/sandbox.md). # Sygnal Sandbox An open test network where teams connect their health platforms and try care coordination with test data. The Sygnal Sandbox is an open test network. Teams connect their health platforms and try out care coordination with other platforms, using **test data only**. Medtronic LABS operates it as part of Sygnal, an open initiative led by Medtronic LABS. ## What you can do * **Find care providers.** Search the network's discovery service for services that other platforms offer. * **Send and manage referrals.** Run complete referral journeys with other platforms: sending a referral, the provider accepting it, the patient attending, and the referral being completed. * **Raise referral issues.** Flag problems, such as a referral that isn't acknowledged in time or isn't honoured, and see how the other side responds. * **See the network view.** Watch your traffic appear on the sandbox dashboards. They show how referrals move across the network, without any patient or clinical details. The [reference flows](/build-and-join/running-reference-flows.md) are a good way to start: they run the [use cases](/use-cases/use-cases.md) end to end. ## Sandbox rules * **Test data only.** Never send real patient information, including in notes. * **Data may be reset.** The sandbox may be cleared from time to time, with notice where possible. * **No service guarantees.** The sandbox is for testing and learning. It may change, or be unavailable at times. * **Shared space.** Other teams can see the overall activity on the dashboards, including your platform's name. ## Getting started To connect your platform, email with a short note about your platform and what you'd like to test. You'll get the sandbox network's details and dashboard addresses. The general steps are in [Joining a network](/build-and-join/joining-a-network.md). For help once you're connected, email . ## After the sandbox Production access opens network by network. Once a network has tested in the sandbox and is ready to go live, production use is agreed with it, including hosting, data handling, availability and support. See [Protocol, platform and services](/concepts/protocol-platform-services.md). --- # 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.sygnal.network/build-and-join/sandbox.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.