Budget impact
Set up, run, and review this analysis in Lifescio.
Supported analysis
For each year, multiply the eligible population by the cost of the current and proposed treatment mixes. Uptake determines the share receiving the new intervention. The app reports annual and cumulative undiscounted differences.
Supported scope: Population is the annual eligible stock, not automatically accumulated incident cases. Costs are annual per-person values; avoid counting the same resource twice. Patient progression, treatment duration and future population changes are not inferred from the input rows.
Prepare data and configure the analysis
In Annual assumptions, enter years in increasing order and one row per year: eligible population, current uptake, proposed new uptake, comparator annual cost, new-treatment annual cost, and other incremental cost. Uptake uses proportions such as 0.25; all costs and population values must be nonnegative.
The final cost column is charged per new-treatment user in the proposed scenario. It is not a one-off whole-program total and is not applied to the current scenario. Include only the extra component intended by that definition. The calculation is annual and undiscounted; it does not carry individual patients between rows.
Input reference (1 fields)
Enter your data and prespecified choices. Ranges include both limits. For table fields, use cell editing, Paste data, or Import CSV / TSV. Review whether the first imported row contains headings and map the source columns before applying the import. Empty numeric cells are not treated as zero. Open file is for an exported Lifescio analysis JSON file, not a spreadsheet.
| Input | Format | Allowed range | Guidance |
|---|---|---|---|
| Annual assumptions | Table | — | Costs are per treated person per year; population is the annual eligible stock. Columns in order: Year; Eligible population; Current uptake; New uptake; Comparator cost; New-treatment cost; Other incremental cost. |
Run and review
- Give the analysis a descriptive name and review every example value. Record units, data preparation, and planning assumptions in Reproducibility & notes. For simulations, record the seed and replication or sampling settings.
- Choose Run analysis. Resolve input errors before interpreting output. In the connected app, a run uses a saved input revision; local preview runs need the page to stay open.
- Review Diagnostics for method limitations, warnings, and available numerical checks. A completed run means computation finished; it does not establish that the assumptions fit your study.
- Use the Result table selector to inspect each output. Editing inputs does not recalculate existing results: an earlier-input notice means you need to run again to obtain matching results.
Understand the outputs
Annual budget impact shows current spending, proposed spending, their difference, and the cumulative sum. Current spending uses current uptake and the two treatment costs. Proposed spending uses new uptake and adds the other incremental cost to each proposed new-treatment user.
Check one year's arithmetic before interpreting the graph. If current and new uptake are equal but other incremental cost is positive, proposed spending can still be higher. These are budget totals, not per-person cost-effectiveness results.
Troubleshooting and common mistakes
A rejected table commonly contains unordered years, negative costs, or uptake entered as 25 instead of 0.25. Ensure that the other incremental cost is per treated person rather than the total program budget.
If expected savings cannot be represented because a cost-offset component would be negative, revise a transparently defined net annual cost outside this input model or use a more suitable budget model. Do not enter a negative value into a field that requires nonnegative costs.
After correcting inputs, run again and check that the results belong to the new input snapshot. Increasing simulation draws improves numerical precision only; it does not repair invalid data or an unsuitable model.
Save, compare, and export
In the connected app, Save analysis retains the inputs in your account. Run history lets you inspect earlier runs, each with the input revision it used. In local preview, Save analysis downloads an input file instead; download results before leaving the page.
Use Result + inputs for a JSON archive containing the completed result and its inputs, Download CSV for the selected result table, PDF report for a report, and a chart's SVG button for its figure. Table displays round to three decimals; CSV and JSON exports retain calculation precision. Use those values when assessing a result near a decision boundary.
To reopen an archive, select the matching analysis method and choose Open file. Imported inputs start a new draft; a result archive can also display its retained result. It does not attach itself to an existing account analysis or recompute the result. Save or run the imported draft when you want a new account record.