RCM & insurance

Draft provider contracts and policies with explicit unresolved facts

Follow the actual contract UI, verified document chain, policy API continuation and remaining activation guards.

Current source · Source reviewed; exact stated local synthetic UI/API continuation and independent readback observed · 12 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. Save the dated provider contract draft

Open Provider Contracts → Add contract. Choose type, provider, counterparty and evidenced tax recipient. Commit the applicable period, separately from future document signed/received dates. The current contract UI saved the fictional 2026 period correctly.

**Create a dated provider contract draft · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The current contract UI correctly exposes provider, counterparty, tax recipient and effective dates. The operator committed 1 January through 31 December 2026 and clearly marked the dispute process as fictional; no executed real contract or tax determination is asserted.
**Contract type**: Choose the actual contracting structure.
**Provider and counterparty**: Distinct legal participants remain explicit.
**Tax recipient**: The recipient is a separate evidenced fact.
**Applicable dates**: The contract period is separate from signed and received dates.

**Inspect the actual UI-created contract draft · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The UI-created contract persisted its period and fictional parties, remains Draft/not engine selectable and shows missing pricing method/date rule, network, tariff, calendar, billing customer role and service levels as unknown. Unknown values are not zero or defaults.
**Draft saved**: Creation did not approve or activate the contract.
**Persisted effective period**: Independent API readback confirms these dates.
**Pricing date unresolved**: The pricing date need not be the transport submission date.
**Tariff absent**: No default price list was silently selected.

2. Select a verified source for the document chain

Open Document chain → Add document. Select kind and sequence, retain title, signed date and received date, and select the reviewed source. Hash and storage reference come from that source. The fictional base example uses mock signed metadata from the retained test PDF; it represents no executed agreement.

**Read document-chain requirements before attaching · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The document dialog distinguishes base/amendment/addendum/annex, sequence, signed date, received date and a verified source selector. Hash and private storage reference derive from the selected verified source rather than editable text.
**Kind and sequence**: Retain amendment chronology instead of replacing old bytes.
**Signed and received**: Receipt is not legal commencement.
**Verified source selector**: Select an already reviewed retained source.

**Select the retained mock source for a chain row · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. Actual Admin UI selected the independently reviewed mock source, base kind, sequence 1, fictional title and separate signed/received dates. At 1280px the dialog clips its right side; this frame proves source selection, not a visible Save control.
**Base document kind**: Use the correct kind rather than replacing an existing document.
**Mock signed metadata**: This date is fictional fixture metadata with no execution effect.
**Selected verified source**: Hash derives from this retained source.

3. Verify the saved chain row

After Save, confirm sequence, source identity, dates and content hash through the chain and independent readback. The example persisted base sequence 1, signed 2026-01-01 and received 2026-10-18. A green chain-consistency message does not activate the contract.

**Verify the persisted chain after actual UI Save · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. Actual UI Save added the fictional base document with signed 2026-01-01, received 2026-10-18, sequence 1 and the reviewed source hash. Independent normal API GET confirms the exact document/source IDs and digest. Contract evidence, SLA, approvals and package remain separate requirements.
**Chain consistency result**: Sequence/hash consistency is not legal contract qualification.
**Saved fictional document**: The title explicitly denies legal effect.
**Different signed/received dates**: Independent GET confirms both dates.

4. Resolve remaining contract prerequisites separately

Open Governance and read every reason. Linking the chain removed the missing-chain finding after reload, while four named remedy rules, contract-level evidence/source, package and lifecycle approval still remained. Do not assume a source link fills SLA triggers, day basis, dates, pricing, tax or independent approvals.

**Read all original contract blockers · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. Before linking its document chain, the draft correctly refused activation for missing signed scope, four named SLA rules, direct draft-to-active transition, evidence/source provenance and configuration package. No gate was closed to make the demonstration green.
**Missing signed scope**: A public instrument cannot substitute for bilateral signed scope.
**Named remedy rules required**: A duration alone does not establish trigger or day basis.
**Evidence and lifecycle guards**: Fix the stated evidence and approval prerequisites.

**Recognize remaining guards after document linking · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. After reloading, the signed-chain missing error is gone, but missing four SLA rules, direct draft-to-active transition, contract evidence/source and package still prevent activation. A chain link does not automatically attach contract-level provenance.
**Remaining readiness findings**: Resolve every named prerequisite separately.

5. Capture a policy without manufacturing a product

In Products & Policies, select programme first, then the actual product or explicit unknown state. Preserve insurer, policy system, policy-number leading zeros, currency and verification source. The current draft form omits required holder/effective period and produced a nested validation failure.

**Draft a policy without inventing product mapping · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The policy UI distinguishes insurer, programme, optional product, policy system/number, currency and verification source. It retains leading zeros. This form omits required holder and effective_from fields; its save failed and the separate normal API continuation supplied a fictional corporate holder and period.
**Programme first**: Do not infer programme from a class or card brand.
**Product explicitly unknown**: Pending mapping is not a placeholder product.
**Policy number text**: Keep leading zeros.
**Attempted save**: The current UI failure is documented separately.

**Recognize the current policy save failure · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The policy form returned a nested validation refusal for missing policyholder and effective_from; the current error renderer showed an unexpected-error fallback. Repeated clicking does not repair the required data.
**Unexpected-error fallback**: Inspect the normal API constraint details and saved records before retrying.

6. Verify the separately supported policy continuation

A normal authenticated API continuation supplied a fictional corporate policyholder and explicit period. The refreshed draft retains 000-KB-SYNTHETIC-2026, product mapping pending, no source schedule/version and no policy-specific classes. Complete actual schedule, product, class, network, benefit, evidence and governance prerequisites before production activation.

**Inspect the policy produced by the separate API continuation · 2026-10-18**Actual audited MANSOQ production frontend in isolated synthetic training. The refreshed policy readback comes from a separately documented normal authenticated API continuation with a fictional corporate holder and 2026 effective period. It remains Draft with unknown product mapping, no source schedule/version, no policy-specific classes, absent evidence and no package.
**Product mapping pending**: Provisional coverage capture is restricted.
**Leading zeros retained**: Policy identity includes insurer, system and number.
**Source schedule/version missing**: Do not activate an unversioned schedule.
**Policy classes missing**: A policy number alone establishes no usable benefit class.

Source evidence

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