> 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/hent_patient.md).
# Hent patient
Der er flere måder at hente en patient på. Patienten aktiveres i EG Clinea og fjernes samtidig fra køen.
{% hint style="info" %}
**Bemærk!** Er det opsat på den enkelte kø, hvilket gøres i Systemmanager, er det muligt at bevare patienten i køen.
{% endhint %}
### Hent med Enter
Tryk Enter på en patient for at hente den aktuelle patient ud af køen.
### Hent med Shift+Enter
Tryk Shift+Enter for at hente den øverste/første patient ud af køen.
### Hent med talkode (Nr.)
Tast et tal mellem 1-9 for en given patient for at hente den aktuelle patient ud af køen.
{% hint style="info" %}
**Bemærk!** Det er tallene ovenover bogstaverne på tastaturet, der skal bruges.
{% endhint %}
---
# 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/hent_patient.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.