> For the complete documentation index, see [llms.txt](https://docs.payerset.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payerset.com/payers/optum-price-transparency.md).

# Optum

This data contains the price transparency machine-readable files provided by Optum that have been normalized into easy-to-use tables.

### Payerset Notes

**Table of Contents**

<https://mrf.payerset.com/optum>

### Compliance Scorecard

Overall Rating: <mark style="color:green;">**4/5**</mark>**&#x20;- Good**

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Table of Contents</strong></td><td><strong>★★★★★</strong></td><td><mark style="color:green;"><strong>5/5</strong></mark></td><td><ul><li>Are the MRFs kept up to date each month?</li><li>Is the Table of Contents link easily accessible?</li><li>Is the Table of Contents properly formatted?</li></ul></td><td></td></tr><tr><td><strong>File Accessibility</strong></td><td><strong>★★★★★</strong></td><td><mark style="color:green;"><strong>5/5</strong></mark></td><td><ul><li>Are there any barriers to downloading the files?</li><li>Do the Table of Contents links expire before publishing new links?</li></ul></td><td></td></tr><tr><td><strong>Data Quality</strong></td><td><strong>★★★★☆</strong></td><td><mark style="color:green;"><strong>4/5</strong></mark></td><td><ul><li><p>What percentage of the MRFs are properly formatted and parseable</p><ul><li>5 Stars - 100%</li><li>4 Stars - 80%...</li></ul></li></ul></td><td></td></tr></tbody></table>

### Schema: OPTUM

#### **Data Validation**

| Record Type                   | Record Count   |
| ----------------------------- | -------------- |
| Providers                     | 460,144,515    |
| Rates                         | 10,521,157,765 |
| Nonstandard Codes             | 0              |
| Bundled Codes                 | 0              |
| Covered Services (Capitation) | 0              |

*Counts are from the May 2026 cycle; data was not available for August 2026.*

**August 2026 Status:** Files for the August 2026 cycle were acquired, but no records were loaded for this cycle.

#### **Cycle History**

| Cycle         | Status        | Rates          |
| ------------- | ------------- | -------------- |
| February 2026 | Loaded        | 10,940,192,874 |
| May 2026      | Loaded        | 10,521,157,765 |
| August 2026   | Not available | —              |

*Rates as published each cycle. Provider counts are not compared across cycles because the counting method changed in August 2026.*

### Additional Observations

**Machine-Readable Price Transparency Files Review**

* **MRFs Up-to-Date:** ✔️ Yes, the MRFs are kept up to date each month, though each region appears to be updated separately and at different times.
* **Table of Contents Accessibility:** ✔️ The Table of Contents link is easily accessible.
* **Table of Contents Formatting:** ✔️ Table of Contents is properly formatted.
* **File Download Barriers:** ✔️ There are no barriers to downloading the files, though there are mostly zip files that contain thousands of other files, which makes processing a little challenging.
* **File Accessibility Percentage:** ✔️ 100% of the files are accessible and uncorrupted.

**Overall Assessment:** Optum publishes their files regularly and mostly very well, though there are many hundreds of files inside zip folders that are linked in the Table of Contents, which can present challenges for processing and managing the data.


---

# 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://docs.payerset.com/payers/optum-price-transparency.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.