> 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/medicin_fmk/ajourfoer_medicinkort.md).

# Ajourfør medicinkort

Ajourføring af patientens medicin foretages af patientens egen læge sammen med patienten eller uden patienten i de tilfælde lægen selv har overblik over patientens aktuelle medicin.

Ved at gennemgå medicinkortets ordinationer og løse recepter og derefter ajourføre afspejler medicinkortet patientens aktuelle medicin. De [løse recepter](/medicin_fmk/loese_recepter.md) oprettes som ny ordination, knyttes til en ordination eller markeres som uaktuel. Ved tilknytning af løse recepter til ordination, vil systemet advare i det tilfælde præparatet på den løse recept er forskellig fra præparatet på ordinationen. Det er dog fortsat muligt at tilknytte.\
 \
**Ajourfør** efter gennemgang af medicinkortet med knappen **Ajourfør**.

Kvittering for ajourføring registreres i historikken på FMK, så andre instanser kan se, hvem der sidst har ajourført patientens medicinkort.

[Læs trinvis eksempel på ajourføring af en patients medicinkort.](/medicin_fmk/ajourfoer_medicinkort/trinvis-eksempel_ajourfoer-medicinkort.md)


---

# 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/medicin_fmk/ajourfoer_medicinkort.md?ask=<question>&goal=<user_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.