---
title: Health insurance (GKV)
description: >-
  Overview of FuxamCMS GKV and Krankenkassen integration — statutory student
  insurance reporting, Meldegründe, Dakota exchange, and how immatriculation and
  exmatriculation notices connect to users, cohorts, and study timelines.
sidebar:
  order: 8
  label: Overview
---

The **GKV / Krankenkassen integration** connects FuxamCMS to the German statutory health insurance reporting workflow. Institutions with students subject to GKV reporting use it to send immatriculation notices (**Meldegrund 20**), exmatriculation notices (**Meldegrund 30**), and related insurance notifications through the **Dakota** middleware. In day-to-day operations, student services and registrar staff configure the interface once, then monitor per-student progress, incoming Krankenkasse responses, and transmitted notices on each user's **Health Insurance** tab.

This area is not a general analytics export. It is a **statutory Meldeverfahren** (reporting procedure): German universities and academies must exchange insurance events with *gesetzliche Krankenkassen* when students enroll, change status, or leave. Fuxam turns those obligations into structured institution settings, role-gated student steps, and automated outbound jobs — while keeping the operational record next to the same user and study-timeline data that drive the rest of Campus Management.

:::info
The **Health Insurance** user tab appears once the setup in **Settings → Integrations → Health Insurance** is complete and saved, and only for users whose role has **Report health insurance data** set to visible in **Settings → Roles & Permissions → [role] → Profile Information**.
:::

## Why it matters

In Germany, most students fall under **gesetzliche Krankenversicherung (GKV)** — statutory health insurance. Since the electronic *Studenten-Meldeverfahren* (student reporting procedure) under **§ 199a SGB V**, paper attestations are no longer the primary channel: Hochschulen and Krankenkassen exchange structured notices digitally. Universities must inform insurers when study begins and when it ends; insurers report insurance status, fund changes, and contribution arrears back to the institution.

Without a working interface, staff fall back to fragmented email and paper trails, students stall at enrollment, and exmatriculation can leave insurers with stale membership data. With Fuxam's GKV integration:

- **Legal reporting** — Meldegrund 20 and Meldegrund 30 notices leave the institution through Dakota in a controlled, auditable way.
- **Student onboarding** — Eligible students complete KV number and provider-notification steps on their dashboard instead of handing paper certificates to the registrar.
- **Operational visibility** — Staff see progress, inbound notifications, and sent M20/M30 history on one user tab tied to the study timeline.
- **Cleaner handoffs** — Immatriculation and exmatriculation dates used for insurance export are the same academic lifecycle facts that live on the study plan — not a separate spreadsheet.

### Domain context: Studenten-Meldeverfahren and GKV-DAV

German law requires **state and state-recognized Hochschulen** to exchange insurance information for students with the statutory health funds. The electronic procedure is commonly called the **Studenten-Meldeverfahren** (also associated with **GKV-DAV** / *Datenaustauschverfahren* materials published for the GKV). In practice:

1. A **study applicant** asks their Krankenkasse to report insurance status to the Hochschule.
2. The **Krankenkasse** sends a status notice (typically Meldegrund **10**) to the institution.
3. After enrollment, the **Hochschule** reports the **start of study** (Meldegrund **20**), including semester start and enrollment day.
4. When study ends, the **Hochschule** reports the **end of study** (Meldegrund **30**), typically tied to semester end and — when exmatriculation happens earlier — the exmatriculation day.
5. Along the way, insurers may report **fund changes** (11) or **contribution arrears / settlement** (12 / 13), which can affect whether the institution may enroll or re-enroll the student.

Fuxam does not replace the statutory rules. It gives your institution a place to finish onboarding (Absendernummer, ITSG, Hochschuldatei), collect student insurance steps, drive outbound notices from the **study timeline**, and keep an auditable record on the user.

:::note
This handbook explains how Fuxam supports the Meldeverfahren. It is **not legal advice**. Your student services or legal office should confirm how your institution applies § 199a SGB V and the current Gemeinsame Grundsätze published for the procedure.
:::

