EESSI-EUX Skill

Quick Reference

What is EESSI?

EESSI (Electronic Exchange of Social Security Information) is the EU system for electronic exchange of social security data between member states. Melosys integrates with EESSI through:

• EUX - Norwegian middleware/facade for RINA (managed by Team EUX)
• RINA - The EU's case management system for EESSI
• melosys-eessi - Melosys's internal facade service for EUX

Architecture Overview

                    ┌─────────────────┐
                    │   RINA (EU)     │
                    └────────┬────────┘
                             │
                    ┌────────▼────────┐
                    │     EUX         │   (Team EUX)
                    │  (NAV Facade)   │
                    └────────┬────────┘
                             │
                    ┌────────▼────────┐
                    │  melosys-eessi  │   (Team Melosys)
                    └────────┬────────┘
                             │
┌──────────────────────┐     │     ┌──────────────────────┐
│    Kafka Topic       │◄────┴────►│    REST API          │
│ (incoming SED)       │           │ (outgoing operations)│
└──────────────────────┘           └──────────────────────┘
           │                                  │
           ▼                                  ▼
┌──────────────────────┐           ┌──────────────────────┐
│ EessiMeldingConsumer │           │   EessiClient        │
└──────────────────────┘           └──────────────────────┘
           │                                  │
           └─────────────┬────────────────────┘
                         │
                ┌────────▼────────┐
                │  EessiService   │
                └─────────────────┘

Key Components

BUC Types (Business Use Cases)

LA_BUC - Lovvalg (Applicable Legislation):

BucType.fraBestemmelse() only ever maps to LABUC01, LABUC02, LABUC04 and
LABUC05 (see BucType.kt). LABUC03 and LABUC06 exist in the BucType enum
but are not produced from a lovvalgsbestemmelse — they are info/notification BUCs.

HBUC - Helytelser (Health benefits): Various HBUC types for health benefit coordination.

SED Types (Structured Electronic Documents)

A-series (Applicable Legislation):

X-series (Administrative):

Core Operations

// Create BUC and send SED
eessiClient.opprettBucOgSed(
    sedDataDto,      // SED content
    vedlegg,         // Attachments
    bucType,         // LA_BUC_02, etc.
    sendAutomatisk,  // true = send immediately
    oppdaterEksisterendeOmFinnes // true = update if exists
)

// Send SED on existing BUC
eessiClient.sendSedPåEksisterendeBuc(
    sedDataDto,
    rinaSaksnummer,  // RINA case ID
    sedType          // A012, A004, etc.
)

// Get recipient institutions
eessiClient.hentMottakerinstitusjoner(
    bucType,         // "LA_BUC_02"
    landkoder        // Set("DE", "SE")
)

Incoming SED Flow

1. melosys-eessi receives SED from EUX
           │
           ▼
2. Publishes to Kafka topic
           │
           ▼
3. EessiMeldingConsumer.mottaMeldingAiven()
           │
           ▼
4. ProsessinstansService.opprettProsessinstansSedMottak()
           │
           ▼
5. SedRuter.rutSedTilBehandling() - routes to correct handler:
   ├── AnmodningOmUnntakSedRuter (A001)
   ├── ArbeidFlereLandSedRuter (A003)
   ├── SvarAnmodningUnntakSedRuter (A011/A002)
   └── DefaultSedRuter (others)
           │
           ▼
6. Creates/updates behandling based on SED content

Outgoing SED Flow

1. Vedtak fattet (decision made)
           │
           ▼
2. IVERKSETT_VEDTAK prosessinstans starts
           │
           ▼
3. AbstraktSendUtland.sendUtland()
           │
           ▼
4. EessiService.opprettOgSendSed()
           │
           ▼
5. SedDataBygger builds SED payload
           │
           ▼
6. EessiClient.opprettBucOgSed() / sendSedPåEksisterendeBuc()
           │
           ▼
7. melosys-eessi → EUX → RINA

Quick Debugging

melosys-api does NOT persist SEDs or the BUC↔NAV-case relationship in its own Oracle DB. There is no seddokument or saksrelasjon table here — saksrelasjon exists only as SaksrelasjonDto and as PROSESSSTEG name strings (e.g. OPPDATER_SAKSRELASJON). The actual saksrelasjon data lives in the melosys-eessi service's own database. To trace SED activity from melosys-api, query the saga tables:

-- Find SED-send / SED-mottak saga runs for a behandling.
-- NB: column is PROSESS_TYPE (not "type") and SIST_FULLFORT_STEG (not "sist_utforte_steg").
SELECT pi.uuid, pi.prosess_type, pi.status, pi.sist_fullfort_steg, pi.endret_dato
FROM prosessinstans pi
JOIN behandling b ON pi.behandling_id = b.id
WHERE b.id = :behandlingId
  AND pi.prosess_type LIKE 'IVERKSETT_VEDTAK%'
ORDER BY pi.endret_dato DESC;

-- The BUC↔NAV-case relationship (rina_saksnummer/gsak_saksnummer) is owned by
-- melosys-eessi. From melosys-api, look it up at runtime via
-- EessiClient.hentSakForGsakSaksnummer(gsakSaksnummer) /
-- EessiClient.hentSakForRinasaksnummer(rinaSaksnummer).

When to Use This Skill

• Understanding BUC lifecycle and SED exchange
• Debugging SED sending/receiving issues
• Understanding which BUC/SED applies to which lovvalg article
• Investigating EUX API errors
• Understanding institution catalog lookup
• Troubleshooting Kafka message processing

Reference Files

Deeper detail lives in this skill's references/ directory:

• [references/api.md](references/api.md) — full EessiClient method/endpoint reference and Kafka message shapes
• [references/buc-types.md](references/buc-types.md) — BUC types, bestemmelse→BUC mapping, BUC lifecycle states
• [references/sed-types.md](references/sed-types.md) — SED types, content, routing, and SedType enum
• [references/debugging.md](references/debugging.md) — SQL queries, common error scenarios, log patterns, code entry points

Related Skills

• lovvalg: Law determination that triggers SED sending
• sed: Detailed SED document types and content
• saksflyt: Saga steps for SED operations
• behandling: Behandlinger created from incoming SEDs