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

# VIVA Health

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

### Payerset Notes

**Table of Contents**

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

### Compliance Scorecard

Overall Rating: <mark style="color:$success;">**4/5**</mark> <mark style="color:$success;">**- Good**</mark>

<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:yellow;"><strong>4/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: VIVA

#### **Data Validation**

| Record Type                   | Record Count |
| ----------------------------- | ------------ |
| Providers                     | 14,025       |
| Rates                         | 15,546,645   |
| Nonstandard Codes             | 1,275        |
| Bundled Codes                 | 0            |
| Covered Services (Capitation) | 0            |

*Updated for August 2026.*

**August 2026 Status:** Files for the August 2026 cycle were acquired and loaded.

### Additional Observations

**Machine-Readable Price Transparency Files Review**

* **MRFs Up-to-Date:** ✔️ Yes, the MRFs have been updated for February 2026.
* **Table of Contents Accessibility:** ❌ There is no table of contents, one has to be made.
* **Table of Contents Formatting:** ❌ There is no table of contents, one has to be made.
* **File Download Barriers:** ✔️ No barriers to downloading the MRFs.
* **File Accessibility Percentage:** ✔️ 100% of the files are accessible.

**Overall Assessment:**

VIVA has changed the way they publish the data to eliminate the single very large file in favor of smaller files. However, gathering the individual tables of contents is now difficult, so procuring the entire dataset is a challenge. Getting a single plan is significantly easier, and they are now using schema 2.0, and the new website they created for the employer plans is quite nice!


---

# 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/viva-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.