> 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/koe/saet-i-koe.md).

# Sæt i kø

Der er flere måder at sætte en patient i kø på.

{% hint style="info" %}
**Bemærk!** I kalenderen bliver patientens tid markeret, når patienten er sat i kø.
{% endhint %}

### Sæt i kø med F7

1. Tryk `F7`.
2. Kør patientens sygesikringskort igennem.
3. Tryk `F4`.

Uanset hvilken kalender patienten har en tid i, sender systemet patienten over i den kø, som hører til den pågældende kalender. Det vil altid være den første aftale, der findes, som bruges.

### Sæt i kø med F4

1. Gå i kalenderen, og brug pil ned til at markere patienten.
2. Tryk <kbd>F4</kbd>.

Patienten sættes nu i den pågældende kø.

### Sæt i kø med genvejstast

Sæt en patient i kø med <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+**kø-nr.**, eller vælg fra kølisten med <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>+</kbd>, uanset hvor fokus er i EG Clinea.

### Vælg kø med Shift+F4

1. Gå i kalenderen.
2. Tryk <kbd>Shift</kbd>+<kbd>F4</kbd> for at åbne skærmbilledet *Vælg kø*.

En oversigt over alle køer, der er opsat i systemet, vises. Vælg den ønskede kø fra oversigten.

I notefeltet står, hvilken kø patienten er sat i.


---

# 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/koe/saet-i-koe.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.
