> For the complete documentation index, see [llms.txt](https://manual-egcliniccare.eghealthcare.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-egcliniccare.eghealthcare.dk/moduler-og-funktioner/dokumentation/opret-nyt-notat.md).
# Opret nyt notat
Klik på knappen  øverst til venstre for at oprette et nyt notat. Editoren åbnes i venstre side af skærmen, mens alle eksisterende notater forbliver synlige til højre – så du kan referere til tidligere behandlinger og observationer mens du skriver.
Når editoren er åben, så vælger du den type skabelon du vil oprette. Her justerer du dato og tidspunkt efter behov, hvoraf standardværdien er det aktuelle tidspunkt.
Vælg den skabelontype der passer til notatet. Følgende skabeloner er tilgængelige som standard:
* Anamnese
* Behandlingsnotat
* Overblik
* Medicin
* Samtykke
* Vedhæftede filer
{% hint style="info" %}
Din klinik kan desuden have egne [skabeloner](/moduler-og-funktioner/dokumentation/skabeloner.md) tilgængelige i listen.
{% endhint %}
Alle tekstfelter understøtter grundlæggende formatering via værktøjslinjen øverst i feltet:
Funktion
Beskrivelse
B
Fed tekst
I
Kursiv
U
Understreget
"
Citat
Liste
Punktliste eller nummereret liste
Tilføj ny frase, dvs. foruddefinerede standardtekster.
Klik på **\** når du er færdig, eller **X** for at lukke uden at gemme.
---
# 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-egcliniccare.eghealthcare.dk/moduler-og-funktioner/dokumentation/opret-nyt-notat.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.
