RCM & insurance

Create insurance parties, roles, identifiers and administration drafts

Separate legal identity, licence facts, environment-qualified identifiers, delegated functions and settlement responsibility.

Current source · Source reviewed; exact stated local synthetic UI/API continuation and independent readback observed · 10 min read

Before you begin

Use a separate synthetic training estate and authorized maker/reviewer accounts for demonstrations. For production, use the actual approved organizational and contract sources.

1. Create one bilingual organization

Search existing entities first. Add the organization’s internal code, actual Arabic/English legal names, registered name, country and local classifications. An Insurer label or brand does not establish an insurer role or licence.

**Draft one bilingual fictional legal entity · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The Facility Admin prepared one insurer organization with distinct Arabic/English legal names, registered name, country and local payer classification. A name containing Insurer does not grant an insurer role, licence or routing authority.
**Internal code**: Unique organization reference, separate from routing identifiers.
**Bilingual legal names**: Record each language from its actual source.
**Registered name**: Retain the source name as written.
**Local payer class**: Unclassified remains unresolved.

**Verify a saved unclassified organization draft · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. Actual organization UI creation saved the fictional insurer as Draft, unclassified, without evidence and not engine selectable. Independent API readback confirms its entity identity; no licence or insurer authority exists.
**Saved internal code**: Open this exact entity.
**Draft retained**: Creation did not activate the organization.
**Evidence absent**: Nothing establishes the row for production.

2. Add each evidenced role separately

Open Roles and record role, licence requirement, issuing authority, number, status and validity. The current form omits required configuration effective_from, and its attempted save produced a nested-refusal page error. In the teaching case a normal authenticated API continuation supplied the explicit 2026 period; the resulting role remains Draft with unknown licence status.

**Keep role and licence facts separate · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The actual role form distinguishes Insurer, licence-required state, issuing authority, number, licence status and licence validity. This 1728px frame has a horizontally clipped left edge. The form omits the separate required row effective_from; its attempted save failed.
**Insurer role**: Risk bearing does not imply administration authority.
**Licence requirement unknown**: Unknown does not mean no licence is required.
**Fictional number**: SYNTHETIC-NOT-A-LICENCE is not legal evidence.
**Attempted draft save**: The current UI attempt was refused; do not treat this as success.

**Recognize the current nested-refusal rendering failure · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The role form sent no row effective_from, the backend returned the effective-date constraint refusal, and the nested error renderer fell back to a page error. This is a current implementation defect, not a successfully saved role.
**Error fallback**: Reopen the entity and inspect whether any row persisted before retrying.
**Return control**: Do not repeatedly create duplicate roles.

**Inspect the separate normal API continuation · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. A separately documented normal authenticated role-create endpoint supplied the required row effective period 2026-01-01 to 2026-12-31 and saved Draft. This refreshed UI shows the saved insurer role, while licence status/requirement remain unknown and licence validity open-ended. The defective UI save did not produce it.
**Saved insurer role**: One entity may have separately evidenced roles.
**Licence status unknown**: A recorded fictional number is not a current licence.
**Licence versus row dates**: Licence validity and configuration effective period are separate fields.

3. Record the canonical system, opaque value and environment

Open Registered identifiers. Use the audited identifier namespace, preserve the registered opaque value and select the actual environment. The fictional Test value is not a genuine payer licence. Prepared date fields in the intermediate frame were not saved; the final independently read-back teaching identifier is open-ended.

**Use the canonical identifier namespace and Test environment · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The corrected draft uses the audited canonical NPHIES payer-licence namespace, an expressly fictional NOT-A-PAYER-LICENCE value and Test environment. Prepared dates here were not the final saved values: the saved teaching identifier is open-ended, as shown in the subsequent readback.
**Canonical namespace**: System URI is part of identity, not arbitrary branding.
**Opaque test value**: Never manufacture a genuine licence to match an expected prefix.
**Test environment**: Environment is part of identifier uniqueness.

**Read the exact saved identifier and qualification limits · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. Normal UI save created the fictional Test identifier with canonical system URI and open-ended validity. The NII/NIIP dictionary/expansion facts remain unknown and evidence absent; valid-on-date does not mean licensed or qualified.
**Stored test value**: Match system, value and environment together.
**Actual saved dates**: This record is open-ended; the earlier date draft is not its saved period.
**Vocabulary remains unknown**: No field-dictionary/value-set qualification was invented.
**Evidence still absent**: Test identifier does not establish routing authority.

4. Keep the administrator as a separate entity

Create or locate the TPA identity, then establish its own role and evidence. The demonstration saved a separate bilingual draft with non-routable branding and unknown classifications; no administration authority was inferred.

**Draft the administrator as its own entity · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The existing Admin entered a separate bilingual fictional TPA entity. Display branding and local classifications cannot replace registered identifiers, role evidence or delegated authority.
**Distinct organization**: The insurer and administrator are separate entities.
**Administrator legal name**: A TPA display name grants no delegated function.
**Unclassified local category**: No legal classification is inferred from a brand.

123

Read the TPA identity without inferring routing · 2026-10-18Actual audited MANSOQ production frontend in isolated synthetic training. Actual UI creation saved the separate TPA draft with bilingual names, unknown registered-language/type/regulator and a non-routable display brand. Independent normal API readback confirms it remains draft with absent evidence.

Draft and not selected: Saved identity is not operational authority.
Local class unresolved: Unclassified is not a commercial-insurer conclusion.
Brand does not route: Searchable branding is separate from role-qualified routing identity.

5. Model delegation and settlement facts explicitly

In Administration Agreements, distinguish insurer, administrator, settlement mover, liability party, transaction scope and routing date basis. The current form also omits required row effective_from, so its save failed. A separate normal validated API continuation supplied dates and retained a draft. Each actual delegated function and production scope still needs its own evidence.

**Separate delegated parties from settlement responsibility · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The draft distinguishes insurer, administrator, settlement owner, settlement liability party, transaction scope and routing date basis. This exact UI attempt omitted the required row effective_from and failed; the successful dated draft came from the separately documented normal API continuation.
**Insurer and administrator**: Eligibility delegation does not imply authorization or claims delegation.
**Settlement mover**: Who moves money is separate from who owes the liability.
**Liability party**: Do not substitute the administrator automatically.
**Explicit transaction scope**: Each transaction must resolve its own delegation.

**Recognize the agreement effective-period refusal · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The backend refused the UI agreement payload for its missing required effective_from and the nested refusal renderer showed a page error. A normal validated API continuation supplied dates and saved a draft without inventing actual delegated authority.
**Failed UI save**: Inspect the saved state and API refusal before retrying.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.