> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# CL-04-EN-67: Jurisdiction-Aware Progress Note Requirements — Integration Document

> Feature ID: CL-04-EN-67 Core: CL Status: ✅ Complete Spec: CL-04-EN-67 Last Updated: 2026-04-09

# Jurisdiction-Aware Progress Note Requirements — Integration Document

**Feature ID:** CL-04-EN-67\
**Core:** CL\
**Status:** ✅ Complete\
**Spec:** [CL-04-EN-67](../../../specs/cl/specs/CL-04-EN-67-jurisdiction-aware-progress-note-requirements.md)\
**Last Updated:** 2026-04-09

***

## Summary

CL-04-EN-67 replaces hardcoded Arizona/AHCCCS values in the CL-04 note signing flow and EN-66 Policy 940 validation gate with profile-driven values from PF-96 jurisdiction profiles.

***

## Integration Pattern

* **Publisher Core:** PF (jurisdiction profile data ownership via PF-96)
* **Consumer Core:** CL (progress note requirements and validation)
* **Pattern:** Platform Layer dependency — CL reads PF-96 jurisdiction profile values via `useClinicalRules()` and `useComplianceRules()` hooks from `@/platform/jurisdiction`

No direct PM or other core imports are introduced.

***

## Data Contract (Read)

CL-04-EN-67 consumes the following from PF-96 resolved profiles:

| Field                             | Source        | Default (AZ)       | Purpose                                              |
| --------------------------------- | ------------- | ------------------ | ---------------------------------------------------- |
| `clinical.required_note_elements` | PF-96 profile | 12-element model   | Dynamic required elements for progress notes         |
| `clinical.attestation_text`       | PF-96 profile | AHCCCS attestation | Profile-driven attestation wording                   |
| `compliance.policy_citation`      | PF-96 profile | AHCCCS Policy 940  | Citation metadata for compliance UI                  |
| `compliance.mandatory_validation` | PF-96 profile | `true` (AHCCCS)    | Whether validation is mandatory for the jurisdiction |

Fallback behavior: If a field is absent, Arizona/AHCCCS defaults are used.

***

## Consumer Integration Points

| Consumer                         | What It Reads                         | How It Integrates                                      |
| -------------------------------- | ------------------------------------- | ------------------------------------------------------ |
| `useNoteRequirements()` hook     | All fields above                      | Combines `useClinicalRules()` + `useComplianceRules()` |
| `note-requirements-resolver.ts`  | Same                                  | Pure functions with AZ AHCCCS fallbacks                |
| `Policy940ValidationFeedback` UI | `attestation_text`, `policy_citation` | Profile-driven display text                            |

***

## Security and Tenant Isolation

* Profile reads scoped by `organization_id` (and `site_id` when supplied).
* No PHI in profile resolution requests.
* Existing CL-04 RLS policies and audit paths remain unchanged.

***

## Permissions

No new permission keys. EN-67 reuses existing EN-66 permissions:

* `cl.note_940_validation.override`
* `cl.compliance_settings.manage`

***

## Related Specs

* `specs/cl/specs/CL-04-EN-67-jurisdiction-aware-progress-note-requirements.md`
* `specs/cl/specs/CL-04-EN-66-note-quality-pre-submission-validation.md`
* `specs/pf/specs/PF-96-medicaid-state-compliance-configuration.md`
* `docs/architecture/integrations/CL-04-EN-66-note-quality-pre-submission-validation-INTEGRATION.md`