Event-Based Updates

Events are the backbone of the DGM integration architecture, enabling real-time notifications about funeral data changes across all connected systems.

Event System Overview

DGM uses Altinn Events for notification distribution:

sequenceDiagram participant FS as Your System participant DGM as DGM Hub participant AE as Altinn Events participant OS as Other Systems FS->>DGM: 1. Submit funeral data DGM->>AE: 2. Publish event AE->>FS: 3. Deliver event AE->>OS: 3. Deliver event FS->>DGM: 4. Request updated data

Cloud Events

DGM uses Altinn Events to publish events to subscribers. Altinn Events is based on the CloudNative CloudEvents specification.

Resource types

Note

Not all event types are necessarily available for all resource types. Check the event type you are interested in to see which resource types it is available for.

The following resource types are available:

urn:altinn:resource:dgm-external-funeral-home-events
urn:altinn:resource:dgm-external-graveyard-authority-events

Event types

To get notified by the system about certain events, you can subscribe to events. The following event types are available:

no.dgm.v1.funeral.updated - A funeral has been updated
no.dgm.v1.funeral.closed - A funeral has been closed

no.dgm.v1.funeral.updated

This event is triggered when a funeral has been updated. The event contains the following fields:

{
    funeralId: uuid,
    responsibilityStatementId: uuid,
    partyId: uuid, 
    locationIds: string[],
    crematoriumId: string | null,
    funeralHomeId: string | null
}

FuneralId is the ID of the funeral that triggered the event.

ResponsibilityStatementId is the ID of the responsibility statement that triggered the event.

PartyId is the ID of the party that owning the responsibility statement.

LocationIds is a list of municipality numbers to filter on. This is used to filter out events that are not relevant for the subscriber.

CrematoriumId is the organization numbers of the crematorium and that is associated with the responsibility statement. It can be used to filter out events that are not relevant for the subscriber.

FuneralHomeId can point to one of two things. It can either be an organization number of a specific funeral home, or it can be the identifier of a specific department within a funeral home.

If your organization has multiple departments, you can contact us, and we can set up listings for your specific departments. To do this, either contact us directly on Slack, or send an email to. After creating new departments, the listings also become searchable in the Altinn form that users have access to.

As you consume the event, you can use FuneralHomeId to filter out events that are relevant for your organization and department.

Available for the following resource types:

urn:altinn:resource:dgm-external-funeral-home-events
urn:altinn:resource:dgm-external-graveyard-authority-events

See the API pattern pages for more information on how to use the events.

no.dgm.v1.funeral.closed

This event is triggered when a funeral has been closed. The event contains the following fields:

{
    funeralId: uuid
}

The FuneralId is the ID of the funeral that triggered the event.