Claim

Readiness: In development.

Open Claim profile on Simplifier

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

Design choices

Claim stores an actual reimbursement claim to one public benefit payer or insurer. Each flat tariff line identifies one Procedure, the tariff code, quantity and amount claimed. The tariff code may differ from the price code on ChargeItem. Patient invoices, preauthorisation and settlement are outside this compact profile.

One Claim has one payer and one reference to DigiDOT Coverage. FHIR R4 requires this supporting record to identify the patient coverage used for the request. Reuse it across claims under the same arrangement. Its patient must match Claim.patient and its payer must match Claim.insurer; the receiving service checks both. Different payers use separate Claims. Coverage does not replace the patient health group or establish entitlement to reimbursement.

A ChargeItem does not require a Claim. When a Claim is supplied, every claim line must link to exactly one supporting ChargeItem. Create a Claim only when there is an actual reimbursement request to retain. An amount requested is not an awarded benefit or money received. The profile does not define Helfo's submission format or prove eligibility.

Linking the claim to treatment and price

Link Standard R4 representation
Claim line to Procedure item.procedureSequence identifies an entry in procedure, whose procedureReference points to the performed Procedure.
Claim line to ChargeItem item.informationSequence (1..1) identifies one entry in supportingInfo, whose valueReference points to the ChargeItem. The standard attachment category includes referenced resources.

This uses existing FHIR fields, without a new linking extension. Sequence numbers are local to each Claim. Each claim line refers to one ChargeItem. If a reimbursement request covers several ChargeItems, the EHR must split and allocate it into separate claim lines before submission. The profile checks that referenced sequence numbers exist; the receiving service checks that resolved ChargeItems, Procedures, Coverage and Claim concern the same patient and that each linked charge belongs to the line's Procedure. These checks also apply when resources arrive together in a transaction.

The financial JSON example shows a full fee of NOK 1000 and a public-benefit claim for NOK 600. A separate insurance example demonstrates the same structure with another payer. The scenarios and tariff codes are fictional; they do not specify combined coverage or actual benefits.

Use the actual payer's tariff source in production. The EHR calculates the claimed line amount; a common tariff code is not a substitute for the explicit links above. See Finance for the distinction between claims and KPR results.

Corrections and totals

Claim status describes the claim record; active does not mean approved or paid. Follow the R4 lifecycle when correcting a submitted claim: retain the original and identify any replacement. Do not sum superseded claims or alternative payer scenarios as additional claims. Detailed correction and payer-allocation rules remain under review.

EHDS and later FHIR versions

R4 makes provider, priority and insurance mandatory. These are not all extra DigiDOT requirements: an R4 constraint profile cannot remove them. Known profile values and sequence numbers can be populated by the EHR integration; they need not become separate clinician input fields.

FHIR R5 Claim makes provider, priority and the insurance array optional, adds patientPaid and changes body-site representation. These changes cannot relax the R4 requirements. Patient-paid amounts remain distinct from the requested reimbursement and the calculated remainder.

The R6 September 2026 snapshot renames patient to subject and uses CodeableReference for the diagnosis and procedure links. These affect fields used by DigiDOT and require explicit migration mapping. This snapshot is not a final R6 release. Coverage also requires migration review.

See Finance for shared EHDS considerations and the shared migration assessment.