Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Contract Modeling Simulation Wizard guides users through a five-step process to model and version revenue scenarios for payer contracts. Route: /pm/contracts/modeling/new.

​
Overview

ContractModelingWizardPage renders WizardShell with five steps driven by useContractModelingWizard:
  1. Baseline Selection — choose a contract and timeframe
  2. Volume Assumptions — enter service volume projections
  3. Rate Adjustments — make code-level rate changes
  4. Forecast Output — view modeled revenue metrics; a Recompute action marks the forecast fresh
  5. Review & Submit — save and version the scenario
On success, the user is redirected to /pm/contracts.

​
Who it’s for

Requires permission pm.contracts.view (PM_PERMISSIONS.CONTRACTS_VIEW).

​
Before you start

  • An existing payer contract must be present at /pm/contracts to use as a baseline.
  • Ensure volume projections data is available for the scenario period.

​
Steps

1

Open the wizard

Navigate to Practice Management → Contracts → Modeling → New, or go to /pm/contracts/modeling/new.
2

Select a baseline contract and timeframe

On the Baseline Selection step, choose an existing payer contract and define the modeling period.
3

Enter volume assumptions

On the Volume Assumptions step, provide service volume projections for the scenario.
4

Adjust rates

On the Rate Adjustments step, apply code-level rate changes to model a proposed contract scenario.
5

Review forecast output

On the Forecast Output step, review computed revenue metrics. If inputs changed, click Recompute to refresh the forecast.
6

Save and version the scenario

On the Review & Submit step, confirm all inputs and submit. The scenario is versioned and you are redirected to /pm/contracts.

​
Key concepts

  • Stale forecast — the forecast is marked stale when volume or rate inputs change; a recompute is required before submission.
  • Scenario versioning — each submission creates a versioned snapshot; existing contracts are not modified.

Practice Management

Practice Management core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/pm.tsx
  • src/cores/pm/pages/ContractModelingWizardPage.tsx
  • src/cores/pm/hooks/useContractModelingWizard.ts