> 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/cms-prior-auth-compliance-dataset/schema-reference.md).

# Schema Reference

Full table-by-table reference for the CMS Prior Authorization Compliance Intelligence Dataset. All tables are exposed through the `DWV` schema on Snowflake. Column-level descriptions for every table are also available in the `DATA_DICTIONARY` table.

{% hint style="warning" %}
Informational reference compiled from public Federal Register, eCFR, and CMS sources. Not legal advice; consult counsel for compliance decisions.
{% endhint %}

## Universal column blocks

Every **curated reference table** (the nine tables in the first group below) carries three standard column blocks in addition to its own columns. They are documented once here and referenced by each table.

### Provenance block: every curated row traces to a source

| Column                 | Type           | Description                                                                                  |
| ---------------------- | -------------- | -------------------------------------------------------------------------------------------- |
| source\_doc\_id        | VARCHAR        | FK to `RULE_DOCUMENTS`; the document that asserts this row                                   |
| fr\_citation           | VARCHAR        | Federal Register citation, e.g. `89 FR 8758`                                                 |
| cfr\_citation          | VARCHAR        | CFR citation, e.g. `42 CFR 422.122` (NULL where genuinely not applicable)                    |
| source\_pinpoint       | VARCHAR        | Federal Register full-text section reference, e.g. `II.B.2.a`; a URL alone is not a pinpoint |
| source\_url            | VARCHAR        | Deep link to the source                                                                      |
| verbatim\_excerpt      | VARCHAR(300)   | Verbatim rule-text quote (public domain, 17 USC 105)                                         |
| source\_document\_date | DATE           | Publication date of the source                                                               |
| retrieved\_at          | TIMESTAMP\_NTZ | When the source was pulled                                                                   |

### Interpretation block: how strong is the assertion

| Column                     | Type    | Description                                                                                                             |
| -------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------- |
| assertion\_type            | VARCHAR | `FACT` \| `INTERPRETATION` \| `DERIVED`                                                                                 |
| interpretation\_confidence | VARCHAR | `HIGH` \| `MEDIUM` \| `LOW`                                                                                             |
| interpretation\_notes      | VARCHAR | Why we read it this way (NULL when a plain FACT)                                                                        |
| needs\_verification        | BOOLEAN | `TRUE` quarantines the row; it is excluded from `COMPLIANCE_GOLD` and all derived views                                 |
| reviewed\_by               | VARCHAR | Editorial sign-off identity (`Dataplex Editorial`); every production row is individually human-reviewed before it ships |
| review\_date               | DATE    | Review date                                                                                                             |

### Lifecycle block: append-only versioning

| Column                  | Type           | Description                                                           |
| ----------------------- | -------------- | --------------------------------------------------------------------- |
| row\_version            | INT            | Monotonic version per natural key                                     |
| row\_status             | VARCHAR        | `ACTIVE` \| `SUPERSEDED` \| `PENDING_FINALIZATION`                    |
| is\_current             | BOOLEAN        | Exactly one `TRUE` per natural key                                    |
| superseded\_by\_row\_id | VARCHAR        | Forward pointer to the superseding row                                |
| superseding\_doc\_id    | VARCHAR        | FK to `RULE_DOCUMENTS`; the document that caused supersession         |
| curation\_valid\_from   | TIMESTAMP\_NTZ | Curation-time validity start (named distinctly from compliance dates) |
| curation\_valid\_to     | TIMESTAMP\_NTZ | Curation-time validity end (NULL while current)                       |

### Dataset provenance variant (payer tables)

The three payer tables (`PAYER_DIRECTORY`, `PAYER_METRIC_SOURCES`, `PAYER_METRICS`) are web/dataset-derived facts, not rule text, so they carry a **dataset provenance block** in place of the Federal Register one; the interpretation and lifecycle blocks above are identical. The rule-text provenance columns (`fr_citation`, `cfr_citation`, `source_document_date`) do not apply. `PAYER_METRICS` still carries `source_pinpoint` and `verbatim_excerpt` as value-evidence columns on the table itself.

