Health insurance (GKV)
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.
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 Krankenkasse 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 OrgHub.
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:
- A study applicant asks their Krankenkasse to report insurance status to the Hochschule.
- The Krankenkasse sends a status notice (typically Meldegrund 10) to the institution.
- After enrollment, the Hochschule reports the start of study (Meldegrund 20), including semester start and enrollment day.
- 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.
- 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.
How this fits into Fuxam
GKV reporting sits at the intersection of identity, academic lifecycle, and specialized statutory export. It complements — but does not replace — university statistics and Report Builder exports.
| Related area | Relationship to GKV |
|---|---|
| User Management | Insurance is per user. Admins open OrgHub → User Management → [User] → Krankenkasse. The required role is an institution role assigned in User Management; staff need permission to view insurance data for admin views. |
| Study programs and cohorts | Cohort membership and study plans supply the study timeline (immatriculation, leave, exmatriculation). Wrong cohort or plan dates produce wrong Meldegründe. |
| Statistics and reports | University Statistics and Report Builder serve accreditation and ministry schemas. GKV Meldeverfahren is a separate statutory channel for Krankenkassen — related as institutional compliance, not as a Statistics Center report type. |
| OrgHub basics | The Health Insurance feature must be enabled for your institution before the integration UI is available. See also Permissions, features and visibility. |
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. |
| 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. |
| Required role | Institution role that must complete student-side Krankenkasse steps. Only users with this role see the Krankenkasse tab. |
| Health Insurance feature | FuxamCMS capability that must be enabled for your institution before the integration UI appears. |
| Integration switched on | Happens automatically when you save a complete configuration in Settings → Krankenkassen Integration. The feature alone is not enough. |
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 surfaces outbound M20 / M30 under Sent notices, and inbound responses under Insurance notices, on the per-user Krankenkasse 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.
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. |
| Eligible students | Complete Krankenkasse steps (KV number, provider email, confirmations) on their dashboard when assigned the required role. |
Prerequisites
Two gates control visibility:
- The Health Insurance feature must be enabled for your institution.
- Integration settings must be fully completed and saved in Settings → Krankenkassen Integration so the health-insurance integration is fully set up and switched on (Fuxam does this automatically when the checklist is complete).
Additionally:
- Configure a required role in integration settings — only users with that role see the Krankenkasse tab.
- Staff need permission to view insurance data for admin views of insurance data.
Roles and responsibilities
| Role | Typical responsibility |
|---|---|
| Institution administrator | Complete Configure GKV integration (requires administrator permission to change settings); keep Absendernummer and ITSG onboarding current. |
| Student services / registrar | Assign the required role; manage insurance data; correct study-timeline dates before relying on exmatriculation export. |
| Students with the required role | Complete Dashboard → Management → Krankenkasse checklist (KV number, provider email, confirmations). |
| Fuxam operators | May manually trigger exmatriculation export jobs when testing Dakota or after bulk timeline fixes — not a self-service Settings button for institutions. |
Where to start
A practical onboarding order for a German institution going live:
- Confirm the Health Insurance feature is enabled, then configure GKV integration end to end (Absendernummer through insurance start date).
- Assign the required role to the student population that must complete Krankenkasse steps (User Management).
- Verify study timeline accuracy for immatriculation and planned exmatriculation on study plans tied to cohorts.
- Read Reporting reasons and lifecycle so staff share a common vocabulary for Meldegründe 10–13 and 20 / 30.
- Monitor a few pilot users on the Krankenkasse tab (manage insurance data).
- Rely on nightly exmatriculation export for Meldegrund 30 and review Sent notices afterward.
In this section
Configure GKV integration
Set up Absendernummer, ITSG onboarding, required role, and insurance start date in Settings.
Manage insurance data
Review and update per-student Krankenkasse information, inbound notices, and sent M20/M30 history.
Export exmatriculations
Understand automated Meldegrund 30 exports, daily timing, and manual operator triggers.
Reporting reasons and lifecycle
Meldegründe 10 to 30, how timelines drive notices, and how insurers typically respond.