Scope: professional education and governance analysis, not patient-specific medical, reimbursement, or legal advice. Translations of China-specific policy terms are unofficial.

Executive takeaways

  • An awarded procurement price is not automatically the patient charge or the medical-service price.
  • Committed volume does not replace clinical suitability.
  • Hospitals need end-to-end evidence from procurement and inventory to use, billing, and traceability.

Separate five price concepts

Award price, platform-listed price, hospital purchase price, medical-service item price, and payer standard serve different institutional purposes. Substituting one for another can create patient-charge and fund-use risk.

Shared accountability across clinical, procurement, and payer teams

Clinicians determine suitability; procurement manages awards, committed volume, and supply; finance and pricing teams verify billing boundaries; payer and IT teams maintain codes and traceability. Shortage, substitution, returns, and recalls require auditable records.

  • Before procurement: forecast need from clinical demand, not mechanical historical extrapolation.
  • At use: reconcile product, patient, procedure, lot, and charge.
  • After settlement: monitor abnormal price, volume, duplicate charging, and external purchasing.

How payment changes behaviour

Fee-for-service raises boundary and duplicate-billing risks. DRG/DIP can encourage under-provision or self-pay shifting if badly governed. Per-diem arrangements require relief for clinically justified high-cost cases. Legitimate tools include pathway review, exception mechanisms, and supply coordination.

Cross-system control table

Clinical eventPayment contextReview signalHospital action
Care, medicine, device, or documentation changesSeparate FFS, DRG/DIP, and fixed-payment effectsReconcile orders, records, charges, claims, and outcomesVerify facts, correct records and rules, document remediation

Updated 2026-07-06. Always verify the current national and local documents before operational use.