Actors and information flow

Last modified: 2026-11-21 00:25by Erik Hagen ID: 9df441eb-96d2-49d3-a015-8103b279a237 SAMT-X/samt-bu-pilot-6
Work in progress

Who is involved, and how information flows between the actors in the chosen solution: parents and guardians, the channels, the common Altinn solutions and the data sources. The flow today is described under Current situation, and the desired flow under Target picture.

The solution concept (see Chosen solution now) has two flows: retrieval on demand and event-driven retrieval.

Flow A: retrieval on demand

Flow A in five steps: 1) the parent logs in to the channel with ID-porten; 2) the channel checks custody in the Population Register; 3) the channel calls the service «Foresattinnsyn» in data.altinn.no with the pupil’s national identity number as subject, authenticated with Maskinporten; 4) Udir and the school systems deliver data; 5) the channel combines and shows progress over time as a combined overview. The parent never uses data.altinn.no directly.

Typically when the parent opens the service:

  1. The parent logs in to the channel with ID-porten.
  2. The channel (the consumer solution) checks that the logged-in person has parental responsibility for the pupil. data.altinn.no already has a relationship dataset from the Population Register.
  3. The consumer calls the service «Foresattinnsyn» (parental access) in data.altinn.no with the pupil’s national identity number as subject, authenticated with Maskinporten as an organisation.
  4. data.altinn.no retrieves from Udir and the school systems and minimises the data.
  5. The consumer combines and shows progress over time.

data.altinn.no logs which organisation asked, not which parent. The consumer must log that itself.

Flow B: event-driven retrieval

Flow B in five steps: 1) a new result is registered in the data source; 2) the source publishes a thin event in Altinn Events, only a reference; 3) the channel receives the event through a subscription; 4) the channel retrieves the data via data.altinn.no, with access control and minimisation; 5) the parent is notified via Dialogporten. Polling is an alternative where the source does not publish events, and whether data holders can publish events must be clarified with each of them.

  1. A new result is registered in the source, for example a result from a national test.
  2. The source publishes a thin event in Altinn Events – only a reference, no case data.
  3. Channels that subscribe receive the event.
  4. The channel retrieves the actual data via data.altinn.no, with the same access control and minimisation as in flow A.
  5. The channel creates or updates a dialogue in Dialogporten, so that the parent sees in the Altinn workspace that something new exists. The dialogue links back to the channel’s own solution.

The division of work is deliberate: Altinn Events signals, data.altinn.no manages access and case data. Where the source cannot publish events, regular or on-demand polling is a full alternative. Whether the data holders can deliver push must be clarified with each actor.

Basis

The figures and text build on the presentation Samt-BU and pilot 6 – concept and solution (in Norwegian, download).