Version: 1.0.0Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
Status: ✅ Complete — 2026-03-01
Last Updated: 2026-02-27
Spec: PM-27 Multi-Site & Multi-NPI Configuration
Constitution Reference: Section 1.2 (Core Independence), Section 1.3 (Integration Patterns)
Overview
PM-27 provides site-level billing configuration (billing NPI, tax ID, addresses, fee schedule, clearinghouse routing, claim defaults) and optional patient site-transfer workflow. Claim generation (PM-08) and clearinghouse submission (PM-15) consume site billing config per encounter/appointment site. Key tables:pm_site_billing_config, pm_patient_site_transfers (optional)
Integration Points (from spec)
| Dependency | Pattern | Purpose | Status |
|---|---|---|---|
| PF-01 | Data (sites) | Organizations and sites; site list and attributes | ✅ Available |
| PM-08 | Data (read config) | Claim generation reads site billing config for NPI, tax ID, address, POS, fee schedule; claim lines use site-appropriate provider | 📝 Planned |
| PM-15 | Data (routing) | Clearinghouse config per site for submission routing | 📝 Planned |
| PM-11 | Data (filter/group) | Filter and group reports by site_id; site-level KPIs | 📝 Planned |
| PM-17 | Data (optional) | Provider enrollment may be site-specific; link to site billing NPI where applicable | 📝 Planned |
Platform Integration Layer Usage
- PF-01: Site list and attributes via
pf_sites; organization context viapf_organizations. - PM-08: Resolve site from encounter/appointment → load
pm_site_billing_configfor that site → apply NPI, tax ID, address, default POS, fee schedule, claim defaults when building claim. - PM-15: Per-site
clearinghouse_config_iddetermines which clearinghouse/config is used for submission when claim is associated with a site.
Event Contracts
No new events defined in PM-27. Optional: future eventpatient_site_transferred if transfer workflow triggers notifications or downstream consumers (documented in EVENT_CONTRACTS.md when implemented).
API Contracts
Internal PM only. Hooks and queries for site billing config and patient site transfers; no external API exposed. PM-08 and PM-15 integration is via shared tables and in-process resolution of site → config.Integration Matrix
| From | To | Pattern | Status | Doc |
|---|---|---|---|---|
| PM (PM-27) | PF-01 | Data (sites) | ✅ Available | This doc |
| PM (PM-27) | PM-08 | Data (site billing config) | 📝 Planned | PM-08 Integration |
| PM (PM-27) | PM-15 | Data (clearinghouse per site) | 📝 Planned | PM-15 Integration |
| PM (PM-27) | PM-11 | Data (site dimension) | 📝 Planned | PM-11 Integration |
| PM (PM-27) | PM-17 | Data (optional NPI link) | 📝 Planned | PM-17 Integration |