We'll update priceOverride to be  totalPriceComponent  as a BackboneElement element with the same structure as is seen on Invoice and ChargeItemDefinition.  Note: FHIR-16380 may add a metadata type for priceComponent, in which case this tracker would use that instead of the BackboneElement described here.   totalPriceComponent 0.. BackboneElement* (same structure as priceComponent in Invoice) Definition: The total price for the chargable item, accounting for the quantity. Comments:   Often, the total price may be be calculated and recorded on the Invoice, but if a calculated total price must be exchanged prior to Invoice creation, it can be communicated in this property.   unitPriceComponent  0..1 BackboneElement* (same structure as priceComponent in Invoice) Definition: The unit price of the chargable item. Comments:    This could be communicated in ChargeItemDefinition.  But if ChargeItemDefinition is not supported or not available, the unit price can be communicated in this property.   factorOverride will be removed, as it is incorporated in the priceComponent structure   overrideReason Update the data type for overrideReason from string to CodableConcept. Remove the Comments for overrideReason, since of course profiles can add invariants for whatever, and the totalPriceComponent may be override related or it may not.