> 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/journal/funktioner_og_felter_journal/kopier-diagnoser-til-resume.md).
# Kopier diagnoser til resume
{% hint style="info" %}
**Bemærk!** Dette er en valgmulighed, som ikke er slået til som standard. Kontakt EG Clinea Support, hvis funktionen ønskes.
{% endhint %}
Tilføjer du en kontaktdiagnose, kan du få den kopieret til resuméet via afkrydsningsfeltet **Kopier til resumé**, som vises på skærmbilledet med koder.
* Sætter du kryds i feltet, tilføjes markeringen "r" ud for diagnosen i listen over kontaktårsager. Det viser, at diagnosen overføres til resumé, når journalnotatet gemmes. Ved selve overførslen ændres markeringen fra "**r**" til "**R**".
* Diagnosen tilføjes sidst i det eksisterende resumé, med dato for tilføjelsen. Den seneste kopierede diagnose står altid nederst.
* Der er ingen direkte relation mellem diagnosen markeret i journalen og diagnosen i resuméet. Ophæves markeringen på kontaktdiagnosen senere, slettes diagnosen derfor ikke i resuméet.
**Bemærk!** Er funktionen slået til, kan du ikke redigere direkte i resuméet på Patienthovedet. For at redigere skal du trykke Ctrl+F8 for fuld skærm. Det er for at undgå, at resuméet konstant er låst.
---
# 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/journal/funktioner_og_felter_journal/kopier-diagnoser-til-resume.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.