> 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/systemmanager/systemmanager_laboratorietal/laboratorietal_inr.md). # INR INR indikationer og prøvekoder til INR håndteres fra **Systemmanager** → **Laboratorietal** → **INR**. ### Indikation * Opret en ny indikation med Ins eller klik på knappen **Ny**. * Ret en indikation ved at markere og vælge F2. Alternativt klik på knappen **Ret**. Indikationen kan sættes til aktiv eller inaktiv. Klik på knappen **Vis alle** eller brug Alt+A for at få vist alle indikationer, inklusive de indikationer, der ikke har markering i *Aktiv*. ![](https://3548167157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfDHx4SrlSNAKGCJ3m7yH%2Fuploads%2Fgit-blob-2a4491689ce7119cac3cfae9c3d984dcb4114ace%2Fhmfile_hash_79e5ebc5.png?alt=media) ### Prøvekoder * **Tilføj** en ny prøvekode med Ins eller klik på knappen **Ny**. * **Fjern** en prøvekode med Del eller klik på knappen **Slet**. Ved valg af ny prøvekode, åbnes skærmbilledet til at fremfinde prøvekoder. Det er muligt at søge i øverste felt ved at skrive eksempelvis INR. Vælg en prøvekode ved at markere prøvekoden og dobbeltklikke. Alternativt klik på **OK**. --- # 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/systemmanager/systemmanager_laboratorietal/laboratorietal_inr.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.