> 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/allergivacc_/vaccinationsforloeb.md).
# Vaccinationsforløb
De allergener, som er angivet positive under priktests, vises i allergenlisten. Som standard er de angivet som et ikke aktivt vaccinationsforløb.
## Opret vaccinationsforløb
Når et allergen sættes til aktivt med <F2>, oprettes et tomt vaccinationsforløb på baggrund af opsætningen i [Systemmanager](/systemmanager/allergivaccination.md).
**Åbn** redigeringsbilledet for den enkelte opdosering/vedligehold med<Ins>.
* Inj.nr, SQ-U/ml. og ml. angives automatisk.
* Er der tidligere givet en vaccination i forløbet med samme styrke foreslås samme batchnummer.
* Er der foretaget en spirometri samme dag foreslås peakflow fra denne som peakflow før. Er der foretaget en spirometri post samme dag foreslås denne som peakflow efter.
* Ønskes en ekstraordinær injektion, kan denne indsættes ved brug af <Shift+Ins>. Her angives injektionen f.eks. med 1a, 1b osv.
* Peakflow afspejles i grafen med 2 forskellige farver, rød før – blå efter.
## Skærmbillede
## Notat i Journal
I Journalen kan et notat automatisk blive oprettet indeholdende styrke, mængde, hævelse og kommentar. Det forudsætter en indstilling hertil er valgt.
---
# 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/allergivacc_/vaccinationsforloeb.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.