> 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/opfoelgning/lpr2.md).
# LPR
Fanebladet '*LPR*' viser status på forløbskontakters indberetning til [Landspatientregisteret](/journal/lpr.md).
## Funktioner
**Spring** direkte til patientens journal med fokus på den aktuelle forløbskontakt med Enter.
## Status og visning
Alle forløbskontakter med status 'Kladde', 'Under afsendelse', 'Faktureringsklar' og 'Fejlet' bliver vist i oversigten.
Forløbskontakter med status 'Sendt' kan blive vist ved at vælge **Vis alle**.
Med en indstilling er det muligt få overblik over, hvilke LPR-forløb, der er uafsluttede inden for et givent antal dage. Indstillingen er som standard sat til de seneste 30 dage.
* Sættes indstillingen til 0 dage, vil alle forløbskontakter, der er '*Under afsendelse*', '*Faktureringsklar*' eller '*Fejlet*', fremgå i Opfølgning.
* Sættes indstillingen til 1 dag eller mere, vises alle forløbskontakter som er uafsluttede inden for det valgte antal dage, uanset status. Dette skal være med til at sikre, at alle LPR-forløb bliver faktureret.
Antal dage tilpasses i *Indstillinger > Opfølgning > Uafsluttede LPR 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/opfoelgning/lpr2.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.