| Column          | Type           | Description                                                                                |
| --------------- | -------------- | ------------------------------------------------------------------------------------------ |
| source\_dataset | VARCHAR        | The dataset the row was derived from (e.g. a CMS enrollment file, the payer's own website) |
| source\_url     | VARCHAR        | Deep link to the source                                                                    |
| retrieved\_at   | TIMESTAMP\_NTZ | When the source was pulled                                                                 |

The lifecycle block is the same, except `superseding_doc_id` is a plain nullable column (a payer refresh is a data update, not a rule document).

***

## Curated reference tables

### RULE\_DOCUMENTS

**Grain:** one Federal Register document. **PK:** `document_id`.

| Column                      | Type    | Description                                                                                               |
| --------------------------- | ------- | --------------------------------------------------------------------------------------------------------- |
| document\_id                | VARCHAR | Human-readable slug: `CMS-0057-F`, `CMS-0062-P`, `CMS-0053-F`, `IPPS-FY2026`                              |
| fr\_doc\_number             | VARCHAR | Federal Register document number, e.g. `2024-00895`                                                       |
| citation                    | VARCHAR | e.g. `89 FR 8758`                                                                                         |
| rin                         | VARCHAR | Regulatory Identifier Number                                                                              |
| regulations\_gov\_docket    | VARCHAR | Docket to poll for finalization, e.g. `CMS-2026-1255` on CMS-0062-P                                       |
| document\_type              | VARCHAR | `RULE` \| `PRORULE`                                                                                       |
| publication\_date           | DATE    | Federal Register publication date                                                                         |
| effective\_date             | DATE    | Rule effective date (NULL for proposed rules)                                                             |
| comment\_close\_date        | DATE    | Comment period close (proposed rules)                                                                     |
| comment\_count              | INT     | Number of comments received                                                                               |
| document\_status            | VARCHAR | `PROPOSED` \| `FINAL` \| `FINALIZED_AS_OTHER` \| `WITHDRAWN` \| `SUPERSEDED`                              |
| finalized\_as\_document\_id | VARCHAR | FK to `RULE_DOCUMENTS`; set when a proposed rule is finalized (the live watch column; NULL on CMS-0062-P) |
| pa\_relevance               | VARCHAR | `CORE` \| `ADJACENT`                                                                                      |
| cfr\_parts                  | VARCHAR | Affected CFR parts                                                                                        |
| full\_text\_xml\_url        | VARCHAR | Federal Register full-text XML URL                                                                        |
| fact\_sheet\_url            | VARCHAR | CMS fact-sheet URL                                                                                        |
| pdf\_url                    | VARCHAR | Rule PDF URL                                                                                              |
| *+ universal blocks*        |         | Provenance, interpretation, lifecycle                                                                     |

### RULE\_OBLIGATIONS

**Grain:** one obligation per document. **PK:** `obligation_id`.

| Column                              | Type    | Description                                                                              |
| ----------------------------------- | ------- | ---------------------------------------------------------------------------------------- |
| obligation\_id                      | VARCHAR | Stable slug, e.g. `CMS-0057-F:PA-DECISION-TIMEFRAMES`                                    |
| document\_id                        | VARCHAR | FK to `RULE_DOCUMENTS`                                                                   |
| obligation\_category                | VARCHAR | `API` \| `OPERATIONAL` \| `REPORTING` \| `DENIAL_NOTICE` \| `DOCUMENTATION` \| `MEASURE` |
| obligation\_name                    | VARCHAR | Human-readable obligation name                                                           |
| requirement\_text\_verbatim         | VARCHAR | Verbatim requirement text from the rule                                                  |
| requirement\_summary                | VARCHAR | Plain-language summary                                                                   |
| is\_pa\_scope                       | BOOLEAN | `FALSE` on every CMS-0053-F adjacency row                                                |
| applies\_regardless\_of\_api\_build | BOOLEAN | `TRUE` for the three January-1-2026 operational obligations                              |
| related\_obligation\_id             | VARCHAR | FK to `RULE_OBLIGATIONS`; links related obligations across documents                     |
| binding\_status                     | VARCHAR | `FINAL_BINDING` \| `PROPOSED_NOT_BINDING` (every CMS-0062-P row the latter)              |
| audit\_relevance                    | VARCHAR | Why this obligation matters for an audit                                                 |
| penalty\_enforcement\_notes         | VARCHAR | Enforcement / penalty context                                                            |
| *+ universal blocks*                |         |                                                                                          |

### ENTITY\_TYPES

**Grain:** one entity/program type, **including explicit out-of-scope rows**. **PK:** `entity_type_id`.

| Column                   | Type    | Description                                                                                                              |
| ------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------ |
| entity\_type\_id         | VARCHAR | e.g. `MA_ORG`, `MEDICAID_FFS`, `QHP_FFE`, `MIPS_CLINICIAN`, `HIPAA_COVERED_ENTITY`                                       |
| entity\_type\_name       | VARCHAR | Full program name                                                                                                        |
| in\_scope                | BOOLEAN | `FALSE` for explicit out-of-scope rows (`MEDICARE_FFS`, `PART_D`, `QHP_SBE`, `STANDALONE_DENTAL`, `COMMERCIAL_ERISA`)    |
| scope\_basis             | VARCHAR | Verbatim citation for inclusion or exclusion                                                                             |
| date\_semantics\_default | VARCHAR | `LITERAL` \| `RATING_PERIOD_ON_OR_AFTER` \| `PLAN_YEAR_ON_OR_AFTER` \| `PERFORMANCE_PERIOD` (NULL for out-of-scope rows) |
| approx\_entity\_count    | INT     | Approximate population (from research, not rule text)                                                                    |
| program\_notes           | VARCHAR | Program-specific notes                                                                                                   |
| *+ universal blocks*     |         |                                                                                                                          |

### OBLIGATION\_APPLICABILITY

**Grain:** (obligation × entity type × version); the central fact, append-only SCD2. **Natural key:** `(obligation_id, entity_type_id)`; `unique_key` is the list `['obligation_id','entity_type_id','row_version']`.

| Column                      | Type    | Description                                                                                                                    |
| --------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------ |
| obligation\_id              | VARCHAR | FK to `RULE_OBLIGATIONS`                                                                                                       |
| entity\_type\_id            | VARCHAR | FK to `ENTITY_TYPES`                                                                                                           |
| applicability               | VARCHAR | `REQUIRED` \| `EXEMPT` \| `OPTIONAL` \| `EXTENSION_AVAILABLE` \| `NOT_APPLICABLE`; exemptions are explicit rows                |
| compliance\_date\_anchor    | DATE    | Verbatim on-or-after anchor. Never a resolved per-payer due date; never fabricated (a dateless row ships quarantined)          |
| compliance\_date\_type      | VARCHAR | `LITERAL_DATE` \| `RATING_PERIOD_ON_OR_AFTER` \| `PLAN_YEAR_ON_OR_AFTER` \| `PERFORMANCE_PERIOD` \| `RELATIVE_TO_FINALIZATION` |
| compliance\_date\_display   | VARCHAR | Human phrasing of the anchor                                                                                                   |
| date\_certainty             | VARCHAR | `FINAL` \| `PROPOSED`                                                                                                          |
| first\_deliverable\_due     | DATE    | Actual literal deadline where the rule states one, e.g. `2026-03-31`                                                           |
| recurrence                  | VARCHAR | e.g. `ANNUAL`                                                                                                                  |
| timeframe\_detail           | VARCHAR | e.g. `72h expedited / 7 calendar days standard`                                                                                |
| extension\_exemption\_notes | VARCHAR | Extension paths and exemption bases                                                                                            |
| *+ universal blocks*        |         |                                                                                                                                |

### STANDARDS\_REGISTRY

**Grain:** one standard or implementation-guide **version**. **PK:** `standard_id`.

| Column                | Type    | Description                                                             |
| --------------------- | ------- | ----------------------------------------------------------------------- |
| standard\_id          | VARCHAR | e.g. `hl7.fhir.us.davinci-pas#2.2.1`, `X12N-275-006020X314`             |
| standard\_family      | VARCHAR | `HL7_FHIR_IG` \| `X12` \| `NCPDP` \| `HL7_CDA`                          |
| standard\_name        | VARCHAR | Standard / implementation-guide name                                    |
| version               | VARCHAR | Version identifier                                                      |
| canonical\_url        | VARCHAR | Canonical URL (facts only)                                              |
| npm\_package          | VARCHAR | HL7 NPM package identifier where applicable                             |
| version\_status       | VARCHAR | `CURRENT` \| `EXPIRING` \| `EXPIRED`                                    |
| version\_expiry\_date | DATE    | e.g. STU-2 stack `2028-01-01` (proposed)                                |
| baseline\_note        | VARCHAR | Baseline-stack note (NULL for `PROPRIETARY_IDENTIFIER_ONLY` rows)       |
| license\_class        | VARCHAR | `PUBLIC_DOMAIN` \| `HL7_CC_FACTS_ONLY` \| `PROPRIETARY_IDENTIFIER_ONLY` |
| *+ universal blocks*  |         |                                                                         |

{% hint style="info" %}
**Licensing firewall.** Where `license_class = PROPRIETARY_IDENTIFIER_ONLY` (X12, NCPDP), all prose columns are NULL by construction; only the identifier, family, and version are shipped. The fact of a standard's adoption is public domain (it is in the Federal Register); the proprietary specification text is never redistributed.
{% endhint %}

### OBLIGATION\_STANDARDS

**Grain:** (obligation × standard) bridge. **Natural key:** `(obligation_id, standard_id)`.

| Column               | Type    | Description                                         |
| -------------------- | ------- | --------------------------------------------------- |
| obligation\_id       | VARCHAR | FK to `RULE_OBLIGATIONS`                            |
| standard\_id         | VARCHAR | FK to `STANDARDS_REGISTRY`                          |
| binding\_strength    | VARCHAR | `REQUIRED` \| `NAMED` \| `ENCOURAGED` \| `PROPOSED` |
| *+ universal blocks* |         |                                                     |

### REPORTING\_REQUIREMENTS

**Grain:** one reporting obligation and required content element. **PK:** `reporting_requirement_id`.

| Column                     | Type    | Description                                      |
| -------------------------- | ------- | ------------------------------------------------ |
| reporting\_requirement\_id | VARCHAR | e.g. `CMS-0057-F:RPT-WEB-02`                     |
| obligation\_id             | VARCHAR | FK to `RULE_OBLIGATIONS`                         |
| destination                | VARCHAR | `PAYER_WEBSITE` \| `CMS`                         |
| cadence                    | VARCHAR | e.g. `ANNUAL`                                    |
| due\_rule                  | VARCHAR | e.g. `March 31 for prior CY`                     |
| first\_due\_date           | DATE    | e.g. `2026-03-31` (verified for website metrics) |
| content\_element           | VARCHAR | The required metric / content element            |
| metric\_id                 | VARCHAR | FK to `METRIC_DEFINITIONS`                       |
| *+ universal blocks*       |         |                                                  |

### DENIAL\_NOTICE\_ELEMENTS

**Grain:** one required denial-notice element. **PK:** `element_id`. (Element-grain by design, not a denial-reason code taxonomy.)

| Column                         | Type    | Description                                                                        |
| ------------------------------ | ------- | ---------------------------------------------------------------------------------- |
| element\_id                    | VARCHAR | e.g. `CMS-0057-F:DNE-01-PROVIDER-SPECIFIC-REASON`                                  |
| obligation\_id                 | VARCHAR | FK to `RULE_OBLIGATIONS`                                                           |
| element\_name                  | VARCHAR | Element name                                                                       |
| element\_description\_verbatim | VARCHAR | Verbatim rule-text description                                                     |
| channel\_scope                 | VARCHAR | e.g. `ANY_CHANNEL`, `PRIOR_AUTH_API`, `ENROLLEE_WRITTEN_NOTICE`, `PROVIDER_NOTICE` |
| *+ universal blocks*           |         |                                                                                    |

### METRIC\_DEFINITIONS

**Grain:** one operational metric. **PK:** `metric_id`. The stable FK spine for PA-metric definitions and benchmarking.

| Column                 | Type    | Description                                             |
| ---------------------- | ------- | ------------------------------------------------------- |
| metric\_id             | VARCHAR | e.g. `PA_APPROVAL_RATE_STD`, `API_USAGE_PATIENT_ACCESS` |
| metric\_name           | VARCHAR | Operational metric name                                 |
| numerator\_text        | VARCHAR | Numerator definition                                    |
| denominator\_text      | VARCHAR | Denominator definition                                  |
| breakdown\_dimensions  | VARCHAR | Reporting breakdowns                                    |
| source\_obligation\_id | VARCHAR | FK to `RULE_OBLIGATIONS`                                |
| benchmarkable          | BOOLEAN | `TRUE` for payer-comparable rate metrics                |
| *+ universal blocks*   |         |                                                         |

### PAYER\_DIRECTORY

**Grain:** one payer parent organization. **PK:** `payer_id`. **Ungated.** Uses the dataset provenance variant.

| Column                                                             | Type       | Description                                                                     |
| ------------------------------------------------------------------ | ---------- | ------------------------------------------------------------------------------- |
| payer\_id                                                          | VARCHAR    | Kebab-case slug PK, e.g. `unitedhealth-group`                                   |
| payer\_name                                                        | VARCHAR    | Payer parent organization name                                                  |
| payer\_kind                                                        | VARCHAR    | `MA_PARENT_ORG` \| `MEDICAID_MCO_PARENT` \| `STATE_MEDICAID_AGENCY`             |
| entity\_type\_ids                                                  | VARCHAR    | Comma-separated FKs into `ENTITY_TYPES`; every token resolves to an entity type |
| state                                                              | VARCHAR(2) | Two-letter state (state Medicaid agencies; NULL for multi-state parents)        |
| states\_operating                                                  | VARCHAR    | Comma-separated operating states (non-FK)                                       |
| approx\_enrollment                                                 | INT        | Approximate enrollment                                                          |
| enrollment\_as\_of                                                 | VARCHAR    | Enrollment period text, e.g. `2026-01`                                          |
| cms\_contract\_ids                                                 | VARCHAR    | Comma-separated CMS contract IDs (Medicare Advantage only)                      |
| *+ dataset provenance variant + interpretation + lifecycle blocks* |            |                                                                                 |

### PAYER\_METRIC\_SOURCES

**Grain:** one posting location per payer. **PK:** `source_id`. **Gated** (a small payer cohort is trial-visible). Uses the dataset provenance variant. **Contains no metric values**: it is the registry of where each payer posts its CMS-required PA metrics, not the metrics themselves.

| Column                                                             | Type    | Description                                                                                   |
| ------------------------------------------------------------------ | ------- | --------------------------------------------------------------------------------------------- |
| source\_id                                                         | VARCHAR | Posting-location id                                                                           |
| payer\_id                                                          | VARCHAR | FK to `PAYER_DIRECTORY`                                                                       |
| posting\_url                                                       | VARCHAR | URL where the payer posts its public PA metrics (NULL when not located)                       |
| posting\_format                                                    | VARCHAR | `HTML` \| `PDF` \| `DASHBOARD` \| `OTHER` \| `NOT_FOUND`                                      |
| covers\_lobs                                                       | VARCHAR | Comma-separated lines of business the posting covers (non-FK)                                 |
| cy\_covered                                                        | VARCHAR | Calendar year covered, e.g. `CY2025`                                                          |
| found                                                              | BOOLEAN | `TRUE` when a posting location was located and verified; `FALSE` recorded explicitly when not |
| first\_verified\_at                                                | DATE    | First verification date                                                                       |
| last\_verified\_at                                                 | DATE    | Most recent verification date                                                                 |
| verification\_method                                               | VARCHAR | How the location was confirmed (e.g. dual-verified)                                           |
| search\_notes                                                      | VARCHAR | Notes on the search / verification                                                            |
| *+ dataset provenance variant + interpretation + lifecycle blocks* |         |                                                                                               |

### PAYER\_METRICS

**Grain:** one posted metric value per (payer × metric × line of business × period). **PK:** (`payer_id`, `metric_id`, `lob`, `period`). **Gated** (a small payer cohort is trial-visible). Uses the dataset provenance variant. The values table: what each covered payer actually posted under its CMS public-reporting obligation, keyed to `METRIC_DEFINITIONS` so the same metric is comparable across payers. **Only human-reviewed values appear**: a value that hasn't been individually reviewed never reaches this view, and every promotion is recorded as a `VERIFIED` entry in `RULE_AUDIT_LOG`.

| Column                                                             | Type    | Description                                                                                |
| ------------------------------------------------------------------ | ------- | ------------------------------------------------------------------------------------------ |
| payer\_id                                                          | VARCHAR | FK to `PAYER_DIRECTORY`                                                                    |
| source\_id                                                         | VARCHAR | FK to `PAYER_METRIC_SOURCES`; the posting this value was read from                         |
| metric\_id                                                         | VARCHAR | FK to `METRIC_DEFINITIONS`; identifies which operational PA metric this is                 |
| lob                                                                | VARCHAR | Line of business / contract as the payer scoped it (e.g. `Medicaid`, `Medicare Advantage`) |
| period                                                             | VARCHAR | Reporting period as posted (e.g. `CY2025`)                                                 |
| value\_text                                                        | VARCHAR | The value exactly as printed in the posting                                                |
| value\_numeric                                                     | FLOAT   | Numeric form when the value is a single number; NULL for list/compound values              |
| unit                                                               | VARCHAR | `percent` \| `hours` \| `days` \| `count` \| `other`                                       |
| snapshot\_sha256                                                   | VARCHAR | SHA-256 of the archived snapshot of the posting the value was read from                    |
| source\_pinpoint                                                   | VARCHAR | Page / heading in the posting where the value appears                                      |
| verbatim\_excerpt                                                  | VARCHAR | The exact quote from the posting that contains the value                                   |
| harvest\_run\_id                                                   | VARCHAR | Provenance: which extraction run produced the row                                          |
| prompt\_version                                                    | VARCHAR | Provenance: extraction prompt version                                                      |
| extraction\_method                                                 | VARCHAR | How the value was extracted (e.g. dual-pass, reconciled)                                   |
| quarantine\_reason                                                 | VARCHAR | NULL on every visible row (a quarantined value never reaches this view)                    |
| quarantine\_note                                                   | VARCHAR | NULL on every visible row                                                                  |
| *+ dataset provenance variant + interpretation + lifecycle blocks* |         |                                                                                            |

***

## Derived analytics tables

### COMPLIANCE\_GOLD

**Grain:** (entity type × obligation), `is_current` rows only. Derived: excludes every `needs_verification = TRUE` row; surfaces (never hides) the certainty and confidence flags.

| Column                     | Type    | Description                                  |
| -------------------------- | ------- | -------------------------------------------- |
| entity\_type\_id           | VARCHAR | The entity type                              |
| obligation\_id             | VARCHAR | The obligation                               |
| obligation\_category       | VARCHAR | Obligation category                          |
| applicability              | VARCHAR | `REQUIRED` \| `EXEMPT` \| ...                |
| compliance\_date\_anchor   | DATE    | Resolved anchor for this entity + obligation |
| compliance\_date\_display  | VARCHAR | Human phrasing                               |
| date\_certainty            | VARCHAR | `FINAL` \| `PROPOSED`                        |
| binding\_status            | VARCHAR | `FINAL_BINDING` \| `PROPOSED_NOT_BINDING`    |
| interpretation\_confidence | VARCHAR | `HIGH` \| `MEDIUM` \| `LOW`                  |

*Additional joined context (standards summary, reporting summary, timeframe detail) is projected through from the underlying facts; see the `DATA_DICTIONARY` for the full column list.*

### COMPLIANCE\_DEADLINES

**Grain:** one deadline. A pure UNION projection over applicability anchors, recurring reports, document milestones, and implementation-guide expiries. A deadline can never contradict its source fact by construction.

| Column                    | Type    | Description                                                                            |
| ------------------------- | ------- | -------------------------------------------------------------------------------------- |
| deadline\_type            | VARCHAR | `COMPLIANCE` \| `FIRST_REPORT` \| `RECURRING_ANNUAL` \| `COMMENT_CLOSE` \| `IG_EXPIRY` |
| entity\_type\_id          | VARCHAR | Entity context (where applicable)                                                      |
| obligation\_id            | VARCHAR | Obligation context (where applicable)                                                  |
| compliance\_date\_anchor  | DATE    | The anchor date                                                                        |
| compliance\_date\_type    | VARCHAR | Date-semantics type                                                                    |
| compliance\_date\_display | VARCHAR | Human phrasing                                                                         |
| date\_certainty           | VARCHAR | `FINAL` \| `PROPOSED`                                                                  |

### RULE\_AUDIT\_LOG

**Grain:** one field-level editorial change. Customer-visible (trial-visible with value masking). Materialized from explicit changelog entries in the curation store, never from git-history parsing.

| Column                   | Type           | Description                                                                |
| ------------------------ | -------------- | -------------------------------------------------------------------------- |
| audit\_id                | VARCHAR        | Change id                                                                  |
| table\_name              | VARCHAR        | Table changed                                                              |
| row\_pk                  | VARCHAR        | Natural key of the changed row                                             |
| change\_type             | VARCHAR        | `CREATED` \| `SUPERSEDED` \| `STATUS_CHANGE` \| `CORRECTION` \| `VERIFIED` |
| field\_changed           | VARCHAR        | Column changed                                                             |
| old\_value               | VARCHAR        | Prior value (masked to `[full access]` for gated rows on the trial)        |
| new\_value               | VARCHAR        | New value (masked to `[full access]` for gated rows on the trial)          |
| change\_reason           | VARCHAR        | Customer-facing reason for the change (always visible)                     |
| triggering\_document\_id | VARCHAR        | Document that caused the change                                            |
| changed\_by              | VARCHAR        | Editorial identity that made the change (`Dataplex Editorial`)             |
| commit\_hash             | VARCHAR        | Commit that introduced the change                                          |
| pr\_number               | VARCHAR        | Pull request number                                                        |
| changed\_at              | TIMESTAMP\_NTZ | When the change was made                                                   |

{% hint style="info" %}
On the free trial, the change **events** (table, field, change type, reason, timestamp, triggering document) are always visible; only the `old_value` / `new_value` **content** of gated rows is masked to `[full access]`. The event stream is the proof the reference is maintained.
{% endhint %}

### CURATION\_STATUS

The completeness & quarantine ledger, so "where is my row?" is a query, not a support ticket. One row per **currently quarantined** row (held back from `COMPLIANCE_GOLD` pending verification) and per row **verified in the last 180 days**. `row_pk` joins back to the named table; `table_rows_current` is the per-table denominator, so a per-table quarantine percentage is one `GROUP BY` away. Always fully visible (no trial filter), so an evaluator can see exactly what is and isn't in the compliance set.

**Grain:** one quarantined-or-recently-verified row. **PK:** (`table_name`, `row_pk`, `status`).

| Column                     | Type           | Description                                                                                                                                                       |
| -------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| table\_name                | VARCHAR        | The DWV share table this row belongs to (e.g. `OBLIGATION_APPLICABILITY`)                                                                                         |
| row\_pk                    | VARCHAR        | Natural key of the row within its table; composite keys are joined with `\|`                                                                                      |
| status                     | VARCHAR        | `QUARANTINED` (held back from `COMPLIANCE_GOLD` pending verification) or `VERIFIED` (independently confirmed, promoted within the last 180 days)                  |
| quarantine\_reason         | VARCHAR        | Why a quarantined row is held: `AWAITING_ADVERSARIAL_PASS`, `AWAITING_FINALIZATION`, `SOURCE_AMBIGUOUS`, or `PENDING_SOURCE_VERIFICATION`. NULL for verified rows |
| blocked\_on                | VARCHAR        | For an `AWAITING_FINALIZATION` quarantine, the document whose finalization would resolve it (e.g. `CMS-0062-P`); event-bound, not age-bound. NULL otherwise       |
| interpretation\_confidence | VARCHAR        | Confidence in the source reading for a quarantined row (`HIGH`, `MEDIUM`, `LOW`). NULL for verified rows                                                          |
| review\_date               | DATE           | When the quarantined row was last human-reviewed (the age clock). NULL for verified rows                                                                          |
| days\_in\_quarantine       | INT            | Days since `review_date`, computed live. NULL for verified rows; event-bound rows are reported but exempt from age alarms                                         |
| verified\_at               | TIMESTAMP\_NTZ | For a verified row, when it was promoted. NULL for quarantined rows                                                                                               |
| customer\_note             | VARCHAR        | Plain-language note: why a row is held, or what was confirmed on verification                                                                                     |
| table\_rows\_current       | INT            | Total current rows in `table_name`; the denominator for a per-table completeness percentage                                                                       |
| updated\_at                | TIMESTAMP\_NTZ | When dbt last rebuilt this view                                                                                                                                   |

***

## Semantic view: COMPLIANCE\_ANALYST

A **Snowflake semantic view** included in the share: the semantic model that powers natural-language querying with **Cortex Analyst** and structured querying with the SQL `SEMANTIC_VIEW()` construct. It is a lens over the tables above (its relationships mirror the entity-relationship diagram), not a separate copy of the data; the trial and liability gates on the underlying views apply unchanged.

**Logical tables** (SCD2 dimensions are pre-filtered to current rows):

| Logical table  | Over                           | Role                                         |
| -------------- | ------------------------------ | -------------------------------------------- |
| obligations    | `COMPLIANCE_GOLD`              | Fact: one row per (obligation × entity type) |
| entity\_types  | `ENTITY_TYPES` (current)       | Dimension: the regulated programs            |
| payer\_metrics | `PAYER_METRICS`                | Fact: posted PA metric values                |
| payers         | `PAYER_DIRECTORY` (current)    | Dimension: payer parent organizations        |
| metric\_defs   | `METRIC_DEFINITIONS` (current) | Dimension: which PA metric                   |

**Dimensions:** `entity_type_id`, `entity_type_name`, `obligation_id`, `obligation_category`, `applicability`, `compliance_date_anchor`, `date_certainty`, `binding_status`, `payer_name`, `payer_kind`, `metric_name`, `line_of_business`, `reporting_period`, `unit`, each with synonyms so Cortex Analyst understands "insurer", "deadline", "program", etc.

**Metrics:** `obligation_count`, `avg_metric_value`, `min_metric_value`, `max_metric_value`, `value_count`.

**Use it two ways:**

* **Cortex Analyst** (natural language): in Snowsight, AI & ML → Cortex Analyst → select `DWV.COMPLIANCE_ANALYST`, then ask questions in plain English.
* **SQL** via `SEMANTIC_VIEW()`; see the [cookbook examples](/data-catalog/cms-prior-auth-compliance-dataset/compliance-questions-cookbook.md#ask-the-whole-product-a-question-with-the-semantic-view).

***

## Metadata tables

### FEEDS

Dataset catalog. **`last_updated_at` is the greatest `RULE_AUDIT_LOG.changed_at` per table**: curation-driven and honest, never `CURRENT_TIMESTAMP()`.

**Key columns:** `id` (PK), `table_name`, `description`, `last_updated_at`, `total_rows_extracted`, `total_batches`.

### FEEDS\_FILES

Curation-release history: one row per published curation release (e.g. `R1.0.0`), with an `is_latest` flag on the newest release. Unlike Dataplex's file-based products, rows here represent curation releases, not source-file loads; `created_at` is the release date and moves only when a release ships.

**Key columns:** `id` (PK), `release_id` (e.g. `R1.3.0`), `release_date`, `title`, `description`, `is_latest`, `created_at`, `updated_at`.

### CHANGELOG

Change log for curation releases, schema changes, and corrections.

**Key columns:** `event_id` (PK), `event_date`, `event_type`, `table_name`, `description`.

### DATA\_DICTIONARY

Column-level descriptions for every table.

**Key columns:** `entry_id` (PK), `table_name`, `column_name`, `data_type`, `column_description`.

***

*Informational reference compiled from public Federal Register, eCFR, and CMS 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/cms-prior-auth-compliance-dataset/schema-reference.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.