> 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/data-lake/data-dictionary/payer-transparency-tic.md).

# Payer Transparency (TiC)

Data dictionary for the Payer Transparency in Coverage data for medical services. Below are the fields available for Data Lake customers.

There is an additional `PLAN_MAP` table that contains details about the Plans and Plan Types. This may or may not be included in your data output, depending on your license structure.

<table data-full-width="false"><thead><tr><th width="303.5">Field Name</th><th width="304">Description / Sample Values</th><th>Original Source</th><th data-hidden>Field Type</th></tr></thead><tbody><tr><td>ADDITIONAL_INFORMATION</td><td>Additional information relevant to rate</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>BILLING_CLASS</td><td>Institutional or Professional</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>BILLING_CODE</td><td>Billing code as-is in MRF</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>BILLING_CODE_MODIFIER</td><td>Modifiers for different rates (22-99, P1)</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>MRF_BILLING_CODE_NAME</td><td>Billing code name as-is in MRF</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>MRF_BILLING_CODE_TYPE</td><td>HCPCS, CPT, MS-DRG, etc</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>BILLING_CODE_TYPE_VERSION</td><td>Version of the billing code (2023, 2024)</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>EXPIRATION_DATE</td><td>Expiration date of the rate (12/31/2024)</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>NEGOTIATED_RATE</td><td>Negotiated Rate value</td><td>PAYER MRF</td><td>FLOAT</td></tr><tr><td>NEGOTIATED_TYPE</td><td>Fee schedule, negotiated, percentage, per diem</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>NEGOTIATION_ARRANGEMENT</td><td>Fee for service (ffs) or Bundle</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>NPI</td><td>Provider ID</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>SERVICE_CODES</td><td>Location of service (11, 21, 22, etc)</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>TIN_TYPE</td><td>EIN or NPI</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>TIN_VALUE</td><td>Value of associated EIN or NPI</td><td>PAYER MRF</td><td>VARCHAR</td></tr><tr><td>NPPES_CITY</td><td>City Name from NPPES</td><td>NPPES</td><td>VARCHAR</td></tr><tr><td>NPPES_STATE</td><td>State Name from NPPES</td><td>NPPES</td><td>VARCHAR</td></tr><tr><td>NPPES_ORGANIZATION_NAME</td><td>Organization Name from NPPES</td><td>NPPES</td><td>VARCHAR</td></tr><tr><td>NPPES_ORGFRIENDLYNAME</td><td>Org Name + DBA Name if present</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>NPPES_PRIMARY_TAXONOMY_CODE</td><td>Primary taxonomy derived using switches in NPPES file</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>NUCC_TAXONOMY_GROUPING</td><td>High-level taxonomy grouping (Allopathic, Hospitals, Hospital Units, etc)</td><td>NUCC</td><td>VARCHAR</td></tr><tr><td>NUCC_TAXONOMY_CLASSIFICATION</td><td>More granular taxonomy classification (Clinic/Center, Abmulance, Nursing Care, etc)</td><td>NUCC</td><td>VARCHAR</td></tr><tr><td>NUCC_TAXONOMY_SPECIALIZATION</td><td>Most granular taxonomy (Adult Mental Health, Oncology, Orthopedic Surgery, etc...)</td><td>NUCC</td><td>VARCHAR</td></tr><tr><td>PAYER</td><td>Payer column added for convenience</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>PAYERSET_BILLING_CODE_NAME</td><td>Payerset standardized name of 21k+ billing codes</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>PAYERSET_BILLING_CODE_CATEGORY</td><td>Payerset categorization of 21k+ billing codes</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>PAYERSET_BILLING_CODE_SUBCATEGORY</td><td>Payerset subcategorization of 21k+ billing codes</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>PAYERSET_BILLING_CODE_TYPE</td><td>Payerset categorization of billing code types</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr><tr><td>PLAN_ID</td><td>Payerset-created Plan ID that links back to original plan via PLAN_MAP table</td><td>ADDED BY PAYERSET</td><td>VARCHAR</td></tr></tbody></table>


---

# 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/data-lake/data-dictionary/payer-transparency-tic.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.