KuTh Consultants (Pty) Ltd

Medical Products & Consumables Procurement Optimisation · Technical White Paper

Medical Products & Consumables Procurement — Technical White Paper

Invoice reconstruction, product due diligence, supplier negotiation, clinical acceptance governance and the result-state discipline that keeps an opportunity honest.

Publication boundary

Modelled and provisional results only. Neither the initial R992,546.18 opportunity nor the later R1,788,234.30 provisional position is presented as a realised annual saving — the source evidence does not support that classification for the whole amount.

Client, supplier and product-brand identities are withheld, as are unit rates. The engagement’s limitations are stated rather than smoothed over.

Executive overview

The commercial question could not be answered on its own

Medical-product purchasing was reconstructed from supplier invoices across twelve months and separated into three sectors. The analysis moved below supplier totals to individual products, quantities, price ranges and purchasing patterns.

What makes this engagement distinctive is not the size of the opportunity but the gate placed in front of it. In healthcare procurement, commercial optimisation cannot be separated from clinical suitability — so commercial and product-validation work ran as parallel tracks, and the client’s clinical specialists retained the acceptance decision at every point.

6. Product-level due diligence

Comparing products, not brands

Scroll table sideways →

Comparison fieldWhy the field matters
Intended useEstablishes whether the comparison is functionally relevant at all
Available sizesA price advantage is unusable if the patient’s required size is absent
System formatOne-piece and two-piece architecture affects accessories and the user’s daily routine
Wear and fit characteristicsProduct behaviour can determine leakage risk and user acceptance
Price rangeVaries by size, so a single headline price is not a comparison
Related accessoriesBase plates and ancillary requirements can move cost outside the compared item

The control was never the brand name. It was whether the alternative could meet the patient’s physical and clinical requirements, and whether the product family contained an appropriate equivalent for the specific item being replaced.

11. Clinical acceptance governance

An iterative process, not a single sign-off

Scroll table sideways →

StageRecorded decisionFinancial effect
20 February 2024Primary and ancillary alternatives presented for specialist input; patient choice and prescription factors raisedInitial opportunity remains provisional pending product feedback
4 March 2024Primary stoma products to remain unchanged; ancillary described as open to alternativesPrimary substitution scope narrows materially
18 March 2024Further repricing, supplier negotiation, institutional-supplier meetings and anomaly work agreedOpportunity shifts toward repricing plus selective alternatives
3 April 2024Alternative products reported accepted after due diligence; further alternatives requestedCandidates move toward implementation, subject to exact-product control
5 April 2024At least one previously accepted alternative later rejected or reconsideredAssociated benefit can no longer be treated as implementation-ready without resolution

Clinical review did not make optimisation impossible. It changed the set of savings that could responsibly remain in the implementable model. A rejected alternative is a control event that improves the reliability of the final result.

12. Product-identity control

A rejection is only useful if it names the right product

A later dispute exposed a subtle governance failure: the rejection reason appeared to describe a different product from the one that had been proposed and approved. The documentation distinguished a convex barrier-ring product from a different mouldable-ring product discussed in clinical feedback.

This is a classic master-data problem. Similar product names, several rings and seals in the same functional family, and multiple alternatives discussed in one meeting can produce a mismatch between the item being evaluated and the item recorded in the workbook. Once that happens, a saving can be removed for the wrong reason — or retained despite a genuine rejection.

The rule that follows: every approval or rejection must link to an exact product identifier, supplier, description, size and configuration, decision date and named approver. Product-family language should never be the sole key in a clinically sensitive savings model.

12.1 Minimum approval record

Ten fields that make a clinical decision auditable

Scroll table sideways →

FieldRequired entryReason
Current productExact code and descriptionDefines what is being replaced
Alternative productExact code and descriptionPrevents confusion with another product in the same family
SupplierCommercial sourceConfirms the route to which pricing applies
Pack / size / configurationComparable unit basisAvoids approval of a different pack or clinical size
Clinical reviewerNamed authorised specialistCreates decision accountability
DecisionAccepted / rejected / conditional / trialAvoids ambiguous meeting language
ReasonShort technical rationaleAllows later audit and model correction
Effective dateDate the decision appliesSupports version control
Commercial price versionQuote or price-list datePrevents mixing an accepted product with an expired price
Model linkWorkbook row or decision IDEnsures the calculation uses the same product record

13. Invoice anomalies

Seven steps from variance to recovery

01

Identify the price variance

Use invoice-level data to isolate dates, quantities, invoice numbers and unit rates.

02

Establish the agreed comparator

Locate the applicable quotation, price list, contract schedule or purchase order.

03

Test period validity

Confirm the comparator applied on the transaction date and had not been superseded.

04

Reconcile quantities and credits

Check whether rebates, credit notes, backdated adjustments or free stock altered the effective price.

05

Obtain supplier response

A variance is a question until the supplier confirms or disputes it.

06

Reconcile any counter-claim

Do not net an asserted supplier undercharge against a client overcharge without transaction-level evidence.

07

Recognise only the resolved amount

Recovery becomes a result when a credit, refund, corrected invoice or agreed adjustment is evidenced.

11.1 Patient uptake

Assuming full conversion overstates the value

Specialists identified several reasons why uptake could differ from a purely commercial recommendation. Patients may be accustomed to an existing product. A doctor may have prescribed a particular one. Stoma shape and skin condition affect fit. Medical-aid exhaustion can create demand for lower-cost alternatives later in the benefit cycle.

Substitution may therefore need to be patient-selective rather than portfolio-wide — which changes how savings should be measured. Where uptake is uncertain, the correct approach is to calculate scenario ranges, or to measure realised conversion from transaction data, rather than assume full migration.

19. Limitations

What remained unproven, stated plainly

  • Early data completeness. The first clinical review rested on an invoice set described as roughly 80–85% complete.
  • Changing product acceptance. Status changed during the engagement; any model tied to an earlier state must be recalculated.
  • Patient uptake uncertainty. Even an accepted alternative may not achieve full portfolio conversion.
  • Supplier terms still developing. New pricing could carry conditions such as contractual commitments and further qualification.
  • Accounting cross-reference in progress. The later provisional model was still being reconciled to the accounting system.
  • Supply transition. A distributor change created uncertainty over product continuity and future prices.
  • Anomaly counter-position. A supplier asserted an undercharge requiring further reconciliation.
  • Mandate interruption. Some planned supplier and medical work was halted, limiting completion of implementation steps.