Keep Tariff Configuration Traceable

Record the Source: Decouple Benchmarks from Contractual Authority

A tariff calculation is only as defensible as the authority backing it. Across scheme operations, teams frequently confuse a benchmark reference list with an agreed reimbursement mandate:

• Reference Baselines: Historical reference lists, indexed BHF schedules, or published scheme baseline rates serve as calculation benchmarks, but they do not automatically bind independent providers without an explicit agreement.
• Scheme Rules and Benefit Options: Benefit schedules determine what the scheme covers (e.g., 100%, 200%, or 300% of the Scheme Tariff), establishing the member's financial liability and sub-limit allocations.
• Contracted Network Arrangements: Bilateral agreements with DSP networks, preferred hospital groups, or individual general practitioner (GP) associations supersede baseline schedules—mandating specific global fees, fixed basket-of-care rates, or contracted discounts.
• Prescribed Minimum Benefits (PMBs): In emergency conditions or where no designated provider is accessible, Regulation 29(4) under the Medical Schemes Act requires payment in full at cost, overriding standard option limits.

Every line-item adjudication must permanently store its origin metadata: the specific scheme rule version, tariff schedule ID, and contract identifier. Without this lineage, resolving billing disputes with providers requires tedious manual archaeology through spreadsheets and historical emails.

Manage Effective Dates: Decouple Date of Service from Date of Ingestion

Healthcare claims processing does not occur in a static time window. Under the Medical Schemes Act, providers and members may submit claims up to four months following the date of service. Annual tariff escalations—typically executed on 1 January—create an immediate operational overlap where claims processed in February may relate to clinical events delivered in November or December of the previous year.

A robust tariff engine must manage temporal versioning deterministically:

• Date-of-Service Versioning: Claims adjudication rules must apply the exact tariff schedule and contractual rate active on the date the clinical service was rendered—not the date the electronic data interchange (EDI) file arrived at the switch.
• Mid-Year Contract Adjustments: Hospital network negotiations and DSP rate amendments often conclude mid-year with retroactive effective dates. The system must allow versioned tariff adjustments without corrupting already settled payment histories.
• Transparent Remittance Annotations: When a claim is adjudicated under a prior period's rate schedule, the member's and provider's remittance advice must clearly state the applicable rate schedule date, eliminating confusion and avoidable call-centre enquiries.

Reconcile Expected Outcomes: Test Before Release

Modifying a tariff schedule, relative value unit (RVU), or conversion factor is never just an administrative database import. A minor calibration error in a surgical multiplier or consultation code can distort scheme claims expenditure across tens of thousands of future transactions.

Before any tariff schedule or contract amendment is published to production adjudication, teams must validate its operational impact through batch simulation:

• Parallel Batch Simulation: Reprocess representative historical claim batches against the newly configured tariff structures to assess first-pass yield and identify unintended adjudication discrepancies.
• Variance Modeling: Measure total financial variance across risk pools, Medical Savings Accounts, and member out-of-pocket liabilities. Ensure that tariff adjustments have not inadvertently breached option solvency targets or shifted undue liability onto members.
• Discrepancy Reason Verification: Confirm that when a provider's claimed amount exceeds the contracted or scheme tariff, the resulting discrepancy reason code is objective, unambiguous, and compliant with Council for Medical Schemes (CMS) procedural fairness standards.