> 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/bi/sortering-af-kolonner.md).
# Sortering af kolonner
## Ændre sortering af kolonnerne
Hver dataanalyse består af en række filtrerbare lister, opdelt i forskellige kolonner, f.eks. CPR-nr., navn, alder, ATC-koder, ydelseskoder osv. Listerne har alle en standardsortering, når du åbner dataanalysen.
*Eksempel:* I dataanalysen "**Polyfarmaci**" er listen over patienter i venstre side som standard sorteret på kolonnen "*Antal ordinationer*" i faldende orden. Det ses ved, at pilen i kolonnen "*Antal ordinationer*" peger nedad.
### Skift sortering
Denne sortering kan ændres, hvis det ønskes.
1. Vil du f.eks. sortere på patientnavn i stedet, placér musemarkøren over kolonnen "*Patient*". En pil vises nu.
2. **Klik på pilen** for at sortere listen efter denne kolonne, i den orden pilen angiver (**pil op** = stigende orden, **pil ned** = faldende orden).
3. Vil du sortere i den anden orden, **klik på pilen igen**.
### Sekundær sortering
Du kan også tilføje en eller flere sekundære sorteringer, hvis det er nødvendigt:
* Hold Ctrl nede, mens du sætter en eller flere sorteringspile i én eller flere yderligere kolonner, som beskrevet ovenfor.
* Sekundære sorteringer vises med små prikker til højre for sorteringspilen.
* Dataanalysen bruger den sekundære sortering, når der er lighed mellem to eller flere resultater i den primære sortering.
---
# 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/bi/sortering-af-kolonner.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.