← Knowledge library

Security & governance

Review, simulate and publish configuration safely

Move source-backed rules through explicit approval and preserve historical decisions.

Current source · source reviewed · 7 min read

Before you begin

1. Finish the draft and validation

Review missing values, source evidence, overlaps, effective dates and open gates. Use validate to obtain specific blockers rather than entering placeholders.

2. Simulate representative cases

Inspect outpatient, inpatient and pharmacy examples as relevant. The documented simulation transaction rolls back its writes, allowing before/after assessment without a financial posting.

3. Request independent approval

Use the current lock token and have the authorized approver review the latest row. A stale token requires rereading and comparing the current version.

4. Publish an immutable package

After approval and effective-date checks, activate/publish the supported configuration. The package records sequence, hash, manifest, validation/test reference and governance actors.

5. Correct by a new version

To change active configuration, create a successor with its own reason and approvals. Superseded versions remain available for historical decision reconstruction.

Lifecycle

The core lifecycle includes draft, in_review, approved, scheduled, active, suspended and superseded. There is no draft-to-active shortcut. Inspect the authoritative state machine for permitted edges.

Past claims remain explainable

A new package does not recompute a previously submitted claim. Each decision trace names the immutable package that governed it.

Troubleshooting

The save or approval reports a stale lock token

Reload the record, compare the intervening change and repeat review with the latest token. Do not overwrite another editor’s update.

Source evidence

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