EVIDENCE OS / DELIVERY SAMPLE

Update the model only when inputs or conclusions warrant it

Real sources · Illustrative request · Sample version

Customer question

Hypothetical commission: a payer monitors two existing service evaluations for prices and new trials.

Which parameter changes, and is an agreed model update warranted?

Quarterly scans first explain changes; model updates remain distinct from complete reassessments.

Parameter changes to version decisions

Check / stageChart content
Preserve baselineOld inputs, source dates and model version
Assess new informationCheck price/trial applicability and fields affected
Update or retainRecord triggers within two agreed model updates

Fictional workflow, not observed input changes or policy effects. Existing scope: two services, four quarterly briefs and two in-scope model updates.

Analysis excerpt

CheckFinding / sample contentUse
Clinical inputNew trials may not match the original populationRecord applicability and non-adoption rationale
Model versionRetain the old versionCompare inputs and outputs
Trigger decisionScanning does not automatically charge for updatesConfirm out-of-scope reassessment

Delivery manifest

FileFormatContents
Quarterly change briefsPDFFour briefs: new information, parameter mapping and no-change records
Source and parameter versionsXLSXOld/new sources, dates, applicability and triggers for two services
Agreed model update packageXLSX / PDFTwo in-scope updates, version comparisons and four discussions

This is an illustrative formal delivery manifest. This pack supplies an HTML report, CSV tables and a source register. Agree formal formats, quantities and scope in the quote.

Acceptance criteria

Sources

  1. NICE · Economic evaluation (PMG36)
    https://www.nice.org.uk/process/pmg36/chapter/economic-evaluation-2