Health groups

Under development. The profiles define how to exchange health-group periods and contact classifications. The update API, ownership and automatic classification policy still need implementation agreement.

Patient history and the group used at a contact

Record What it stores
DigiDOT Patient with Patient Health Group Known assignments, each with one group and a validity period. Assignments may be absent when the birth date is unknown. Periods must not overlap. The assignment covering a date determines the group for that date.
DigiDOT Encounter with Encounter Health Group The classification applied at that contact. This extension remains optional (0..1), including on finished contacts. Whether to make it mandatory is a separate decision.

Both extensions use the health-group ValueSet. Both bindings are required: a supplied classification must use one of the 20 selectable codes. Grouping concepts, retired codes and alternative codes are not accepted. This does not change the optional Encounter extension (0..1). The CodeSystem defines the codes and labels; the ValueSet selects the permitted terminology. The supplied list is draft and has no confirmed effective date or formal approval recorded.

The timeline contains one selected classification at a time. It does not represent every simultaneous eligibility ground. If several groups could apply, a separate, agreed priority policy must select the group.

Periods on Patient

  • Each assignment has a required group code and a required start date. End is optional when no end is known.
  • Use complete calendar dates (YYYY-MM-DD). Both dates are inclusive: if a new group starts on 1 September, the preceding group ends on 31 August.
  • Keep earlier assignments. Future assignments are allowed. Array order and the most recent update do not determine the applicable group.
  • Gaps are allowed and mean that no classification is recorded for those dates. A gap does not mean that the patient has no entitlement. Only the final period can have no end.

FHIR resource history records when data was edited. The assignment periods record when a group applies. Resource versions do not replace these periods. The inclusive boundary follows FHIR R4 Period.

When a birth date is supplied, at least one health-group assignment is required. Without a birth date, the Patient may have no assignments; a known assignment may still be recorded. The MPI selects and maintains the group using the agreed rules. Profile validation checks that an assignment is present, not that the correct group has been selected or that a period covers today. See the example without a known birth date or health group.

Existing clinical references still target no-basis Patient; the receiving API must explicitly adopt the DigiDOT Patient profile to enforce this rule.

Selecting the Encounter value

When the extension is supplied, select the Patient assignment covering the calendar date of Encounter.period.start, using Europe/Oslo for timestamp conversion. A supplied health group requires a contact start containing a complete calendar date, with or without a time. A year or month alone is insufficient. A contact crossing a classification boundary retains the group selected at its start.

Use the actual contact date also for late entries. Do not use today's group for a historical contact. If no assignment covers the date, leave the optional extension absent and resolve the missing information. Overlapping assignments are invalid and must be corrected, rather than choosing one arbitrarily.

Later Patient changes do not automatically rewrite Encounter values. A correction to a historical assignment may require reviewing affected contacts, but any Encounter correction must be explicit and traceable. This preserves the distinction between the classification used at the time and subsequent corrections.

Updating an assignment

For a change effective on date D, the receiving service must:

  1. Read the current Patient and identify the assignment affected by D.
  2. Close that assignment on the preceding day, if applicable, and add the new assignment starting on D. Preserve earlier and agreed future periods. A correction on an existing start date updates that assignment; it must not create a second assignment with the same start.
  3. Validate the complete resulting timeline and save the changes together. Reject conflicting or overlapping periods. Use version-aware writes, such as ETag and If-Match, to prevent one EHR overwriting another's update.

A backdated change needs review of all affected periods; simply closing the last array entry is insufficient. Coordinate updates with the MPI so that identity refreshes preserve the health-group history. Record the source, author or agreed automatic rule through the audit/provenance process.

Profiles validate the submitted data; they do not close periods automatically, calculate defaults or copy values between resources. These operations belong in the agreed API workflow. Validation must cover the complete Patient even when the client submits a partial update.

Example: a group changes at a calendar-year boundary

Jonas is a synthetic patient born on 9 January 2010. These fictional dates illustrate the calendar-year convention in the supplied list; they do not assert that an automatic classification policy has been approved.

Patient assignment Valid from Valid through
A1: Barn og unge 0–2 år 2010-01-09 2012-12-31
A2: Barn og unge 3–18 år 2013-01-01 2028-12-31

An Encounter on 12 December 2012 records A1. An Encounter on 16 January 2013 records A2. A late entry for 20 December 2012 still records A1, even if entered after the change to A2. The same Patient keeps both periods.

Age-based defaults

The source list states that age limits apply through the calendar year in which the age is reached. For the age groups, use the age reached in the classification year, not the age on the contact's birthday: A1 covers 0–2, A2 3–18, D1 19–20, D2 21–24 and D3 25–28. For example, a person born in 2010 enters the A2 age range on 1 January 2013.

These ranges can support a proposed default when no other applicable classification is established. They are not, by themselves, a complete eligibility algorithm. Before enabling automatic assignment, agree the priority between age and other groups, the evidence needed for special groups, who maintains the rules and how changes are audited. Do not overwrite an applicable special group, infer it from a diagnosis alone, or automatically assign V solely because the patient is older than 28. If classification is unresolved, the MPI must resolve it before a Patient with a birth date can conform to this profile. Do not invent a placeholder group.

What is checked, and what remains to be agreed

Layer Responsibility
Profile validation Health-group presence when a birth date is supplied, required code and period structure, complete dates, ordered date boundaries, no overlapping Patient periods, optional single Encounter group, and a contact date when a group is supplied.
API and integration Authorised updates, atomic period changes, concurrent writes, preservation during MPI refresh, selection from the Patient timeline and explicit historical corrections. A standalone Encounter validator cannot establish agreement with the correct Patient version.
Clinical and terminology governance Approval and lifecycle of the source list, priority between qualifying groups, automatic defaults and correction policy.

The model represents a recorded classification. It does not by itself grant access rights, establish affiliation or calculate payment or entitlement.