> For the complete documentation index, see [llms.txt](https://help.paxton.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paxton.ai/help/matter-record/medical-chronologies.md).

# Medical Chronologies

Build a complete timeline of visits, diagnoses, and procedures from medical records, with every event cited.

A Medical Chronology is a structured summary of a patient's medical history, built from the source records. Every visit, diagnosis, and procedure is cited to the document it came from.

### Build a medical chronology

1. Open the matter. In the left sidebar under **Matter Records**, click **Build a new record**.
2. Choose **Medical Records → Medical Chronology** and click **Continue**.
3. Click **Add Files** and choose the medical records to include.
4. Start the build.

Files can be up to 1 GB each, and PDFs up to 10,000 pages each.

<figure><img src="https://1404317777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCY0Bz9NWp8rqtfuqg7ne%2Fuploads%2FKqgCYwhniVROkYCL3r0F%2Fbuild-medical-chronology.png?alt=media&amp;token=be261ab7-0e1c-4692-b8fc-ca78873dd5c7" alt=""><figcaption></figcaption></figure>

**Good to know**

* Each matter can have one Medical Chronology.
* Only the matter owner and editors can build one.

{% hint style="warning" %}
For complete coverage, use Medical Chronology rather than asking about medical records in a chat. A chat may return a shorter or partial summary.
{% endhint %}

### Review the chronology

Switch between views with the tabs at the top:

* **Overview**: the status of each document and how many events were extracted.
* **All Events**: a chronological list of every event, with date of service, facility, summary, and source file. Use it to scan the treatment timeline and check the order of events.
* **Detailed View**: each event with provider, diagnoses, ICD-10 codes, tests and imaging, procedures, medications, and source file. Use it for medical-legal analysis, demand letters, and spotting gaps in care.

You can download the chronology as an Excel file to share or review.

### Why do some documents show "No events extracted"?

Not every document has treatment events. Administrative, billing, and other non-clinical records are included for completeness but may not produce entries.

### Tips

* **Pair it with a Medical Billing Summary** to show what treatment happened, when, and what it cost. See [Billing Summaries](https://help.paxton.ai/help/matter-record/billing-summaries).
* **Use it in a chat.** Ask Paxton to draft a demand letter, deposition outline, or case summary from the chronology and billing summary.

### Related articles

* [Billing Summaries](https://help.paxton.ai/help/matter-record/billing-summaries)
* [Matter Timeline](https://help.paxton.ai/help/matter-record/matter-timeline)


---

# 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://help.paxton.ai/help/matter-record/medical-chronologies.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.
