Skip to main content

Charge Item

A Charge Item is the actual instance of billing for a specific service or product provided to a patient. It references a Charge Item Definition (i.e., the priced “catalog entry”) to derive the cost, plus actual usage details (quantity, date, any overrides). Each Charge Item links to a specific Account (which accumulates charges for a patient or episode of care) and often to an Encounter (the clinical context).

For example, if a nurse administers 2 doses of an expensive medication, the system may create a Charge Item for “Medication: XYZ” with quantity=2, referencing the relevant charge definition for medication pricing. Once a Charge Item is billable, it can appear on an Invoice.

Schema Definition

{
"id": "<str>", // Internal Identifier
"definition": "<id|fk>", // Definition pointing to Charge Definition
"status": "<string>", // planned | billable | not-billable | aborted | billed | entered-in-error | unknown
"code": "<code>", // A code that identifies the charge, like a billing code
"patient": "<id|fk>", // Patient Associated with the charge
"encounter": "<id|fk>", // Encounter associated with this ChargeItem
"facility": "<id|fk>", // Facility where this Charge Item is created
"quantity": "<float>", // Quantity of which the charge item has been serviced
"unitPriceComponent": [
"MonetaryComponent" // Unit price components
],
"totalPriceComponent": [
"MonetaryComponent" // Total price components
],
"total_price": { // Total Price in Amount
"Money"
},
"overrideReason": { // Reason for overriding the list price/factor
"text": "",
"code": "<code>"
},
"service": { // Why was the charged service rendered?
"resource": "<resource>",
"id": "id"
},
"account": "<id|fk>", // Account to place this charge
"note": "<markdown>", // Comments made about the ChargeItem
"supportingInformation": [
{ "Reference(Any)" } // Further information supporting this charge
]
}

Core Data Structure

Essential Fields

FieldDescriptionTechnical Notes
idInternal system identifierPrimary key, auto-generated
definitionReference to the Charge Item DefinitionLinks to the catalog entry for this service/item
statusCurrent state in the billing lifecycleControls whether the item can be invoiced
codeBilling code for the serviceOften derived from the definition
patientReference to the patientPerson receiving the service
encounterReference to the healthcare encounterLinks to the clinical context
facilityReference to the healthcare facilityLocation where service was provided
quantityNumber of units providedDefault is 1 for most services
unitPriceComponentPrice breakdown per unitIncludes base, surcharges, discounts, taxes
totalPriceComponentPrice breakdown for all unitsUnit price × quantity with all components
total_priceFinal calculated amountSum of all price components
accountReference to the billing accountWhere this charge accumulates

Status Lifecycle

Status ValueDescriptionSystem Behavior
plannedService is scheduled but not yet providedNot counted in account balance; not billable
billableService provided and ready to billIncluded in account balance; can be invoiced
not-billableService provided but won't be billedNot included in account balance; excluded from invoices
abortedService was not completedNot included in account balance; excluded from invoices
billedCharge included on an invoiceIncluded in account balance; cannot be invoiced again
entered-in-errorCharge was created by mistakeExcluded from all calculations and invoices

User Workflows

Editing or Canceling a Charge

  • If a charge is still billable (and not on an issued invoice), staff can adjust quantity, override price, or mark it not-billable.
  • If it is billed (already invoiced), any correction typically requires reversing that invoice or adding a credit note.
  • Marking entered-in-error will remove it from the account’s balance. Log who performed this action.

Automatic Charge Creation

  • The system will automatically create charges when certain clinical events occur (e.g., lab test result posted). Staff can still review them before they become “billable.”