> 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/patienthovedet/skaermbillede_patienthovedet/yderligere-visningsmuligheder_patienthovedet.md).
# Yderligere visningsmuligheder
Der er forskellige muligheder i henhold til hvad der vises i nederste del af skærmbilledet på Patienthovedet.
## Resume
Hvis ønsket er det mulig at få **resume** vist i den nederste del af **Patienthovedet** i stedet for **relationer**. Herfra skiftes der til familierelationer og tilbage igen med F3. Dette er en indstilling på brugerniveau, som sættes op i [Systemmanageren.](/systemmanager/system/brugere.md)
Resume kan også findes under Ctrl+Q. Kun fra Ctrl+Q er det muligt at printe.
I Resume er det via højreklik muligt at vælge en zoom funktion alt efter hvor stor/lille skrifttype, der ønskes.
I Resume kan konverteret resume fra diagnosekoder fra diverse modtagne epikriser i Beskeder og fra journalen vises, såfremt dette er sat op af EG Clinea.
## Billede
En anden mulighed er at få et billede i patienthovedet nederst til højre. Dette sættes op af EG Clinea og kræver modulet Media.
---
# 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/patienthovedet/skaermbillede_patienthovedet/yderligere-visningsmuligheder_patienthovedet.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.