ChargeItem

Readiness: In development.

Open ChargeItem profile on Simplifier

Profile base: FHIR R4 ChargeItem. The selected no-basis 2.2.2 package has no ChargeItem profile.

Design choices

ChargeItem stores one priced service: what was provided, the quantity and the EHR-calculated total fee before allocation between the patient, public funding and insurance. A price code is optional. One line belongs to one Procedure and its Encounter; several lines may belong to the same Procedure.

R4 has no general calculated-total field on ChargeItem. This draft therefore reuses HL7's published R5-to-R4 totalPriceComponent extension, already available through the guide's dependencies. It carries one complete line amount and currency. The R4 override fields are excluded to avoid two competing price representations. This is a trial-use extension, not a new DigiDOT extension. The examples have been validated with HL7 Validator 7.0.5; version 6.10.4 incorrectly rejects the extension’s required datatype marker.

The compact profile excludes pricing rules, account management and product/device details. The EHR manages those processes. A separately priced material can be described as a charge line against its clinical Procedure; a Device instance is not needed for the fee.

Use in practice

Example Quantity Total fee before allocation
Restoration 1 procedure NOK 1000
Radiography 2 images from one Procedure NOK 300
Consultation 30 billable minutes NOK 900

These are synthetic prices. Count and time units follow the actual price basis; elapsed Encounter time is not automatically billable time. Do not multiply the total fee by the quantity again. Split and allocate a charge covering several Procedures before submission, and do not add separate lines for services already included in another charge.

The financial JSON example shows the complete extension syntax and these three cases. A known zero fee is allowed; missing amounts are not zero. ChargeItem can exist without a Claim, including for publicly funded care. A zero patient payment does not imply a zero full fee. Subtracting linked requested amounts gives a remainder not included in those claims, not automatically the patient's final share.

References follow the shared reference rules. The receiving service must check that the linked Procedure, Encounter and patient agree. See Finance for payer allocation and reporting boundaries.

EHDS and later FHIR versions

FHIR R5 ChargeItem introduces native price components, renames context to encounter and changes service to CodeableReference. The backported total-price component gives our amount an explicit R5 origin; the references and JSON structure still need migration.

In the R6 September 2026 snapshot, ChargeItem has moved out of core into HL7's Administrative Incubator, a separate specification under development. This does not invalidate R4 use. A later R6 migration must confirm the target specification, package dependencies and server/tool support rather than assume ChargeItem remains a core resource.

See Finance for shared EHDS considerations and the shared migration assessment. The R6 snapshot and incubator are not final release commitments.