## Key concepts

| Term | Meaning |
|---|---|
| **GKV** | *Gesetzliche Krankenversicherung* — German statutory health insurance operated by Krankenkassen. |
| **Krankenkasse** | An individual statutory insurer (for example AOK, TK, Barmer). Students hold a **KV number** (*Krankenversichertennummer*) with their fund. |
| **Studenten-Meldeverfahren / GKV-DAV** | The electronic student reporting procedure between Hochschulen and Krankenkassen. Notices travel as structured XML through secured middleware (in Fuxam: **Dakota**). |
| **Meldegrund** | The reason code on a notice. Institutions primarily send **20** (start of study / immatriculation) and **30** (end of study / exmatriculation). Insurers send status and change codes such as **10** (insurance status), **11** (fund change), **12** / **13** (contribution arrears and settlement). See [Reporting reasons and lifecycle](/docs/fuxam-web/cms/health-insurance/reporting-reasons-and-lifecycle). |
| **Absendernummer** | The institution's (or service provider's) sender ID for the Meldeverfahren — requested via **ITSG** and recorded in the **Hochschuldatei**. Required before live exchange. |
| **ITSG** | *Informationstechnische Servicestelle der gesetzlichen Krankenversicherung* — issues Absendernummern and maintains the Hochschuldatei on behalf of the GKV-Spitzenverband. |
| **Hochschuldatei** | The register of Hochschulen (and, where applicable, Dienstleister) participating in electronic exchange. Krankenkassen use it to address notices correctly. |
| **Dakota** | Secure transmission middleware used to exchange social-insurance XML with GKV systems. Fuxam background jobs send and receive through this path once live. |
| **Insurance start date** | Institution setting: the date from which Fuxam should begin sending insurance notifications for your institution. |
| **Report health insurance data** | Role profile setting in **Settings → Roles & Permissions → [role] → Profile Information**. Users with a role where it is visible get the **Health Insurance** tab and must report their health insurance number. |
| **Insurance Integration** | Institution switch that Fuxam turns on automatically when you save a complete setup. You do not turn it on by hand. |
| **Health Insurance settings** | The setup checklist in **Settings → Integrations → Health Insurance** (Absendernummer, ITSG email, Hochschuldatei confirmation, start date). |

### Who sends what (domain overview)

| Direction | Typical Meldegründe | Purpose |
|---|---|---|
| **Krankenkasse → Hochschule** | 10, 11, 12, 13 | Confirm insurance status before or during enrollment; report fund changes; signal contribution problems that can block enrollment or re-enrollment. |
| **Hochschule → Krankenkasse** | 20, 30 | Notify start of study (immatriculation) and end of study (exmatriculation / semester end of membership). |

Fuxam shows outbound **M20** / **M30** under **Sent Notices**, and inbound responses under **Insurance Notifications**, on the user's **Health Insurance** tab.

### Absendernummer and ITSG (why they matter)

To participate in the electronic Meldeverfahren, a Hochschule (or its Dienstleister / computing center) needs a **gesonderte Absendernummer** — an eight-character alphanumeric sender ID. Under § 199a SGB V, that ID is applied for with the GKV-Spitzenverband; **ITSG** performs issuance and maintains the **Hochschuldatei**.

Without a valid Absendernummer recorded in the Hochschuldatei:

- Krankenkassen cannot reliably address inbound notices to your institution.
- Outbound Meldegrund 20 / 30 traffic has no trusted sender identity in the procedure.
- Fuxam cannot treat the institution as ready for live Dakota exchange, even if student data looks complete.

If a service provider sends on behalf of several Hochschulen, the provider typically needs its **own** Absendernummer in addition to each Hochschule's ID. Record the correct number in Fuxam during [configuration](/docs/fuxam-web/cms/health-insurance/configure-gkv-integration).

Secured transmission (Dakota and related credentials) is the technical channel that carries those XML notices. The Absendernummer is the **procedural identity**; Dakota is the **pipe**. Both must be in place for live reporting.

