> 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/diagnose-icpc2/patientforloeb.md).
# Patientforløb
{% hint style="info" %}
**Bemærk!** Afsnittet henvender sig til almenlæger.
{% endhint %}
### Patientforløb
Ved oprettelse af journalnotat med en eller flere diagnoser, der er defineret til at have en varighed på mere end seks måneder, oprettes disse automatisk under *Forløb*. Dette gælder også de autogenererede kontakter, der oprettes på baggrund af de modtagne svar.
Alle start- og slutdatoer kan angives manuelt på et forløb.
#### Tilknytning til forløb
Sådan tilknyttes en kontaktdiagnose til et forløb:
1. Placer fokus på kontaktdiagnosen.
2. Tryk Ctrl+Shift+Ins.
* Findes diagnosen allerede som forløb, knyttes kontakten blot til forløbet.
* Findes diagnosen ikke som forløb, oprettes et nyt forløb med den startdato, som kontakten angiver.
Ønskes kontakten i stedet knyttet til en helt anden forløbsdiagnose:
1. Tryk Ctrl+Alt+Ins. En liste over alle åbne forløb vises.
2. Vælg det ønskede forløb. Kontakten knyttes hertil.
Det er muligt at knytte en kontakt til flere forløb.
---
# 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/diagnose-icpc2/patientforloeb.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.