| Tenant | A customer organization with an isolated database. Identified by slug (e.g. acme) and tenant_id UUID. |
| Master DB | Single Postgres database holding cross-tenant registries: identity.tenant, security.platform_user, reference data (payers, procedure codes). |
| Tenant DB | Per-tenant Postgres database with HIPAA-isolated tenant data. Connection resolved at request time by TenantConnectionResolver. |
| Platform admin | MedSuite staff. Authenticates against security.platform_user in master DB. Logs in to the platform console at admin.<env>.medsuiteone.ai (prod: admin.medsuiteone.ai). |
Platform console (admin-app) | The operator SPA at admin.<env>.medsuiteone.ai, with admin-service answering /api/platform/* on the same host. Not to be confused with this manual (docs-admin), which is admin.docs.<env>.medsuiteone.ai. |
admin-service | The platform API process behind the console. Serves /platform/* (reached from a browser as /api/platform/*) and issues the platform JWT. Replaced the /platform/* router that used to live in rcm-core. |
| Tenant user | Customer staff. Authenticates against security.app_user in their tenant DB. Logs in at <slug>.rcm.medsuite.com. |
| Impersonation | Mechanism by which a platform admin gets a tenant-scoped JWT for the chosen tenant. Token carries scope: 'impersonation', platformUserId, and impersonating: true. |
| PLATFORM_ADMIN | Highest platform role. Provision tenants, manage platform users, impersonate any tenant. |
| PLATFORM_SUPPORT | Read + limited writes; may impersonate active and read-only tenants. |
| PLATFORM_READONLY | View-only across master data; cannot impersonate. |
db_server | Master DB row representing a Postgres flexible server that hosts one or more tenant DBs. |
| Tenant status | Lifecycle state on identity.tenant.status: active, read_only, suspended, offboarding. |
| Companion guide | Per-state or per-payer EDI variation rules layered on top of the X12 standard. |
| Program setting | Per-tenant configuration (config.program_config) of how a program (state Medicaid plan, commercial product) is billed: accepts claims, auth workflow, filing window, submission routing. The setting with no payer applies to every payer; a payer-specific setting replaces it for one payer. Was "payer program config". |
| Program rule | MedSuite master rates and code rules for a program in a state (rcm_master.program_rule): standard (no payer), payer exception (one payer) or national (no state). Was "payer program". |
| Trading partner | An EDI counterparty (clearinghouse, state Medicaid MMIS, commercial payer) with a connection config (SFTP, AS2, real-time). |
| Ingestion feed | An inbound channel that delivers raw data files into the platform (SFTP polling or push API). Each feed is bound to a mapping definition. |
| Mapping definition | YAML spec that transforms a raw inbound record into a canonical entity. Versioned and lifecycle-managed (DRAFT → SUBMITTED → ACTIVE → ARCHIVED). |
| ERA / 835 | Electronic Remittance Advice. Inbound payer payment file. Posted via the Receivables workspace. |
| EOB | Explanation of Benefits — the human-readable analog of an ERA. |
| COB | Coordination of Benefits — payment waterfall when a member has multiple payers. |
| Auto-correction | Automated rebill flow that fixes claim denials by adjusting modifiers, hints, or attachments and resubmitting. |