> 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/humana-price-transparency.md).

# Humana

### Payerset Notes

We are currently investigating why recent files of Humana seem to be missing.

Humana has some of the most voluminous data, and we believe they will soon be forced to change their practices, but for now we parse out nearly 12 million files to get to trillions of rows of data. In order to combat this, there is a single table that contains all of the joined data rather than the providers and rates being separate.

{% hint style="warning" %}
Humana is not provided as part of the standard Data Lake or Rate Explorer solutions, as the parsing process to acquire this data is much more in-depth.
{% endhint %}

### Schema: HUMANA

#### **Data Validation**

| Record Type                   | Record Count |
| ----------------------------- | ------------ |
| Providers                     | 0            |
| Rates                         | 0            |
| Bundled Codes                 | 0            |
| Covered Services (Capitation) | 0            |

*Data was not available for May 2026.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payerset.com/payers/humana-price-transparency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.