Feature: PM-01-EN-02Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
Audience: Billing managers, system administrators
Last Updated: 2026-04-05
Configuration
Jurisdiction Profile (PF-96)
Identifier labels and format validation are driven by the organization’s jurisdiction profile. To configure:- Navigate to Settings → Organization → Jurisdiction Profile.
- Under Billing Rules, set:
member_id_label— Display name for the member ID field (e.g., “AHCCCS Member ID”).member_id_format— Regex pattern for validation (e.g.,^\d{10}$). Leave empty for free-text.state_system_id_label— Display name for the state system ID field (e.g., “AHCCCS CIS ID”).
Feature Flag: Alias-First Identifiers
Thepm_alias_first_identifiers feature flag controls whether the UI displays generic alias fields (medicaid_member_id, state_system_id) with fallback to legacy Arizona-specific fields.
- Disabled (default): UI displays legacy field values (
ahcccs_member_id,ahcccs_cis_id). - Enabled: UI displays generic values first, falling back to legacy values if the generic field is empty.
pm_alias_first_identifiers for your organization.
Data Synchronization
Database triggers maintain bidirectional sync between generic and legacy fields:- Writing to
medicaid_member_idauto-populatesahcccs_member_id(and vice versa). - Writing to
state_system_idauto-populatesahcccs_cis_id(and vice versa). - If both generic and legacy values are provided on the same write and they differ, the generic alias is authoritative and a conflict audit entry is logged to
pf_audit_logs.
Reconciliation
To check for any patients where the backfill may have missed records:Rollback
To disable jurisdiction-aware identifiers and revert to legacy behavior:- Disable the
pm_alias_first_identifiersfeature flag. - UI will revert to showing legacy field values. Labels remain profile-driven (from PF-96 jurisdiction profile) regardless of flag state — they do not revert to hardcoded values.
- Database triggers remain active (no data loss) — they continue syncing values bidirectionally.