> 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/bcbs-north-dakota-price-transparency.md).

# Blue Cross Blue Shield North Dakota

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

### Payerset Notes

**Table of Contents**

<https://mrf.payerset.com/bcbs-north-dakota>

### Compliance Scorecard

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

<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>5/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: BCBS\_NORTH\_DAKOTA

#### **Data Validation**

| Record Type                   | Record Count |
| ----------------------------- | ------------ |
| Providers                     | 1,375,076    |
| Rates                         | 985,971,058  |
| Nonstandard Codes             | 35,032,828   |
| Bundled Codes                 | 0            |
| Covered Services (Capitation) | 0            |

*Updated for August 2026.*

**August 2026 Status:** Files for the August 2026 cycle were acquired and loaded. The plan list loaded for this cycle was later found to be Highmark Blue Cross Blue Shield Pennsylvania's rather than the payer's own, so the counts may not include all of the payer's files. The in-network files loaded are dated May 6, 2026 to July 20, 2026.

#### **Cycle History**

| Cycle         | Status | Rates         |
| ------------- | ------ | ------------- |
| February 2026 | Loaded | 1,956,697,127 |
| May 2026      | Loaded | 2,138,083,299 |
| August 2026   | Loaded | 985,971,058   |

*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.
* **Table of Contents Accessibility:** ✔️ The Table of Contents link is easily accessible.
* **Table of Contents Formatting:** ✔️ Yes, the Table of Contents is properly formatted.
* **File Download Barriers:** ✔️ No barriers to downloading the MRFs.
* **File Accessibility Percentage:** ✔️ 100% of the files are accessible.

**Overall Assessment:** BCBS North Dakota generally does a great job of posting these files each month. They duplicate provider data substantially, but that can be a result of interpretation of the CMS rules.

**As of May 2024 this has still not been resolved:**

There are some issues with one of their Dental files that we weren't able to manually fix, but we did not ding them a star for it. See the full JSON error below:

#### Error Explanation - 1 file is corrupted, specifically the Dental In Network Rates file

An error was encountered while processing a file with ID `907002cf-7876-4b2f-95b2-da2b606393e1`. The error indicates a JSON parsing issue, specifically an "unallowed token" error at a certain point in the JSON text.

**Error Details**

* **File ID**: `907002cf-7876-4b2f-95b2-da2b606393e1`
* **Error**: Parse error
* **Issue**: Unallowed token in JSON
* **Location**: Just after a list of numbers before `], "tin": { "type": "ein", "val`

**Possible Cause**

The token causing the error is likely due to a trailing comma after the last item in the array (right before the closing square bracket `]`). JSON does not allow trailing commas in arrays or objects.

**Corrected JSON Excerpt**

```json
...1891139473,1932830130], "tin": { "type": "ein", "value"...
```


---

# 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/bcbs-north-dakota-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.