Skip to content
PV1RX

Methodology

What we calculate, what we do not assume.

Plain, practical statements about how PV1RX reads records and computes economics. Where the evidence is thin, the method says so.

Arithmetic is TypeScript, never a model.

Every economic figure is computed by deterministic, versioned code. Models are limited to constrained support tasks and never touch a number.

Receipt

  1. 01Receipt reads weekly dispensing and purchasing files locally in the browser.
  2. 02A versioned header-alias table maps source headers to expected fields.
  3. 03NDCs are normalized to 11 digits.
  4. 04Matched purchase evidence supports weighted-average unit cost calculations.
  5. 05A fill without supporting purchase evidence remains unmatched.
  6. 06No AWP, NADAC, or external benchmark is used to fill missing cost evidence.
  7. 07Every saved aggregate carries a methodology version, so future logic changes never silently reinterpret historical results.

Ledger and Statement

  1. 01Ledger reconciles claims and remittance before it produces economic findings. Claims must tie to remittance control totals, net of reversals and documented post-adjudication fees.
  2. 02If reconciliation does not meet the defined threshold, the run halts or is explicitly marked incomplete.
  3. 03Cost basis is explicitly labeled as invoice-backed or effective where applicable.
  4. 04Deterministic rules produce candidate findings. Each retains affected transactions, source lineage, economic impact, confidence, materiality, and a disposition.
  5. 05Low-confidence or high-materiality cases enter a human review queue before publication.
  6. 06Follow-up data is processed through the same pipeline, and realized value is written back to individual findings.

Where models are used, and where they are not

  1. 01Models may assist with constrained classification of candidate patterns for human review.
  2. 02Models may draft explanation text from approved facts.
  3. 03Models may extract semi-structured contract terms into candidate fields. Those fields require human confirmation before a deterministic rule can use them.
  4. 04Models may flag anomalies that warrant deterministic review.
  5. 05No model calculates, adjusts, or invents an economic figure.

Audit trail

For every finding, PV1RX must be able to show

  1. The original source records
  2. The normalized fields
  3. The cost basis
  4. The method version
  5. The rule applied
  6. The evidence considered
  7. The finding produced
  8. The action recorded
  9. The outcome measured

Limitations

  • Weekly Receipt data can show a pattern. It usually cannot explain one.
  • Coverage is reported honestly. A week with thin purchase evidence will show low coverage, not a guess.
  • A finding is an observation with a stated confidence. It is not a legal, accounting, or reimbursement conclusion.
  • Modeled opportunity is not realized value until a follow-up export shows the change.