> ## 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.

# Integration Notes

> Feature ID: PM-01-EN-02 Core: PM Status: ✅ Complete Last Updated: 2026-04-02

**Feature ID:** PM-01-EN-02\
**Core:** PM\
**Status:** ✅ Complete\
**Last Updated:** 2026-04-02

## Summary

PM-01-EN-02 introduces jurisdiction-aware patient identifier aliases and removes Arizona-only assumptions from registration and demographic workflows by consuming PF-96 profile configuration.

## Integration Pattern

* Pattern: Platform dependency through PF-96 jurisdiction profile resolution.
* No direct PM-to-CL (or other core) imports.
* No new external API contracts in this enhancement.

## Upstream Dependencies

* PF-96 (platform configuration/profile resolution): source of `billing.member_id_label` and `billing.member_id_format`.
* PF-96 migration plan (A1, C1) (migration guidance): defines alias-first dual-read/dual-write transition and fallback expectations.
* PM-01 parent spec (intra-core workflow dependency): ensures registration/demographic flows adopt aliases without regressions.

## Downstream Consumers

* PM-01 registration UI: displays profile-driven identifier labels and format validation hints.
* PM demographics and search: reads generic aliases with legacy fallback during migration window.
* Audit/reconciliation operations: tracks alias synchronization and mismatch remediation via internal audit-log entries (not published platform events).

## Data and Security Notes

* Organization-scoped lookup and write behavior is required for all identifier operations.
* Existing PM RLS and tenant isolation remain mandatory for alias reads/writes.
* Identifier values are PHI-sensitive and must not be logged outside controlled audit channels.

## Events and APIs

* Events published: None. Mismatch remediation generates internal audit-log entries only — these are not published as platform events.
* Events consumed: None.
* API contracts changed: None.

## Resolver Hook Details

PM-01-EN-02 consumes PF-96 jurisdiction profiles via:

* **`useBillingRules()`** — Frontend hook returning `{ member_id_label, member_id_format, state_system_id_label }` from the resolved jurisdiction profile. Falls back to Arizona defaults if profile is missing.
* **Feature flag:** `pm_alias_first_identifiers` controls whether alias-first UI is active. When disabled, legacy Arizona field names and values are shown. When enabled, generic alias fields are displayed with fallback to legacy values.

See [PF-96 Integration Doc](./medicaid-state-compliance-configuration-integration.md) for resolver function signatures.

***

## Validation Checklist

* [ ] Arizona baseline label/format parity verified.
* [ ] At least one non-Arizona profile fixture verified.
* [ ] Alias synchronization and conflict-resolution audit evidence captured.
* [ ] PM-01 registration and search regression suites pass.