> For the complete documentation index, see [llms.txt](https://docs.dataplex-consulting.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataplex-consulting.com/data-catalog/compliance-intelligence-by-dataplex.md).

# Compliance Intelligence by Dataplex

**Compliance Intelligence by Dataplex** is a family of analytics-ready datasets that turn fragmented federal healthcare regulation and CMS program data into provenance-first, queryable reference layers, so compliance, regulatory-affairs, diligence, and product teams can answer "what applies, to whom, by when" without building the pipeline or reading the PDFs themselves.

Every product in the family shares the same principles:

* **Traceability over assertion.** Values trace to their source (a Federal Register pinpoint and verbatim quote, or a specific CMS source file and batch), never an unattributed claim.
* **Published methodology.** Interpretations, flags, and derived values are labeled and documented; nothing is a black box.
* **Signal, not prediction.** No machine learning, no scoring that hides its formula, no name-based inference.
* **Maintained, not snapshotted.** A change audit trail records what changed and why, so a subscription buys an up-to-date reference, not a one-time export.
* **Analysis-ready on Snowflake**, with the standard Dataplex metadata catalog on every product.

## Products in the family

### [CMS Prior Authorization Compliance Intelligence](/data-catalog/cms-prior-auth-compliance-dataset.md)

A curated, provenance-traced reference layer over the CMS prior-authorization and interoperability rulemaking wave: CMS-0057-F (in effect), CMS-0062-P (proposed), and CMS-0053-F (adjacent). Which obligation applies to which entity type (Medicare Advantage, Medicaid and CHIP fee-for-service and managed care, QHP issuers on the FFEs, MIPS clinicians and hospitals), by exactly what date and under which date semantics, with the API, public-reporting, denial-notice, and documentation duties. Every row is traced to a Federal Register citation and verbatim quote, confidence-rated and human-reviewed.

### [CMS Nursing Home Compliance Intelligence](/data-catalog/cms-nh-compliance-dataset.md)

An analytics-ready intelligence layer over U.S. nursing home data from CMS: a CCN-spined facility master, monthly facility history, effective-dated PECOS ownership with private-equity and REIT flags, chain intelligence reconciled to CMS's own chain file, Payroll-Based Journal staffing compliance, conformed enforcement and deficiency history, and observed closure signals. Built for operator compliance monitoring, PE/REIT and lender diligence, and longitudinal research, with published, deterministic compliance flags and full batch lineage.

## Which one do I need?

* If you are a **payer, health plan, or a consultancy/law firm serving payers**, and you need to know which CMS prior-authorization obligations apply to your entity type and by when, start with **CMS Prior Authorization Compliance Intelligence**.
* If you are an **operator, investor, lender, or researcher** working with skilled nursing facilities, and you need ownership, staffing, and enforcement compliance intelligence, start with **CMS Nursing Home Compliance Intelligence**.

Both are available on the Snowflake Marketplace. [Contact our team](mailto:support@dataplex-consulting.com) for a walkthrough or a private offer.

***

*Informational reference compiled from public sources. Not legal advice; consult counsel for compliance decisions.*


---

# 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.dataplex-consulting.com/data-catalog/compliance-intelligence-by-dataplex.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.