## Who needs it

| Audience | Why |
|---|---|
| **German universities and academies** | Legal obligation to notify Krankenkassen when students enroll, change status, or exmatriculate. |
| **Student services / registrar staff** | Configure the integration, monitor per-student insurance status, and correct sent notices. |
| **Students** | Complete their insurance steps (health insurance number, email to their Krankenkasse, confirmation) in **Home → Management → Health Insurance** when their role reports insurance. |

## Prerequisites

| Requirement | Detail |
|---|---|
| Setup complete | Every step in **Settings → Integrations → Health Insurance** is done and saved, including the start date. Fuxam then switches on **Insurance Integration** automatically. |
| Settings permission | The admin doing the setup needs `read-write:settings-krankenkassen`. |
| Reporting roles | **Report health insurance data** is set to visible on each role that must report insurance. This option appears only after the setup is saved. |
| Staff permission | Staff who open the **Health Insurance** tab need the **User insurance** permission. |
| Study plans | Each student needs a study plan with a starting semester before insurance data can be reported. |

:::warning
Until the setup is complete, the **Health Insurance** tab shows "Insurance settings have not been configured for this institution".
:::

## Roles and responsibilities

| Role | Typical responsibility |
|---|---|
| **Institution administrator** | Complete [Configure GKV integration](/docs/fuxam-web/cms/health-insurance/configure-gkv-integration) and turn on **Report health insurance data** for the student roles. |
| **Student services / registrar** | Keep study plans correct, remind students with **Insurance Bulk Request**, and [manage insurance data](/docs/fuxam-web/cms/health-insurance/manage-insurance-data) before relying on the [exmatriculation export](/docs/fuxam-web/cms/health-insurance/export-exmatriculations). |
| **Students** | Complete **Home → Management → Health Insurance** (health insurance number, email to their Krankenkasse, confirmation). |
| **Fuxam operators** | May trigger exmatriculation export jobs manually when testing or after bulk timeline fixes. This is not a button in your Settings. |

## Where to start

A practical order for going live:

1. [Configure GKV integration](/docs/fuxam-web/cms/health-insurance/configure-gkv-integration) in **Settings → Integrations → Health Insurance**, from Absendernummer to start date, and select **Save Settings**.
2. In **Settings → Roles & Permissions**, set **Report health insurance data** to visible on every role that must report insurance (see [Roles and permissions](/docs/fuxam-web/base/user-management/roles-and-permissions)).
3. Check that every student has a study plan with correct immatriculation and planned exmatriculation dates, usually through their [cohort](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts).
4. Read [Reporting reasons and lifecycle](/docs/fuxam-web/cms/health-insurance/reporting-reasons-and-lifecycle) so staff share the same vocabulary for Meldegründe 10 to 13 and 20 / 30.
5. Send students their instructions with **Insurance Bulk Request** in **Campus Management → User Management**, then check a few pilot users on the **Health Insurance** tab ([manage insurance data](/docs/fuxam-web/cms/health-insurance/manage-insurance-data)).
6. Let the daily [exmatriculation export](/docs/fuxam-web/cms/health-insurance/export-exmatriculations) send Meldegrund 30 and review **Sent Notices** afterwards.

## In this section

**[Configure GKV integration](/docs/fuxam-web/cms/health-insurance/configure-gkv-integration)**

Work through the Absendernummer, ITSG and start-date checklist in Settings → Integrations → Health Insurance.

**[Manage insurance data](/docs/fuxam-web/cms/health-insurance/manage-insurance-data)**

Work with the Health Insurance tab: progress, inbound notifications, and sent M20/M30 notices.

**[Export exmatriculations](/docs/fuxam-web/cms/health-insurance/export-exmatriculations)**

Understand automated Meldegrund 30 exports, daily timing, and manual operator triggers.

**[Reporting reasons and lifecycle](/docs/fuxam-web/cms/health-insurance/reporting-reasons-and-lifecycle)**

Meldegründe 10 to 30, how timelines drive notices, and how insurers typically respond.
