Coverage

Readiness: Experimental.

Open Coverage profile on Simplifier ↗

Purpose: identify the patient's benefit arrangement or insurance coverage used by a Claim. FHIR R4 requires this link. DigiDOT limits Coverage to a small supporting record: prices remain in ChargeItem and tariff lines and requested amounts remain in Claim. Patient and Encounter continue to hold health-group information.

Profile base: FHIR R4 Coverage. No Coverage resource profile was found in the selected no-basis 2.2.2 package.

Use with Claim

  1. The EHR identifies the actual patient coverage and payer. It supplies a stable source identifier and readable coverage type; a known validity period may also be supplied. Do not invent a policy number or assume that a health-group code establishes coverage for the treatment.
  2. Reuse the same stored Coverage for later claims under the same patient, payer and arrangement. A different policy or arrangement may require a separate record; a new procedure or claim does not.
  3. Claim references it through insurance.coverage. The receiving service resolves the reference and checks that Coverage.beneficiary identifies Claim.patient and Coverage.payor identifies Claim.insurer. These are service checks, not guaranteed by structural validation alone.

When coverage is first registered, it can be submitted with its Claim in a transaction if both resource workflows are supported. Later claims reference the stored record. The draft Bundle catalogue permits Coverage; this does not establish that a deployed DENT release accepts it.

For example, a patient has one recorded public-benefit arrangement. A restoration and a later extraction can generate separate Claims referencing that same Coverage. Each Claim line still identifies its own Procedure and ChargeItem. The Coverage itself contains neither treatment nor claim amounts.

Why this is a small separate record

The profile requires an identifiable source record and a readable coverage type in addition to the mandatory R4 status, beneficiary and payor. There is one payer per record, matching the compact Claim model. The existing FHIR type binding is retained and text is allowed, so no new code system or ValueSet is needed.

Policyholder/family relationships, benefit tables, deductibles, cost-sharing amounts and contracts are outside this profile. Coverage is stored and referenced using the same pattern as other shared resources; it is not embedded in Claim. Reuse avoids repeating the coverage facts for every claim.

The EHR supplies and corrects the record. Preserve its identity and history when correcting it, and do not change an existing record to identify a different patient or policy. Follow the R4 financial-resource lifecycle. Neither active nor the existence of Coverage proves eligibility, claim approval or payment.

Examples and later versions

All examples are synthetic. They demonstrate the structure, not Helfo eligibility or a payer submission specification. See Finance for amounts and reporting.

FHIR R5 Coverage adds a mandatory kind and changes the payer representation. A later migration therefore needs an explicit mapping; R4 remains the current basis. The choice of this supporting resource does not establish EHDS conformance; shared considerations are in Finance.