> For the complete documentation index, see [llms.txt](https://manual.egclinea.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.egclinea.com/statistik.md).

# Statistik

Statistik modulet er bygget op af mange elementer, som kan sammensættes som ønsket for at specificere en søgning.

### Indstillinger

#### Hvilke indstillinger kan ændres af klinikken/brugeren selv?

Åbn '**Indstillinger**' og vælg '**Statistik**' for at se, hvilke indstillinger, klinikken/brugeren selv kan administrere.

Læs mere om, hvordan en indstilling generelt kan ændres [her](/tips_og_tricks/tilpas_indstillinger.md).

Se eventuelt næste punkt for yderligere beskrivelse.

#### Beskrivelse af de tilgængelige indstillinger

* **Max poster:** Angiver, hvor mange poster, der maks. må hentes ad gangen.\
  **OBS!** Dette kan have indflydelse på hastigheden.
* **Start skabelon:** Skabelonen som programmet skal hente ved opstart angives her.
* **Tidshorisont i dage:** Angiver, hvor mange dage tilbage i tiden, data skal hentes, når programmet starter.
* **Timeout:** Angiver, hvor mange minutter, der skal gå fra en søgning sættes i gang, til der kommer en timeout.\
  Dette skal forhindre, at programmet kan komme til at låse fast i en data søgning.


---

# 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://manual.egclinea.com/statistik.md?ask=<question>&goal=<user_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.