> ## 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. # Cross-Core Integration Matrix > Version: 2.19.10 Last Updated: 2026-05-18 **Version:** 2.19.10 **Last Updated:** 2026-05-18 Matrix of cross-core integrations: who publishes/consumes what, with links to contract docs. *** ## Quick Reference | I need to… | Pattern | Location | | ------------------------------------------------------------------------ | ----------------------------------------- | -------------------------------------------------------------------- | | Identify an integration between two cores | Integration matrix lookup by From/To core | [Integration Matrix](#integration-matrix) | | Determine event payload contract source | Event contract reference | [EVENT\_CONTRACTS.md](./EVENT_CONTRACTS.md) | | Confirm whether dependency should be platform-layer, event, API, or data | Integration pattern governance | [PLATFORM\_INTEGRATION\_LAYERS.md](./PLATFORM_INTEGRATION_LAYERS.md) | | Find PM/CL cross-core integration mappings quickly | CL/PM EHR & Practice Management block | [Integration Matrix](#integration-matrix) | *** ## Integration Matrix | From Core | To Core | Integration Pattern | Status | Documentation | | ----------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Platform Integration Layers** | | | | | | PF | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md) | | PF-71 | PM (PM-01), CL (CL-01) | Data (shared table) | ✅ | [PF-71 Patient Identity Boundary](./patient-identity-boundary-integration.md) - `pf_patient_identities`; no CL↔PM direct dependency | | PF-27 | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#pf-27-platform-ai-integration-layer) - Platform AI | | PF-60 | All Cores | Platform Layer | 📝 | [PF-60 Integration](./rag-infrastructure-integration.md) - RAG Infrastructure (semantic search) | | PF-62 | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#pf-27-platform-ai-integration-layer) - AI Skills System (extends PF-27) | | PF-72 | PF-27, PF-59, PF-62, PF-60 | Platform internal | ✅ | [PF-72 Agent SDK Integration](./agent-sdk-integration-integration.md) - Skill-aware agent execution; consumes PF-27/PF-59/PF-62/PF-60; Phase 4 MCP integration complete | | PF-64 Phase 2 | PF-27, PF-72 | Platform Layer / Edge | ✅ | [PF-64 AI Template Generation](./ai-template-generation-integration.md) - Description-to-template and section suggestions; edge function `ai-generate-template`; no PHI in prompts (constitution §4.3) | | PF-73 | GR | Platform Layer | ✅ | [PF-73 Integration](./workflow-builder-swim-lane-integration.md) - Swim Lane Diagrams (consumes GR-01 policies, GR-11 procedures for diagram generation). Phase 2.2 realtime: see [EVENT\_CONTRACTS.md#pf-73-realtime-channel](./EVENT_CONTRACTS.md#pf-73-realtime-channel). Phase 3 (keyboard shortcuts, undo/redo, validation, BPMN export, auto-layout, accessibility) complete. | | PF-74 | PF-01, PF-50, PF-10, PF-81 | Platform internal | 📝 | [PF-74 Integration](./organization-url-routing-integration.md) - Path-based org routing; slug resolution; orgPath utility | | PF-19 | HR (pf\_sites, pf\_departments) | FK / Data Lookup | ✅ | Organizational Data Consolidation — employee primary site and department | | PF-19 | FA (pf\_departments) | FK / Data Lookup | ✅ | Organizational Data Consolidation — cost center allocation | | PF-19 | RH (pf\_sites) | FK / Data Lookup | ✅ | Organizational Data Consolidation — residence location | | PF-18 | HR, FA, RH | Event (pg\_notify) | ✅ | [PF-18 Integration](./org-data-sync-lineage-integration.md) - Org Data Sync & Lineage; propagates dept/site changes to affected modules | | PF-54 | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#pf-54-formatting-utilities-integration-layer) - Formatting Utilities | | PF-51 | All Cores | Platform Layer | ✅ | [PF-51 Integration](./caching-layer-integration.md) - Caching (query, config, reference data) | | PF-15-EN-01 | GR, PM | Platform Layer | ✅ | Centralized Reference Data — `useReferencePicklist` hook replaces hardcoded regulatory bodies, accreditation bodies, POS codes in GR and PM. **Contract:** `useReferencePicklist(category: string, options?: { includeInactive?: boolean })` returns `{ data: PicklistItem[], isLoading, error }`. Categories: `regulatory_body`, `accreditation_body`, `place_of_service`. Source: `@/platform/reference-data`. | | PF-32 Server-Side | PF-51, PF-07 | Platform internal | ✅ | [PF-32 Server-Side Integration](./server-side-condition-evaluation-integration.md) - Condition evaluation cache, performance metrics | | PF-56 | FW, HR, PF, FA, RH | Platform Layer | 📝 | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#pf-56-file-upload-framework-integration-layer) - File Upload Framework | | PF-63 | IT-16, IT, PF | Platform Layer | 📝 | PF-63 Integration - Device Compliance Integration Layer (MDM posture, compliance status, remote actions) | | PF-65 | HR | Platform Layer | 📝 | [PF-65 Integration](./gusto-embedded-payroll-integration.md) - Gusto Embedded Payroll | | PF-68 | CE, PF-27, PF-60 | Edge Function / Event | ✅ | [PF-68 Integration](./website-chatbot-integration.md) - Website Chatbot Widget (AI chat, lead capture) | | PF-70 | CL, PM | Platform Layer | ✅ | [PF-70 Integration](./medical-terminology-code-libraries-integration.md) - Medical Terminology & Code Libraries (ICD-10-CM, CPT, HCPCS, modifiers; search & validation) | | PF-70-EN-01 | CL, PM | Platform Layer | ✅ | Terminology Service Layer — code search edge function, ICD-10 hierarchy navigator, version management, cross-code-set mapping (2026-04-13) | | PF-37 Phase 2/3 | PF-06, Settings Hub | Platform Layer | ✅ | [PF-37 Phase 2/3 Integration](./phase-2-3-integration-pf-37.md) - Gesture preferences, analytics, pinch-to-zoom; Platform Layer (gestures) consumed by all cores | | PF-93 | PF-13, PF-10, Radix UI | Platform Layer | 🔜 85% | [PF-93 Integration](./platform-accessibility-infrastructure-integration.md) - Shared a11y utilities, skip links, announcer, keyboard shortcut registry, axe CI; aligns touch targets with PF-13; toast live regions with PF-10 | | PF-58 Phase 2-3-4 | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#pf-58-data-table-integration-layer) - Table-v2 expansion: inline edit, column manager, export, matrix layout, grouping | | PF-23 | PF-25, PF-26, PF-31, PF-28 | Platform Layer (embed/link) | 📝 | [PF-23 Data Manager Integration](./data-manager-integration.md) - Object detail tabs (Raw Data, Permissions), layout, relationships | | PF-53 | PF (internal) | Platform internal | 📝 | [PF-53 Integration](./migration-management-integration.md) - Migration Management UI (view + dashboard; PF-45 platform admin) | | PF-90 | PF-01, PF-04, PF-44, PF-48; S3-compatible storage (external) | Platform internal / Edge / Cron | 📋 | [PF-90 Integration](./disaster-recovery-business-continuity-integration.md) - Backup orchestration, tenant restore, DR drills; consumes PF-44 export patterns; audit via PF-04 | | PF-79 | PF-49 (Session Management) | Platform / Context | ✅ | [PF-79 Integration](./mobile-app-security-integration.md) - App Lock (PIN + biometric); client-side session lock gate; depends on PF-49 session context | | PF-77 | PF-01, PF-74, Vercel (external) | Data / API | 📝 | [PF-77 Integration](./tenant-domain-management-integration.md) - Tenant custom domain lifecycle; Vercel add/verify/remove; canonical host policy | | PF-81 | PF (internal) | Reference / Strategy | ✅ | [PF-81 Integration](./multi-tenant-host-url-strategy-integration.md) - Multi-tenant host & URL strategy; references PF-74, PF-77, canonical-host-policy | | PF-82 | FW-03, FW-06, PF-04, PF-10, PF-29, PF-36, PF-83 | Platform Layer / Event / Data | ✅ | [PF-82 Integration](./business-process-registry-integration.md) - Business process registry with auto-discovery, health scoring, and notification/dashboard event contracts | | PF-84 | FW-35, FW-16, All Cores | Platform Layer / API | ✅ Phase 1 | [PF-84 Integration](./business-calendar-service-integration.md) - Business calendar service wrapper (`@/platform/calendar`), shared edge utility, template/CSV holiday import | | FW-35 | PF-83 (calendar\_id FK), PF-84 (platform wrapper) | Data (FK reference) | ✅ Implemented | [PF-84 Integration](./business-calendar-service-integration.md) - Business calendar tables consumed by PF-83 and wrapped by PF-84 | | PF-83 | FW-16, PF-84, PF-10, FW-03 | Platform Layer / Event / API | ✅ | [PF-83 Integration](./sla-management-platform-layer-integration.md) - Event-driven cross-core SLA tracking and escalation orchestration | | PF-85 | FW-22, PF-82, PF-83, PF-36, PF-10 | Platform Layer / Data / Navigation | ✅ Phase 1 | [PF-85 Integration](./automation-observability-dashboard-integration.md) - Unified automation observability dashboard with threshold alerting and drill-down navigation (DLQ integration: FW-47 ✅) | | PF-86 | PF-01, PF-06, PF-10, CE | Platform Layer / shared Edge util | ✅ | [PF-86 Integration](./platform-email-signature-service-integration.md) - Org/user HTML & text email signatures; `@/platform/email-signatures`; PF-10 + CE MVP consumers | | PF-88 | PF-23, PF-24, PF-25, PF-47, PF-70; HR, PM, FA (import targets) | Platform Layer / Data | 🔨 | [PF-88 Integration](./tenant-onboarding-data-import-integration.md) - `pf_import_*`, onboarding wizard, adapters (CSV/XLSX/JSON); multi-entity batch import; PHI-safe storage and previews | | PF-89 | PF-07, PF-36, PF-48; all cores (Edge consumers) | Edge / CI / Platform | ✅ | [PF-89 Integration](./api-versioning-edge-function-lifecycle-integration.md) - `X-API-Version` middleware, file-based contracts, CI contract-diff, deprecation headers; opt-in per function | | PF-91 | PF-04, PF-05, PF-10, PF-36, PF-48, PF-90, CL-11, GR-03 | Platform Layer / Edge / Event | 🔨 | [PF-91 Integration](./compliance-automation-regulatory-dashboard-integration.md) - Compliance dashboard, PHI classification, drift detection, audit evidence packages; Part 2 enforcement with CL-11 | | PF-96 | CL-02, CL-04, CL-11, CL-40, PM-07, PM-08, PM-10, PM-18, PM-41, PF-91 | Platform Layer / Event / RPC | ✅ | [PF-96 Integration](./medicaid-state-compliance-configuration-integration.md) - Jurisdiction profile system: state Medicaid rule packs (clinical, billing, compliance) with four-tier inheritance; `useJurisdictionProfile()` hook + `pf_resolve_jurisdiction_profile()` RPC; `pf_jurisdiction_profile_changed` event | | PF-94 | PF-01, PF-54, PF-84, PF-83, PF scheduling | Platform Layer / Data | 📋 | [PF-94 Integration](./multi-timezone-organization-management-integration.md) - Site IANA timezone, `pf_site_business_hours`, hooks for SLA/scheduling/reporting; no core-to-core imports | | PF-95 | PF-01, PF-74, PF-77, PF-81, PF-86, Vercel (external) | Platform Layer / Data | 🔨 | [PF-95 Integration](./tenant-white-labeling-theming-integration.md) - `pf_tenant_themes` (single-active DB enforcement), org `subdomain` + `subdomain_verified` + `prefer_subdomain_redirect`, pre-auth branding RPCs, CSS variables; PF-74 implements canonical 308 redirect matrix; PF-86 consumes theme tokens (Phase 4) | | PF-97 | PF-01, PF-30, PF-42, PF-43, PF-48, PF-89 | Platform internal / Edge | ✅ Phase 1 | [PF-97 Integration](./multi-tenant-organization-api-access-integration.md) - Service accounts, API key lifecycle, token exchange edge function, machine auth middleware; PF-only (no cross-core consumers yet) | | PF-98 | PF-10, PF-43 | Event / Platform Layer | ✅ | [PF-98 Integration](./ai-staff-headshot-generator-integration.md) - AI Staff Headshot Generator; events to PF-10 (notifications) and PF-43 (quota tracking); Supabase Storage for images | | PF-101 | HR, CE, PF-10, PF-11, PF-35, PF-76, PF-86; Google Workspace (external) | Platform Layer / Event / Edge | 🚧 | [PF-101 Integration](./google-workspace-integration-integration.md) - Google Workspace connector for Admin SDK directory lifecycle, Gmail, Calendar/Meet, Drive, Chat, licensing, Reports API; consumes HR lifecycle events and wraps existing CE Gmail/Calendar paths. **Status (2026-04-28):** WS1/WS2/WS3/WS5/WS7 complete; WS6 5/8 (Calendar, Licensing, Reports, Directory Reconcile shipped; Drive/Chat/CE-cutover deferred); WS4 1/5 (inventory only — Gmail compatibility adapter pending BAA staging tenant). 38/44 tasks. | | PF-10-EN-01 | PF-10 | Platform Layer / Data / RPC | ✅ | [PF-10-EN-01 Spec](../../../specs/pf/specs/PF-10-notifications-system.md) — Org-Configurable Notification Templates — `pf_notification_templates` (event\_key), `pf_notification_template_variables`, resolution/render RPCs, management UI at `/settings/notifications/templates` | | PF-11 Phase 5 | PF-10 (Notifications) | Edge Function / Cron | ✅ | Document Expiration & Analytics — `document-expiration-reminders` sends PF-10 notifications at 30/7/1 day thresholds; `process-document-expiration` archives expired docs | | **Event-Based Integration** | | | | | | FW-16 | FW-03, PF-83, FW-46, PF-84, HR, RH, FA (publish) | Event / Platform Layer | ✅ | [FW-16 Integration](./event-based-workflow-triggers-integration.md) — Event registry, domain event log, publishEvent() platform layer. **Phase 2 (🔧 Core T1–T9 complete; T10–T17 pending):** [FW-16-PHASE-2-EVENT-SCHEMA-EXPANSION.md](../../../specs/fw/archive/FW-16-PHASE-2-EVENT-SCHEMA-EXPANSION.md) — payload JSON Schema validation, `correlation_id` on `fw_domain_events`, deprecation workflow, registry UI, CI schema checks | | FW-30 | PF-27 | Platform Layer | ✅ | Workflow Optimization & AI Suggestions — uses Platform AI for suggestion generation | | FW-51 | FW-03, PF-27, FW-44, FW-50, PF-10 | Platform Layer | ✅ | [FW-51 Automation Rule Copilot](./automation-rule-copilot-integration.md) — NL drafting for automation rules via Platform AI; persists to existing `fw_automation_rules` / `fw_automation_actions`; no new tables | | FW-15 | PF-08, PF-15 (Data Lookup), PF-01, Workforce | Platform Layer | ✅ | [FW-15 Form Field Lookups](./form-field-lookups-integration.md) - Table lookups in form fields; consumes platform data-lookup and workforce | | FW-60 | FW-01, FW-02, FW-05, FW-15, FW-19, PF-01, PF-02, PF-08, domain tables (RLS) | Platform Layer / Data | ✅ | [FW-60 Form Prefill & Smart Defaults](./form-prefill-smart-defaults-integration.md) - Prefill rules, carry-forward, submission provenance JSONB | | FW-17 | PF-17, FW-16 | Platform Layer / Intra-core | ✅ | [FW-17 Advanced Condition Builder](./advanced-condition-builder-integration.md) - Two-pane condition builder; PF-17 field discovery, FW-16 event payload attributes | | FW-05 | PF-01, PF-02, PF-08, FW-01, FW-02 | Platform Layer | ✅ | [FW-05 Multi-Page Forms](./multi-page-forms-integration.md) - Page structure, progress, drafts; consumes PF-08, FW-01, FW-02 | | FW-45 | FW-03, FW-06, FW-07, FW-17, PF-01, PF-02 | Platform Layer / Event / API | ✅ | [FW-45 Decision Tables](./decision-tables-integration.md) - Versioned decision-table authoring, workflow condition/node integration, and server-side evaluation audit logging | | FW-46 | FW-03, FW-06, FW-16, PF-01, PF-10 | Platform Layer / Event / Scheduled Worker | ✅ | [FW-46 Durable Execution Worker](./durable-execution-worker-integration.md) - Queue-backed durable execution, retry + DLQ routing, cron-triggered worker | | FW-59 | FW-46, FW-06, FW-16, PF-01, PF-04, PF-10, PF-42 | Edge Function / Data / Platform Layer | ✅ | [FW-59 External Webhook Triggers](./external-webhook-triggers-integration.md) - Inbound webhooks → validated enqueue to FW-46; org slug + endpoint slug routing | | FW-47 | FW-46, FW-03, PF-01, PF-10 | Queue / Data / Scheduled Worker / Platform Layer | ✅ | [FW-47 Dead Letter Queue](./dead-letter-queue-integration.md) - Captures permanently failed executions, enables manual retry/discard flows, and sends DLQ threshold notifications | | FW-48 | FW-46, FW-22, FW-25, FW-18, FW-23, PF-01, PF-04 | Data / Platform Layer / Realtime | ✅ | [FW-48 Execution Step Checkpointing](./execution-step-checkpointing-integration.md) - Step-level checkpoint persistence, deterministic resume, variable output tracking, timeline/realtime integration | | FW-49 | FW-46, FW-47, FW-25, PF-10, PF-01 | Scheduled Worker / Event / Platform Layer | ✅ | [FW-49 Execution Timeout & Watchdog](./execution-timeout-watchdog-integration.md) - pg\_cron timeout watchdog, terminal timeout handling, warning/escalation notifications | | FW-53 | FW-46, FW-47, FW-16, FW-03, PF-10, PF-04, PF-43, PF-42 | Scheduled Worker / Data / Platform Layer | ✅ | [FW-53 Workflow Rate Limiting & Throttling](./workflow-rate-limiting-throttling-integration.md) - Org/workflow rate limits, debounce, cascade depth, backpressure with FW-46 worker; counters + dashboard | | FW-50 | PF-27, FW-06, FW-18, FW-44 | Platform Layer | ✅ | [FW-50 Natural Language Workflow Generation](./natural-language-workflow-generation-integration.md) - AI-suggested workflow nodes/edges from description; merges into `fw_workflow_definitions` JSONB columns; no PHI in prompts | | FW-54 | FW-34, FW-45, FW-17, FW-35, PF-10, PF-30 | Intra-core / Platform Layer | ✅ | [FW-54 Conditional Approval Routing](./conditional-approval-routing-integration.md) - Prioritized rules + optional FW-45 output select chain at submit; allowlisted dynamic approver lookups; fallback aligned with FW-34 escalation | | FW-56 | FW-22, FW-48, FW-24, FW-06, FW-18, FW-43, PF-04, PF-46 | Intra-core / Platform Layer | ✅ | [FW-56 Workflow Execution Replay & Time Travel](./workflow-execution-replay-time-travel-integration.md) - Historical replay from `fw_execution_steps`, what-if forks via `fw_sandbox_executions`, dual-run compare, single-execution JSON/PDF export | | FW-52 | FW-06, FW-07, FW-01, FW-45, PF-08 | Edge / Platform Layer | 📝 | [FW-52 Workflow Import/Export & Portability](./workflow-import-export-portability-integration.md) - JSON/YAML packages; `fw_import_logs`; transactional import RPC; optional form + decision-table bundle (no automation rules in Phase 1) | | FW-55 | FW-01, FW-03, FW-06, FW-15, FW-16, FW-41, FW-54, PF-30, PF-04 | Intra-core / Platform Layer | ✅ | [FW-55 Form & Workflow Dependency Graph](./form-workflow-dependency-graph-integration.md) - `fw_dependency_graph` edge store; incremental scanners on save; impact analysis, orphans, xyflow graph; FW-internal only MVP | | FW-43 | GR-08, IT, PF-04, PF-10, FW-46/47/48/49, FW-16 | API / Platform Layer / Data (trigger) | ✅ | [FW-43 Audit Trail & Compliance Reporting](./workflow-audit-trail-compliance-reporting-integration.md) - Compliance-grade audit trail, report export (PDF/CSV/Excel/FHIR), retention management, FHIR AuditEvent alignment | | FW-58 | FW-23, FW-34, FW-35, FW-05, PF-10, PF-58 | Data / Platform Layer / Edge | ✅ | [FW-58 Workflow Metrics & KPI Dashboards](./workflow-metrics-kpi-dashboards-integration.md) - KPI snapshots, dashboard, drill-down, scheduled PDF via PF-10 | | FW-25 | FW-46, FW-47, FW-48, FW-49, PF-01, PF-02, PF-10 | Intra-core / Platform Layer | ✅ | [FW-25 Advanced Error Recovery & Retry](./advanced-error-recovery-retry-integration.md) - Configurable retry strategies, circuit breakers, recovery workflows, compensation actions | | FW | FW-03 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fw-03-form-submission-events) | | FW | PF-10, FW-03 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#fw-34-approval-request-submitted-event) - FW-34 Approval Submitted | | FW | FW-03, PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#fw-34-approval-request-completed-event) - FW-34 Approval Completed | | FW | PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#fw-34-approval-escalated-event) - FW-34 Approval Escalated | | **Cross-Core FW Integration Guides** | | | | | | HR | FW (FW-01, FW-03, FW-15, FW-16, FW-34, FW-45, FW-54) | Event / Platform Layer | 📝 | [HR-FW Integration](./HR-FW-INTEGRATION.md) - Leave approval, onboarding/offboarding workflows, credential reminders, performance review chains, compensation routing; conditional routing (FW-54) | | FA | FW (FW-01, FW-03, FW-15, FW-16, FW-34, FW-45, FW-54) | Event / API / Platform Layer | 📝 | [FA-FW Integration](./FA-FW-INTEGRATION.md) - Expense/PO/budget/JE/bill approval chains, amount-based decision tables, AP automation, period close workflows; conditional routing (FW-54) | | RH | FW (FW-01, FW-03, FW-15, FW-16, FW-33, FW-34, FW-45, FW-54) | Event / Platform Layer | 📝 | [RH-FW Integration](./RH-FW-INTEGRATION.md) - Intake forms, phase progression approval, safety event investigation, pass request approval, compliance reminders; conditional routing (FW-54) | | HR | Event Consumer, HR-04 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#hr-02-credential-management-events) | | HR | Event Consumer | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#hr-03-onboarding--offboarding-events) | | HR-04 | HR-02 | Event Subscription | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#hr-02-credential-management-events) - Credential blocking | | HR-05 | PF-10 | Event (DB trigger → Edge Fn) | ✅ | [HR-05 Integration](./enhancements-integration-hr-05.md) - Exception alerts via `time-exception-notify`; geofencing intra-core | | HR-01 | GR-01, RH-01, HR-04, HR-05, FM, FA | Event / API | 📝 | [HR-01 Integration](./employee-directory-integration.md) - Employee lifecycle events, employee lookup API, org chart data | | HR-02 | HR-04, HR-05, FW, PF-10, PF-11 | Event / Platform Layer | 📝 | [HR-02 Integration](./credentialing-compliance-integration.md) - Credential expiration/verification events, renewal workflows | | HR-03 | IT-08, PF-10, PF-11 | Event | 📝 | [HR-03 Integration](./onboarding-offboarding-integration.md) - Onboarding/offboarding events for IT provisioning | | HR-31 | HR-01, HR-03, HR-12, PF-10, PF-11, GR-01 (event consumer) | Event / Platform Layer | ⛔ Deprecated | [HR-31 Integration](./employee-document-policy-acknowledgment-integration.md) - ~~Workforce policy distribution & acknowledgments~~ Consolidated into GR-01 (2026-03-26); tables dropped in migration `20260326034722` | | HR-26 | HR-01, HR-03, PF-10, PF-30, External (USCIS) | Edge / Event / Platform Layer | ✅ | [HR-26 Integration](./e-verify-integration.md) - E-Verify cases from I-9 Section 2; USCIS API via edge; notifications; `hr.everify.*` permissions | | HR-28 | HR-01, HR-02, HR-03, HR-14, PF-10, PF-04, PF-30, PF-56 | Platform Layer / Event | ✅ | [HR-28 Integration](./fingerprint-clearance-card-management-integration.md) - Arizona fingerprint clearance tracking; onboarding/credential gates; expiration notifications; audit logging via PF-04 | | HR-09-ENHANCEMENTS | HR-09, HR-09 Phase 5, HR-13, PF-10, PF-30 | Platform Layer / Data | ✅ Implemented | [HR-09-ENHANCEMENTS Integration](./enhancements-integration-hr-09.md) - EN-1 structured interview scorecards; blind peer evaluation; comparison grid; PDF export; optional HR-13 competency linkage; PF-10 assign/remind (no PHI in body) | | HR-09-P5.4 | HR-09 (HR-internal; uses PF-Vault for credentials) | Edge / Schema | ✅ | Job Board Production Hardening — Vault credentials, circuit breaker, webhook signature/replay/idempotency, import pipeline; HR-internal only, listed for PF-Vault dependency visibility (2026-04-02) | | HR-29 | HR-01, HR-07, HR-07-EN-1, HR-05, PF-10, PF-30 | Event / Platform Layer | 📝 | [HR-29 FLSA Classification Integration](./flsa-classification-integration.md) - FLSA classification change events; retroactive pay request generation via HR-07 EN-1; threshold monitoring cron | | HR-30 | HR-03, HR-07, HR-06, HR-05, HR-11, PF-10, PF-30 | Event / Platform Layer | 📝 | [HR-30 Integration](./final-paycheck-termination-pay-compliance-integration.md) - Final paycheck on `hr_employee_terminated`; Arizona deadline tracking; HR-07 payroll handoff | | HR-10 | LO-11, HR-15, HR-16, HR-03, HR-14, PF-08, PF-10, PF-11 | Event / Platform Layer | 📝 | [HR-10 Integration](./performance-management-integration.md) - Performance review/goal/PIP events, review export API | | HR-11 | HR-06, HR-07, FA-15, PF-10 | Event / API | 📝 | [HR-11 Integration](./benefits-administration-integration.md) - Benefits enrollment events, enrollment status query hook | | HR-14 | HR-01, HR-03, HR-04, GR-06, GR-03, PF-10, PF-11, Platform Layer (PF: Storage) | Event / Platform Layer | 📝 | [HR-14 Integration](./employee-relations-integration.md) - Disciplinary/incident events; **HR-14-ENHANCEMENTS EN-1** (ADA accommodations): HR-01/HR-04 reads, notifications, PF / Supabase Storage for PHI medical attachments — see integration doc § ADA reasonable accommodations | | HR-15 | HR-07, FA, HR-10, PF-10, PF-11 | Event / Platform Layer | 📝 | [HR-15 Integration](./compensation-management-integration.md) - Merit increase, compensation cost allocation, analysis completion events | | HR-16 | HR-01, HR-10, HR-13, PF-10, PF-12 | Platform Layer / Data | 📝 | [HR-16 Integration](./succession-planning-integration.md) - Succession planning with HR-10 performance and HR-13 skills integration | | HR-17 | HR-03, PF-08, PF-10 | Event / Platform Layer | 📝 | [HR-17 Integration](./employee-engagement-integration.md) - Survey and exit interview completion events | | FA | FW-03, PF-10, FA-03 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-02-vendor-bill-approved-events) | | FA | FA-02, PF-10, FA-06 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-03-payment-processed-events) | | FA (FA-06 Phase 2/3) | External (bank feed, banks) | API / Export | 📝 | [FA-06 Phase 2 & 3 Integration](./phase2-3-integration.md) | | FA | Event Consumer, PF-10, FA-11 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-04-purchase-order-events) - purchase\_order\_approved | | FA | Event Consumer, PF-10, FA-11 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-04-purchase-order-events) - goods\_received | | FA | Event Consumer, FA-07, PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-02-journal-entry-posted-events) | | FA (FA-02 Phase 2/3) | FA-19, FA-01 | Data / Query | ✅ | FA-02-EXPANSION: JE Import (fa-je-import edge fn), Inter-Fund Transfers, Period Close Validation (widget on FA-19), GL Migration (fa\_account\_mappings with fund\_id) | | FA (FA-07 Phase 2/3) | FA-08, PF-10 | Data / API | ✅ | FA-07-PHASE-2-3-EXPANSION: Custom Report Builder, Dashboard, Annotations, BI API (fa-report-data edge fn), Cash Flow Direct, Functional Expenses Matrix | | FA | FW-16, PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#fa-22-accounts-payable-automation-events) - fa\_bill\_scan\_completed, fa\_bill\_duplicate\_flagged | | FA | FW-03, PF-10, FA-07 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-08-budget-approved-events) | | FA | PF-10, FA-08 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-08-budget-exceeded-events) | | FA | FA-07, PF-10, Event Consumer | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#fa-09-consolidation-completed-events) | | FM | PF-10, GR | Event | ✅ | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#vendor_certification_expiring) | | FM | PF-10, FA-03 | Event | ✅ | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#vendor_work_order_assigned) | | FM | FA, FM-04, FM-05, FM-06, FM-03 | Event | ✅ | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#work_order_completed) — work\_order\_completed | | FM | PF-10, FA-04 | Event | ✅ | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#inventory_low_stock) — inventory\_low\_stock | | FM | PF-10, FM-05 | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#pm_due) — pm\_due, pm\_overdue, pm\_completed | | FM | FA | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#asset_purchased) — asset\_purchased, asset\_disposed | | FM | PF-10, GR, FM-01 | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#inspection_due) — inspection\_due/failed/compliant (FM-06) | | FM | PF-10, GR | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#vehicle_registered) — fleet events (FM-13) | | FM | PF-10, FA-08 | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#budget_variance_alert) — budget\_variance\_alert (FM-09) | | FM | FA-09, PF-10 | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#capital_project_approved) — capital\_project\_approved (FM-12) | | FM | PF-10, GR | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#energy_anomaly_detected) — energy\_anomaly\_detected (FM-10, deferred) | | FM | PF-10, HR | Event | 📝 | [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#space_occupancy_threshold) — space\_occupancy\_threshold (FM-11) | | LO | FA, PF-10, PF-04 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-01-vision--strategic-planning-events) | | LO | PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-04-to-dos--task-management-events) | | LO | PF-10, LO-03 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-04-to-dos--task-management-events) | | LO | PF-10, PF-12 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-05-scorecards--kpi-tracking-events) | | LO | PF-10, LO-06 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-05-scorecards--kpi-tracking-events) | | LO | PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-06-structured-meetings-events) | | LO | PF-04, PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-06-structured-meetings-events) | | LO | LO-04, PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-06-structured-meetings-events) | | LO | PF-10, LO-06 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-07-issues--problem-solving-events) | | LO | PF-04, PF-10 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-07-issues--problem-solving-events) | | LO | PF-10, PF-12 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#lo-09-assessments--surveys-events) | | RH | FA | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-01-resident-admission-events) | | RH | FA | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-01-resident-discharge-events) | | RH | FA | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-01-invoice-creation-request-events) | | RH (Billing) | FA-05 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-04-resident-billing-events) - resident\_charge\_created | | RH | PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-02-phase-progression-events) | | RH-02 | PF-10, FA, RH-01, RH-03, RH-04, RH-05 | Event / Platform Layer | 📝 | [RH-02 Integration](./programs-phases-integration.md) - Program/phase lifecycle, milestone, and completion integration surfaces | | RH-01.1 → CL-68 / PM-74 / GR-27 | CL, PM, GR | Event / Platform Layer | 📝 | [CL-GR-PM-BHRF-EPISODE-LIFECYCLE](./CL-GR-PM-BHRF-EPISODE-LIFECYCLE.md) - BHRF (A.A.C. R9-10-701–722, adult) clinical residential episode lifecycle. RH publishes the canonical `rh_resident_admitted` (filtered to `facility_type='psychiatric_residential'` = `rh_psychiatric_residential_admission` alias; bed/census substrate only); CL-68 opens clinical episode + assessment/LOC; PM-74 per-diem + 5-day PA; GR-27 licensure/staffing/incident/retention. **CL is downstream — GR-27/PM-74 consume CL-68 events but do NOT depend on CL.** No cross-core imports/FKs. | | RH | PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-03-critical-incident-events) | | RH-03 | PF-08, PF-10, PF-11, RH-02, RH-06 | Event / Platform Layer | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-03-critical-incident-events); [RH-03 Integration](./safety-events-compliance-integration.md) - Significant event lifecycle, investigation completion, UDS-positive workflow, compliance export handoff | | RH-04 | RH-05, PF-10, RH-01, RH-02, RH-03 | Event / Platform Layer | 📝 | [RH-04 Integration](./participation-attendance-integration.md) - Attendance threshold breach events, participation tracking | | RH | PF-10, RH-05 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-04-attendance-threshold-breached-events) | | RH-06 | HR, PF-10, PF-11, RH-01, RH-02, RH-03 | Event / API / Platform Layer | 📝 | [RH-06 Integration](./compliance-staff-operations-integration.md) - Compliance deadline and non-compliance events, HR employee lookup API | | RH | PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#rh-06-compliance-events) | | FA | RH | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#fa-01-payment-received-events) | | HR | RH | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#hr-01-employee-assignment-events) | | HR | GR | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#hr-01-employee-created-events) | | **PF-48 Security Event Monitoring** | | | | | | PF-48 | PF-04, PF-10, PF-36 | Event | ✅ | [PF-48 Integration](./security-event-monitoring-integration.md) - security\_event\_detected | | PF-52 | PF-36 | Data / Platform | ✅ | [PF-52 Integration](./query-performance-monitoring-integration.md) - Query performance metrics on health dashboard | | PF-92 | Vite build, GitHub Actions, PF-07 (reference) | CI / Build | 📝 | [PF-92 Integration](./performance-budget-enforcement-integration.md) - Bundle and Lighthouse budgets in CI; no runtime API | | PF-36 | PF-10, PF-07 | Platform Layer | ✅ | [PF-36 Integration](./system-health-dashboard-integration.md) - Health dashboard alerts (Phase 1); custom metrics & SLA alerts (Phase 2) | | PF-07 (Phase 2/3) | All Cores (RH, FA, HR, GR, FW, FM, CL), PF-36, External (Sentry) | Platform Layer / API | ✅ | [PF-07 Integration](./error-handling-monitoring-integration.md) - Error boundaries, auth logging with correlation IDs, feature-level crash isolation, performance monitoring; Sentry PHI scrubbing | | PF-42 | PF-10, PF-04, PF-01 | Event / Platform | ✅ | [PF-42 Integration](./rate-limiting-throttling-integration.md) - rate\_limit\_violated; consumes PF-01 org context | | PF-43 | PF-10, PF-04, PF-11, PF-42, PF-01 | Event / Platform | ✅ | [PF-43 Integration](./tenant-resource-quotas-integration.md) - quota\_violated; storage/API/user/workflow quotas; consumes PF-01, PF-11, PF-42 | | PF-46 | PF-04, PF-11 | Platform / Data | ✅ | [PF-46 Integration](./data-retention-lifecycle-integration.md) - Audit logging, cold storage (archival); scheduled retention jobs | | PF-04 (Phase 2/3) | PF-12, PF-14 | Platform / Data | ✅ | [PF-04 Phase 2/3 Integration](./phase-2-3-audit-analytics-export-integration.md) - Audit analytics dashboard, export, realtime feed, SIEM export | | PF-47 | All Cores | Platform Layer | ✅ | [PF-47 Integration](./bulk-operations-integration.md) - Bulk operations framework (delete, update, assign; progress, rollback, rate limit) | | **PF RAG Infrastructure Events** | | | | | | PF-11 | PF-60 | Event | 📝 | [PF-60 Integration](./rag-infrastructure-integration.md) - document\_published | | PF-11 | PF-60 | Event | 📝 | [PF-60 Integration](./rag-infrastructure-integration.md) - document\_updated | | PF-11 | PF-60 | Event | 📝 | [PF-60 Integration](./rag-infrastructure-integration.md) - document\_deleted | | **PF Knowledge Base Events** | | | | | | PF-61 | PF-60 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#pf-61-knowledge-base-system-events) - knowledge\_article\_published | | PF-61 | PF-60 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#pf-61-knowledge-base-system-events) - knowledge\_article\_unpublished | | PF-61 | PF-11 | Platform Layer | 📝 | [PF-61 Integration](./knowledge-base-integration.md) - Document import | | **IT Module Events** | | | | | | IT | FA | Event | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-01-asset-purchased-event) - Asset purchased | | IT | FA | Event | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-04-license-renewed-event) - License renewed | | IT | FM | Event | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-01-asset-maintenance-required-event) - Asset maintenance required | | IT | GR | Event | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-05-security-incident-created-event) - Security incident | | IT | PF-10 | Event | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md) - All alert events (SLA, expiration, compliance) | | IT | FW-34 | Workflow | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-06-purchase-request-submitted-event) - Procurement approvals | | **CE Module Events & Platform Telephony** | | | | | | CE-03 | All Cores | Platform Layer | ✅ | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#ce-03-platform-telephony-integration-layer) - Platform Telephony | | CE-03-E1 | CE-03 | Platform Layer | ✅ | [CE-03-E1 Spec](../../../specs/ce/specs/CE-03-E1-click-to-call-screen-pop.md) - Click-to-Call & Screen Pop | | CE-01 | RH-01 | Event | ✅ | [CE-17 Spec](../../../specs/ce/specs/CE-17-ce-rh-admission-handoff.md), [Event Contracts](./EVENT_CONTRACTS.md#ce-lead-converted) - `ce_lead_converted` (lead → resident admission) | | CE-29 | PM-01 | Event | ✅ | [CE-29 Integration](./lead-conversion-integration.md) - `ce_lead_converted_to_patient` (lead → patient creation) | | CE-29 | RH-01 | Event | ✅ | [CE-29 Integration](./lead-conversion-integration.md) - `ce_lead_converted_to_resident` (lead → resident creation) | | CE-63 | CE-17, CE-19, CE-60, RH-01 | Event / Data | ✅ | [CE-63 Integration](./CE-63-pipeline-stage-transition-INTEGRATION.md) — pipeline stage prompts; terminal success publishes `ce_lead_converted_to_resident` (CE-29); `ce_lead_closures` + CE-19 referral logging + CE-60 audit (2026-05-16) | | CE-60 | RH-01, CE-29, CE-63, CE-04, CE-28, CE-59 | Event / Data | ✅ | [CE-60 Integration](./CE-60-contact-history-audit-trail-INTEGRATION.md) — All History unified timeline; admission milestones consumed from CE/RH integration events only (no CE→RH table reads); profile audit via `ce_contact_audit_log` with FORCE RLS + immutable (no UPDATE/DELETE policies); permission-gated sensitive redaction via `ce.contacts.history.sensitive_view` (2026-05-17) | | CE-29 | PM-38 | Event | ✅ | [CE-29 Integration](./lead-conversion-integration.md) - `ce_lead_converted_to_patient` → PM-38 auto-schedules intake appointment | | CE-18 | FA-31, FA-07 | Event | 📝 | [CE-18 Spec](../../../specs/ce/specs/CE-18-fundraising-donation-events-fa.md), [Event Contracts](./EVENT_CONTRACTS.md#donation-received) - `donation_received`, `fundraising_campaign_completed` | | CE-10 | CE-01, CE-05, PF-10 | Event | 📝 | [CE-10 Spec](../../../specs/ce/specs/CE-10-web-to-lead-capture.md), [Event Contracts](./EVENT_CONTRACTS.md#ce_web_form_submitted) - `ce_web_form_submitted` | | CE-28 | PM-38, PM-39, CE-29, FW-16, RH-01 | Event | ✅ | [CE-28 Integration](./intake-screening-integration.md) - `ce_screening_completed`, `ce_lead_waitlisted` (intake screening → appointment/waitlist/conversion) | | CE-28-ENH | PF-83, PF-10, CE-29, RH-01, External EDI vendor | Event / Platform / API | 🟡 Phase 1 ✅ | [CE-28 Integration](./intake-screening-integration.md) — **Phase 1 complete 2026-05-17**: EN-01 keyword crisis detection + `ce_crisis_alert_created` event (PHI-free) + crisis queue UI at `/ce/intake/crisis`; EN-02 business-hours evaluator + on-call rotations + after-hours handover queue. Org kill-switch via `ce_module_settings.crisis_detection_enabled`. Pending: EN-03 (translations), EN-04 (X12 270/271 + BAA), EN-05 (`@/platform/rh` bed availability), EN-06 (coaching), EN-07 (A/B). | | CE-20 | CE-01, CE-04, PF-15 | Data / Platform Layer | ✅ | [CE-20 Integration](./contact-relationship-mapping-integration.md) - Contact relationship graph, CE-04 activity logging, PF-15 relationship-type picklists | | CE-21 | CE-04, PF-10, PF-29 | Data / Platform | ✅ | [CE-21 Integration](./calendar-scheduling-integration-integration.md) - Calendar OAuth, two-way sync, meeting scheduler; `ce_calendar_events.activity_id` → CE-04 | | CE-65 | RH (bed inventory) | Platform Layer | ✅ | [CE-65 Integration](./CE-65-pipeline-tile-customization-dashboard-embeds-INTEGRATION.md) - Pipeline bed board embed reads aggregated occupancy via `@/platform/rh`; permission `ce.pipeline.view_bed_board`; no CE → RH direct imports | | CE-64 | (intra-core CE) | Platform (PF tenancy only) | ✅ | [CE-64 Integration stub](./CE-64-multi-track-service-line-pipeline-INTEGRATION.md) - Multi-track pipeline; no cross-core events in v1; future `ce_lead_track_changed` deferred | | CE-61 | CE-60, CE-65, CE-05 | Data / Platform | ✅ | [CE-61 spec](../../../specs/ce/specs/CE-61-contact-tagging-alert-system.md) — Contact tagging & alert system. CE-60: `tag_added` / `tag_removed` rows via `ce_log_contact_audit_event` (category `tag`, extended actor/context fields packed in `p_details` JSONB; no helper-signature changes). CE-65: tile metadata extension `tags: TagBadge[]` + `has_alert_tag: boolean` semantic state (rendering owned by CE-65, distinct from CE-58 urgency). CE-05: tag-name reporting dimension deferred to CE-05 reporting surface (tracked as IOU; no schema blocker). No new domain events; EVENT\_CONTRACTS.md unchanged. | | PM (PM-38) | CE-28, CE-29, PM-10, PM-39, PM-02, RH-01 | Event / API / Data | ✅ | [PM-38 Integration](./intake-appointment-automation-integration.md) - Intake appointment auto-creation; consumes `ce_screening_completed`; queries PM-10 slots; publishes `pm_appointment_created` and `pm_no_suitable_provider` | | PM (PM-38) | PM-40, PF-29, PF-11 | Event / Platform | ✅ | [PM-40 Integration](./digital-preadmission-packet-esignatures-integration.md) - `pm_appointment_created` → pre-admission packet, e-sign, document storage | | CE | CE-04 | Event | ✅ | [CE-07 Email Integration](./email-integration.md) - Email synced → Activity (database trigger) | | CE | PF-10 | Event | ✅ | [CE-07 Email Integration](./email-integration.md) - Email tracking notifications (opens, clicks) | | CE | CE-04 | Event | ✅ | CE-08 SMS Integration - SMS sent/received → Activity (database trigger) | | CE | PF-10 | Event | ✅ | CE-08 SMS Integration - SMS opt-out confirmations | | CE | CE-05 | Event | 📝 | CE-09 Marketing Campaigns - Campaign events (planned) | | **CL/PM EHR & Practice Management** | | | | | | CL | PM, FW, PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) - assessment\_completed, treatment\_plan\_signed, progress\_note\_signed, encounter\_completed, etc. | | PM (PM-45) | FA, PF-10, PM-09, PM-16, PM-32 | Event / Platform Layer | ✅ | [PM-45 Integration](./patient-payment-plans-collections-integration.md) · [EVENT\_CONTRACTS: pm.payment\_plan.created](./EVENT_CONTRACTS.md#pm.payment_plan.created) · [EVENT\_CONTRACTS: pm.bad\_debt\_writeoff.approved](./EVENT_CONTRACTS.md#pm.bad_debt_writeoff.approved) - PF-10 for aging reminders; PM-16 statement data; PM-32 charity care routing. 6 tables, 6 pages, 5 hooks, 1 edge function (pm-collections-aging-cron), 6 permissions. Completed 2026-04-08 | | PM | FA, PF-10, PM-09 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) - claim\_submitted, claim\_adjudicated, prior\_auth\_required, eligibility\_verified, patient\_registered | | PM | CL, RH (optional), PF-10 | Event | 📝 | [Event Contracts](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) - appointment\_scheduled, patient\_registered | | PM (PM-06) | CL-12 | Event | 📝 | [CL-PM Referrals](./CL-PM-REFERRALS.md) - referral\_accepted; [PM-06 Integration](./referral-management-integration.md) | | PM (PM-06-EN-01) | PF-10, PF-11 | Platform Layer | ✅ | [PM-06-EN-01 Spec](../../../specs/pm/specs/PM-06-EN-01-referral-management-enhancements.md) — court-ordered tracking, fax-to-digital intake, SLA monitoring, packet checklist. Platform-only deps (PF-10 notifications, PF-11 documents). **No new cross-core event contract.** Complete 2026-05-04. | | PM (PM-07) | CL-04, PM-02, PM-08, PF-70 | Event / Data | 📝 | [CL-PM Encounter-to-Billing](./CL-PM-ENCOUNTER-TO-BILLING.md) - clinical\_note\_finalized; PM-02 fee schedules; PM-08 claims from charges; PF-70 code library | | PM (PM-07-EN-14) | PM-07, PM-18-EN-06, PF-96, PF-30 | Data / Platform Layer | ✅ | [PM-07-EN-14 Integration](./payer-specific-modifier-rules-engine-integration.md) - Payer-specific modifier rules engine; resolution cascade: payer rule → PF-96 jurisdiction → system default; permissions via PF-30 | | PM (PM-09) | FA | Event | 📝 | [PM-09 Payment Posting & ERA](./payment-posting-era-processing-integration.md), [EVENT\_CONTRACTS – payment\_posted, write\_off\_approved](./EVENT_CONTRACTS.md#payment_posted-pm-09--fa) - Revenue and write-off posting to GL | | PM (PM-15, PM-15-P2) | PM-08, PM-09, PM-02, PM-10, PM-29, PM-30, PF-10, External (Waystar) | Data / API / Event | ✅ | [PM-15 Clearinghouse Integration](./clearinghouse-integration-integration.md) - Batch submission (PM-08), ERA retrieval (PM-09), eligibility 270/271 (PM-02), prior auth (PM-10); PM-15-P2 adds production REST transport (Waystar OAuth2), X12 837P/835/270/271/999/277CA, health monitoring, retry logic; CARC/RARC to PM-29; COB from PM-30; events `clearinghouse_batch_submitted`, `clearinghouse_batch_error`, `clearinghouse_era_received`, `clearinghouse_health_changed`. SFTP deferred (Deno Deploy incompatible). Complete 2026-04-09. | | PM (PM-15-P2-EN-01) | PM-15, PM-28, PF-30, PF-95 | Data / Platform Layer | ✅ | [PM-15-P2-EN-01 spec](../../../specs/pm/specs/PM-15-P2-EN-01-clearinghouse-multi-vendor-failover.md) — Clearinghouse multi-vendor failover. Adds `secondary_vendor`, `failover_enabled`, `failover_threshold_minutes` to `pm_clearinghouse_config`; new `pm_payer_clearinghouse_routes` for per-payer overrides. Pure router (`resolveVendorRoute`) with precedence `payer override → primary → failover secondary` after threshold. BAA gate via `custom_fields.baa_approved_vendors` blocks enabling Availity/Change Healthcare without compliance approval. Audit trail emitted on config change. Availity/Change Healthcare adapters scaffolded as stubs. Complete 2026-05-14. | | CL, PM | PF (platform) | Platform Layer | 📝 | [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md#planned-platform-layers-clpm-ehr--practice-management) - CL Consent Service, CL Billing Adapter, CL Document Export (EHI) | | CL-39 | PM-10, PM-12, PM-14, CL-04, CL-14, CL-16 | Platform Layer | ✅ Complete | [CL-39 Platform Integration Hooks](./platform-integration-hooks-integration.md) - `usePatientContext`, `useEncounterContext`, `useBillingAdapter`, `useDocumentExport`, `useExportStatus`; no core-to-core imports | | CL-41 | CL-39, PM-07, CL-04, CL-14 | Platform Layer / Data | ✅ Complete | [CL-41 spec](../../../specs/cl/specs/CL-41-payer-billing-suggestion-overrides.md) - `useBillingOverrides`, `applyBillingOverrides`, `useBillingWithOverrides`; PM table `pm_billing_suggestion_rules`; 3-tab settings UI at `/cl/settings/billing-overrides`; composes with CL-39. Complete 2026-04-01. | | CL-46 | CL-08 (event), PM-07 (platform layer), PF-70, PF-15, PF-30 | Event / Platform Layer | ✅ Complete (2026-05-12) | [CL-46 spec](../../../specs/cl/specs/CL-46-problem-list-management-icd10.md) — Problem List Management (ICD-10). Publishes `cl_problem_list_updated` (→ CL-08 CDS re-eval). Exposes `usePatientActiveProblems` via `@/platform/clinical` for PM-07 encounter diagnosis pre-population (no direct CL→PM import). PF-70 for ICD-10-CM code search; PF-15 for status/resolution picklists; PF-30 for `cl.problems.{view,create,update,delete}` permissions. | | PM (PM-41) | CE-28, CE-29, PM-38, PM-39, PM-40, PM-42, FW-16, GR | Event / Data / Realtime | ✅ | [PM-41 Integration](./intake-funnel-analytics-integration.md) - Intake funnel analytics logs; triggers + aggregates; FW-16 for UI/downstream; feeds PM-42. All 4 phases complete 2026-03-29 | | **API Contracts** | | | | | | CL (CL-01) | PM (PM-01), PF-01, PF-02, PF-04, PF-11 | API / Data | ✅ | [CL-01 Patient Chart & Clinical Summary](./patient-chart-clinical-summary-integration.md) - Chart shell, problem list, allergies; patient identity boundary in spec errata | | PM (PM-01) | PF-01, PF-02, PF-08, PF-16 | Platform / Data | 📝 | [PM-01 Patient Registration & Demographics](./patient-registration-demographics-integration.md) - Patient registration, USCDI v3 demographics, MPI; consumed by CL-01, PM-02, PM-03 | | PM (PM-01-EN-02) | PF-96, PM-01 | Platform Layer | ✅ | [PM-01-EN-02 Jurisdiction-Aware Patient Identifiers](./jurisdiction-aware-patient-identifiers-integration.md) - Profile-driven identifier labels/validation via PF-96; alias-first dual-read; bidirectional sync triggers; no new tables | | PM (PM-08-EN-13) | PF-96, PM-08, PM-26 | Platform Layer | ✅ | [PM-08-EN-13 Jurisdiction-Aware Filing Deadlines](./jurisdiction-aware-filing-deadlines-integration.md) - Profile-driven filing deadline and compliance window via PF-96; generic export filenames; no new tables | | PM (PM-07-EN-13) | PF-96, PM-07 | Platform Layer | ✅ | [PM-07-EN-13 Jurisdiction-Aware Billing Rules](./jurisdiction-aware-billing-rules-integration.md) - Profile-driven timed-unit thresholds, modifier conventions, IOP/PHP thresholds, and program label via PF-96; AZ defaults preserved as fail-safe fallback; no new tables, no new permissions | | PM (PM-02) | PM-01, PM-08, PM-15, AHCCCS (external) | Data / API | 📝 | [PM-02 Insurance & Eligibility Verification](./insurance-eligibility-verification-integration.md) - Insurance policies, eligibility checks (270/271), payers; consumed by PM-08 | | PM (PM-08) | PM-07, PM-09, PM-15, PM-02, PM-10, PF-70 | Data / API / Platform | 📝 | [PM-08 Claims Management & Submission](./claims-management-submission-integration.md) - Claims from charges; submission; PF-70 code library | | PM (PM-03) | PM-01, PM-05, PM-07, PM-13, CL-04, PF-10 | Data / Event / Platform | 📝 | [PM-03 Appointment Scheduling](./appointment-scheduling-integration.md) - Appointments consume PM-01/PM-05; events to PM-07, CL-04; PF-10 reminders; PM-13 telehealth | | PM (PM-10) | PM-01, PM-02, PM-08, CL-16, PF-10 | Data / API / Event | 📝 | [PM-10 Prior Authorization Management](./prior-authorization-management-integration.md) - PA requests; auth verification at claim scrub (PM-08); payer requirements (PM-02); Da Vinci PAS (CL-16); expiration alerts (PF-10) | \| PM (PM-39) | PM-38, PM-10, CE-28, CE-29, PM-02, PM-41, FW-16 | Event / Data | ✅ | [PM-39 Waitlist Management](./waitlist-management-integration.md) - no\_match → waitlist; availability re-check → promotion | \| PM (PM-12) | PM-01, PM-03, PM-09, PM-14, PF-08, CL-11 | Platform Layer / Data | 📝 | [PM-12 Patient Portal & Self-Service](./patient-portal-self-service-integration.md) - Self-scheduling, demographics, statements, messaging, clinical record (CL-11 Part 2); PF-08 intake/consent | \| PM (PM-12-EN-01) | PM-12, PM-40, PM-42, PM-03, PF-08, PF-29 | Intra-core (PM) | ✅ | Patient Portal Intake Enhancements — `pm_portal_packet_assignments` + `pm_portal_packet_items` (FORCE RLS, portal-patient scoped via `pm_portal_visible_patient_ids`); scheduling-readiness guardrails; PM-42 staff workbench tab. Intra-core only — see `.intra-core-only.json`. | \| PM (PM-14) | PM-12, PF-10, CL-01, CL-11 | Platform Layer / Data / Event / API | 📝 | [PM-14 Secure Messaging](./secure-messaging-integration.md) - Messaging UI (PM-12); notifications (PF-10); chart docs (CL-01); Part 2 (CL-11) | \| CL (CL-23) | PF-10, PM-14, CL-04, CL-08, CL-09, CL-11, PF-29 | Platform Layer / Event | ✅ | [CL-23 Clinical In-Basket](./clinical-in-basket-provider-messaging-integration.md) - In-basket items from co-sign, CDS, labs, referrals; PF-10 notifications; PM-14 deep-links | \| PM (PM-11) | PM-07, PM-08, PM-09, PM-10, PF-12, FA-07 | Data / Platform Layer | 📝 | [PM-11 Revenue Cycle Dashboard & Analytics](./revenue-cycle-dashboard-analytics-integration.md) - RCM KPIs, snapshots, benchmarks; PF-12 reports; FA-07 financial reporting (future) | \| PM (PM-17) | PM-08, PM-15, HR (Platform Layer), PF-10 | Data / Platform Layer | 📝 | [PM-17 Provider Credentialing & Enrollment Verification](./provider-credentialing-enrollment-verification-integration.md) - Enrollment status for claim scrub (PM-08); clearinghouse readiness (PM-15); HR provider/credential context via platform; alerts (PF-10) | \| PM (PM-16) | PF-10, PF-11, PM-09, PM-12 | Platform Layer / Data | ✅ | [PM-16 Patient Statement Generation & Billing Communications](./patient-statement-generation-billing-communications-integration.md) - Statement runs, delivery (PF-10/PF-11), PM-09 statements/balances, PM-12 portal posting; payment plans and financial assistance | \| PM (PM-18) | PM-08, PF-70 | Data / Platform Layer | ✅ | [PM-18 Configurable Claim Scrubbing](./configurable-claim-scrubbing-integration.md) - Org-level scrub rule overrides; extends PM-08 claim scrubbing. EN-06: per-payer/claim-type overrides, `pm_scrub_custom_edits` table (custom rule overrides, not an event contract), effectiveness reporting; PF-70 for code validation in custom edits. Completed 2026-03-27 | \| PM (PM-19) | FW-03, PM-07, PM-08, PM-09 | Event | 🔨 | [PM-19 PM-Triggered Business Rule Automation](./pm-triggered-business-rule-automation-integration.md) - Automation rules triggered by PM events (claim status, charge approval, payment posting) | \| PM (PM-20) | PF-01, PF-02, PF-10, PM-01, PM-02, PM-03, PM-07, PM-16 | Platform Layer / Data | ✅ | [PM-20 Good Faith Estimate & Price Transparency](./good-faith-estimate-price-transparency-integration.md) - NSA GFE generation, delivery timing (1/3 BD), acknowledgment, \$400+ dispute workflow; same-core dependencies only. Completed 2026-02-28 | \| PM (PM-21) | PM-01, PM-07 | Data (same core) | ✅ | PM-21 Sliding Fee Discount Schedule Management - FPL-based patient discounts; PM-07 charge capture applies discount\_pct from active assessment. Completed 2026-02-28 | \| PM (PM-23) | PM-07, PM-08, PM-09, PM-11 | Data (same core) | ✅ | [PM-23 Contract & Fee Schedule](./contract-fee-schedule-integration.md) - Contracted rates for expected amount, underpayment detection, expiration alerts, analytics. Completed 2026-02-28 | \| PM (PM-48) | PM-02, PM-09, PM-11, PM-20, PM-23, PM-32, PF-10, PF-11, PF-96 | Data / Event / Platform Layer | ✅ | [PM-48 Patient Cost Estimation & Financial Clearance](./patient-cost-estimation-financial-clearance-integration.md) - Insured-patient cost estimates (benefit data from PM-02, rates from PM-23); financial clearance workflow; auto-route to PM-32 above threshold; events `pm_cost_estimate_generated`, `pm_financial_clearance_completed`; accuracy tracking via PM-09 adjudication write-back. Completed 2026-04-07 | \| PM (PM-24) | PM-02, PM-07, PM-08, PM-15, PF-30 | Data (same core) / Platform Layer | ✅ | [PM-24 Batch Operations](./batch-operations-integration.md) - Batch claim generation/submission, eligibility checks, charge approval; pm\_batch\_jobs audit table; 4 permission keys. Completed 2026-03-01 | \| PM (PM-27) | PF-01, PM-08, PM-15, PM-11, PM-17 | Data / Platform Layer | ✅ | [PM-27 Multi-Site & Multi-NPI Configuration](./multi-site-multi-npi-configuration-integration.md) - Site-level billing config (NPI, tax ID, fee schedule, clearinghouse); claim defaults per site; patient site transfers; PM-08/PM-15 consume config. Completed 2026-03-01 | \| PM (PM-46) | PM-17, PM-15, PM-27, PM-07, PM-08, PF-10 | Data / Event / Platform Layer | ✅ | [PM-46 Payer Enrollment & EDI Onboarding](./payer-enrollment-edi-onboarding-integration.md) - EDI enrollment lifecycle tracking per payer/NPI/transaction type; 2 tables (pm\_payer\_edi\_enrollments, pm\_edi\_enrollment\_status\_history) + FORCE RLS + pm\_user\_has\_org\_access + append-only history + pm\_transition\_edi\_enrollment\_status RPC + 5 permissions + domain types (edi-enrollment.ts) + 6 hooks + EdiEnrollmentHubPage (3-tab: Matrix, ERA/EFT Gaps, Dashboard) + EdiEnrollmentDetailSheet + BulkCreateDialog + 2 Recharts + sidebar nav. Completed 2026-04-09 | \| PM (PM-28) | PF-01, PF-30, PM-01, PM-08, PM-09 | Data / Platform Layer | ✅ | [PM-28 PM System Configuration & Admin Settings](./pm-system-configuration-admin-settings-integration.md) - Single org-level PM settings admin surface; pm\_module\_settings key reference; permission-gated (pm.settings.view/manage); PM-01/PM-08/PM-09 consume settings; Phase 2: PM-20/PM-22/PM-23 cards. Completed 2026-03-03 | \| PM (PM-29) | PM-08, PM-09, PM-10, PM-11, PM-18 (Phase 2), PF-29, PF-70 | Data (same core) / Platform Layer | 🟡 | [PM-29 Claims Denial Management & Appeals](./claims-denial-management-appeals-integration.md) - Denial intake from ERA (PM-09), auth-denial link (PM-10), claim status/resubmit (PM-08), KPI analytics feed (PM-11), PF-29 auto-tasks on appeal submission, PF-70 CARC/RARC lookup; 3 permission keys. Phase 1 in progress — queue, detail, appeal workflow implemented; T6 analytics, T7 ERA intake pending. | \| PM (PM-50) | PM-08, PM-18, PM-29, CL-36, PF-96, PF-10 | Platform Layer / Event / Data (same core) | ✅ | [PM-50 AI-Powered Denial Prediction & Prevention](./ai-denial-prediction-prevention-integration.md) - Pre-submission ML risk scoring in PM-08 queue; complements PM-18 scrubbing; CL-36 documentation completeness metadata via `@/platform/clinical`; PF-96 jurisdiction context; PM-29 outcomes feed retraining; 4 permission keys; 2 events planned. Completed 2026-04-07 | \| PM (PM-25) | PM-11, CL-10, CL-15, PM-02, PM-01 | Data / Platform Layer | ✅ | [PM-25 VBP & APM Tracking](./vbp-apm-integration.md) - VBP programs, measures, incentives; PM-11 dashboards; CL-10/CL-15 gap identification; attribution (PM-02/PM-01). Completed 2026-03-01 | \| PM (PM-33) | FA, PM-11, PM-01, PM-09 (future) | Event / Data (same core) | ✅ | [PM-33 Capitation & PMPM Revenue Reconciliation](./capitation-pmpm-revenue-reconciliation-integration.md) - Capitation contracts, PMPM periods, roster events, reconciliation with disposition state machine; capitation revenue in PM-11 dashboard. `capitation_payment_received` event to FA is planned for FA integration phase — not blocking PM-33 core completion. Completed 2026-03-26 | \| PM (PM-42) | PM-38, PM-39, PM-40, PM-41, CE (`ce_leads`), FW-16, PF-30 | Data / Event / Platform Layer | ✅ | [PM-42 Coordinator Workbench](./coordinator-workbench-integration.md) - `pm_coordinator_tasks`, `pm_task_audit_log`; nullable `lead_id` (no composite FK); intake task queue, bulk actions, compliance export; realtime via FW-16. Completed 2026-03-29 | \| PM (PM-51) | PM-08, PM-02, PM-09, PF-75, FW-46, PF-10, PF-11 | Event / Data (same core) / Platform Layer | ✅ | [PM-51 Payer Portal Automation (RPA)](./payer-portal-automation-rpa-integration.md) - Headless browser RPA for payer portals; claim status → PM-08, remittance staging → PM-09, eligibility → PM-02; PF-75 credential vault; FW-46 durable worker; events `pm.rpa.execution_completed`, `pm.rpa.consecutive_failures` | \| PM (PM-36) | PM-07, PM-08, PM-09, PM-11, PF-29 | Data (same core) / Platform Layer / Scheduled Edge Function | ✅ | [PM-36 Automated Charge Reconciliation](./automated-charge-reconciliation-integration.md) - Nightly edge function detects 5 gap types (encounter→charge, charge→claim, claim→payment, duplicate, zero-amount); PF-29 tasks per gap; pm\_charge\_recon\_daily\_summary feeds PM-11 KPIs; 2 permission keys (pm.charge\_recon.view/manage) | \| PM (PM-44) | PM-09, PM-23, PM-29, PM-11, PF-10, PF-12, PF-96 | Event / Data (same core) / Platform Layer / Scheduled Edge Function | ✅ | [PM-44 ERA Reconciliation & Underpayment Detection](./era-reconciliation-underpayment-detection-integration.md) - Consumes `payment_posted` from PM-09; compares paid vs PM-23 contracted rates; publishes `pm_underpayment_detected`; payer performance snapshots (daily cron); AI pattern detection (weekly cron); appeal initiation via PM-29; 5 permission keys | \| PM (PM-53) | FA, PM-09, PM-15, PM-29, PM-37 (proposed), PM-44, PM-45, PF-04, PF-10, PF-30, PF-44, PF-96 | Event / Data (same core) / Platform Layer | 📝 | [PM-53 Refund, Recoupment & Takeback Management](./refund-recoupment-takeback-management-integration.md) · [Spec](../../../specs/pm/specs/PM-53-refund-recoupment-takeback-management.md) - Publishes `payment_refund_issued` (FA consumes → GL journal entry writeback) and `payer_recoupment_detected` (PM-44 consumes → exclude active recoupment lines). 3 tables (`pm_refunds`, `pm_refund_approvals`, `pm_payer_recoupments`); multi-tier refund approval state machine; CARC `CO-45/100/104` + PLB `WO/50/72` takeback detection inside `process-era`; PM-29 dispute pre-population; 5 permission keys (`pm.refunds.view/create/approve`, `pm.recoupments.view/manage`); jurisdiction-aware dispute deadlines via PF-96; contextual contract rate interpretation via PM-44 (which depends on PM-23). Supersedes lite alternatives `PM-09-EN-11` and `PM-09-EN-15`. | \| PM (PM-49) | PM-19, PM-29, PM-09, PM-45, PM-11, PF-01, PF-02, PF-10, PF-29, PF-96 | Event / Data (same core) / Platform Layer / Scheduled Edge Function | 📝 | [PM-49 Revenue Cycle Automation Rules Engine](./revenue-cycle-automation-rules-engine-integration.md) - Configurable RCM rules engine: small balance auto-adjust, denial resubmit via PM-29, collections transfer via PM-45, dynamic AR work queue scoring; 3 tables, 3 edge functions, 3 consumed events, 1 published event; PF-96 filing deadline resolution | \| PM (PM-49) | PM-19, PM-29, PM-09, PM-45, PM-11, PF-01, PF-02, PF-10, PF-29, PF-96 | Event / Data (same core) / Platform Layer / Scheduled Edge Function | ✅ | [PM-49 Revenue Cycle Automation Rules Engine](./revenue-cycle-automation-rules-engine-integration.md) - Configurable RCM rules engine: small balance auto-adjust, denial resubmit via PM-29, collections transfer via PM-45, dynamic AR work queue scoring; 3 tables, 3 edge functions, 3 consumed events, 1 published event; PF-96 filing deadline resolution. Completed 2026-04-08 | \| PM (PM-47) | PM-08, PM-10, PM-01, PF-10, PF-29 | Data (same core) / Platform Layer / Scheduled Edge Function | ✅ | PM-47 Managed Care Authorization Tracking — Auth lifecycle dashboard, concurrent review scheduling, denial appeals, auth-to-claim validation gate (pm-auth-claim-validation edge function), expiration alerts (pm-auth-expiration-alerts cron); 3 tables, 2 edge functions, 7 permissions. Completed 2026-04-08 | \| PM (PM-26) | PF audit, PM-08, PM-09, PM-11 | Data (same core) / Platform Layer | ✅ | PM-26 Audit Trail & Compliance Reporting — Centralized billing audit log (pm\_audit\_log), compliance reports, payer audit export, internal controls, fraud/abuse flags. Completed 2026-03-01 | \| PM (PM-31) | PM-07, PM-08, PM-09, PM-10, PM-15, PM-18, CL-17 (UUID ref), PF-70 | Data (same core) / Platform Layer / Cross-core UUID ref | ✅ | [PM-31 OTP/MAT-Specific Billing](./otp-mat-billing-integration.md) — OTP program config (G2067–G2080, G2215/G2216, H0020, T1012), weekly/daily billing periods, service components, charge/claim generation via PM-07/PM-08, PM-10 prior auth, CL-17 PDMP reference (ADR-002 UUID, no FK). Completed 2026-03-26 | \| PM (PM-34) | PM-02, PM-03, PM-07, PM-12, PF-10, PM-28 | Event / Data / Platform Layer | ✅ | [PM-34 Real-Time Eligibility at Check-In](./realtime-eligibility-checkin-integration.md) - Auto-triggers PM-02 on PM-03 checked\_in status; discrepancy detection (new plan, copay/deductible change, coverage gap, COB order change); pm\_checkin\_discrepancies; PF-10 notification to front desk; copay feed to PM-07 charge defaults; kiosk/portal trigger via PM-12; PM-28 configures timeout and notification. Completed 2026-03-26 | \| PM (PM-34-EN-01) | PM-01, PM-02, PM-03, PM-09, CL-11, PF-10, PF-11, PM-28 | Data / Platform Layer | ✅ | PM-34-EN-01 Check-in Kiosk Self-Service — patient self-service check-in with demographics review, insurance card capture (PF-11), consent signing (CL-11 via @/platform/clinical), copay collection (PM-09), arrival notification (PF-10), kiosk device config (PM-28). 1 table (pm\_kiosk\_checkins), 5 settings columns, 9 hooks, 15 components, 2 permissions, 59 tests. Completed 2026-04-10 | \| PM (PM-35) | PM-07 (charge snapshot), PM-25 (VBP consumer), FA-35 (event) | Event / Data (same core) | ✅ | [PM-35 Encounter-Level Cost Accounting](./cost-accounting-integration.md) - Cost categories, rates, auto-calculation on encounter\_completed; pm\_encounter\_costs; encounter\_cost\_calculated event to FA-35; margin analysis (cost vs charge); PM-25 reads pm\_encounter\_costs for TCOC benchmarking. Completed 2026-03-28 | \| PM (PM-30) | PM-01, PM-02, PM-07, PM-08, PM-09, PM-15, PM-16 | Data (same core) | ✅ | [PM-30 COB & Secondary Claims](./coordination-of-benefits-secondary-claims-integration.md) — COB priority order (pm\_insurance\_policies.priority\_order); secondary/tertiary 837P/837I claim generation from primary ERA (COB2300/COB2400); Medicare–AHCCCS dual-eligible crossover; secondary ERA posting and patient balance update (PM-09, PM-16). Completed 2026-03-27 | \| PM (PM-32) | PM-01, PM-02, PM-16, PM-20, PM-21, PF-08, PF-10 | Data (same core) / Platform Layer | ✅ | [PM-32 Patient Financial Counseling & Charity Care](./patient-financial-counseling-integration.md) — Financial counseling sessions with FPL calculation (pm\_fpl\_thresholds); assistance program referral tracking (AHCCCS, Medicare Savings, ACA, LIAP); charity care applications per board policy; PM-16 live join for charity indicator; PM-21 FPL-based sliding fee; PM-02 policy linkage on referral approval; PF-10 expiration reminders; HRSA FQHC compliance workflow. Completed 2026-03-26 | \| CL (CL-02) | PF-01, PF-02, PF-08, PF-33, PF-10, CL-01, CL-03, CL-07 | API / Event | ✅ | [CL-02 Comprehensive Assessments](./comprehensive-assessments-integration.md) - 18-element assessments, CALOCUS/ASAM, expiration alerts, signatures; events to CL-03, CL-07 | \| CL (CL-02-EN-60) | PF-96 | Platform Layer / RPC | ✅ | [CL-02-EN-60 Jurisdiction-Aware Assessment Requirements](./jurisdiction-aware-assessment-requirements-integration.md) - `useClinicalRules()` + `pf_resolve_jurisdiction_profile()` RPC for dynamic required elements; `cl_check_intake_elements` generic function; `intake_element_complete` column; AZ 18-element parity preserved as default profile. Complete 2026-04-03. | \| CL (CL-02-EN-61) | PF-96, CL-02-EN-60 | Platform Layer / Merge Engine | ✅ | [CL-02-EN-61 Integration](./configurable-clinical-assessment-templates-integration.md) — Configurable clinical assessment templates; `cl_assessment_templates` + `cl_assessment_template_sections` tables; `mergeAssessmentSections` pure engine combining jurisdiction-required + org template sections; editor/list/version-history UI at `/cl/settings/assessment-templates`; 22 unit tests. Complete 2026-04-03. | \| CL (CL-02-EN-59) | CL-02 (parent) | CL-internal | ✅ | CL-02-EN-59 Cognitive Screening Instruments — MoCA, SLUMS, MMSE seed into `cl_assessment_instruments`; `cognitiveScoring.ts` (6 pure scoring/threshold functions); `CognitiveAssessmentForm` + `CognitiveResultAlert` UI; 42 CFR Part 2 consent gating via `cl_has_sud_consent`; `cl_assessment_completed` event; 25 unit tests. Complete 2026-04-04. | \| CL (CL-03) | PF-01, PF-02, PF-33, PF-10, CL-01, CL-02, CL-04 | API / Event | ✅ | [CL-03 Treatment Planning](./treatment-planning-integration.md) - Measurable goals, signatures, appeal rights, multi-disciplinary sign-off; review-due and event-triggered alerts; CL-02 findings, CL-04 progress; **Phase 2-3:** Goal progress viz, caregiver tracking, life-event automation, template library | \| CL (CL-04) | PM (PM-07), PF-10, PF-33, HR-19, CL-01, CL-03 | Event / API | 📝 | [CL-04 Progress Notes & Session Documentation](./progress-notes-session-documentation-integration.md) - clinical\_note\_finalized event for charge capture; co-sign workflow (HR-19); signatures (PF-33); alerts (PF-10) | \| CL (CL-04-EN-67) | PF-96 | Platform Layer | ✅ | [CL-04-EN-67 Integration](./jurisdiction-aware-progress-note-requirements-integration.md) — `useNoteRequirements` hook consuming `useClinicalRules()` + `useComplianceRules()` from PF-96; profile-driven attestation text, required note elements (12-element model), policy citation metadata, mandatory validation flag; `note-requirements-resolver.ts` pure functions with AZ AHCCCS fallbacks; 11 unit tests. Complete 2026-04-04. | \| CL (CL-05) | CL-01, CL-06, CL-08, CL-09, CL-12 | API / Data | 📝 | [CL-05 Medication Management](./medication-management-integration.md) - Medication list, reconciliation at transitions, drug interaction (RxNav/NLM), monitoring protocols; CL-12 triggers reconciliation | \| CL (CL-05-EN-01) | CL-05, CL-06, CL-08, CL-11, PM-10, PF-01, PF-96, External (FDB/Medi-Span) | API / External / Platform Layer | ✅ | [CL-05-EN-01 DDI Checking](./drug-drug-interaction-checking-integration.md) - Real-time DDI alerts during medication entry/reconciliation (CL-05) and e-prescribing (CL-06); override documentation with co-signature for contraindicated; provider alert suppression for minor interactions; CL-08 CDS delegates `drug_interaction` rule type; CL-11 consent gating for SUD meds (42 CFR Part 2); jurisdiction-aware (PF-96). Migration (`cl_ddi_overrides`, `cl_ddi_alert_suppressions`), types, 3 hooks, 3 UI components (DdiAlertPanel, DdiOverrideDialog, DdiSuppressionSettings), 4 permissions, 26 unit tests. Complete 2026-04-13. | \| CL (CL-06) | CL-01, CL-05, CL-08, CL-17, Surescripts (external) | API / External | 📝 | [CL-06 E-Prescribing (EPCS)](./e-prescribing-epcs-integration.md) - Prescription routing, EPCS, RTPB; medication list (CL-05), CDS (CL-08), CSPMP (CL-17) | \| CL (CL-07) | PF-10, PF-33, CL-01, CL-13 | Event / API | ✅ | [CL-07 Suicide Risk Screening & Safety Planning](./suicide-risk-screening-safety-planning-integration.md) - C-SSRS/PHQ-9/ASQ/SAFE-T; Stanley-Brown safety plan; high/imminent alerts (PF-10); signatures (PF-33); risk flag (CL-01); **EN-23–EN-26 (Phase 1, no domain events; PF-10 via direct `pf_notifications` insert):** lethal means counseling on `cl_safety_plans`, clinician-initiated patient PDF view, family notification (`cl_designated_contacts` + `cl_family_notification_log`, consent-gated), 988 transfers (`cl_988_transfers`, HCPCS free-text — PF-70 deferred). See [CL-07-ENHANCEMENTS-CONTEXT.md](../../../specs/cl/specs/CL-07-ENHANCEMENTS-CONTEXT.md). | \| CL (CL-07-EN-01) | PF-01, PF-10, PF-96, PM-03, CL-07, CL-11 | Platform Layer / Event | ✅ | [CL-07-EN-01 Zero Suicide Framework](./zero-suicide-framework-integration.md) — Lethal means assessment instrument (`cl_lethal_means_assessments`), safety plan emergency contact sharing (`cl_safety_plan_shares`) with Part 2 consent gating (CL-11 `useConsentCheck`), automated 24/48/72 follow-up scheduling (PM-03 via `@/platform/scheduling`). Share uses Supabase Storage signed URL + PF-10 `action_url`. Events: `cl_safety_plan_shared`, `cl_zero_suicide_followup_scheduled`. Extends CL-07 EN-23 (assessment instrument) and EN-24 (emergency contact sharing). | \| CL (CL-08) | CL-01, CL-05, CL-06, CL-10, PF-10, PF-70, RxNav (external) | API / Event / Edge Function | ✅ | [CL-08 Clinical Decision Support](./clinical-decision-support-integration.md) - Drug/allergy alerts, monitoring reminders, documentation/quality gaps; CL-05/CL-06 trigger; PF-10 delivery; CL-10 quality data; **EN-27:** evaluate-cds Edge Function (RxNav); **EN-28:** pathway guidance; **EN-29:** alert fatigue analytics | \| CL (CL-09) | CL-01, CL-05, CL-08, PF-10, External Labs | Event / API / External | 📝 | [CL-09 Lab & Diagnostic Orders](./lab-diagnostic-orders-results-integration.md) - Lab orders, result ingestion (HL7v2/FHIR), trending; CL-08 abnormal alerts; CL-05 monitoring protocols | \| CL (CL-09-ENH) | CL-09 (internal) | CL-internal | ✅ | CL-09-ENHANCEMENTS (EN-30, EN-31, EN-32): Standing order protocols, POC result entry, reference range customization. No cross-core deps beyond parent CL-09. Complete 2026-02-26. | \| CL (CL-10) | PF-01, PF-02, PF-12, CL-01, CL-02, CL-03, CL-12, CL-15, RH | Data / Platform | 🏗️ | [CL-10 Outcomes Tracking & Measurement](./outcomes-tracking-measurement-integration.md) - PROMs, HEDIS (FUH/FUM/IET/AMM), program outcomes; RH program\_id FK; CL-12 transitions; CL-15 quality reporting. **CL-10-ENHANCEMENTS** (EN-1, EN-2): Performance instrumentation, SAMHSA NOMs/CBE/HEDIS MY 2026 terminology, source tags. Complete 2026-02-26. | \| CL (CL-12) | PF-01, PF-02, PF-10, PF-11, CL-01, CL-03, CL-05, CL-07, CL-16, PM-06 | Event / Data / API | 📝 | [CL-12 Care Coordination & Transitions](./care-coordination-transitions-integration.md) - Care teams, transitions, discharge checklist, FUH 7/30-day; referral\_accepted (PM-06); C-CDA/ADT (CL-16) | \| CL (CL-12-EN-67) | CL-12, PM-06, FindTreatment.gov (external) | Data / External API | ✅ | [CL-12-EN-67 Integration](./bidirectional-referral-community-integration.md) — Closed-loop referral status tracking (`cl_referral_status_history`); `cl_referral_current_status` view; optional FindTreatment.gov directory search edge function; `cl_referral_status_updated` event. Complete 2026-04-14. | \| CL (CL-15) | PF-12, CL-10, CL-01, CL-02, CL-03, CL-04, GR-03, GR-08, PF-10, CL-13 | Platform Layer / Event / Data | ✅ Phase 1 / 🏗️ Phase 2-3 partial | [CL-15 Clinical Reporting & Quality Measures](./clinical-reporting-quality-measures-integration.md) - Phase 1 (✅): Report definitions, runs, AZDHS incidents; PF-12 report engine; CL-10 outcome data for HEDIS/CARF; `cl_incident_reported` event consumed by GR (compliance/accreditation) and PF-10 (notifications). Phase 2/3 (🏗️ partial, see [CL-15-PHASE-2-3-EXPANSION](../../../specs/cl/specs/CL-15-PHASE-2-3-EXPANSION.md)): **shipped 2026-05-18** — `cl_module_settings` dual-track columns + dual-track deadline util + CL settings dual-track subsection + patient-context portal QM view. **Pending** — T5 clinical\_audit report renderer, T7 deployment guide, T9 automated HEDIS QM, T10 CarfReadinessPage. **Blocked on CL-13** — T2 restraint\_event\_id migration, T4 restraint picker. Last verified: 2026-05-18 | \| CL (CL-16) | CL-01, CL-11, CL-12, PM-10 | API / Event | 🟡 | [CL-16 FHIR Interoperability](./fhir-interoperability-data-exchange-integration.md) - Phase 1 (FHIR R4 facade, schema, RLS) in progress; Edge Function `fhir-r4` deployed; consent gating (CL-11); API contracts in [API\_CONTRACTS.md](./API_CONTRACTS.md#cl-16-fhir-r4-api--edge-function-facade); events: `cl_fhir_bundle_exported` (Phase 1), `cl_ccda_document_sent`/`cl_ccda_document_received` (Phase 2) in [EVENT\_CONTRACTS.md](./EVENT_CONTRACTS.md#cl-16-fhir-interoperability--data-exchange-events); Phase 2 (C-CDA/HIE) blocked on Contexture; Phase 3 (Da Vinci) blocked on PM-10. Last verified: 2026-02-23 | \| CL (CL-16-EN-01) | CL-16, CL-11, CL-12, PM-10, PF-04, PF-11 | API / Event | ✅ | [CL-16-EN-01 TEFCA/QHIN Connectivity](./tefca-qhin-connectivity-integration.md) - TEFCA exchange log, patient matching, consent-gated outbound exchange, 42 CFR Part 2 redisclosure notices, HIPAA minimum necessary filter, exchange telemetry; extends CL-16 without duplicating CL-11 consent ownership. Last verified: 2026-04-09 | \| CL (CL-17) | CL-06, CL-01, External (PMP Gateway/NABP, Bamboo Health, Arizona HIE) | API / External | 🏗️ | [CL-17 Arizona CSPMP/PDMP](./arizona-cspmp-pdmp-integration-integration.md) - PDMP query-in-workflow, prescriber attestation, delegate access; A.R.S. § 36-2606; scaffold complete (DB, RLS, hooks, UI, routes, edge fn scaffold); gateway integration pending vendor selection. Last verified: 2026-02-24 | \| CL (CL-18) | PF-01, PF-02, PF-08, PF-70, CL-01, CL-02 | API / Data / Event | ✅ | [CL-18 SDOH Screening & Social Needs](./sdoh-screening-integration.md) - SDOH screening, referrals, Z-codes (PF-70); chart/assessment visibility; optional `cl_sdoh_screening_completed` event (deferred). Last verified: 2026-02-23 | \| CL (CL-19) | CL-01, CL-04, CL-11, PM-03, PM-07, PF-70 | Event / Data / Platform | ✅ | [CL-19 Peer Recovery Support](./peer-recovery-support-services-integration.md) - Peer encounter docs; encounter-to-billing (PM-07); HCPCS (PF-70); Part 2 (CL-11). Last verified: 2026-02-23 | \| CL (CL-40) | CE-28, PM-38, CL-18, CL-19, PM-07, PF-33, PF-70 | Event / Data / Platform | ✅ | [CL-40 Clinical Intake & SDOH](./clinical-intake-integration.md) - Intake orchestrator; consumes pm\_appointment\_created + ce\_screening\_completed; publishes cl\_intake\_finalized, cl\_sdoh\_referral\_created, cl\_peer\_encounter\_documented; PF-70 (ICD-10); PF-33 (e-sig); Part 2 (CL-11). Last verified: 2026-03-29 | \| CL (CL-20) | PF-64, PF-11, CL-01, CL-02, CL-03, CL-04, CL-07, CL-11, CL-13, CL-14 | Platform Layer / Data | ✅ | [CL-20 Medical Record Export & Document Generation](./medical-record-export-document-generation-integration.md) - Per-document and full chart PDF export; PF-64 templates; Part 2 consent (CL-11). Last verified: 2026-02-23 | \| CL (CL-21) | CL-05, CL-06, CL-10, CL-11, PM-07, PF-10, PF-70 | Data / Platform / Event | ✅ | [CL-21 MAT/MOUD Tracking](./medication-assisted-treatment-moud-tracking-integration.md) — MAT enrollment, medication/monitoring events; CBE #3400 (CL-10); consent (CL-11); charge triggers (PM-07); alerts (PF-10). **Breakdown by type:** Data → CL-05, CL-06, CL-10, CL-11; Event → PF-10; API → PM-07; Platform → PF-10, PF-70 (see integration doc). Last verified: 2026-02-23 | \| CL (CL-36) | CL-04, CL-11, CL-14, CL-24, PF-01, PF-02, PF-27, PF-30, pm\_encounters, External AI Vendors | Data / Platform / API (edge fn) | ✅ | [CL-36 AI-Assisted Clinical Documentation](./ai-documentation-integration.md) — AI draft generation from structured encounter data; ambient voice integration (Phase 3); attribution + attestation (`cl_ai_note_attributions`); Policy 940 quality validation; 42 CFR Part 2 consent gate (CL-11); tenant opt-in; PHI via edge function only. **No PHI may be sent to any external AI vendor until a BAA is fully executed** (CL-36 NFR-4; HIPAA 45 CFR 164.502(e)). See [REGULATORY\_COMPLIANCE\_TRACKER.md](../../compliance/REGULATORY_COMPLIANCE_TRACKER.md) — "HIPAA — AI Vendor BAA" row for consistency. | \| CL (CL-36-EN-01) | CL-36 (parent), CL-04, CL-11, PF-01, PF-02, PF-30, pm\_encounters | Data / Platform | ✅ | CL-36-EN-01 AI Ambient Listening & Auto-Documentation — 3 tables (`cl_ambient_sessions`, `cl_ambient_transcripts`, `cl_ambient_session_events`); SOAP structuring; review queue/detail UI; ambient settings; 5 permissions (`cl.ambient.*`); RLS with SECURITY DEFINER helpers; 29 unit tests. Completed 2026-04-09. | \| PF (PF-100) | PF-01, PF-04, PF-10, PF-27, PF-30, PF-46, PF-66, PF-70, PF-71, PF-76, PF-91, PF-93, PF-95, PF-96, CL-11, CL-36, CL-36-EN-01, pm\_encounters, External AI Vendors (Deepgram, AssemblyAI, AWS Bedrock/Transcribe Medical/HealthScribe, Recall.ai, Plaud) | Platform Layer / Event / Data / API (edge fn) | 🚧 | [PF-100 Platform Ambient Recording, Transcription & AI Note Generation](./platform-ambient-transcription-integration.md) — Productizes CL-36's ambient pipeline as a PF capability consumable by CL/PM/HR/GR/CE/RH via `@/platform/transcription`. 14 `pf_transcription_*` tables; 16 permission keys (`pf.transcription.*`); 10 published events + 3 consumed events (`pf.transcription.session.*`, `.draft.*`, `.audio.*`, `.deletion_*`, `.policy.*`); per-tenant + Part-2 KMS aliases; vendor BAA matrix enforcement (PF-91); right-to-deletion processing. **Phase 3 CL-36 backend swap is non-breaking** — `cl_ambient_*` tables become VIEWs over `pf_transcription_*` (`module_key='cl'`) per ADR-002 (PF→PM `encounter_id` is a UUID with no FK; CL→PM FK preserved on the CL projection independently). 42 CFR Part 2 segmentation post-deadline remediation tracked in `REGULATORY_COMPLIANCE_TRACKER.md`. **No PHI may be sent to any external AI vendor until a BAA is fully executed** (HIPAA 45 CFR 164.502(e)). | \| CL (CL-34) | CL-09, CL-21, CL-04, CL-11, CL-33, PM-07, PF-01, PF-02, PF-10, PF-30 | Data / Event / API / Platform | ✅ | [CL-34 Drug Testing / UDS Workflow](./drug-testing-uds-workflow-integration.md) — UDS orders with chain-of-custody; presumptive/definitive ordering; results interpretation (CL-05 cross-check); MOUD unexpected-negative alerts (CL-21 + PF-10); court-reportable flag → CL-33; billing CPT/G-codes → PM-07; Part 2 consent gating (CL-11). Migration, types, hooks, UI, RLS tests complete. Event/API contracts: planned for Phase 2. | \| CL (CL-22) | CL-01, CL-08, CL-09, CL-10, CL-11, CL-16, PF-01, PF-02, PF-10, PF-70 | Data / Platform | ✅ | [CL-22 Vital Signs & Biometric Tracking](./vital-signs-biometric-tracking-integration.md) — Vitals, biometrics, metabolic monitoring; chart display (CL-01); CDS thresholds (CL-08); lab linkage (CL-09); outcomes inputs (CL-10); consent for metabolic events (CL-11); FHIR Observation mapping (CL-16). All integrations intra-CL or PF; no cross-core dependencies. Last verified: 2026-02-23 | \| CL (CL-24) | PF-01, PF-02, CL-04, CL-07, CL-11, CL-14, PM (PM-07) | Data / API | 📝 | [CL-24 Telehealth Documentation & Compliance](./telehealth-documentation-compliance-integration.md) — Telehealth consent, session modality/location; GT/95 modifier logic (PM-07); CL-04 progress note link; CL-07 safety; CL-11/CL-14 consent and group telehealth | \| CL (CL-25) | PF (audit), PF-01, CL-04, CL-07, CL-11, CL-15 | Data / Platform Layer | ✅ | [CL-25 Clinical Audit & Compliance Dashboard](./clinical-audit-compliance-dashboard-integration.md) — Read from pf\_audit\_logs and CL tables; break-glass review queue; anomaly detection RPC. Complete 2026-04-01 | \| CL (CL-26) | CL-02, CL-03, CL-07, CL-10, CL-11, CL-23, PM-12, PM-14 | Platform Layer / Data / Event | ✅ | [CL-26 Patient-Reported Outcomes & Self-Service Portal](./patient-reported-outcomes-self-service-portal-integration.md) — Patient screenings, check-ins, treatment plan view, consent self-service, messaging (PM-14), crisis resources; in-basket (CL-23); portal identity (PM-12) | \| CL (CL-27) | PF-01, CL-14, PM-03, PM-04, RH | Data / Platform / Event | ✅ | [CL-27 Behavioral Health Program Scheduling Templates](./behavioral-health-program-scheduling-templates-integration.md) — Program templates (IOP/PHP/residential/outpatient), enrollment, group session auto-creation (CL-14), conflict check (PM-03/PM-04), RH census alignment. Last verified: 2026-02-25 | \| CL (CL-29) | PF-01, CL-12, CL-03, CL-07, CL-10, CL-18, RH | Data / Event | ✅ | [CL-29 Discharge & Aftercare Planning](./discharge-aftercare-planning-integration.md) — Aftercare plans, follow-up contacts (HEDIS FUH), readmission risk; transition link (CL-12); housing coordination at residential discharge (RH). **Event contracts:** Discharge.AftercarePlan.Finalized (platform.events.aftercare; publisher CL-29, subscribers RH, reporting); RH.Referral.Status (platform.events.referrals; publisher RH, subscriber CL-29). Integration owners: CL team (CL-29), RH team (referral status). | \| CL (CL-29-EN-65) | CL-29, CL-15, CL-35, PM (via platform), PF-70 | Data / Platform Layer | ✅ | [CL-29-EN-65 HEDIS FUH/FUM Tracking](./hedis-fuh-fum-tracking-integration.md) — HEDIS FUH/FUM flag columns on `cl_aftercare_plans`; `cl_hedis_fuh_fum_summary` view (security\_invoker); CL-15 and CL-35 consume view for rates/export and care gap. Permission gates: `cl.hedis-tracking.view`, `cl.hedis-tracking.export`. ⚠️ AHCCCS HEDIS FUH/FUM MY 2025 reporting deadline: June 15, 2026 (9:00 PM ET), subject to final confirmation — track in [REGULATORY\_COMPLIANCE\_TRACKER](../../compliance/REGULATORY_COMPLIANCE_TRACKER.md); confirm HOQ (House of Quality) status. | — HEDIS FUH/FUM flag columns on `cl_aftercare_plans`; `cl_hedis_fuh_fum_summary` view (security\_invoker); CL-15 and CL-35 consume view for rates/export and care gap. Permission gates: `cl.hedis-tracking.view`, `cl.hedis-tracking.export`. ⚠️ AHCCCS HEDIS FUH/FUM MY 2025 reporting deadline: June 15, 2026 (9:00 PM ET), subject to final confirmation — track in [REGULATORY\_COMPLIANCE\_TRACKER](../../compliance/REGULATORY_COMPLIANCE_TRACKER.md); confirm HOQ (House of Quality) status. | \| CL (CL-31) | CL-02, CL-03, CL-04, CL-11, CL-15, CL-21, PF-01, PF-02, PF-30 | Data / Platform | ✅ | [CL-31 Spec/Integration Document](../../../specs/cl/specs/CL-31-co-occurring-disorder-integrated-documentation.md) — Complete 2026-05-12. Extends CL-02 (COD assessment tab + ASI-6/BASIS-32/GAIN-SS), CL-03 (treatment plan extension), CL-04 (progress note SUD section, consent-gated via CL-11 `cl_check_sud_consent()`), CL-15 (IET-COD HEDIS measure in `cl-hedis-calculator`); MOUD link via CL-21 FK. **Intra-CL only; no separate `CL-31-*-INTEGRATION.md` doc required** (no cross-core FKs, no published domain events; SUD redaction is request-time, not event-driven). | \| CL (CL-35) | CL-02, CL-03, CL-07, CL-10, CL-15, CL-22, PF-01, PF-02, PF-30 | Data / Platform Layer / Event | ✅ | [CL-35 Integration](./population-health-integration.md) — Phase 2/3 complete: cl\_risk\_stratifications, cl\_quality\_measure\_periods tables; dashboard, quality measures, clinician panel, supervisor panels pages; cl-risk-stratification and cl-hedis-calculator edge functions; FA VBP event contract. Last verified: 2026-04-01 | \| CL (CL-04-EN-66) | CL-04, PF-02, PF-30, PF-70, PF-10 | Platform Layer / Data | ✅ | [CL-04-EN-66 Note Quality Pre-Submission Validation](./note-quality-pre-submission-validation-integration.md) — Pre-finalize Policy 940 validation gate on `cl_progress_notes`; INSERT-only override audit `cl_note_940_override_audit`; org-configurable enforcement (block/warn); break-glass with PF-10 notification; credential check (PF-02); diagnosis match (PF-70). Complete 2026-04-03 | \| CL (CL-11-EN-01) | CL-11, PF-01, PF-02, PF-04, CL-16 | Data / Platform Layer | ✅ | [CL-11-EN-01 Electronic Consent & Redisclosure](./electronic-consent-42cfr-redisclosure-integration.md) — E-signature consent capture (`cl_electronic_consents`); 42 CFR Part 2 redisclosure chain-of-custody (`cl_redisclosure_log`, append-only); extends CL-11 consent framework; deferred CL-16 HIE coordination. Complete 2026-04-10 | \| CL (CL-14) | CL-01, CL-03, CL-11, PM-04, PM-07 | Platform Layer / Data | ✅ | [CL-14 Group Therapy Documentation](./group-therapy-documentation-integration.md) - Group sessions, attendance, individual documentation; Part 2 consent (CL-11); scheduling (PM-04); billing/HQ (PM-07). **CL-14-ENHANCEMENTS:** Curriculum library (cl\_group\_curricula), outcome metrics dashboard, family/multi-family group subtype. Last verified: 2026-02-26 | \| CL (CL-14-EN-01) | CL-14, PM-07, PM-08, CL-39, PF-70, PF-96 | Event / Data / Platform | ✅ | [CL-14-EN-01 Group Encounter Generation](./group-encounter-generation-integration.md) — Auto-generates `pm_encounters` + `cl_group_encounter_generations` from group attendance; consumes `cl_group_session_documented`; publishes `cl_group_encounters_approved` → PM-07 charge creation; batch review/reconciliation UI; jurisdiction-aware CPT proposal (PF-96). Complete 2026-04-09 | \| PM, CL | Platform / PM, CL | API | 📝 | [API Contracts](./API_CONTRACTS.md#planned-api-contracts-clpm-ehr--practice-management) - Eligibility check, Claim status, Consent check, Document export, Patient demographics | \| PM (PM-05) | PM-03, PM-04 | Data / API | ✅ | [PM-05 Provider Schedule & Availability](./provider-schedule-availability-integration.md) — Availability consumed by appointment and group scheduling. Complete 2026-02-20 | \| PM (PM-05) | HR-04 | Boundary | ✅ | [PM-05 Provider Schedule & Availability](./provider-schedule-availability-integration.md) — No shared tables; HR-04 may consume availability for display. Complete 2026-02-20 | \| PM (PM-04) | CL (CL-14) | Data / Platform | 📝 | [CL-PM Group Sessions](./CL-PM-GROUP-SESSIONS.md) - Group scheduling (PM-04) vs clinical documentation/attendance (CL-14); ownership boundaries and schedule\_id linkage | \| PF-27/PF-59 | All Cores | API (Edge Functions) | ✅ | [API Contracts](./API_CONTRACTS.md#pf-59-ai-edge-functions-openrouter) - AI Edge Functions (OpenRouter) | \| PF-30 | All Cores | API (DB Function) | 🟡 | [API Contracts](./API_CONTRACTS.md#pf-30-permission-check-api) - Phase 1 Complete | \| PF-30 | PF-26 | Direct Dependency | 🟡 | Three-tier permission check integration (Phase 2) | \| PF-30 | PF-02 | Direct Dependency | 🟡 | System role integration (Phase 2) | \| FA | RH | API | 🟡 | [API Contracts](./API_CONTRACTS.md#fa-01-episode-balance-query) — Edge function `fa-episode-balance` (cached `rh_episode_payment_status`; FA AR linkage 📋) | \| FA-UX-05 | FW-03 | API | 📝 | [FA-UX-05 / FW-03 Integration](./FA-UX-05-FW-03-INTEGRATION.md) - Purchase Order Approval Submission | \| HR | RH | API | 📝 | [API Contracts](./API_CONTRACTS.md#hr-01-employee-lookup) | \| HR | RH | API | 📝 | [API Contracts](./API_CONTRACTS.md#hr-01-employee-search) | \| RH | CL | API | 📝 | [API Contracts](./API_CONTRACTS.md#rh-01-current-residencebed-query-cl-chart--optional) | \| HR | FA | Platform Layer | 📝 | [HR-PAY-03 Integration](./HR-PAY-03-direct-deposit-INTEGRATION.md) - Direct deposit & Plaid (FA-20). **Security:** AES-256-GCM encryption (NIST SP 800-38D) for `plaid_access_token_encrypted` and `account_number_encrypted`; key rotation via Supabase Vault (annual or on compromise); SOC 2 Type II and PCI-DSS compliance; all operations audit-logged to `pf_audit_logs`; Plaid tokens retained per NACHA/Open Finance Data Security Standard (max 7 years or per org policy). | \| HR (HR-PAY-03) | HR (HR-12) | In-App | 📝 | [HR-PAY-03 Integration](./HR-PAY-03-direct-deposit-INTEGRATION.md) - Pay stubs & bank accounts (self-service) | \| HR-11 | HR-PAY-02 | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#hr-11--hr-pay-02-benefit-enrollment-events-payroll-deductions) - Benefit enrollment created/terminated → auto-create or end-date deductions | \| HR-PAY-02 | HR-07 | Data | ✅ | [HR-PAY-02 Integration](./HR-PAY-02-payroll-deductions-INTEGRATION.md) - Payroll run consumes deductions; creates deduction items and YTD updates | \| HR-PAY-02 | HR-PAY-01 | Data | ✅ | [HR-PAY-02 Integration](./HR-PAY-02-payroll-deductions-INTEGRATION.md) - Pre-tax deductions reduce taxable income before tax calculation | \| HR-PAY-02 | PF-11 | Outbound | ✅ | [HR-PAY-02 Integration](./HR-PAY-02-payroll-deductions-INTEGRATION.md) - Court order document storage; link via custom\_fields on employee deduction | \| HR | FA | Event | ✅ | [Event Contracts](./EVENT_CONTRACTS.md#hr-pay-04-employer-tax-liability-events-tax-forms-compliance) - hr.employer\_tax\_liability.calculated (HR-PAY-04 → FA; Phase 2/3 e-filing + multi-state W-2 complete). See HR-PAY-03 security constraints for payroll data handling. | \| HR-34 | HR-PAY-04, PF-10, HR-02 | Platform Layer / Data / Event | ✅ | [HR-34 Integration](./contractor-contingent-workforce-integration.md) - Contractor profiles, contracts, classification, approved time → 1099-NEC inputs via `hr_get_contractor_1099_totals` RPC ([API\_CONTRACTS](./API_CONTRACTS.md#hr-34-contractor-1099-totals-rpc)); renewal/credential notifications via PF-10; event stubs: `hr_contractor_created`, `hr_contractor_contract_renewal_due`, `hr_contractor_credential_expiring` ([EVENT\_CONTRACTS](./EVENT_CONTRACTS.md#hr-34-contractor--contingent-workforce-events)); credential types FK → HR-02. Complete: schema, hooks, UI, routes, notifications, 1099 export, 62 tests, compliance evidence. | \| IT | IT-02, IT-05 | API | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-01-asset-lookup-api) - Asset lookup | \| IT | IT-01, IT-04, IT-06 | API | 📝 | [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-03-vendor-lookup-api) - Vendor lookup | \| **External API Integrations** | \| HR | Checkr (External) | API (Edge Function) | 📝 | HR-20 Checkr Integration (superseded by HR-09-P5.2; archived at `docs/archive/architecture/integrations/HR-20-checkr-background-check-INTEGRATION.md`) | \| FA | Ramp (External) | API (Edge Function) | ✅ | [FA-30 Ramp Corporate Cards & Spend](./ramp-integration.md) - Card transaction sync, connection management; FA-12 Phase 2 corporate card integration | **Legend:** * ✅ **Implemented** - Fully implemented and tested * 📝 **Planned** - Specified but not yet implemented * 📋 **Draft/Spec** - Specification complete, implementation not started * 🟡 **In Progress** - Partially implemented * 🚧 **Work in progress / partial delivery** - Active development with partial feature delivery *** ## Encounter Lifecycle (CL-PM) The encounter (`pm_encounters`, owned by PM) is the canonical entity linking scheduling, clinical documentation, and billing. State transitions are driven by events and platform layer usage. ```mermaid theme={null} stateDiagram-v2 scheduled --> checked_in: pm_appointment_checked_in checked_in --> in_progress: CL documentation started in_progress --> documented: clinical_note_finalized documented --> charge_captured: PM-07 charge capture charge_captured --> billed: PM-08/PM-15 claim submission billed --> claimed: claim submitted claimed --> adjudicated: claim_adjudicated (ERA/835) scheduled --> no_show: pm_appointment_no_show scheduled --> cancelled: appointment cancelled ``` **References:** [CL-PM Encounter-to-Billing](./CL-PM-ENCOUNTER-TO-BILLING.md), [ADR-002](../decisions/ADR-002-cl-pm-cross-core-foreign-keys.md) (cross-core FK exception for encounter references). *** ## Integration by Core ### RH (Recovery Housing) **Integration Doc:** [RH-01 Bed Board & Census Integration](./bed-board-census-integration.md) **Facility Types (added RH-01.1):** * `recovery_housing` (POS 55) — NARR Level 2/3 recovery housing * `psychiatric_residential` (POS 56) — Behavioral health residential (RTC/BHRF) * `inpatient_unit` (POS 51) — Inpatient psychiatric unit **Bed Board:** `/rh/bed-board` — real-time board with facility\_type filter, accessible from RH module launcher. **Publishes Events (persisted to `fw_domain_events`):** * `rh_resident_admitted` → FA / PM (🟡 persistence ✅; batch consumers 📋) — `facility_type` for PM-07 POS * `rh_resident_discharged` → FA / PM (🟡 persistence ✅; batch consumers 📋) * `rh_phase_advanced` → FW-16 / PF-10 (🟡 persistence ✅; automations 📋) * `invoice_creation_requested` → FA (📝 Planned) — includes `facility_type`; align name with FA before implement (see [EVENT\_CONTRACTS](./EVENT_CONTRACTS.md#rh-lifecycle-events-canonical-names--persistence-fw-16)) * `rh_bed_assigned` / `rh_bed_released` → HR (📝 Planned) — register in `KnownEventName` + triggers when HR consumer is scheduled (legacy names `bed_assigned` / `bed_released` deprecated) * `critical_incident_reported` → PF-10 (📝 Planned) * `attendance_threshold_breached` → PF-10, RH-05 (📝 Planned) * `compliance_deadline_approaching` → PF-10 (📝 Planned) * `non_compliance_detected` → PF-10 (📝 Planned) **Consumes Events:** * `payment_received` from FA (📝 Planned) * `employee_assigned_to_site` from HR (📝 Planned) **Consumes APIs:** * `/api/v1/fa/episode-balance` from FA (🟡 Edge function `fa-episode-balance`; uses cached `rh_episode_payment_status` until FA episode AR is linked) * `/api/v1/hr/employees/{employee_id}` from HR (📝 Planned) * `/api/v1/hr/employees` from HR (📝 Planned) **Exposes APIs:** * `/api/v1/rh/current-residence` → CL (📝 Planned) — current residence/bed for patient chart; [API Contracts](./API_CONTRACTS.md#rh-01-current-residencebed-query-cl-chart--optional) **Provides Census Data (Platform Layer):** * `src/platform/census` reads `rh_beds` and `rh_residences` (including `facility_type`) for HR workload and PM reporting * See [Platform Census README](../../../src/platform/census/README.md) **Uses Platform Layers:** * Forms (PF-08) - Resident intake forms * Census (Platform) - `useCensusData`, `useSiteCensus` consumed by HR/PM * Workforce (Platform) - Staff assignments * Data Lookup (PF-15) - Site and staff selectors * Notifications (PF-10) - Compliance alerts * Documents (PF-11) - Resident agreements *** ### FA (Finance & Accounting) **Publishes Events:** * `vendor_bill_approved` → FW-03, PF-10, FA-03 (✅ Implemented) * `payment_processed` → FA-02, PF-10, FA-06 (✅ Implemented) * `journal_entry_posted` → Event Consumer, FA-07, PF-10 (✅ Implemented) * `budget_approved` → FW-03, PF-10, FA-07 (✅ Implemented) * `budget_exceeded` → PF-10, FA-08 (✅ Implemented) * `consolidation_completed` → FA-07, PF-10, Event Consumer (✅ Implemented) * `payment_received` → RH (📝 Planned) * `tax_1099_generated` → PF-10 (📝 Planned - FA-10) * `tax_w2_generated` → PF-10, HR-07 (📝 Planned - FA-10) * `tax_year_closed` → PF-10, FA-07 (📝 Planned - FA-10) * `asset_created` → FM-05, PF-10 (📝 Planned - FA-11) * `asset_disposed` → FM-05, PF-10, FA-02 (📝 Planned - FA-11) * `depreciation_posted` → FA-02, FA-07 (📝 Planned - FA-11) * `expense_report_submitted` → FW-03, PF-10 (📝 Planned - FA-12) * `expense_report_approved` → FA-05, PF-10 (📝 Planned - FA-12) * `expense_report_rejected` → PF-10 (📝 Planned - FA-12) * `expense_reimbursement_processed` → FA-02, PF-10 (📝 Planned - FA-12) * `project_created` → FA-08, PF-10 (📝 Planned - FA-13) * `project_budget_exceeded` → PF-10, FA-08 (📝 Planned - FA-13) * `grant_drawdown_received` → FA-02, PF-10 (📝 Planned - FA-13) * `cash_position_updated` → FA-07, PF-10 (📝 Planned - FA-14) * `investment_maturity_approaching` → PF-10 (📝 Planned - FA-14) * `credit_limit_approaching` → PF-10 (📝 Planned - FA-14) * `idc_rate_calculated` → FA-13, PF-10 (📝 Planned - FA-15) * `idc_allocated` → FA-13, FA-02 (📝 Planned - FA-15) * `kpi_threshold_exceeded` → PF-10 (📝 Planned - FA-16) * `intercompany_transaction_created` → FA-02, FA-09 (📝 Planned - FA-17) * `intercompany_elimination_generated` → FA-09, FA-02 (📝 Planned - FA-17) * `fa_revenue_recognized` → FA-02, FA-05, FA-13 (✅ Implemented FA-18 Phase 2 WS3 — published via `fw_domain_events` from `fa_process_revenue_recognition`) * `fa_revenue_schedule_completed` → FA-05, FA-13, LO (✅ Implemented FA-18 Phase 2 WS3 — emitted when a schedule fully recognizes its total revenue) * `close_period_started` → PF-10, FA-02 (✅ Implemented - FA-19) * `close_period_completed` → PF-10, FA-07 (✅ Implemented - FA-19) * `close_period_approved` → PF-10, FA-07, FW-03 (✅ Implemented - FA-19) * `close_task_assigned` → PF-10 (✅ Implemented - FA-19) * `close_task_completed` → PF-10 (✅ Implemented - FA-19) **Consumes Events:** * `rh_resident_admitted` from RH (🟡 Event persisted; FA batch consumer 📋) — `facility_type` for service-line tagging * `rh_resident_discharged` from RH (🟡 Event persisted; FA batch consumer 📋) — `facility_type` and LOS * `invoice_creation_requested` from RH (📝 Planned) — payload includes `facility_type` * `resident_charge_created` from RH → FA-05 (📝 Planned - Auto-invoice generation) * `merit_increase_approved` from HR-15 → FA-08 (✅ Implemented) - Budget impact tracking * `compensation_cost_allocated` from HR-15 → FA-08 (✅ Implemented) - Departmental cost forecasts * `compensation_analysis_completed` from HR-15 → FA-16 (✅ Implemented) - Analytics integration * `payroll_run_completed` from HR-07 → FA-10 (📝 Planned - W-2 generation) * `vendor_payment_processed` from FA-03 → FA-10 (📝 Planned - 1099 updates) * `purchase_order_received` from FA-04 → FA-11 (📝 Planned - Asset creation) * `workflow_approved` from FW-03 → FA-12 (📝 Planned - Expense approval) * `workflow_rejected` from FW-03 → FA-12 (📝 Planned - Expense rejection) * `journal_entry_posted` from FA-02 → FA-13, FA-15 (📝 Planned - Project/cost allocation) * `vendor_bill_approved` from FA-03 → FA-13 (📝 Planned - Project expense allocation) * `invoice_sent` from FA-05 → FA-13, FA-16, FA-18 (📝 Planned - Project revenue, DSO, revenue recognition) * `bank_balance_updated` from FA-06 → FA-14 (📝 Planned - Cash position updates) * `payment_processed` from FA-03 → FA-14 (📝 Planned - Cash flow forecast) * `fiscal_period_closed` from FA-02 → FA-19 (📝 Planned - Close period linking) **Exposes APIs:** * `/api/v1/fa/episode-balance` → RH (🟡 Edge function `fa-episode-balance`; full FA AR join 📋) * `/api/v1/fa/tax/1099/generate` → Internal (📝 Planned - FA-10) * `/api/v1/fa/assets/{asset_id}/depreciation` → FA-07 (📝 Planned - FA-11) * `/api/v1/fa/assets/register` → FA-07 (📝 Planned - FA-11) - Fixed asset register report * `/api/v1/fa/depreciation/schedule` → FA-07 (📝 Planned - FA-11) - Depreciation schedule report * `/api/v1/fa/depreciation/run` → Internal (📝 Planned - FA-11) - Run monthly depreciation * `/api/v1/fa/expenses/reports/{report_id}/approve` → FW-03 (📝 Planned - FA-12) * `/api/v1/fa/projects/{project_id}/budget-vs-actual` → FA-07, FA-08 (📝 Planned - FA-13) * `/api/v1/fa/idc/rates/{rate_id}/allocate` → FA-13 (📝 Planned - FA-15) * `/api/v1/fa/analytics/dashboard` → Internal (📝 Planned - FA-16) * `/api/v1/fa/intercompany/eliminations/generate` → FA-09 (📝 Planned - FA-17) * `/api/v1/fa/revenue/recognize` → Internal (✅ Implemented FA-18 Phase 2 — RPC `fa_process_revenue_recognition` + edge function `fa-process-revenue-recognition` HTTP wrapper) * `/api/v1/fa/close/periods/{period_id}/approve` → FW-03, Internal (✅ Implemented - FA-19) * `/api/v1/fa/close/periods/{period_id}/status` → FA-07, FA-02 (✅ Implemented - FA-19) * `/api/v1/fa/cash/position` → FA-07, FA-16 (📝 Planned - FA-14) **Consumes APIs:** * `/api/v1/hr/payroll/tax-data` from HR-07 → FA-10 (📝 Planned - W-2, 941/940) * `/api/v1/fa/vendors/payments` from FA-03 → FA-10 (📝 Planned - 1099) * `/api/v1/fa/purchase-orders/{po_id}` from FA-04 → FA-11 (📝 Planned - Asset creation) * `/api/v1/fm/assets/{asset_id}` from FM-05 → FA-11 (📝 Planned - Facilities asset reference) * `/api/v1/it/assets/{asset_id}` from IT-01 → FA-11 (📝 Planned - IT asset reference) * `/api/v1/hr/employees/{employee_id}` from HR-01 → FA-12 (📝 Planned - Employee data) * `/api/v1/fa/accounts` from FA-01 → FA-12, FA-13, FA-15 (📝 Planned - GL accounts) * `/api/v1/fa/payments/create` from FA-05 → FA-12 (📝 Planned - Reimbursement) * `/api/v1/fa/budgets/{budget_id}` from FA-08 → FA-13 (📝 Planned - Project budgets) * `/api/v1/hr/employees/ftes` from HR-01 → FA-15 (📝 Planned - FTE allocation base) * `/api/v1/fa/projects/{project_id}/direct-costs` from FA-13 → FA-15 (📝 Planned - Direct cost base) * `/api/v1/fa/reports/balance-sheet` from FA-07 → FA-16 (📝 Planned - Ratio calculations) * `/api/v1/fa/reports/statement-activities` from FA-07 → FA-16 (📝 Planned - Analytics) * `/api/v1/fa/budgets/variance` from FA-08 → FA-16 (📝 Planned - Variance analysis) * `/api/v1/fa/journal-entries/create` from FA-02 → FA-17 (📝 Planned - Intercompany entries) * `/api/v1/fa/consolidations/{consolidation_id}` from FA-09 → FA-17 (📝 Planned - Consolidation) * `/api/v1/fa/invoices/{invoice_id}` from FA-05 → FA-18 (📝 Planned - Revenue schedule) * `/api/v1/fa/projects/{project_id}` from FA-13 → FA-18 (📝 Planned - Project revenue) * `/api/v1/fa/fiscal-periods/{period_id}` from FA-02 → FA-19 (📝 Planned - Close periods) * `/api/v1/fa/reports/close-status` from FA-07 → FA-19 (📝 Planned - Close reports) * `/api/v1/fa/bank-accounts` from FA-06 → FA-14 (📝 Planned - Cash positions) * `/api/v1/fa/budgets/cash-flow` from FA-08 → FA-14 (📝 Planned - Cash forecasts) **Uses Platform Layers:** * Forms (PF-08) - Payment forms, vendor portal forms, expense forms * Workforce (Platform) - Employee selection for expenses * Notifications (PF-10) - Budget alerts, tax deadlines, collection notices, close notifications * Documents (PF-11) - Vendor contracts, tax forms, receipts, close documentation * Reports (PF-12) - Financial reports *** ### HR (Workforce) **Publishes Events:** * `credential_expired` → Event Consumer, HR-04 (✅ Implemented) * `credential_verified` → Event Consumer (✅ Implemented) * `onboarding_completed` → Event Consumer (✅ Implemented) * `offboarding_completed` → Event Consumer (✅ Implemented) * `performance_review_completed` → LO-03, HR-15, HR-16 (✅ Implemented - HR-10) * `performance_goal_completed` → LO-03 (📝 Planned - HR-10) * `performance_improvement_plan_terminated` → HR-03, HR-14 (✅ Implemented - HR-10) * `benefits_enrollment_approved` → HR-07 (📝 Planned - HR-11) * `benefits_enrollment_terminated` → HR-07 (📝 Planned - HR-11) * `disciplinary_action_termination` → HR-03 (✅ Implemented - HR-14) * `incident_reported` → GR-06, PF-10 (✅ Implemented - HR-14) * `grievance_filed` → GR-03 (✅ Implemented - HR-14) * `merit_increase_approved` → HR-07, FA, PF-10 (✅ Implemented - HR-15) * `compensation_analysis_completed` → FA, PF-10 (✅ Implemented - HR-15) * `compensation_cost_allocated` → FA (✅ Implemented - HR-15) * `successor_identified` → PF-10 (📝 Planned - HR-16) * `talent_promoted` → HR-16 (📝 Planned - HR-16) * `survey_completed` → PF-10 (📝 Planned - HR-17) * `exit_interview_completed` → HR-03 (📝 Planned - HR-17) * `employee_assigned_to_site` → RH (📝 Planned) * `employee_created` → GR (📝 Planned) **Consumes Events:** * `credential_expired` from HR-02 → HR-04 (✅ Implemented) - Blocks employee from scheduling * `employee_hired` from HR-09 → HR-10 (📝 Planned) - Create initial performance goals * `organizational_goal_created` from LO-03 → HR-10 (📝 Planned) - Link to employee goals * `performance_review_completed` from HR-10 → HR-15 (✅ Implemented) - Trigger merit increase planning * `employee_terminated` from HR-03 → HR-11, HR-14, HR-17 (✅ Implemented for HR-14) - Terminate benefits, close cases, trigger exit interview **Exposes APIs:** * `/api/v1/hr/employees/{employee_id}` → RH (📝 Planned) * `/api/v1/hr/employees` → RH (📝 Planned) * `/api/v1/hr/performance/reviews/:id/export` → PF-12 (📝 Planned - HR-10) **Uses Platform Layers:** * Forms (PF-08) - Onboarding forms, performance review forms, feedback forms, benefits enrollment forms, exit interview forms * Workforce (Platform) - Employee selection (internal use) * Notifications (PF-10) - Credential alerts, review reminders, feedback requests, enrollment reminders, incident notifications * Documents (PF-11) - Employee documents, review documents, benefits documents, compensation statements * Reports (PF-12) - Employee reports, performance analytics, workforce analytics **Internal Integrations:** * HR-04 (Scheduling) subscribes to HR-02 credential events for automatic blocking * HR-10 (Performance) integrates with HR-01, HR-02, HR-09, HR-14, GR-02 (✅ Complete - PIP Termination → HR-14, Competency → HR-02/GR-02) * HR-11 (Benefits) integrates with HR-01, HR-06, HR-07, FA * HR-12 (Self-Service) integrates with all HR modules (HR-01 through HR-11) * HR-13 (Skills) integrates with HR-01, HR-02, HR-04, HR-09, GR-02 * HR-14 (Employee Relations) integrates with HR-01, HR-03, GR-03, GR-06, PF-10, PF-11 (✅ Phase 4 Complete) * HR-15 (Compensation) integrates with HR-01, HR-07, HR-10, FA (✅ Phase 4 Complete) * HR-16 (Succession Planning) integrates with HR-01, HR-10 * HR-17 (Engagement) integrates with HR-01, HR-03, PF-08 * HR-18 (Analytics) aggregates data from all HR modules (HR-01 through HR-17) *** ### FW (Forms & Workflow) **Database Tables (FW-57):** * `fw_workflow_templates` — extended with healthcare pattern metadata (`pattern_category`, `compliance_tags`, `required_node_ids`, `regulatory_references`) (✅ Implemented) * `fw_regulatory_change_log` — org-scoped regulatory change tracking for templates (✅ Implemented) **Publishes Events:** * `automation_trigger` → FW-03 (✅ Implemented) * `execution_failed` → PF-10 (📝 Planned - FW-22) * `fw_external_form_submitted` → PF-10, FW-03 (✅ Implemented - FW-32; published via `pg_notify` in `portal-form-submit` edge function) * `fw_approval_submitted` → PF-10, FW-03 (📝 Planned - FW-34) * `fw_approval_completed` → FW-03, PF-10 (📝 Planned - FW-34) * `fw_approval_escalated` → PF-10 (📝 Planned - FW-34) **Exposes APIs (Edge Functions):** * `workflow-query-action` → Automation Executor (📝 Planned - FW-19) * `workflow-api-action` → Automation Executor (📝 Planned - FW-19) * `workflow-debug-control` → Debug UI (📝 Planned - FW-22) * `sandbox-execute` → Testing UI (📝 Planned - FW-24) * `test-datasets-import` → Testing UI (📝 Planned - FW-24) * `test-cases-run` → Testing UI (📝 Planned - FW-24) * `approval-escalation` → Scheduled cron job (📝 Planned - FW-34) **Uses Platform Layers:** * Data Lookup (PF-15) - Dynamic form field lookups, Query action whitelist base * Custom Fields (PF-16) - Custom field definitions * Field Configuration (PF-17) - Field layout configuration (Phase 4/5 Complete: versioning + wizard forms) * Workflow Variables (FW-18) - Query result storage * Notifications (PF-10) - Failed execution alerts (FW-22), Approval notifications (FW-34) * Permissions (PF-30) - Approval authorization (FW-34) * Supabase Realtime - Live execution dashboard (FW-22), Approval inbox updates (FW-34) **Database Tables (FW-19):** * `fw_api_connections` - SFTP/API connection configs (📝 Planned) * `fw_query_whitelist` - Org-specific table whitelist (📝 Planned) **Database Tables (FW-22):** * `fw_execution_logs` - Searchable execution logs (📝 Planned) * `fw_debug_sessions` - Debug session state (📝 Planned) **Database Tables (FW-24):** * `fw_test_datasets` - Test data storage (📝 Planned) * `fw_test_scenarios` - Scenario definitions (📝 Planned) * `fw_test_cases` - Automated test cases (📝 Planned) * `fw_sandbox_executions` - Sandbox execution history (📝 Planned) * `fw_test_coverage` - Coverage metrics (📝 Planned) **Database Tables (FW-25):** * `fw_workflow_retry_configs` - Retry configuration per node (✅ Implemented) * `fw_workflow_circuit_breakers` - Circuit breaker state per node (✅ Implemented) * `fw_workflow_recovery_workflows` - Recovery workflow definitions (✅ Implemented) * `fw_workflow_compensation_actions` - Compensation action definitions (✅ Implemented) **SECURITY DEFINER Functions (FW-25):** * `fw_has_rule_org_access(rule_id, user_id)` - Check org access via automation rule for RLS (✅ Implemented) **Database Tables (FW-34):** * `fw_approval_chains` - Approval chain definitions (📝 Planned) * `fw_approval_steps` - Steps in approval chains (📝 Planned) * `fw_approval_requests` - Submitted approval requests (📝 Planned) * `fw_approval_assignments` - Approver assignments (📝 Planned) * `fw_approval_delegations` - Delegation records (📝 Planned) * `fw_approval_history` - Audit trail (📝 Planned) **SECURITY DEFINER Functions (FW-34):** * `fw_user_can_view_request(request_id, user_id)` - Check if user can view approval request (📝 Planned) * `fw_get_pending_approvals(user_id)` - Get pending approvals for user including delegations (📝 Planned) * `fw_process_approval_action(assignment_id, action, comment, reason)` - Process approval/reject action (📝 Planned) **Scheduled Jobs (FW-34):** * `fw-approval-escalation` - Hourly cron job for reminder/escalation processing (📝 Planned) **Database Tables (FW-16):** * `fw_workflow_events` - Global event registry with 11 seed events (✅ Implemented) * `fw_domain_events` - Organization-scoped event log (✅ Implemented) **Platform Integration Layer (FW-16):** * `/src/platform/events/` - Event publishing for all cores (✅ Implemented) * `publishEvent()` - Direct function for event publication * `usePublishEvent()` - React hook with loading state * Type definitions for known events **Database Tables (FW-17):** * Conditions stored in `fw_workflow_definitions.node_data` JSONB (✅ Implemented) **Platform Integration (FW-17 → PF-17):** * Field discovery via `useConditionAttributes` hook (✅ Implemented) * Documented in [PLATFORM\_INTEGRATION\_LAYERS.md](./PLATFORM_INTEGRATION_LAYERS.md#fw-17--pf-17-condition-builder-field-discovery) **Database Updates (FW-18):** * `fw_workflow_executions.variables` - JSONB column for variable state (✅ Implemented) * Index: `idx_fw_executions_variables` - GIN index for variable queries (✅ Implemented) **Edge Function Shared Code (FW-18):** * `supabase/functions/_shared/expressionEvaluator.ts` - Deno-compatible evaluator (✅ Implemented) **Database Tables (FW-29):** * `fw_workflow_notification_rules` - Notification rules per workflow (✅ Implemented) * `fw_workflow_alert_rules` - Alert rules for conditions (✅ Implemented) * `fw_workflow_alerts` - Active and historical alerts (✅ Implemented) * `fw_workflow_notification_preferences` - User notification preferences (✅ Implemented) **Edge Functions (FW-29):** * `workflow-notification-trigger` - Process status changes, evaluate alert rules (✅ Implemented) * `process-alert-escalations` - Scheduled escalation processing (✅ Implemented) **Database Triggers (FW-29):** * `fw_execution_status_notification_trigger` - Triggers notification on execution status change (✅ Implemented) *** ### LO (Leadership Operating System) **Publishes Events:** * `rock_completed` → FA, PF-10, PF-04 (✅ Implemented) * `todo_created` → PF-10 (✅ Implemented) * `todo_completed` → PF-10, LO-03 (✅ Implemented) * `todo_overdue` → PF-10 (✅ Implemented) * `scorecard_updated` → PF-10, PF-12 (✅ Implemented) * `metric_threshold_breached` → PF-10, LO-06 (✅ Implemented) * `meeting_scheduled` → PF-10 (✅ Implemented) * `meeting_completed` → PF-04, PF-10 (✅ Implemented) * `action_item_created` → LO-04, PF-10 (✅ Implemented) * `issue_identified` → PF-10, LO-06 (✅ Implemented) * `issue_resolved` → PF-04, PF-10 (✅ Implemented) * `assessment_distributed` → PF-10 (✅ Implemented) * `assessment_completed` → PF-12, PF-10 (✅ Implemented) * `goal_created` → FA, GR, FW (📝 Planned - LO-16) * `goal_completed` → RH, FA, GR (📝 Planned - LO-16) * `action_assigned` → HR, PF-10 (📝 Planned - LO-16) * `action_completed` → LO-14, PF-10 (📝 Planned - LO-16) **Uses Platform Layers:** * Forms (PF-08) - Assessment forms * Notifications (PF-10) - Task and meeting notifications * Documents (PF-11) - Knowledge articles * Tasks (PF-29) - Unified task system (✅ Phase 2/3 Complete — 2026-02-27) * Reports (PF-12) - Scorecard and assessment reports *** ### FM (Facilities Management) > **Full contract schemas:** [FM\_INTEGRATION\_CONTRACTS.md](./FM_INTEGRATION_CONTRACTS.md) **Publishes Events — Implemented (FM-01 through FM-05, FM-13):** * `work_order_created` → PF-10, FA (✅ Implemented) * `work_order_completed` → FA, FM-04, FM-05, FM-06, FM-03 (✅ Implemented) * `work_order_overdue` → PF-10 (✅ Implemented) * `inventory_low_stock` → PF-10, FA-04 (✅ Implemented) * `inventory_item_used` → FM-01, FA (✅ Implemented) * `vendor_certification_expiring` → PF-10, GR (✅ Implemented) * `vendor_work_order_assigned` → PF-10, FA-03 (✅ Implemented) * `pm_due` → PF-10, FM-05 (📝 Planned — FM-04 publisher not yet wired) * `pm_overdue` → PF-10, GR (📝 Planned) * `pm_completed` → FM-05, FA (📝 Planned) * `asset_purchased` → FA (📝 Planned — FM-05 publisher not yet wired) * `asset_disposed` → FA, FM-04 (📝 Planned) * `asset_warranty_expiring` → PF-10 (📝 Planned) * `vehicle_registered` → PF-10, FM-05 (📝 Planned — FM-13 publisher) * `vehicle_status_changed` → PF-10, FM-05 (📝 Planned) * `license_expiring` → PF-10, GR (📝 Planned) * `registration_expiring` → PF-10, GR (📝 Planned) * `fleet_maintenance_due` → PF-10, FM-01 (📝 Planned) * `fleet_maintenance_overdue` → PF-10, GR (📝 Planned) **Publishes Events — Planned (FM-06 through FM-12, pending implementation):** * `inspection_due` → PF-10, GR (📝 Planned — FM-06) * `inspection_failed` → PF-10, GR, FM-01 (📝 Planned — FM-06) * `inspection_compliant` → GR, FM-05 (📝 Planned — FM-06) * `budget_variance_alert` → PF-10, FA-08 (📝 Planned — FM-09) * `capital_project_approved` → FA-09, PF-10 (📝 Planned — FM-12) * `energy_anomaly_detected` → PF-10, GR (📝 Planned — FM-10 Deferred Expansion) * `space_occupancy_threshold` → PF-10, HR (📝 Planned — FM-11) * `facilities_report_generated` → PF-10 (📝 Planned — FM-07) **Consumes Events:** * `work_order_completed` → Updates vendor performance (✅ Implemented) * `purchase_order_approved` → Update FM-02 inventory preferred vendor PO (📝 Planned — from FA-04) * `vendor_invoice_matched` → Update FM-03 vendor WO invoice status (📝 Planned — from FA-03) * `budget_approved` → Unlock FM-09 budget period for actuals (📝 Planned — from FA-08) * `it_asset_maintenance_required` → Create FM work order from IT asset alert (📝 Planned — from IT) **Uses Platform Layers:** * Forms (PF-08) — Work order forms, inspection checklists * Workforce (Platform) — Staff assignments * Finance (`@/platform/finance`) — FM cost summary interface for FM-09/FM-12 (📝 Stub per FM-16) **API Contracts (FM as provider, pending implementation):** * `GET /api/v1/fm/budgets/{id}/actuals` → FA-08 (📝 Planned — FM-09) * `GET /api/v1/fm/capital-projects/{id}` → FA-09 (📝 Planned — FM-12) * `GET /api/v1/fm/spaces/{id}/occupancy` → HR (📝 Planned — FM-11) * Data Lookup (PF-15) - Site and asset selectors * Notifications (PF-10) - Work order and maintenance alerts * Documents (PF-11) - Equipment manuals, certifications *** ### GR (Governance) **GR-15 Platform Layer Integrations:** | From Core | To Core | Integration Pattern | Status | Documentation | | --------- | ------- | ----------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | GR-15 | PF-10 | Platform Layer (notifications) | ✅ Complete | [GR-15 Integration](./nonprofit-governance-controls-integration.md) — COI cycle reminders, whistleblower alerts, board approvals, retention warnings | | GR-15 | PF-46 | Platform Layer (data retention) | ✅ Complete | [GR-15 Integration](./nonprofit-governance-controls-integration.md) — Retention policy registration; legal hold enforcement for governance docs | | GR-15 | HR-01 | Data lookup via `pf_profiles` (PF shared table) | ✅ Complete | [GR-15 Integration](./nonprofit-governance-controls-integration.md) — COI participant roster seeded from active profiles | | GR-15 | FA | UUID cross-reference (manual workflow) | 📋 Deferred | [GR-15 Integration](./nonprofit-governance-controls-integration.md) — Related-party transaction cross-reference for Form 990 Schedule L | **GR-16 Platform Layer Integrations:** | From Core | To Core | Integration Pattern | Status | Documentation | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | GR-16 | GR-08, PF-11, PF-12, PF-27, PF-10 | Platform Layer + Intra-core data | ✅ | [GR-16 Integration](./accreditation-tracer-readiness-integration.md) — Tracer packs, CAP lifecycle, mock surveys; PF-11 document export, PF-27 AI question simulator, PF-10 deadline alerts | | GR-14 | GR-09 (consumer), PF-10, PF-11, PF-12 | Event Consumer + Platform Layer | ✅ | [GR-14 Integration](./regulatory-incident-reporting-automation-integration.md) — Subscribes to `incident_created`; classifies incidents against reporting rules; tracks statutory deadlines; generates report packages; sends deadline alerts via PF-10 | | GR-UX-06 | GR-09 (writer), GR-14 (preview), PF-41 | Wizard entry point | ✅ | Incident Reporting Wizard at `/gr/incidents/report` — 6-step `ModuleWizardRenderer` flow; custom regulatory step calls `gr_check_regulatory_obligations` RPC for server-side obligation preview from `gr_regulatory_reporting_rules`; INSERTs `gr_incidents` only and relies on `gr_publish_incident_created` trigger pipeline (GR-14) to auto-create `gr_incident_regulatory_reports` (no double insert) | | GR-UX-05 | GR-03 (writer), PF-41 | Wizard entry point | ✅ | Compliance Requirement Setup Wizard at `/gr/compliance/requirements/new` — 7-step `ModuleWizardRenderer` flow; 4 custom steps (regulatory-body, schedule, documentation, review); reuses `useRegulatoryRequirementMutation.createRequirement`; non-fatal ancillary inserts to `gr_compliance_checks` (initial schedule) + `gr_compliance_evidence` (document placeholders); wizard-only fields persist into `gr_regulatory_requirements.custom_fields` JSONB; `frequency` defaults to `as_needed` to satisfy NOT NULL + CHECK; gated by `gr.compliance.admin` | | GR-UX-04 | GR-05 (writer), PF-29 (best-effort task sync), PF-41 | Wizard entry point | ✅ | Risk Assessment Wizard at `/gr/risks/wizard` (and `/gr/risks/wizard/:riskId`) — 6-step horizontal `WizardShell` flow; submit sequence (D-12) `createRisk` → `createAssessment` → `createMitigation × N` (blocking) → best-effort `pf_tasks` insert per mitigation action (failures flag mitigation `custom_fields.task_sync_status='pending'` for retry, never abort); D-11 score/rating bands (Low 1–6 / Medium 7–12 / High 13–18 / Critical 19–25) computed via canonical `calculateRiskScoreAndRating` from `useRiskAssessment.ts`; localStorage drafts `gr_risk_assessment_new` / `gr_risk_assessment_{riskId}` with 30-day TTL; entry button + resume banner on RiskList; gated by `gr.risks.admin`; edit-mode (load existing risk into wizard) deferred — current `/wizard/:riskId` resumes drafts only | | GR-06-EN-01 | PF-96, PF-60, PF-61, PF-62, PF-27, PF-72, PF-10, GR-03, GR-02, GR-16, PF-91 | Platform Layer + Event | 📝 | [GR-06-EN-01 Integration](./ai-state-compliance-checking-integration.md) — State-aware AI compliance checking; jurisdiction profile injection, state regulatory RAG KB, state gap analysis, multi-state comparison; publishes `gr_state_gap_analysis_completed` | | GR-19 | GR-02 (substrate), GR-02-EN-02 (`@/platform/training`), GR-02-EN-05 (mandatory seed), GR-18 (optional), GR-03 (writer), GR-08 (consumer), PF-10, PF-11, PF-30, PF-46, PF-96 | Platform Layer + Intra-core data | 📝 | [GR-19 Integration](./mandatory-inservice-compliance-monitor-integration.md) — Mandatory in-service survey-readiness dashboard (matrix + scorecard) over GR-02 substrate; reminder cron via PF-10 (`in_service_due` template); surveyor PDF packet via PF-11 (`inservice_survey_packet` template); writes `gr_compliance_evidence` rows on export; new permissions `gr.compliance.{view,export}`; HIPAA §164.530(j)(2) 6-yr retention floor enforced | **Publishes Events:** * `policy_created` → GR-02, GR-03 (📝 Planned — GR-01) * `policy_acknowledged` → GR-02, GR-03 (📝 Planned — GR-01) * `training_completed` → GR-03, HR-02 (📝 Planned — GR-02) * `requirement_created` → GR-04, GR-06 (📝 Planned — GR-03) * `compliance_status_changed` → GR-04, GR-05, GR-06 (📝 Planned — GR-03) * `audit_created` → GR-06 (✅ Complete — GR-04 / GR-UX-07) * `audit_finding_created` → GR-05, GR-06 (📝 Planned — GR-04) * `risk_created` → GR-06 (📝 Planned — GR-05) * `risk_assessed` → GR-06 (📝 Planned — GR-05) * `qi_project_created` → GR-03, GR-04 (✅ Complete — GR-07 / GR-UX-08) * `accreditation_created` → GR-03, GR-04 (📝 Planned — GR-08) * `incident_created` → GR-05, GR-06, CL (✅ Implemented — GR-09; also see CL-GR bridge) * `incident_resolved` → GR-05, GR-06 (✅ Implemented — GR-09) * `gr_incident_created` → CL (chart flag), **GR-14** (regulatory classification) (✅ Implemented — GR-09 trigger deployed; emits only for chart-linked incidents where `custom_fields->>'chart_id'` is present; GR-14 should subscribe to `incident_created` for all incidents; see [CL-GR-CLINICAL-INCIDENT-INTEGRATION.md](./CL-GR-CLINICAL-INCIDENT-INTEGRATION.md), [GR-14 Integration](./regulatory-incident-reporting-automation-integration.md)) * `regulatory_report_submitted` → GR-03 (compliance evidence), GR-08 (accreditation evidence), PF-10 (notification) (📝 Planned — GR-14) * `gr_state_gap_analysis_completed` → PF-91 (compliance dashboard), PF-10 (critical gap notifications) (📝 Planned — GR-06-EN-01) * `procedure_approved` → GR-02, GR-03, PF-10 (✅ Complete — GR-11) * `procedure_execution_completed` → GR-03, PF-10 (✅ Complete — GR-11) * `procedure_gap_identified` → GR-07 QI project candidate (✅ Complete — GR-13-EN-01, 2026-04-19; see [GR-13 Integration](./procedure-analytics-integration.md)) * `gr_template_instantiated` → GR-03, PF-10 (📝 Planned — GR-12) * `gr_template_contributed` → GR-03 (📝 Planned — GR-12) * `gr_coi_cycle_launched` → PF-10 (notifications to participants), GR-03 (compliance tracking) (✅ Complete — GR-15) * `gr_whistleblower_report_submitted` → PF-10 (notify compliance officer) (✅ Complete — GR-15) * `gr_template_instantiated` → GR-03, PF-10 (✅ Complete — GR-12) * `gr_template_contributed` → GR-03 (✅ Complete — GR-12) **Consumes Events:** * `employee_created` from HR → GR onboarding policy/training assignment (📝 Planned — [Event Contracts](./EVENT_CONTRACTS.md#hr-01-employee-created-events)) * `incident_reported` from HR → GR-03, GR-04 (✅ Implemented — HR-14) * `grievance_filed` from HR → GR-03 (✅ Implemented — HR-14) * `vendor_certification_expiring` from FM → GR compliance check (✅ Implemented — [FM Integration Contracts](./FM_INTEGRATION_CONTRACTS.md#vendor_certification_expiring)) * `pm_overdue` from FM → GR (📝 Planned) * `inspection_due` from FM → GR (📝 Planned) * `inspection_failed` from FM → GR (📝 Planned) * `inspection_compliant` from FM → GR (📝 Planned) * `it_security_incident_created` from IT → GR (📝 Planned — [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md#it-05-security-incident-created-event)) * `it_critical_vulnerability_detected` from IT → GR (📝 Planned) * `it_asset_disposed` from IT → GR (📝 Planned) * `cl_safety_plan_activated` from CL → GR draft incident (📝 Planned — [CL-GR Bridge](./CL-GR-CLINICAL-INCIDENT-INTEGRATION.md)) * `cl_restraint_event_documented` from CL → GR draft incident (📝 Planned — [CL-GR Bridge](./CL-GR-CLINICAL-INCIDENT-INTEGRATION.md)) * `cl_incident_reported` from CL-15 → GR-03, GR-04, GR-08 (✅ Implemented — [CL-15 Integration](./clinical-reporting-quality-measures-integration.md)) * `goal_completed` from LO → GR (📝 Planned — LO-16) **Uses Platform Layers:** * Forms (PF-08) — Policy acknowledgment forms, audit checklists, compliance surveys * Notifications (PF-10) — Policy review reminders, compliance check due dates, audit finding alerts * Documents (PF-11) — Policy documents, audit evidence, compliance certificates * AI (PF-27) — AI Compliance Advisor (GR-06); AI contract analysis (GR-10 Phase 2, planned) * Permissions (PF-30) — Granular permission system for GR access control * Workflow (PF-73) — Swim lane diagram generation from GR-01 policies and GR-11 procedures (✅ Implemented) **Integration Docs:** * See [GR-INTEGRATION.md](./GR-INTEGRATION.md) for full GR integration contract anchor document. * See [GR-13-procedure-analytics-INTEGRATION.md](./procedure-analytics-integration.md) for GR-13 procedure analytics → GR-07 / PF-12 integration contracts. * See [GR-15-nonprofit-governance-controls-INTEGRATION.md](./nonprofit-governance-controls-integration.md) for GR-15 COI, whistleblower, board governance, and PF-46/PF-10 integration contracts. * See [CL-GR-CLINICAL-INCIDENT-INTEGRATION.md](./CL-GR-CLINICAL-INCIDENT-INTEGRATION.md) for bi-directional incident bridge with CL. *** ### IT (Information Technology) **Publishes Events:** * `it_asset_purchased` → FA (📝 Planned) * `it_asset_assigned` → PF-10, HR (📝 Planned) * `it_asset_maintenance_required` → FM (📝 Planned) * `it_asset_disposed` → FA, GR (📝 Planned) * `it_ticket_created` → PF-10 (📝 Planned) * `it_ticket_status_changed` → PF-10 (📝 Planned) * `it_sla_breached` → PF-10 (📝 Planned) * `it_contract_expiring` → PF-10 (📝 Planned) * `it_license_created` → FA (📝 Planned) * `it_license_expiring` → PF-10 (📝 Planned) * `it_license_renewed` → FA (📝 Planned) * `it_license_compliance_alert` → PF-10 (📝 Planned) * `it_security_incident_created` → GR, PF-10 (📝 Planned) * `it_critical_vulnerability_detected` → GR, PF-10 (📝 Planned) * `it_patch_deployment_overdue` → PF-10 (📝 Planned) * `it_purchase_request_submitted` → FW-34, PF-10 (📝 Planned) * `it_purchase_request_approved` → FA-04, PF-10 (📝 Planned) * `it_purchase_request_received` → IT-01, PF-10 (📝 Planned) **Exposes APIs:** * `/api/v1/it/assets/{asset_id}` → IT-02, IT-05 (📝 Planned) * `/api/v1/it/assets` → IT-02, IT-04, IT-05, IT-06 (📝 Planned) * `/api/v1/it/vendors/{vendor_id}` → IT-01, IT-04, IT-06 (📝 Planned) * `it_check_license_compliance()` → IT-04 Dashboard (📝 Planned) **Consumes APIs:** * `/api/v1/hr/employees/{employee_id}` from HR (📝 Planned) * `/api/v1/hr/employees` from HR (📝 Planned) **Uses Platform Layers:** * Forms (PF-08) - Ticket submission, purchase request forms * Workforce (Platform) - Employee assignments for assets/tickets * Data Lookup (PF-15) - Asset, vendor, employee selectors * Notifications (PF-10) - SLA, expiration, compliance alerts * Documents (PF-11) - Warranties, attachments, contracts * Approval Workflows (FW-34) - Purchase request approvals * Custom Fields (PF-16) - Org-specific metadata on all IT entities **Internal Integrations:** * IT-02 links tickets to IT-01 assets * IT-04 links licenses to IT-01 assets and IT-03 vendors * IT-05 links patches/vulnerabilities to IT-01 assets * IT-06 uses IT-03 vendors and creates IT-01 assets on receipt **Full Documentation:** [IT Integration Contracts](./IT_INTEGRATION_CONTRACTS.md) *** ### CE (Community Engagement / CRM) **Publishes Events:** * `ce.email.synced` → CE-04 (📝 Planned - CE-07) - Auto-create activity * `ce.email.tracking` → PF-10 (📝 Planned - CE-07) - Open/click notifications * `ce.sms.sent` → CE-04 (📝 Planned - CE-08) - Auto-create activity * `ce.sms.received` → CE-04 (📝 Planned - CE-08) - Auto-create activity * `ce.campaign.started` → PF-10 (📝 Planned - CE-09) - Campaign notifications * `ce.campaign.completed` → CE-05 (📝 Planned - CE-09) - Analytics update * `ce_web_form_submitted` → CE-01, CE-05 (📝 Planned - CE-10) - Lead creation * `ce_screening_completed` → PM-38, PM-39, CE-29 (📝 Planned - CE-28) - Screening disposition triggers appointment/waitlist/conversion * `ce_lead_waitlisted` → PM-39 (📝 Planned - CE-28) - Screened lead routed to waitlist (no bed available) * `ce_crisis_alert_created` → PF-83, PF-10, CE-29 (📝 Planned - CE-28-ENHANCEMENTS EN-01) - Crisis-keyword detection on inbound intake; ID-only payload (no PHI) **Consumes Events:** * N/A (CE is primarily a publisher of CRM events) **Exposes APIs:** * N/A (internal module APIs only) **Consumes APIs:** * `/api/v1/hr/employees/{employee_id}` from HR (📝 Planned) - Contact assignment * `/api/v1/hr/employees` from HR (📝 Planned) - Staff search **Uses Platform Layers:** * Notifications (PF-10) - Email tracking alerts, SMS delivery * Documents (PF-11) - Email attachments * Reports (PF-12) - Campaign analytics (CE-05) * Custom Fields (PF-16) - Contact/partner custom data **Internal Integrations:** * CE-07 creates activities in CE-04 via database trigger * CE-08 creates activities in CE-04 via database trigger * CE-07 links emails to CE-01 contacts and CE-02 partners * CE-08 links SMS to CE-01 contacts * CE-09 creates leads in CE-01 contacts * CE-10 creates leads in CE-01 and triggers CE-09 campaign tracking **External Integrations:** * Gmail API (OAuth 2.0) - CE-07 * Microsoft Graph API (OAuth 2.0) - CE-07 * Twilio SMS API - CE-08 **Full Documentation:** [CE-07 Email Integration](./email-integration.md) *** ### CL (Clinical & EHR) **Note (EN-66):** CL-04-EN-66 is complete. EN-66 uses a shared canonical `validatePolicy940` function from `src/cores/cl/shared/validation/validatePolicy940.ts`. CL-36 Phase 2 ambient documentation should consume this same validator to avoid duplication. See [CL-04-EN-66 integration doc](./note-quality-pre-submission-validation-integration.md) Contract Validation Checklist. **Publishes Events:** * `assessment_completed` → PM (optional), FW, PF-10 (📝 Planned) — [Event Contracts](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) * `treatment_plan_signed` → FW, PF-10 (📝 Planned) * `progress_note_signed` → PM (charge capture), PF-10 (📝 Planned) * `medication_recon_completed` → PF-10 (📝 Planned) * `prescription_sent` → PM, PF-10 (📝 Planned) * `pdmp_query_completed` → CL (audit) (📝 Planned) — [CL-17](../../../specs/cl/specs/CL-17-arizona-cspmp-pdmp-integration.md) * `cl_lab_order_created` → PF-10, FW (📝 Planned) — CL-09 * `cl_lab_result_received` → CL-08, PF-10 (📝 Planned) — CL-09 * `cl_lab_result_reviewed` → PF-10, PF-04 (📝 Planned) — CL-09 **Consumes Events:** * `prior_auth_required` from PM (📝 Planned) * `prior_auth_received` from PM (📝 Planned) * `eligibility_verified` from PM (📝 Planned) * `patient_registered` from PM (📝 Planned) * `appointment_scheduled` from PM (📝 Planned) * `encounter_completed` (CL/PM) (📝 Planned) **Uses Platform Layers:** * [CL Consent Service](./PLATFORM_INTEGRATION_LAYERS.md#cl-consent-service) — Consent evaluation (Part 2, TPO); CL-11 * [CL Billing Adapter](./PLATFORM_INTEGRATION_LAYERS.md#cl-billing-adapter) — Encounter-to-charge context; PM-07, CL-04 * [CL Document Export (EHI)](./PLATFORM_INTEGRATION_LAYERS.md#cl-document-export-ehi) — FHIR/USCDI export; CL-16 *** ### PM (Practice Management) **Publishes Events:** * `claim_submitted` → FA (optional), PF-10 (📝 Planned) — [Event Contracts](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) * `claim_adjudicated` → PM-09, PF-10 (📝 Planned) * `prior_auth_required` → CL, PF-10 (📝 Planned) * `prior_auth_received` → CL, PM-07/08, PF-10 (📝 Planned) * `eligibility_verified` → CL, PM-07, PF-10 (📝 Planned) * `patient_registered` → CL, RH (optional), PF-10 (📝 Planned) * `appointment_scheduled` → CL, PF-10 (📝 Planned) * `encounter_completed` (CL/PM) → PM (charge capture), PF-10 (📝 Planned) * `pm.fhir_app_authorized` → PF-04 audit, GR (📝 Planned, PM-55) * `pm.fhir_app_revoked` → PF-04 audit, GR (📝 Planned, PM-55) * `pm.fhir_information_blocking_logged` → GR-08 incident reporting (📝 Planned, PM-55) * `pm.fhir_access_logged` → PF-04 audit stream (📝 Planned, PM-55) **Consumes Events:** * `assessment_completed` from CL (optional billing) (📝 Planned) * `treatment_plan_signed` from CL (📝 Planned) * `progress_note_signed` from CL (charge capture) (📝 Planned) * `prescription_sent` from CL (📝 Planned) * `cl.part2_consent_granted` / `cl.part2_consent_revoked` from CL-11 (📝 Planned, PM-55) — re-evaluate active FHIR app consents that include SUD scopes **Uses Platform Layers:** * [CL Consent Service](./PLATFORM_INTEGRATION_LAYERS.md#cl-consent-service) — TPO/Part 2 gating for billing * [CL Billing Adapter](./PLATFORM_INTEGRATION_LAYERS.md#cl-billing-adapter) — Charge capture context from encounters * [CL Document Export (EHI)](./PLATFORM_INTEGRATION_LAYERS.md#cl-document-export-ehi) — PM-12 patient access, EHI export *** ## Dependency Graph ``` Platform Foundation (PF) ↓ ├─→ Forms (PF-08) → All Cores ├─→ Workforce → RH, FA, GR, IT ├─→ Data Lookup (PF-15) → FW, HR, RH, IT ├─→ Custom Fields (PF-16) → All Cores ├─→ Field Config (PF-17) → All Cores (Phase 4/5 ✅) ├─→ Notifications (PF-10) → All Cores ├─→ Documents (PF-11) → All Cores └─→ Reports (PF-12) → All Cores Event-Based Integration: RH → FA (resident admission/discharge) FA → RH (payment received) HR → RH (employee assignment) HR → GR (employee created) HR-02 → HR-04 (credential expired → scheduling block) FW → FW-03 (form submission) FA → FW-03, PF-10 (financial events) LO → FA, PF-10 (leadership events) FM → PF-10, GR (vendor certification expiring) FM → PF-10, FA-03 (vendor work order assigned) FM → FA, FM-04, FM-05 (work order completed) IT → FA (asset purchased, license costs) IT → FM (asset maintenance required) IT → GR (security incidents) IT → PF-10 (SLA, expiration, compliance alerts) IT-06 → FW-34 (procurement approval workflow) CL-09 → CL-08, PF-10 (lab result received → abnormal alert) External Labs → CL-09 (result ingestion via HL7v2/FHIR) API Contracts: FA → RH (episode balance query) HR → RH (employee lookup/search) IT → IT-02, IT-05 (asset lookup) IT → IT-01, IT-04, IT-06 (vendor lookup) ``` *** ## Integration Pattern Usage ### When to Use Each Pattern **Platform Integration Layer (Pattern 1):** * ✅ Multiple cores need the same functionality * ✅ Reusable UI components or hooks * ✅ Domain-agnostic functionality * Examples: Forms, Workforce, Data Lookup, Custom Fields **Event-Based Integration (Pattern 2):** * ✅ Loose coupling between cores * ✅ Asynchronous workflows * ✅ Audit trails of state changes * Examples: Resident admission → Billing account creation **API Contracts (Pattern 3):** * ✅ Synchronous request-response * ✅ Real-time data queries * ✅ Event-driven patterns not suitable * Examples: Episode balance queries, Employee lookups *** ## Spec Coverage Index (Q2 2026 closure waves) This section guarantees every spec under `specs/{core}/specs/` has at least one row in the canonical contract surface. Each row points to the integration pattern, key publishers/consumers, and either an existing dedicated `*-INTEGRATION.md` file, the relevant `EVENT_CONTRACTS` / `API_CONTRACTS` anchor, or a per-spec note here. Rows added during the **Q2 2026 closure waves** are tracked in the archived triage report at [`docs/archive/integrations/_GAP_TRIAGE_2026Q2.md`](../../archive/integrations/_GAP_TRIAGE_2026Q2.md). > **Status meanings as of 2026-04-17 closure pass:** ✅ contract documented and matches implementation; 📝 contract documented as planned (spec implementation pending); 🟡 contract partially documented; the spec is implemented but the contract surface here is the new authoritative summary. ### CE — Community Engagement (Wave CE) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ------------------------------------------------ | --------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | CE-03-E0 | RingCentral Setup Wizard | External (RingCentral) | ✅ | Provisions CE-03 platform telephony for tenant; consumes `@/platform/telephony` and PF-76 credential vault | [CE-03 spec](../../../specs/ce/specs/CE-03-call-management-ringcentral.md) · [EXTERNAL\_INTEGRATIONS § RingCentral](./EXTERNAL_INTEGRATIONS.md) | | CE-05-EN-01 | Pipeline Reporting Speed-to-Contact | Event / Data | 📝 | Extends CE-05 pipeline events with first-contact latency telemetry; PF-12 reporting consumer | [CE-05 spec](../../../specs/ce/specs/CE-05-pipeline-reporting.md) | | CE-06 | Partner Progress Monitoring | Event | ✅ | Publishes `ce_partner_milestone_reached` (consumed by CE-02 partners, PF-10 notifications) | [CE-06 spec](../../../specs/ce/specs/CE-06-partner-progress-monitoring.md) | | CE-11 | Partner Self-Service Portal | API / Platform | 📝 | External-facing portal over CE-02 partners; PF-30 permission gating; PF-08 forms; CE-06 milestones consumer | [CE-11 spec](../../../specs/ce/specs/CE-11-partner-self-service-portal.md) | | CE-12 | AI-Powered Lead Scoring | Platform Layer / Data | 📝 | PF-27 platform AI consumer; updates CE-01 lead score column on schedule; no PHI in prompts (constitution §4.3) | [CE-12 spec](../../../specs/ce/specs/CE-12-ai-lead-scoring.md) | | CE-13 | Automated Follow-up Sequences | Event / Platform | 📝 | FW-46 durable worker consumer; publishes to PF-10 notifications and CE-04 activities | [CE-13 spec](../../../specs/ce/specs/CE-13-automated-follow-up-sequences.md) | | CE-16 | Communications Compliance & Suppression | Event / Data | 🔜 | Registry tables (`ce_suppressions`, `ce_consent_evidence`, `ce_suppression_audit_log`), permissions, hooks, compliance dashboard, DNC import + CSV export shipped 2026-05-14. Pre-send suppression checks in CE-08/CE-09/CE-03, STOP/bounce → suppression handlers, and `ce.suppression.created` event publication still pending. GR audit-export integration deferred to CE-16-EN-08. | [CE-16 spec](../../../specs/ce/specs/CE-16-communications-compliance-suppression.md) | | CE-19 | Referral Outcome Tracking & ROI | Data / Event | 📝 | Extends CE-29 lead conversion with downstream PM-09 revenue attribution and CL-10 outcome correlation | [CE-19 spec](../../../specs/ce/specs/CE-19-referral-outcome-tracking-roi.md) | | CE-24 | Partner Document & Contract Management | Data / Event | 🚧 | WS1–WS5 shipped (2026-05-18): `ce_partner_contracts` + `ce_partner_documents` + `ce_contract_renewal_log` with FORCE RLS and lifecycle transition trigger (extended to allow `active → pending_renewal`/`renewed`). Hooks aligned to DB enum (`renewal_started`/`renewed`/`notification_sent`/`expired_without_action`); paired `useMarkRenewalInProgress`/`useMarkContractRenewed` mutations. `PartnerDocumentsPanel` grouped by `document_type`; `/ce/contracts/renewals` dashboard with `ScrollableTabsList` + `useTabUrlState` URL-synced 30/60/90 tabs, responsive table/card layout, renewal confirmation dialog with notes. Consumes CE-02 partners + PF-11 storage. **Deferred:** `ce-contract-renewal-check` edge function + pg\_cron schedule (T037) and PF-10 notification wiring (T038). | [CE-24 spec](../../../specs/ce/specs/CE-24-partner-document-contract-management.md) | | CE-25 | Community Event Management | Event / Platform | ✅ | CE-04 activities; PF-29 task consumer; PF-10 reminders | [CE-25 spec](../../../specs/ce/specs/CE-25-community-event-management.md) | | CE-27 | Social Media Integration | External | 📝 | OAuth-based social posting (LinkedIn, Facebook, Twitter/X) via CE-09 marketing campaigns; PF-76 credential vault | [CE-27 spec](../../../specs/ce/specs/CE-27-social-media-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CE-57 | Contact Profile Phase 2 Enhancements | Intra-core (Data / RPC) | 🔜 | Extends `ce_contacts` (DOB, gender, pronouns, `contact_category`). Reuses CE-20 relationships for family/emergency links; consumed by CE-66 partner picker via `contact_category = 'community'` filter. Read-time `last_contact_at` derived from CE-60 / `ce_activities`. SECURITY DEFINER RPC `ce_check_contact_duplicate` enforces `ce.contacts.view_dob` masking. No new cross-core event introduced; existing CE events MUST continue to omit DOB. **Status (2026-05-15):** Migration + RPC + permission seed shipped; ContactForm/ContactInfoCard updated; RLS test for DOB masking added. | [CE-57 spec](../../../specs/ce/specs/CE-57-contact-profile-phase2-enhancements.md) | | CE-59 | Contact Document Management & AI Data Extraction | Intra-core (Data / Storage) | ✅ | Phase 1 + Phase 2 implemented. New `ce_contact_documents` (FORCE RLS via `ce_has_org_access`; admin-gated DELETE via `ce_is_org_admin`); private `ce-contact-documents` storage bucket with org-segment path policies; 4 permissions (`ce.contacts.documents.{view,upload,delete,ai_extract}`). Consumes PF-11 storage primitives via greenfield shared CE adapter (`src/cores/ce/lib/document-storage-adapter.ts`, designed for future CE-24 reuse). Phase 2 adds `ce-extract-document-data` edge function with redaction preflight (≥0.95 confidence; CAC-2), identifier-stripped outbound payload (CAC-3), 42 CFR Part 2 fail-closed gate (CAC-4), confirm-only writes to `ce_contacts.custom_fields.extracted_intake` (CAC-5), and append-only `ce_contact_document_extraction_audit` table (CAC-6). No cross-core events; allowlisted in `.intra-core-only.json`. **Status (2026-05-15):** Phase 2 default-OFF; per-tenant enablement via CE Settings → AI Document Extraction admin card after Compliance review per `specs/ce/reviews/CE-59-COMPLIANCE-SIGNOFF.md`. | [CE-59 spec](../../../specs/ce/specs/CE-59-contact-document-management-ai-extraction.md) | ### CL — Clinical (Wave CL) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | CL-01-EN-03 | Chart Summary AI Readiness | Platform Layer | 📝 | Extends CL-01 chart with PF-27 AI summary block; no PHI in prompts | [CL-01-EN-03 spec](../../../specs/cl/specs/CL-01-EN-03-chart-summary-ai-readiness.md) | | CL-01-EN-04 | Problem List SNOMED Mapping | Data | 📝 | PF-70 medical terminology consumer; extends CL-01 problem list with SNOMED CT codes | [CL-01-EN-04 spec](../../../specs/cl/specs/CL-01-EN-04-problem-list-snomed-mapping.md) | | CL-09-EN-60 | UDS Chain-of-Custody (Interim) | Data / Event | 📝 | Extends CL-09 lab orders and CL-34 UDS workflow with chain-of-custody tracking; events to GR | [CL-09-EN-60 spec](../../../specs/cl/specs/CL-09-EN-60-uds-chain-of-custody-interim.md) | | CL-10-EN-61 | Medicare Advantage STARS BH Quality Measures | Data / Platform | 📝 | Extends CL-10 outcomes with CMS STARS measure calculation; CL-15 quality reporting consumer | [CL-10-EN-61 spec](../../../specs/cl/specs/CL-10-EN-61-medicare-advantage-stars-measures.md) | | CL-15-EN-62 | CCBHC Service Category Tags (Interim) | Data | 📝 | Extends CL-15 reporting with CCBHC service tags on encounter / service log records | [CL-15-EN-62 spec](../../../specs/cl/specs/CL-15-EN-62-ccbhc-service-category-tags-interim.md) | | CL-22-EN-63 | Remote Patient Monitoring (RPM) Device Integration | External / Event | 📝 | External device API (Bluetooth/cellular vital sign devices); publishes `cl_rpm_reading_received` consumed by CL-22 vital signs and CL-08 CDS | [CL-22-EN-63 spec](../../../specs/cl/specs/CL-22-EN-63-remote-patient-monitoring.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CL-26-EN-64 | Multi-Language Portal (CLAS) | Platform Layer | 📝 | Extends CL-26 patient portal with PF-87 i18n framework; CLAS standards 1, 5, 6, 7 | [CL-26-EN-64 spec](../../../specs/cl/specs/CL-26-EN-64-multi-language-portal.md) | | CL-28 | Clinical Supervision Documentation | Event / API | 📝 | Co-sign workflow events (`cl_supervision_documented`); HR-19 clinical oversight consumer; CL-04 progress notes link | [CL-28 spec](../../../specs/cl/specs/CL-28-clinical-supervision-documentation.md) | | CL-32 | Family Therapy Documentation | Event | 📝 | Extends CL-04 progress notes with multi-attendee family session events; CL-37 caregiver portal consumer; PM-07 charge capture (90847/90849) | [CL-32 spec](../../../specs/cl/specs/CL-32-family-therapy-documentation.md) | | CL-37 | Family & Caregiver Portal | Event / Platform | 📝 | Publishes `cl_caregiver_consent_changed`; CL-26 portal extension; CL-12 transitions and CL-32 family therapy consumer; CL-11 consent gating | [CL-37 spec](../../../specs/cl/specs/CL-37-family-caregiver-portal.md) | | CL-38 | CCBHC Compliance & Service Documentation | Data / Event | 📝 | Publishes CCBHC quality measures consumed by CL-15 quality reporting and GR-08 accreditation | [CL-38 spec](../../../specs/cl/specs/CL-38-ccbhc-compliance-service-documentation.md) | | CL-40-EN-01 | Multi-Language Clinical Forms | Platform Layer | 📝 | Extends CL-40 intake with PF-87 i18n; FW-38 form translation consumer | [CL-40-EN-01 spec](../../../specs/cl/specs/CL-40-EN-01-multi-language-clinical-forms.md) | | CL-42 | Clinical Pathways & Protocol-Driven Care | Event | 📝 | Publishes `cl_pathway_milestone_completed` (→ CL-10 outcomes, CL-08 CDS), `cl_pathway_variance_created` (→ CL-08 CDS, CL-15 quality), `cl_pathway_milestone_overdue` (→ PF-10 notifications, CL-23 in-basket). UUID-only payloads; SUD-program pathways gated by `cl_pathway_consent_ok`. Schemas added in T061. | [CL-42 spec](../../../specs/cl/specs/CL-42-clinical-pathways-protocol-driven-care.md) | | CL-43 | Concurrent Review & Utilization Management | Event / Data (placeholder) | 📝 | UM review events consumed by PM-47 auth tracking; per-payload schemas land with CL-43 PLAN.md | [CL-43 spec](../../../specs/cl/specs/CL-43-concurrent-review-utilization-management.md) | | CL-44 | Clinical Order Sets & Standing Orders | Intra-core (Phase 1) | ✅ | Phase 1 shipped 2026-05-08 — 4 tables with FORCE RLS, activation delegates to CL-05/CL-09 hooks (atomic rollback), structured standing-order parameters + renewal flow, server-side `cl_enforce_standing_order_frequency` trigger and `cl_expire_standing_orders` helper. Allowlisted in `.intra-core-only.json`; no cross-core events in Phase 1. | [CL-44 spec](../../../specs/cl/specs/CL-44-clinical-order-sets-standing-orders.md) | | CL-43 | Concurrent Review & Utilization Management | Event / Data | ✅ | CL-43 reads PM-10 prior authorizations via `@/platform/scheduling` (UUID-only, no FK). Publishes `cl_review_overdue` (consumed by PF-10 + CL-08) and `cl_review_determination_recorded` (consumed by PM-11 revenue cycle analytics). Subscribes to `pm_authorization_status_changed` from PM-10. Full payloads in [EVENT\_CONTRACTS.md § CL-43](EVENT_CONTRACTS.md) and [CL-43 INTEGRATION](concurrent-review-utilization-management-integration.md). | [CL-43 spec](../../../specs/cl/specs/CL-43-concurrent-review-utilization-management.md) | | CL-45 | Allergy & Adverse Reaction Tracking | Data / Event | ✅ | Phases 1–5 shipped 2026-05-08. Schema extends `cl_allergies` in place (criticality, verification\_status, allergen\_class\_code, reaction\_code, is\_sud\_mat\_class, NKA/NKDA sentinel flags) + append-only `cl_allergy_alert_overrides`. RLS via `cl_has_org_access`; SUD-MAT gated by `cl_has_sud_consent` (CL-11). Publishes `cl_allergy_recorded`, `cl_allergy_status_changed`, `cl_allergy_alert_overridden`, `cl_nka_confirmed` (UUID-only). API `getActiveAllergies(chartId)` filters sentinel rows for CL-05/CL-06 consumption. FHIR US Core 6.x `AllergyIntolerance` mapper (`allergy-fhir.ts`) and CCDA LOINC 48765-2 section builder (`allergy-ccda.ts`) ship redisclosure notice when SUD-MAT rows are included. | [CL-45 spec](../../../specs/cl/specs/CL-45-allergy-adverse-reaction-tracking.md) · [INTEGRATION](allergy-tracking-integration.md) | | CL-46 | Problem List Management (ICD-10) | Event / Platform Layer | ✅ Complete (2026-05-12) — CL side ready | See row above (CL-46 → CL-08 / PM-07). Publishes `cl_problem_list_updated`; exposes `usePatientActiveProblems` via `@/platform/clinical`. | [CL-46 spec](../../../specs/cl/specs/CL-46-problem-list-management-icd10.md) | | CL-47 | Behavioral Health Screening Instruments Library | Data (placeholder) | 📝 | Extends CL-02 assessment library; instrument metadata consumed by CL-07 risk screening, CL-10 outcomes | [CL-47 spec](../../../specs/cl/specs/CL-47-behavioral-health-screening-instruments-library.md) | | CL-48 | Clinical Document Architecture (CDA) Generation | API / Events | 📝 | Extends CL-16 FHIR interoperability + CL-20 export with C-CDA R2.1 documents; publishes `cl_cda_document_generated` and `cl_cda_transmission_status_changed`; HIE consumer via Direct messaging edge function | [CL-48 spec](../../../specs/cl/specs/CL-48-clinical-document-architecture-cda.md) · [INTEGRATION](clinical-document-architecture-cda-integration.md) | | CL-49 | Automated Level-of-Care Assessment (ASAM/LOCUS) | Events: cl\_loc\_assessment\_completed / cl\_loc\_recommendation\_changed / cl\_loc\_override\_recorded | ✅ | Publishes UUID-only LOC events on sign; CL-43 UM consumer + CL-08 CDS subscriber stubs deferred | [CL-49 spec](../../../specs/cl/specs/CL-49-automated-level-of-care-asam-locus.md) | | CL-50 | PDMP (Multi-State) | External (placeholder) | 📝 | Multi-state extension of CL-17 Arizona CSPMP via PF-96 jurisdiction profile; PMP Gateway / Bamboo Health | [CL-50 spec](../../../specs/cl/specs/CL-50-pdmp-multi-state-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CL-51 | Clinical Quality Measures (CQM) Reporting Engine | Data / API (placeholder) | 📝 | Extends CL-15 quality reporting with CMS CQM calculation engine; PF-12 reporting consumer | [CL-51 spec](../../../specs/cl/specs/CL-51-clinical-quality-measures-reporting-engine.md) | | CL-52 | Genomics & Pharmacogenomics Integration | External (placeholder) | 📝 | External lab partner; CL-05 medication management consumer for pharmacogenomic alerts via CL-08 CDS | [CL-52 spec](../../../specs/cl/specs/CL-52-genomics-pharmacogenomics-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CL-53 | Wearable Device Integration & Continuous Monitoring | External / Event (placeholder) | 📝 | Apple HealthKit / Google Health Connect integration; publishes vital sign events to CL-22 | [CL-53 spec](../../../specs/cl/specs/CL-53-wearable-device-continuous-monitoring.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CL-13-EN-01 | Restraint/Seclusion Time-Limited Orders & 1-Hour F2F | Event / Data | 📝 | Extends CL-13 crisis intervention with 42 CFR 482.13 timed-order tracking and 1-hour face-to-face evidence; PF-29 task generation; GR-09 incident reporting | [CL-13-EN-01 spec](../../../specs/cl/specs/CL-13-EN-01-restraint-seclusion-time-limited-orders.md) | | CL-16-EN-02 | USCDI v3 Read-Only Patient Access FHIR R4 API | API | 📝 | Extends CL-16 FHIR R4 façade with USCDI v3 read-only patient access endpoints (CMS-9115-F compliance); CL-11 consent gating | [CL-16-EN-02 spec](../../../specs/cl/specs/CL-16-EN-02-uscdi-v3-patient-access-api.md) | | CL-17-EN-01 | PMP Gateway Vendor-Agnostic Adapter | External / Platform | 📝 | Extends CL-17 Arizona CSPMP with adapter pattern enabling Bamboo Health / NABP PMP Gateway / state-direct integration; PF-76 vault | [CL-17-EN-01 spec](../../../specs/cl/specs/CL-17-EN-01-pmp-gateway-vendor-adapter.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | CL-26-EN-66 | WCAG 2.1 AA + HHS Section 504 Portal Audit | Platform / Tooling | 📝 | Extends CL-26 patient portal with axe CI audit; PF-93 platform a11y consumer | [CL-26-EN-66 spec](../../../specs/cl/specs/CL-26-EN-66-wcag-section-504-portal-audit.md) | | CL-54 | Patient Cohort & Clinical Registry Management | PIL hook + Event | 🚧 | UI ✅ (list/detail/rule builder/snapshot/export with 42 CFR Part 2 redisclosure + audit). Pending follow-ups: `usePatientCohort` PIL hook in `@/platform/clinical` (F1) and `cl_cohort_membership_recomputed` event publishing on `cl_events` (F2). Consumers: CE-09/10 (outreach audience), FA (VBP attribution), CL-35 (panel/dashboard refresh), CL-29-EN-65 / CL-15 (HEDIS & quality denominators). | [CL-54 spec](../../../specs/cl/specs/CL-54-patient-cohort-clinical-registry.md) · [EVENT\_CONTRACTS](./EVENT_CONTRACTS.md#planned-events-clpm-ehr--practice-management) | | CL-55 | Virtual / Telehealth Group Therapy | Event / Platform | 🚧 | UI ✅ (host/list/detail + multi-party + patient join `/cl/virtual-groups/:sessionId/join`); PHI-free `cl_virtual_group_started`/`cl_virtual_group_concluded` published to PM-07 (US-3 SC-003) — payloads carry only UUIDs, modality, counts, durations, modifier codes, jurisdiction profile id (no patient identifiers, names, DOB, content, or join URLs). Extends CL-14/CL-24 for virtual/hybrid groups and multi-party encounters; consumes PM-13 telehealth lifecycle | [CL-55 Integration](./virtual-telehealth-group-therapy-integration.md) · [CL-55 spec](../../../specs/cl/specs/CL-55-virtual-telehealth-group-therapy.md) | | CL-56 | Centralized Clinical Notification & Critical Result Alerting | PIL + Event | ✅ (2026-05-11) | Policy-driven fan-out for clinical signals from CL-08 (CDS), CL-09 (labs), CL-22 (vitals), CL-23 (in-basket), CL-25 (break-glass), CL-29 (readmission), CL-36 (AI). Dispatches via PF-10 (direct `pf_notifications` insert from `cl-clinical-notify` edge function). Publishes `cl_notification_dispatched` and `cl_notification_sla_breached` (PHI-free, IDs + severity only). Consumers: **GR-09** (auto-creates safety incident on SLA breach), **CL-25** (audit dashboard SLA metrics for Joint Commission NPSG.02.03.01 evidence). HR-19 supervisor/on-call resolution falls back to `pf_user_role_assignments.system_role` → `org_admin` until a Phase-2 on-call roster spec lands. | [CL-56 spec](../../../specs/cl/specs/CL-56-centralized-clinical-notification-service.md) · [EVENT\_CONTRACTS](./EVENT_CONTRACTS.md#cl-56-centralized-clinical-notification--critical-result-alerting-events) | | CL-57 | Clinical Content Marketplace | Data / Event | ✅ MVP (2026-05-11) | Curated read-only catalogue of accreditation-aligned bundles (3 global tables + FORCE RLS). Per-org one-click import materializes `cl_assessment_templates` and `cl_note_templates` (Phase-2 handlers: cds\_rule, pathway\_definition, treatment\_plan\_template, goal\_bank\_entry, order\_set, locus\_instrument, group\_curriculum, screening\_instrument). Publishes `cl_marketplace_bundle_imported` (PHI-free; IDs + counts only, with canonical `event_id` + domain `import_id`). Curator gating via `cl_can_curate_marketplace()` (delegates to platform admin until PF marketplace\_curator role lands). Deferred: edge-function atomic import and curator UI. | [CL-57 spec](../../../specs/cl/specs/CL-57-clinical-content-marketplace.md) · [EVENT\_CONTRACTS](./EVENT_CONTRACTS.md#cl-57-clinical-content-marketplace-events) | ### FA — Finance & Accounting (Wave FA) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----- | ---------------------------------------------- | ----------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | FA-21 | Bank Reconciliation Automation Rules | Data / Event | 📝 | Extends FA-06 reconciliation with rules engine; consumes FA-20 Plaid feed; publishes `fa_recon_rule_matched` | [FA-21 spec](../../../specs/fa/specs/FA-21-bank-reconciliation-automation.md) | | FA-23 | Financial Statement Customization & GAAP | Event / Data | 📝 | Publishes `fa_financial_statement_published`; FA-07 reporting consumer | [FA-23 spec](../../../specs/fa/specs/FA-23-financial-statement-customization.md) | | FA-24 | AR Collections Workflow | Event / Platform | 📝 | Consumes FA-05 AR aging; publishes collections events to PF-10 (notifications) and PF-29 (tasks) | [FA-24 spec](../../../specs/fa/specs/FA-24-ar-collections-workflow.md) | | FA-25 | Financial Audit Trail & Compliance Reports | Data / Platform | ✅ | Append-only ledger over all FA tables; PF-04 audit log integration; SOC2/SOX evidence | [FA-25 spec](../../../specs/fa/specs/FA-25-financial-audit-trail.md) | | FA-26 | Multi-Currency Support | Data | 📝 | Extends FA-02 GL with currency columns and FX rate snapshots; FA-07 reporting consumer | [FA-26 spec](../../../specs/fa/specs/FA-26-multi-currency.md) | | FA-27 | Expense Policy Engine | Data / Platform | 📝 | Extends FA-12 expenses with FW-45 decision-table policy evaluation; FW-34 approval routing | [FA-27 spec](../../../specs/fa/specs/FA-27-expense-policy-engine.md) | | FA-28 | Bank Reconciliation AI | Platform Layer | ✅ | Extends FA-06 with PF-27 platform AI suggestions; no PHI; tenant-scoped models | [FA-28 spec](../../../specs/fa/specs/FA-28-bank-reconciliation-ai-automation-recommendations.md) | | FA-32 | Payment Gateway Integration (Stripe / Square) | External / Event | 📝 | OAuth-based payment processor integration; publishes `fa_payment_received` consumed by PM-09 ERA posting and PM-45 collections | [FA-32 spec](../../../specs/fa/specs/FA-32-payment-gateway-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | FA-33 | Accounting Software Export (QuickBooks / Xero) | External / API | 📝 | One-way export of GL/AP/AR to external accounting; PF-44 export framework consumer | [FA-33 spec](../../../specs/fa/specs/FA-33-accounting-software-export.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | FA-34 | GR-FA Compliance Cost Tracking | Event (consumer) | 📝 | Consumes `compliance_cost_incurred` from GR; routes to FA-13/FA-15 cost pools | [FA-34 spec](../../../specs/fa/specs/FA-34-gr-fa-compliance-cost-tracking.md) | | FA-35 | CL-FA Clinical Program Cost Allocation | Event (consumer) / Data | 📝 | Consumes `clinical_program_cost_allocated` (CL → FA-15 allocation base driver weights) via `cl_events`; Phase 2 consumes `encounter_cost_calculated` (PM-35 → FA) via `fa_events`; admin mapping table `fa_cl_program_mapping`; activity log `fa_cl_allocation_activity`; 2 edge function consumers; 2 permission keys | [FA-35 spec](../../../specs/fa/specs/FA-35-cl-fa-clinical-program-cost-allocation.md) | | FA-36 | Federal Financial Reporting | Data / API | 📝 | Federal grantee SF-425 / SF-270 reporting; consumes FA-13 grant tracking; OMB 2 CFR 200 compliance | [FA-36 spec](../../../specs/fa/specs/FA-36-federal-financial-reporting.md) | | FA-37 | Subrecipient & Vendor Compliance | Data / Event | 📝 | Extends FA-13 grants with subrecipient monitoring (2 CFR 200.331–332); GR-10 contract consumer | [FA-37 spec](../../../specs/fa/specs/FA-37-subrecipient-vendor-compliance.md) | | FA-38 | ASC 842 Lease Accounting | Data | 📝 | New ROU asset / lease liability tables; FA-02 GL consumer; FA-07 reporting | [FA-38 spec](../../../specs/fa/specs/FA-38-asc-842-lease-accounting.md) | | FA-39 | Bill Pay & Vendor Payment Rails | External / Event | 📝 | ACH/check payment rails (Modern Treasury / Bill.com); extends FA-03 AP and FA-22 AP automation | [FA-39 spec](../../../specs/fa/specs/FA-39-bill-pay-vendor-payment-rails.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | FA-40 | Multi-State Payroll Tax Withholding | Data / Platform | 📝 | Extends HR-PAY with multi-state withholding rules via PF-96 jurisdiction profile | [FA-40 spec](../../../specs/fa/specs/FA-40-multi-state-payroll-tax-withholding.md) | ### FM — Facilities Management (Wave FM) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ---------------------------------------- | ------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | FM-06-EN-09 | Inspection → GR Risk Register | Event | 📝 | Failed FM-06 inspection publishes risk-register entry consumed by GR-05 risk management | [FM-06-EN-09 spec](../../../specs/fm/specs/FM-06-EN-09-inspection-to-gr-risk-register.md) | | FM-09-EN-09 | Grant Fund Tagging | Data | 📝 | Extends FM-09 facilities budgeting with FA-13 grant fund tags for cost allocation | [FM-09-EN-09 spec](../../../specs/fm/specs/FM-09-EN-09-grant-fund-tagging.md) | | FM-14-EN-01 | Platform Consumer Verification Promotion | Platform / Tooling | 📝 | Promotes `verify-fm-integration-gates.js` pattern to a generic platform tool for cross-core consumer verification | [FM-14-EN-01 spec](../../../specs/fm/specs/FM-14-EN-01-platform-consumer-verification-promotion.md) | | FM-17 | Service Request Portal | API / Platform | 📝 | External-facing service request intake; PF-08 forms; routes to FM-01 work orders | [FM-17 spec](../../../specs/fm/specs/FM-17-service-request-portal.md) | | FM-18 | Sustainability & EOC Reporting | Data | 📝 | Extends FM-10 energy management with sustainability KPIs; PF-12 reporting consumer | [FM-18 spec](../../../specs/fm/specs/FM-18-sustainability-eoc-reporting.md) | | FM-19 | IoT Sensor / BMS Integration | External / Event | 📝 | Building management system integration; publishes `fm_sensor_threshold_breached` consumed by FM-01 work orders and PF-10 | [FM-19 spec](../../../specs/fm/specs/FM-19-iot-sensor-bms-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | FM-20 | Key & Lock Access Management | Data / Event | 📝 | Key/lock inventory; assignment events to HR-03 onboarding/offboarding | [FM-20 spec](../../../specs/fm/specs/FM-20-key-lock-access-management.md) | | FM-21 | Warranty & Service Contract Management | Data / Event | 📝 | Extends FM-05 assets with warranty tracking; expiration events to PF-10 | [FM-21 spec](../../../specs/fm/specs/FM-21-warranty-service-contract-management.md) | | FM-22 | Recall & Field Bulletin Tracker | Data / Event | 📝 | External recall feeds (FDA, CPSC); affected FM-05 assets surface to FM-01 work orders | [FM-22 spec](../../../specs/fm/specs/FM-22-recall-field-bulletin-tracker.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | ### FW — Forms & Workflow (Wave FW) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----- | ----------------------------------- | ---------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | FW-20 | Bulk Operations & Batch Processing | Platform Layer | 📝 | PF-47 bulk operations consumer for form submission and workflow execution batches | [FW-20 spec](../../../specs/fw/specs/FW-20-bulk-operations.md) | | FW-26 | Workflow Scheduling & Resource Mgmt | Event / Platform | 📝 | Extends FW-46 durable worker with cron-style scheduling and resource quotas; PF-43 quota consumer | [FW-26 spec](../../../specs/fw/specs/FW-26-workflow-scheduling-resource-management.md) | | FW-31 | Multi-Step Form Wizards | Platform Layer | ✅ | PF-41 wizards platform layer; FW-05 multi-page forms consumer | [FW-31 spec](../../../specs/fw/archive/FW-31-multi-step-form-wizards.md) | | FW-37 | Payment Form Collection | External / Event | 📝 | Stripe payment intents from FW forms; publishes `fa_payment_received` consumed by FA-05/PM-09 | [FW-37 spec](../../../specs/fw/specs/FW-37-payment-form-collection.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | FW-38 | Multi-Language Form Support | Platform Layer | 📝 | PF-87 i18n framework consumer; CL-40-EN-01 and CL-26-EN-64 portal consumer | [FW-38 spec](../../../specs/fw/specs/FW-38-multi-language-form-support.md) | | FW-39 | Third-Party E-Signature Integration | External / Event | 📝 | DocuSign / Adobe Sign / HelloSign integration; alternative to FW-33 native signature; publishes `fw_external_signature_completed` | [FW-39 spec](../../../specs/fw/specs/FW-39-third-party-e-signature-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | ### GR — Governance & Risk (Wave GR) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ------------------------------------------- | --------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | GR-01-EN-01 | Policy Categories Picklist | Data | ✅ | PF-15 `gr.policy.category` picklist seeded for all orgs + new-org trigger; `gr_policies` BEFORE INSERT/UPDATE trigger enforces category against active picklist via `gr_validate_policy_category()`; `usePolicyCategories()` hook with `(legacy)` fallback consumed by `PolicyFormDialog`, `PolicyReviewDashboard`, and the GR-UX-12 wizard (2026-05-01) | [GR-01-EN-01 spec](../../../specs/gr/specs/GR-01-EN-01-policy-categories-picklist.md) | | GR-01-EN-02 | Policy Custom Fields & Config Form | Data / Platform | ✅ Complete (2026-05-01, intra-core only) | PF-16 custom fields wiring on `gr_policies` (`entity_type='gr_policy'`) + PF-08 `fw_forms` acknowledgment form rendering on existing `gr_policy_acknowledgments.acknowledgment_form_id` / `custom_fields` columns. Code-first default form (read\_confirmation + notes) when no form id is set. Admin pages at `/gr/settings/policy-custom-fields` and `/gr/settings/policy-acknowledgment-forms`. No cross-core event or API surface — allowlisted in [`.intra-core-only.json`](./.intra-core-only.json). | [GR-01-EN-02 spec](../../../specs/gr/specs/GR-01-EN-02-policy-custom-fields-and-config-form.md) | | GR-13-EN-01 | GR-07 Consumer (Procedure Gap) | Data / Event | ✅ | GR-13 `procedure_gap_identified` auto-creates draft `gr_qi_projects` row via DB trigger + edge function (2026-04-19) | [GR-13-EN-01 spec](../../../specs/gr/specs/GR-13-EN-01-gr-07-consumer-procedure-gap.md) | | GR-13-EN-02 | Step-Level Procedure Analytics | Data | ✅ | New `gr_procedure_step_execution_summary` MV + `gr_get_procedure_step_execution_summary` RPC; consumed by GR-13 dashboard drilldown (2026-04-20) | [GR-13-ENHANCEMENTS spec](../../../specs/gr/specs/GR-13-ENHANCEMENTS.md) | | GR-13-EN-03 | 12-Month Compliance Score Trend | Data | ✅ | Daily snapshots in `gr_procedure_compliance_score_snapshots`; multi-series trend chart in GR-13 Trends tab (2026-04-20) | [GR-13-ENHANCEMENTS spec](../../../specs/gr/specs/GR-13-ENHANCEMENTS.md) | | GR-13-EN-04 | Cross-Org Benchmarking | Data / Platform | ✅ | Opt-in cross-tenant `gr_benchmarking_aggregates` (k≥5); consent ledger `gr_benchmarking_consents`; new permissions `gr.procedure-analytics.benchmark.{opt-in,view}` (2026-04-20) | [GR-13-ENHANCEMENTS spec](../../../specs/gr/specs/GR-13-ENHANCEMENTS.md) | | GR-14-EN-01 | GR-03 / GR-08 Consumers (Regulatory Report) | Event | 📝 | Adds GR-03 compliance and GR-08 accreditation as named consumers of `regulatory_report_submitted`; pairs with [PENDING\_CONTRACTS row](./PENDING_CONTRACTS.md) | [GR-14-EN-01 spec](../../../specs/gr/specs/GR-14-EN-01-gr-03-gr-08-consumers-regulatory-report.md) | | GR-17 | Regulatory Change Management | Data / Event | ✅ | Sources + change events + impacts + snapshots with severity override and approve/dismiss review flow (2026-04-20). Publish of `gr_regulatory_change_published` reserved for follow-up; consumers (PF-91, GR-01, GR-03) deferred. | [GR-17 spec](../../../specs/gr/specs/GR-17-regulatory-change-management.md) | ### HR — Human Resources (Wave HR) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ---------------------------------------------- | ---------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | HR-08 | Workload Drivers & Staffing | Event / Platform | 📝 | Publishes `hr_workload_calculation_completed`; consumes RH-01 census via `@/platform/census`; HR-04/HR-06 consumer | [HR-08 spec](../../../specs/hr/specs/HR-08-workload-drivers-staffing.md) | | HR-09-P5 | Job Board Production Hardening | External | ✅ | Indeed (and future LinkedIn) job board integration; PF-76 vault credentials; circuit breaker; webhook signature/replay/idempotency | [HR\_ATS\_CONTRACTS § HR-09-P5.4](./HR_ATS_CONTRACTS.md) · [HR-09-P5.4 spec](../../../specs/hr/specs/HR-09-P5-4-job-board-production-hardening.md) | | HR-13-EN-01 | GR-02 (training completions), HR-13 (skills) | Event / Data | 📝 | Skill crediting from completed training — **HR-13-EN-01** consumes GR-02 / platform training completion signals to upsert `hr_employee_skills` | [HR-13-EN-01](../../../specs/hr/specs/HR-13-EN-01-skill-crediting-from-training.md) | | HR-22 | Learning Management System (LMS) Integration | External | 📝 | LMS API (Cornerstone / Workday Learning / SCORM); publishes `hr_training_completed` consumed by HR-02 credentials and HR-27 CE tracker | [HR-22 spec](../../../specs/hr/specs/HR-22-learning-management-system.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | HR-24 | Multi-State Payroll Tax Engine | Platform Layer | 📝 | PF-96 jurisdiction profile consumer; extends HR-PAY with state-specific withholding | [HR-24 spec](../../../specs/hr/specs/HR-24-multi-state-payroll-tax-engine.md) | | HR-25 | Workers' Compensation & Injury Mgmt | Event | 📝 | Publishes `hr_injury_reported` consumed by GR-09 incidents and OSHA reporting | [HR-25 spec](../../../specs/hr/specs/HR-25-workers-compensation-injury-management.md) | | HR-27 | Continuing Education & Training Tracker | Data / Event | 📝 | HR-02 credential renewal evidence; consumes HR-22 LMS completion events | [HR-27 spec](../../../specs/hr/specs/HR-27-continuing-education-training-tracker.md) | | HR-32 | Workplace Violence Prevention Program | Event | 📝 | Publishes `hr_workplace_safety_incident_reported` consumed by GR-09 incidents and OSHA WVP plan compliance | [HR-32 spec](../../../specs/hr/specs/HR-32-workplace-violence-prevention.md) | | HR-33 | Employee Wellness & EAP Management | Data / Event | 📝 | Extends HR-11 benefits with EAP utilization tracking; PF-10 reminders; no PHI in tracking (consents only) | [HR-33 spec](../../../specs/hr/specs/HR-33-employee-wellness-eap-management.md) | | HR-23 | Position Management & Headcount Planning | Data | 📝 | Extends HR-01 directory with position records (FTE, budget); FA-08 budget consumer; HR-15 compensation consumer | [HR-23 spec](../../../specs/hr/specs/HR-23-position-management-headcount-planning.md) | | HR-35 | Internal Mobility & Talent Marketplace | Event / Data | 📝 | Internal job postings consumed by HR-09 ATS; HR-13 skills matching; HR-10 performance | [HR-35 spec](../../../specs/hr/specs/HR-35-internal-mobility-talent-marketplace.md) | | HR-36 | Org Chart & Reporting Hierarchy Visualization | Platform Layer | 📝 | Org chart over HR-01 directory; PF-19 org consolidation consumer | [HR-36 spec](../../../specs/hr/specs/HR-36-org-chart-reporting-hierarchy-visualization.md) | | HR-37 | Mass Pay Action & Bulk Compensation Adjustment | Event / Platform | 📝 | Extends HR-15 compensation with bulk action engine; HR-PAY consumer; PF-47 bulk operations | [HR-37 spec](../../../specs/hr/specs/HR-37-mass-pay-action-bulk-compensation-adjustment.md) | | HR-38 | Volunteer & Student Intern Management | Data / Event | 📝 | Extends HR-34 contractor management with volunteer/intern lifecycle; HR-02 credential consumer; GR-08 accreditation | [HR-38 spec](../../../specs/hr/specs/HR-38-volunteer-student-intern-management.md) | ### IT — IT Asset Management (Wave IT) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----- | ------------------------------------------------ | ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | | IT-11 | Security Operations & HIPAA Safeguards Program | Event / Data | 📝 | Extends IT-05 security with HIPAA Security Rule administrative/physical/technical safeguard tracking; PF-91 compliance dashboard consumer | [IT-11 spec](../../../specs/it/specs/IT-11-security-operations-hipaa-safeguards-program.md) | | IT-12 | Breach Notification & Incident Response Workflow | Event | 📝 | Publishes `it_breach_detected` consumed by GR-09 incidents, GR-14 regulatory reporting, and PF-91 compliance dashboard; HHS HITECH 60-day notification | [IT-12 spec](../../../specs/it/specs/IT-12-breach-notification-incident-response-workflow.md) | | IT-13 | Vulnerability & Patch Management Program | Data / Event | 📝 | Extends IT-01 assets with vulnerability scanning + patch tracking; FW-46 worker for scheduled scans | [IT-13 spec](../../../specs/it/specs/IT-13-vulnerability-patch-management-program.md) | | IT-14 | Vendor Risk & BAA Management | Data | 📝 | Extends IT-03 vendor management with HIPAA BAA tracking; GR-10 contract consumer | [IT-14 spec](../../../specs/it/specs/IT-14-vendor-risk-baa-management.md) | | IT-15 | IAM SSO/SCIM Provisioning | External / Event | 📝 | SCIM 2.0 / SAML SSO provisioning to external apps; consumes HR-03 onboarding/offboarding; extends IT-08 IT onboarding | [IT-15 spec](../../../specs/it/specs/IT-15-iam-sso-scim-provisioning.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | IT-17 | IT Service Catalog & Self-Service | API / Platform | 📝 | Extends IT-02 ticketing with service catalog; PF-08 forms consumer; FW-34 approval routing | [IT-17 spec](../../../specs/it/specs/IT-17-it-service-catalog-self-service.md) | ### LO — Leadership Operating System (Wave LO) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----- | ---------------------------------------- | --------------- | ------ | ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- | | LO-17 | OKR Framework Support | Event / Data | 📝 | Extends LO-11 unified goals with OKR-shaped objectives + key results; events under `lo_events` channel | [LO-17 spec](../../../specs/lo/specs/LO-17-okr-framework.md) · [LO-INTEGRATION-OVERVIEW](./LO-INTEGRATION-OVERVIEW.md) | | LO-19 | Goal Cascading & Alignment Visualization | Data / Platform | 📝 | Extends LO-11 with parent/child goal cascading; LO-16 event integration consumer | [LO-19 spec](../../../specs/lo/specs/LO-19-goal-cascading-alignment.md) · [LO-INTEGRATION-OVERVIEW](./LO-INTEGRATION-OVERVIEW.md) | | LO-22 | Enhanced Execution Tracking | Event | 📝 | Extends LO-15 status events with execution metrics; HR-10 performance and PF-12 reporting consumer | [LO-22 spec](../../../specs/lo/specs/LO-22-execution-tracking.md) · [LO-INTEGRATION-OVERVIEW](./LO-INTEGRATION-OVERVIEW.md) | ### PF — Platform Foundation (Wave PF) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | --------------------------------------------- | ---------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | PF-42-EN-01 | Edge Function Rate Limiting | Platform | 📝 | Extends PF-42 rate limiting middleware to Supabase edge functions | [PF-42-EN-01 spec](../../../specs/pf/specs/PF-42-EN-01-edge-function-rate-limiting.md) | | PF-44-EN-01 | Tenant Data Portability | Platform / Edge | 📝 | Extends PF-44 export framework with full tenant export bundle (HIPAA right of access) | [PF-44-EN-01 spec](../../../specs/pf/specs/PF-44-EN-01-tenant-data-portability.md) | | PF-48-EN-01 | SIEM Integration | External / Event | 📝 | Streams `pf_security_event_detected` to external SIEM (Splunk / Datadog / Sumo); consumes PF-48 | [PF-48-EN-01 spec](../../../specs/pf/specs/PF-48-EN-01-siem-integration.md) · [EXTERNAL\_INTEGRATIONS](./EXTERNAL_INTEGRATIONS.md) | | PF-50-EN-01 | State-Aware Tenant Provisioning Templates | Platform | 📝 | Extends PF-50 provisioning with PF-96 jurisdiction-specific seed data per state | [PF-50-EN-01 spec](../../../specs/pf/specs/PF-50-EN-01-state-aware-tenant-provisioning-templates.md) | | PF-51-EN-01 | Cache Invalidation Contracts | Platform | 📝 | Documents canonical cache invalidation events emitted by mutation operations across cores | [PF-51-EN-01 spec](../../../specs/pf/specs/PF-51-EN-01-cache-invalidation-contracts.md) | | PF-54-EN-01 | CL/PM Formatting Adoption | Platform | 📝 | Extends PF-54 formatting utilities with CL/PM date/time/currency adoption guide | [PF-54-EN-01 spec](../../../specs/pf/specs/PF-54-EN-01-cl-pm-formatting-adoption.md) | | PF-67-EN-01 | Atomic Pin & Reaction Operations | Platform | 📝 | Extends PF-67 messaging with atomic pin/unpin and reaction toggle RPCs | [PF-67-EN-01 spec](../../../specs/pf/specs/PF-67-EN-01-atomic-operations.md) | | PF-73-EN-01 | Workflow Execution Analytics | Platform | 📝 | Extends PF-73 swim-lane visualization with FW-23 execution analytics overlay | [PF-73-EN-01 spec](../../../specs/pf/specs/PF-73-EN-01-workflow-analytics.md) | | PF-76 | Credential Vault | Platform Layer | ✅ | `@/platform/vault` — encrypted credential storage; consumed by HR-09-P5.4 Indeed, CE-03 RingCentral, PM-51 RPA, FA-32 Stripe, PF-65 Gusto | [PF-76 spec](../../../specs/pf/specs/PF-76-credential-vault.md) · [PLATFORM\_INTEGRATION\_LAYERS](./PLATFORM_INTEGRATION_LAYERS.md) | | PF-87 | Internationalization & Localization Framework | Platform Layer | 📝 | `@/platform/i18n` — message catalogs, locale routing, RTL support; consumed by CL-26-EN-64, CL-40-EN-01, FW-38, PM-12 | [PF-87 spec](../../../specs/pf/specs/PF-87-internationalization-localization.md) | | PF-91-EN-01 | White-Label Compliance Dashboards | Platform | 📝 | Extends PF-91 compliance dashboard with PF-95 white-label theming for tenant branding | [PF-91-EN-01 spec](../../../specs/pf/specs/PF-91-EN-01-white-label-compliance-dashboards.md) | ### PM — Practice Management (Wave PM) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ----------- | ------------------------------------------------- | -------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | PM-01-EN-01 | Patient Merge Workflow | Event / API + ADR-002 cross-core write | 🚧 | Publishes `pm_patient_merged` (consumed by CL-01 chart, PM-08 claims, CE-29 lead conversion, PF-71 patient identity boundary). Same-transaction `cl_patient_charts.patient_id` repointing inside `pm_merge_patients()` SECURITY DEFINER under [ADR-002](../decisions/ADR-002-cl-pm-cross-core-foreign-keys.md). | [PM-01-EN-01 spec](../../../specs/pm/specs/PM-01-EN-01-patient-merge-workflow.md), [INTEGRATION](./patient-merge-workflow-integration.md) | | PM-01-EN-03 | Patient Merge UI Workflow | UI (consumes EN-01 RPCs) | ✅ | Consumes `pm_merge_patients()` / `pm_undo_patient_merge()` SECURITY DEFINER RPCs and `pm_patient_merge_log`/`pm_patient_merge_conflicts` tables. UI surface only — no new cross-core writes. | [PM-01-EN-03 spec](../../../specs/pm/specs/PM-01-EN-03-patient-merge-ui-workflow.md) | | PM-02-EN-02 | Real-Time Eligibility w/ Benefit Detail Parsing | API | 📝 | Extends PM-02 271 response parsing with structured benefit/coverage detail; PM-34 check-in consumer | [PM-02-EN-02 spec](../../../specs/pm/specs/PM-02-EN-02-eligibility-benefit-detail-parsing.md) | | PM-08-EN-12 | Void/Replacement Claim Workflow | Intra-core (PM only) | ✅ | Completed 2026-05-05. No cross-core events. Mutates `pm_claims` (status → `void`, `frequency_code` → `8`/`7`, `original_claim_id`) and `pm_claim_notes` (`note_type = 'void'`) only. Replacement claims flow through the existing PM-15 clearinghouse contract. PM-09 refund/takeback coordination and PM-29 denial close-out reactions are tracked as future enhancements (separate spec slices). | [PM-08-EN-12 spec](../../../specs/pm/specs/PM-08-EN-12-void-replacement-claim-workflow.md) | | PM-08-EN-14 | 837I Institutional Claims | API | ✅ | Extends PM-08 claim format with X12 837I; PM-15 clearinghouse consumer. Completed 2026-05-04 — `pm_institutional_claim_details`, `pm_revenue_code_mappings`, `generate-837i-claim` edge function, jurisdiction fail-open scrubber, desktop-only UB-04 dialog. | [PM-08-EN-14 spec](../../../specs/pm/specs/PM-08-EN-14-837i-institutional-claims.md) | | PM-11-EN-01 | RCM KPI Benchmarking | API | 📝 | Read-only KPI snapshot API; PM-25 VBP consumer; external benchmarking comparison data | [PM-11-EN-01 spec](../../../specs/pm/specs/PM-11-EN-01-revenue-cycle-kpi-benchmarking.md) | | PM-29-EN-01 | Automated Denial Appeal Letter Generation | Platform / Event | 📝 | PF-11 document generation consumer; templated appeal letters per CARC/RARC; PF-27 AI assist | [PM-29-EN-01 spec](../../../specs/pm/specs/PM-29-EN-01-automated-denial-appeal-letters.md) | | PM-64 | AI Coding Assistant (Note → ICD-10 / CPT / HCPCS) | Event + Platform Integration Layer | 📋 | Consumes CL-04 `cl_note_finalized` via `@/platform/clinical` (PHI redacted at the boundary; fail-closed). Publishes `pm.ai_coding_suggestion_created` and `pm.ai_coding_decision_recorded`. Accepted codes flow into PM-07 charge capture; PM-50 scores denial risk on the resulting charge. RAG over PF-70 code library + PF-96 jurisdiction profiles; never hard-codes payer rules. NO PHI to LLM (constitution §4.3, GR-06-EN-01 pattern). | [PM-64 spec](../../../specs/pm/specs/PM-64-ai-coding-assistant.md), [INTEGRATION](./ai-coding-assistant-integration.md) | ### RH — Recovery Housing (Wave RH) | Spec | Title | Pattern | Status | Cross-core surface | Reference | | ---------- | ------------------------------------------- | --------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | RH-01-EN-1 | Grievance Tracking (Alternative Slice) | Data / Event | 📝 | Lightweight grievance tracking on RH-01; superseded by RH-09 full grievance management when implemented | [RH-01-EN-1 spec](../../../specs/rh/specs/RH-01-EN-1-grievance-tracking.md) | | RH-01-EN-2 | ADA / Accessibility — Residence | Data | 📝 | Extends RH-01 with ADA-compliant residence attributes; consumes PF-93 a11y standards | [RH-01-EN-2 spec](../../../specs/rh/specs/RH-01-EN-2-ada-accessibility-residence.md) | | RH-04-EN-4 | UDS Part 2 Access Controls | Data / Platform | 📝 | Extends RH-04 attendance with CL-11 42 CFR Part 2 consent gating for UDS results | [RH-04-EN-4 spec](../../../specs/rh/specs/RH-04-EN-4-uds-part2-access-controls.md) | | RH-06-EN-3 | Fire Inspection Compliance (Checklists) | Data / Event | 📝 | Extends RH-06 compliance with FM-06 inspection consumer for fire-life safety checklists | [RH-06-EN-3 spec](../../../specs/rh/specs/RH-06-EN-3-fire-inspection-compliance.md) | | RH-07 | Outcomes, Alumni & Reporting | Event | 📝 | Publishes `rh_alumni_engagement_recorded` consumed by CL-10 outcomes and CE-01 (re-engagement leads) | [RH-07 spec](../../../specs/rh/specs/RH-07-outcomes-alumni-reporting.md) | | RH-09 | Resident Grievance Management | Event | 📝 | Publishes `rh_grievance_filed`, `rh_grievance_resolved` consumed by GR-09 incidents and PF-10 notifications | [RH-09 spec](../../../specs/rh/specs/RH-09-resident-grievance-management.md) | | RH-UX-06 | Resident Grievance Filing Wizard (UI shell) | UI | 🟡 | UI shell only (3-step `WizardShell`); not mounted on a route; submit blocked until RH-09 backend (`rh_grievances` table + RPCs + permissions) lands | [RH-UX-06 spec](../../../specs/rh/ux/RH-UX-06-grievance-filing-wizard.md) | | RH-10 | Fire and Life Safety Compliance | Event / Data | 📝 | Cross-core consumer of FM-06 fire/safety inspection events; per-residence compliance status | [RH-10 spec](../../../specs/rh/specs/RH-10-fire-life-safety-compliance.md) | | RH-11 | NARR Level & AzRHA Certification (LITE) | Data / Event | 📝 | Cross-core consumer of GR-08 accreditation events; tracks NARR Level I–IV and AzRHA cert status | [RH-11 spec](../../../specs/rh/specs/RH-11-narr-level-azrha-certification.md) | *** ## Related Documentation * [Platform Integration Layers](./PLATFORM_INTEGRATION_LAYERS.md) - Detailed platform layer documentation * [Event Contracts](./EVENT_CONTRACTS.md) - Detailed event schemas * [API Contracts](./API_CONTRACTS.md) - Detailed API documentation * [Data Models](./DATA_MODELS.md) - Core data model documentation *** ## Quick Reference Guide ### Integration Pattern Decision Tree **Need to share functionality across multiple cores?** * ✅ Yes → **Platform Integration Layer** (Pattern 1) * Examples: Forms, Workforce, Data Lookup, Custom Fields, Notifications, Documents, Reports **Need asynchronous, loosely-coupled communication?** * ✅ Yes → **Event-Based Integration** (Pattern 2) * Examples: Resident admission → Billing account creation, Credential expiry → Scheduling block **Need synchronous, real-time data query?** * ✅ Yes → **API Contract** (Pattern 3) * Examples: Episode balance query, Employee lookup ### Common Integration Scenarios **Scenario 1: RH needs to display employee information** * ✅ Use: Platform Workforce Integration Layer (`EmployeeSelector`, `useEmployeeLookup`) * ❌ Don't: Direct import from HR core **Scenario 2: FA needs to create billing account when resident is admitted** * ✅ Use: Event-Based Integration (`rh_resident_admitted` in `fw_domain_events`; alias `resident_admitted` deprecated) * ❌ Don't: Direct function call from RH to FA **Scenario 3: RH needs to query episode payment balance** * ✅ Use: API Contract (`/api/v1/fa/episode-balance`) * ❌ Don't: Direct database query to FA tables **Scenario 4: HR-04 needs to block scheduling when credential expires** * ✅ Use: Event-Based Integration (subscribe to `credential_expired` event) * ❌ Don't: Poll HR-02 credential tables ### Integration Status Summary **Platform Integration Layers:** 7 layers (Forms, Workforce, Data Lookup, Custom Fields, Field Config, Notifications, Documents, Reports) * ✅ Complete: 7 * 🟡 In Progress: 0 * 📝 Planned: 0 **Event-Based Integrations:** 50+ events * ✅ Implemented: 22 (including FM-03 vendor events) * 📝 Planned: 28+ (including 18 IT module events) **API Contracts:** 7 contracts * ✅ Implemented: 0 * 📝 Planned: 7 (including 4 IT module APIs) *** ### Status Legend | Icon | Meaning | | ---- | ----------------------------------------------------- | | ✅ | Complete — implemented and verified | | 🔜 | Near-complete — implementation in progress, >75% done | | 🏗️ | In Progress — actively under development | | 🟡 | Partial — some phases complete, others pending | | 📝 | Planned — spec exists, not yet implemented | *** **Next Review:** 2026-06-20 (Quarterly)