> For the complete documentation index, see [llms.txt](https://saint-hollow.gitbook.io/saint-hollow-roleplay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saint-hollow.gitbook.io/saint-hollow-roleplay/normativa-medicos/centralizacion-de-pedidos.md).

# Centralización de Pedidos

Todos los doctores tienen autorización para realizar pedidos de suministros y comparten la responsabilidad sobre los recursos del hospital. Para evitar confusiones, gastos innecesarios o pedidos duplicados, es recomendable mantener una comunicación clara y constante entre el personal.

Cada vez que se realice un pedido, este deberá registrarse en el canal correspondiente de Discord, indicando qué materiales fueron solicitados. Del mismo modo, deberá notificarse cuando el pedido haya sido recogido y si este ya fue pagado o continúa pendiente de pago.

Esta normativa busca facilitar la organización interna, mantener un control eficiente de los suministros y garantizar que todos los miembros del cuerpo médico dispongan de información actualizada sobre el estado de los pedidos y recursos del hospital.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://saint-hollow.gitbook.io/saint-hollow-roleplay/normativa-medicos/centralizacion-de-pedidos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.