> 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/tips_og_tricks/hjaelpelinje.md).
# Hjælpelinje
## Hjælpelinjen nederst i EG Clinea
Fremkommer ved fokus i et felt i det tilfælde, der er funktioner/genveje, som kan anvendes i det pågældende felt.
**Hjælpelinjen varierer** afhængigt af felt, der er i fokus, og kan være særlig brugbar, hvis der er tvivl om brugen af et felt.
#### Eksempler på hjælpelinjen
**Eksempel**: Feltet '*Post/By*' på Patienthovedet.
I feltet er det muligt at;
* vælge postnummer/by fra liste med <Ins>
* rette postnummer/by med <F2>
* slette postnummer/by med <Del>
**Eksempel**: Kalender med fokus på en booket tid.
Orange pil yderst til højre i hjælpelinjen, betyder det, at flere genveje kan vises. Klik på pilen og en linje 2 fremkommer med genveje.
---
# 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/tips_og_tricks/hjaelpelinje.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.
